bs240mt.pdf

Maintenance

Base Transceiver Station Equipment

MMN:BTSEBS-240 / 240 II / 240XL / 240XL II

A30808-X3247-M326-5-7620

MaintenanceBase Transceiver Station Equipment

2 A30808-X3247-M326-5-7620


f Important Notice on Product SafetyDANGER - 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 2006.

Issued by the Communications 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-M326-5-7620 3



Reason for UpdateSummary:

Fifth Edition for Release BR 8.0

Details:

Chapter/Section Reason for Update

3.26 Minor corrections

Issue HistoryIssue

Number

Date of Issue Reason for Update

1 01/2005 First Edition for New Release BR 8.0

2 04/2005 Second Edition for Release BR 8.0

3 07/2005 Third Edition for Release BR 8.0

4 11/2005 Fourth Edition for Release BR 8.0

5 03/2006 Fifth Edition for Release BR 8.0

4 A30808-X3247-M326-5-7620



A30808-X3247-M326-5-7620 5



This document consists of a total of 252 pages. All pages are issue 5.

Contents

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111.1 Structure of the Maintenance Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111.2 Symbols Used. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121.3 Fault Clearance Principle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.4 Fault Clearance Guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141.5 Module Replacement Instructions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161.5.1 ESD Precautions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161.5.2 Avoiding the Loss of Calls. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161.5.3 Removing and Inserting Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181.5.4 Quick Module Replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

2 Tasklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

3 Fault Clearance Procedures for Modules and Interfaces . . . . . . . . . . . . . . 233.1 Abis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243.2 ABISCON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273.3 AC/DC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283.4 ACDCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333.5 ACT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343.6 BATTERY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383.7 BPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413.8 COBA Without CORE Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433.9 COBA With CORE Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493.10 COBA2P8 - COBA4P12 Without CORE Redundancy . . . . . . . . . . . . . . . . 593.11 COBA2P8 - COBA4P12 With CORE Redundancy. . . . . . . . . . . . . . . . . . . 673.12 COREXT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 793.13 COSA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 843.14 CU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 903.15 DCBCTRL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 953.16 DIAMCO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 993.17 DIDCTMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1053.18 DILNA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1073.19 DIPLEXER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1083.20 DUAMCO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1153.21 DUBIAS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1213.22 DUDCTMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1273.23 DULNA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1293.24 ECU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1313.25 FAN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1323.26 FlexCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1353.27 FCUMAIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1433.28 FCUTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1453.29 FDUAMCO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1473.30 FICOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1483.31 Filtermat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

6 A30808-X3247-M326-5-7620



3.32 FTNFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1553.33 FVSWRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1573.34 GCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1593.35 HPDU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1603.36 LAPDLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1673.37 OVPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1683.38 PCM Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1713.39 Rectifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1733.40 Remote Inventory Data Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1753.41 Remote Inventory Data Restoration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1793.42 Remote Inventory Data Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1843.43 TMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1883.44 TX/RX Path (e.g., VSWR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193

4 Tables, Lists and Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1954.1 Hardware Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1974.2 Detailed Information on Hardware Components (Modules, Frames and Racks)

2024.3 Front View of the BS-240 Rack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2034.4 Front View of the BS-240 II Rack. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2084.5 Front View of the BS-240XL Rack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2134.6 Front View of the BS-240XL II Racks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2184.7 Corresponding Hardware Managed Objects (HMO) . . . . . . . . . . . . . . . . . 2234.8 TX/RX Paths of Some Configuration Examples. . . . . . . . . . . . . . . . . . . . . 226

5 Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2355.1 HW/SW Compatibility During Download from LMT/BSC . . . . . . . . . . . . . . 2355.2 State/Status Attributes of BTSE Managed Objects . . . . . . . . . . . . . . . . . . 2365.3 BTSE Alarm Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2385.3.1 Probable Cause Value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2385.3.2 Event Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2385.3.3 Perceived Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2395.3.4 Trend Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2395.3.5 Immediate Defense Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2395.3.6 Threshold Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2405.3.7 Proposed Repair Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2405.3.8 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2405.3.9 Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2405.4 Fault Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2405.4.1 Fault Messages at the Radio Commander. . . . . . . . . . . . . . . . . . . . . . . . . 2405.4.2 Fault Messages at the LMT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2415.5 BTSE Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2415.5.1 BTSE Components Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2415.5.2 Numbering of BTSE Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2415.5.3 Remote Inventory Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2425.6 Diagnostics / Test. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2445.6.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2445.6.2 Requirements for Starting the BTSE Module Test . . . . . . . . . . . . . . . . . . . 245

A30808-X3247-M326-5-7620 7



6 Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249

7 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251

8 A30808-X3247-M326-5-7620



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

Fig. 1.2 Used Symbols. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Fig. 1.3 Fault Clearance Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Fig. 1.4 ESD Symbol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Fig. 1.5 Module Fastening Variants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

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

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

Fig. 3.1 Flow Chart for COBA Replacement Procedure without CORE Redundancy44

Fig. 3.2 Flow Chart for COBA Replacement Procedure with CORE Redundancy,Part I . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Fig. 3.3 Flow Chart for COBA Replacement Procedure with CORE Redundancy,Part II . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Fig. 3.4 Flow Chart for COBA2P8 with COBA4P12 Replacement Procedurewithout CORE Redundancy, Part I . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Fig. 3.5 Flow Chart for COBA2P8 with COBA4P12 Replacement Procedurewithout CORE Redundancy, Part II . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Fig. 3.6 Flow Chart for COBA2P8 with COBA4P12 Replacement Procedure withCORE Redundancy, Part I . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Fig. 3.7 Flow Chart for COBA2P8 with COBA4P12 Replacement Procedure withCORE Redundancy, Part II . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Fig. 3.8 Flow Chart for COREXT Replacement Procedure . . . . . . . . . . . . . . . . . 80

Fig. 3.9 Flow Chart for COSA Replacement Procedure . . . . . . . . . . . . . . . . . . . 85

Fig. 3.10 Flow Chart for Remote Inventory Data Creation. . . . . . . . . . . . . . . . . . 175

Fig. 3.11 Flow Chart for Remote Inventory Data Restoration . . . . . . . . . . . . . . . 180

Fig. 3.12 Flow Chart for Remote Inventory Data Update. . . . . . . . . . . . . . . . . . . 184

Fig. 4.1 BS-240 II . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197

Fig. 4.2 BS-240XL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198

Fig. 4.3 Functional Blocks for BS-240 and BS-240 II. . . . . . . . . . . . . . . . . . . . . 199

Fig. 4.4 Functional Blocks for BS-240XL and BS-240XL II . . . . . . . . . . . . . . . . 200

Fig. 4.5 Functional Blocks of BS-240XL and BS-240XL II Base Rack withCOBA4P12 and COREXT Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

Fig. 4.6 BS-240 Base Rack Design and Configuration (example) . . . . . . . . . . . 203

Fig. 4.7 BS-240 Extension Rack Design and Configuration (example) . . . . . . . 204

Fig. 4.8 BS-240 Service1 Rack Design and Configuration (example) . . . . . . . . 205

Fig. 4.9 BS-240 Service2 Rack Design and Configuration (example) . . . . . . . . 206

Fig. 4.10 24 Carrier BTSE BS-240 (examples) . . . . . . . . . . . . . . . . . . . . . . . . . . 207

Fig. 4.11 BS-240 II Base Rack Design and Configuration (example) . . . . . . . . . 208

Fig. 4.12 BS-240 II Extension Rack Design and Configuration (example) . . . . . 209

Fig. 4.13 BS-240 II Service1A Rack Design and Configuration (example) . . . . . 210

Fig. 4.14 BS-240 II Service2 Rack Design and Configuration (example) . . . . . . 211

Fig. 4.15 24 Carrier BTSE BS-240 II (examples). . . . . . . . . . . . . . . . . . . . . . . . . 212

Fig. 4.16 BS-240XL Base Rack Design and Configuration (example). . . . . . . . . 213

Fig. 4.17 BS-240XL Extension Rack Design and Configuration (example) . . . . . 214

A30808-X3247-M326-5-7620 9



Fig. 4.18 BS-240XL Service1 Rack Design and Configuration (example) . . . . . 215

Fig. 4.19 BS-240XL Service2 Rack Design and Configuration (example) . . . . . 216

Fig. 4.20 24 Carrier BTSE BS-240XL (examples) . . . . . . . . . . . . . . . . . . . . . . . 217

Fig. 4.21 BS-240XL II Base Rack Design and Configuration (example). . . . . . . 218

Fig. 4.22 BS-240XL II Extension Rack Design and Configuration (example) . . . 219

Fig. 4.23 BS-240XL II Service1A Rack Design and Configuration (example) . . 220

Fig. 4.24 BS-240XL II Service2 Rack Design and Configuration (example). . . . 221

Fig. 4.25 24 Carrier BTSE BS-240XL II (examples) . . . . . . . . . . . . . . . . . . . . . . 222

Fig. 4.26 TX/RX Paths of Configuration with FICOM, DIAMCO, HPDU, DUBIAS,TMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227

Fig. 4.27 TX/RX Paths of Configuration with DUAMCO / FDUAMCO . . . . . . . . 230

Fig. 4.28 TX/RX Paths of Configuration with DIPLEXER . . . . . . . . . . . . . . . . . . 232

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

10 A30808-X3247-M326-5-7620



TablesTab. 3.1 Additional Information for COBA Replacement without CORE Redundancy

45

Tab. 3.2 Additional Information for COBA Replacement with CORE Redundancy. .52

Tab. 3.3 Additional Information for COBA2P8 Replacement with COBA4P12,without CORE Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Tab. 3.4 Additional Information for COBA2P8 Replacement with COBA4P12, withCORE Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Tab. 3.5 Additional Information for COREXT Replacement . . . . . . . . . . . . . . . . . 80

Tab. 3.6 Additional Information for COSA Replacement. . . . . . . . . . . . . . . . . . . . 86

Tab. 3.7 Additional Information for Remote Inventory Data Creation . . . . . . . . . 176

Tab. 3.8 Additional Information for Remote Inventory Data Restoration. . . . . . . 181

Tab. 3.9 Additional Information for Remote Inventory Data Update . . . . . . . . . . 185

Tab. 4.1 Possible Modules and their Hardware Managed Objects (HMO) for FlexCU223

Tab. 4.2 Possible Modules and their Hardware Managed Objects (HMO) for ACOM224

Tab. 4.3 Possible Modules and their Hardware Managed Objects (HMO) for MUCO225

Tab. 4.4 Possible Modules and their Hardware Managed Objects (HMO) forDCBCTRL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225

Tab. 4.5 Failure Causes in the TX/RX Path, Configuration with FICOM, DIAMCO,HPDU, DUBIAS, TMA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228

Tab. 4.6 Failure Causes in the TX/RX Path, Configuration with DUAMCO / FDUAM-CO. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231

Tab. 4.7 Failure Causes in the TX/RX Path, Configuration with DUAMCO / FDUAM-CO, FICOM, DIPLEXER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233

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

Tab. 5.2 Rack Numbering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242

Tab. 5.3 List of nob_RIUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243

A30808-X3247-M326-5-7620 11



1 Introduction

1.1 Structure of the Maintenance Manual

The following diagram provides an overview of the structure of this manual and the pur-pose of 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

Chapter 6 Abbreviations

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

Chapter 4

Fault Clearance Procedures for Modulesand Interfaces– Fault clearance procedures for modules,

interfaces and MOs in alphabetical order– Concluding procedure “Remote Inventory

Data Update” that some fault clearanceprocedures require (if necessary, links areprovided to this concluding procedure)

Tables, Lists and Figures– Overview of the HW architecture as

additional information

(Important information to make your workefficient and safe)

(Main Part for Fault Clearance Tasks)

(Reference Chapter)

(Reference Chapter)

(General Maintenance)

(Reference Chapter)

Chapter 7 Index (Reference Chapter)

Task ListInformation on routine tasks that need to becarried out

12 A30808-X3247-M326-5-7620



1.2 Symbols Used

The following symbols are used throughout this manual:

Fig. 1.2 Used Symbols

Reference to another procedure step

Symbol Meaning

ESD (Electrostatic Sensitive Device) precautions to be taken

Note; important information

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

b

h

Use the LMT to enter commands

Reference to another chapter

Reference to another procedure. Return after finishing.i

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

i

!

A30808-X3247-M326-5-7620 13



1.3 Fault Clearance Principle

The high system functionality of the Siemens Base Station System is achieved bymeans of system-integrated routine tests. These routine tests continually check the cor-rect functioning 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.

14 A30808-X3247-M326-5-7620



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 at SystemIntegrated Routine Test

Fault Message Displayedat Radio Commander

6.

2.

Fault Clearance Procedurefor Suspected Module

Local FaultClearance at BTSE

Necessary?

yes

no

End of FaultClearance Procedure

FaultClearance

Successful?

yes

no

AnotherProbableCause?

yes

no

Reinsert ReplacedModule

1.

3.

4.

5.

7.

Call TAC8.

9.

Content of this manual

Fault and TestManagement at

the OMC viaRadio Commander

Local FaultClearance at

the BTSE

A30808-X3247-M326-5-7620 15



Fault Clearance Guidelines

(The numbering refers to the diagram displayed in Fig. 1.3.)

1. The system integrated routine test detects a fault.

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

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

4. Interpret the fault message and go to the fault clearance procedure of the suspectedmodule or interface in chapter 3 "Fault Clearance Procedures for Modules and Inter-faces" (module/interface names as well as LMT terms (Managed Objects) are listedin alphabetical order if they appear in the fault message).Localize the fault and clear it according to the corresponding procedure.

5. As described in the corresponding procedure, verify whether the fault clearance wassuccessful:

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

– Are there any relevant active alarms?

– Do the LEDs signal normal operation?

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

7. If there is another probable cause, reinsert the recently replaced original module 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 followingthe fault clearance procedures described in this manual. However, if the fault shouldstill exist after considering all probable causes, contact the Technical AssistanceCenter (TAC). Here you will obtain help from specially trained troubleshooting ex-perts.

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 PROC: TX/RX Path (e.g., VSWR)).For general module replacement instructions also see 1.5 "Module ReplacementInstructions".

16 A30808-X3247-M326-5-7620



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 by means of a flexible lead inte-grating a 1 MΩ 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 MΩresistor).

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:BSSBE Btsep Br<no>:<NE id>BSS-EQUIPMENTBTSEPBTSEP<no>RACKRACK<no><Module><Module><no>GET <Module>NAME=RACK:<no>/<Module>:<no>REQATTL=RELFUNKOBJ

Get <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> .

iThe following procedure is only relevant if the BTSE is in phase 3. In phase 1 or 2, theBTSE cannot establish calls.

A30808-X3247-M326-5-7620 17



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:BSSBE Btsep Br<no>:<NE id>BSS-FUNCTIONALBTSMBTSM<no>BTSTRXTRX<no>GET <TRX>NAME=BTS:<no>/TRX:<no>REQATTL=OST/AST

Get 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 / operational-State = Disabled or administrativeState = Locked / operationalState = Enabled ,the module is not used for calls anymore. You can start with your maintenance task.

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

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

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

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

18 A30808-X3247-M326-5-7620



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, e.g. the CU, DIAMCO, DUAMCO / FDUAMCO, FICOM, AC/DC, are fas-tened with TORX-headed knurled screws. Replacement of these modules requires spe-cial 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 on the CU, DIAMCO, DUAMCO, FDUAMCO, COAMCO andFICOM must be fastened / unfastened with a torque spanner (2 sizes).

lever mechanism in open position

push together

lever mechanism in locked position torx screw

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

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 forsafety reasons.The modules should be removed and inserted as fast as possible, in order to preventreading in false module addresses from the CAN BUS.

A30808-X3247-M326-5-7620 19



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 code keys of the module (at the rear connector terminals) are mechanically in-tact, and that a code key plug has not been torn out from its socket and is now jammedin the backplane.

When replacing a module, please make sure

– that the code keys of the new module have the same setting as those of the old one(see figure 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

20 A30808-X3247-M326-5-7620



1.5.4 Quick Module Replacement

In general, there are 2 replacement procedures:

– the standard replacement procedure

and

– the facilitated, quick replacement procedure (only applicable for some particularmodules).

For the standard replacement procedure, an LMT is required. The modules are lockedand, after their replacement, tested and unlocked via an LMT.

For the quick replacement procedure, an LMT is not required. The module can be re-placed directly and is put into service automatically after a successful replacement (Au-torecovery).Precondition for the quick replacement procedure: the attribute Autorecovery (EAU-TOREC) is enabled.

To check whether this attribute is enabled, perform the LMT command:

BSS

BE Btsep Br<no>:<NE id>

BSS-EQUIPMENT

BTSEP

BTSEP<no>

GET BTSEP NOSWL

REQATTL

EAUTOREC

Get BTSEP NOSWL:NAME=BTSEP:<no>,REQATTL=EAUTOREC

To set this attribute, refer to ITMN:BTSE BS-240 / 240 II / 240XL / 240XL II, chapter“Setting Attributes for the BTSE”.

– In order to be able to connect the semi-rigid/flexi cables, insert the prepared moduleas far as necessary. It is recommended to leave about 2 cm (.75’’) distance betweenmodule and backplane connectors.

– Connect all semi-rigid/flexi cables.

– Fully insert the module.

iSpecial Behaviour of Modules that are connected by the CAN bus:If Autorecovery is enabled and such a module is mistakenly locked before it is ex-changed, then this module will recover automatically after it is unlocked.This has no further consequences for the system, but is an unspecified behaviour.

iQuick Replacement Procedure and semi-rigid/flexi CablingModules with semi-rigid/flexi cabling require special handling!It is important that all semi-rigid/flexi cables are connected before the module is fully in-serted. Otherwise, the module is not put into service. The reason for this is that the au-tomatic recovery process starts as soon as the module comes into contact with thebackplane connectors. Semi-rigid/flexi cables that are not connected during this pro-cess cause errors which will prevent the autorecovery of the module.

A30808-X3247-M326-5-7620 21



2 Tasklist

2.1 Filter matThe filter mat must be changed annually.

In a very dirty environment, the mat must be changed semi-annually. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . (see 3.31)

22 A30808-X3247-M326-5-7620



A30808-X3247-M326-5-7620 23



3 Fault Clearance Procedures for Modules andInterfaces

24 A30808-X3247-M326-5-7620



3.1 Abis

1 Open the BTSE door

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

2 Check the LEDs on the COBA/COSA

You can recognize an Abis alarm by the red LEDs for Abis 1 to Abis 8 alarm atthe COBA/COSA.

The Abis LEDs indicate the respective Managed Object BPORT, e.g.,:

iIn some cases, Abis alarms originate from loose or damaged PCM cables on the BTSEAbis interface (OVPT) and in the corresponding distribution frame in the BSC direction.Therefore, the relevant cables must be checked first, according to the following proce-dure.

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

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

Abis 1 corresponds to the Managed Object BPORT 0,Abis 2 corresponds to the Managed Object BPORT 1, etc.

A30808-X3247-M326-5-7620 25



3 Optional: Check the active alarms with the LMT

If an LMT is available, you can check the active Abis alarms.

Perform the following command:

b BSS

NE Btsep Br<no>:<NE id>

BSS-EQUIPMENT

BTSEP

BTSEP<no>

GETACTIVEALARMS BTSEP

Getactivealarms BTSEP:NAME=BTSEP:0;

4 Physical check of the Abis / PCM cable connections (OVPT)

Are the Abis / PCM lines fastened correctly

– in the terminal block of the OVPT and

– in the distributing frame in the BSC direction?

Y h...6N h...5

Further information on the Abis interface on the OVPT is documented in theInstallation Manual. ......see

IMN:BS-240/ 240 II / 240XL/ 240XL II

5 Fasten the Abis / PCM Lines correctly in their terminals

Did the red LED of the Abis Alarm on the COBA/COSA and CUs turn off?

This may take up to 10 minutes. Y h...9N h...6

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

Typical failure event report for an Abis / PCM 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

26 A30808-X3247-M326-5-7620



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 Abis / PCM lines in the terminal blocks (OVPT and distributingframe in BSC direction) and examine the cables visually for damages. Do yousee a broken or corroded cable or an insulation that interrupts the contact? Y h...7

N h...8

7 Repair bad Abis / PCM lines

Repair bad Abis / PCM lines or exchange the Abis / PCM lines

Did the red LED of the Abis Alarm on the COBA/COSA and CUs turn off?

This may take up to 10 minutes. Y h...9N h...8

8 Call TAC

Call TAC to clear the fault.

9 Prepare end of fault clearance

If an LMT was connected, log off the LMT and disconnect the LMT cable.

Close the BTSE door.

END

A30808-X3247-M326-5-7620 27



3.2 ABISCON

1 Go to Procedure “OVPT”

Fault clearance is identical for the modules “ABISCON” and “OVPT”.

Therefore, please refer to the procedure “OVPT”. h...Procedure: 3.37

END

28 A30808-X3247-M326-5-7620



3.3 AC/DC

The managed object ACDCP is related to the DCBCTRL, not to the AC/DC module itselfand therefore exists only once.

In BS-240 II / 240XL II the AC/DC system is not configured as managed object. To makeAC/DC alarms visible, Environmental Alarms have to be configured (see ITMN:BTSEBS-240 / 240 II / 240XL / 240XL II, Creating the Alarm Configuration (ENVABTSE)).

If the AC/DC modules are not equipped in redundant configuration, the system uses thebackup battery for power supply and may be in ’Emergency Configuration’.

In redundant configuration only one AC/DC module can be replaced at the same timewithout any interruption.

The fault message indicates the address of the corresponding DCBCTRL.

Examples for Alarms in the Power Supply System

Error ID 53266 mains breakdown

Error ID 53267 battery breakdown

Error ID 53268 -48 V out of tolerance

Error ID 53270 rectifier module fault

1 Interpret the Fault Message ......(see 5.4)

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.8)

iNote that the failure cause may be located in any module of the power sypply system:- the module(s) addressed in the error message- AC/DC- AC Panel or ADP- DCBCTRL- BatteryIt is recommended to start with the replacement of the module which is addressed inthe fault message. Afterwards - if the error is still there - to take the other modules inthe power supply system into consideration.

A30808-X3247-M326-5-7620 29



2 Find the Suspected Module

3 Check the LED Status of Each AC/DC Module

Is any red LED illuminated? Y h...10N h...5

4 No Red LED is Illuminated

– For BS-240 / 240XL continue with step h...5– For BS-240 II / 240XL II continue with step h...7

5 Check Fuses

Disconnect the AC cable from the suspected module.

Are the fuses optically and electrically all right? Y h...9N h...6

6 Change Fuses

Change the defective fuses (10 A, quick act). h...9

7 Check the AC Breakers at ADP

Are all AC breakers switched on? Y h...9N h...8

The additional Information of the fault message contains the number of thefaulty rectifier module. In this case, it should not be necessary to measure allrectifier modules.

Check the output supply current for all AC/DC modules of the rack. This canbe done by measuring the indication voltage at the test connector, seeHW:BTSE Modules, AC/DC for the appropriate module description. The rela-tionship between the indication voltage and the output current is 10 mV/A forBS-240 / 240XL and 100 mV/A for BS-240 II / 240XL II.The module(s) without output current must be investigated further.

Check the fuses F1 and F2, see HW:BTSE Modules, AC/DC for the appropri-ate module description.

see HW:BTSE Frames, ADP.

30 A30808-X3247-M326-5-7620



8 Switch on the AC Breakers

Is it not possible to switch the breaker to on or did the breaker switch back to offimmediately? Y h...16

N h...9

9 Check the Output Current

Does the module supply output current? Y h...14N h...10

10 Module Replacement

1. Disconnect all cables if there are any.

2. Take out the affected module.

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

4. Insert the prepared module.

5. Connect all cables.

11 Run Test for Replaced (Suspected) Module

Does the module supply output current? Y h...12N h...15

12 Mark the Replaced Module as Defective

h...13

13 Updating of the Remote Inventory Data

For updating the remote inventory data, see procedure “Remote Inventory DataUpdate” in this manual.

i....Procedure:3.42

14 End of Fault Clearance Procedure

Close BTSE door.

Check the output current of the suspected module by measuring the indicationvoltage at the test connector, see HW:BTSE Modules, AC/DC for the appro-priate module description.

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

Check the voltage at test connector, see HW:BTSE Modules, AC/DC for theappropriate module description. Take a voltmeter with test cable.The voltage should be 10 mV/A for BS-240 / 240XL and 100 mV/A for BS-240II / 240XL II, depending on the load.

A30808-X3247-M326-5-7620 31



15 Reinsert the replaced module

Remove the currently inserted module and reinsert the old (replaced) modulebecause the old module was probably not defective. Refer to the relevant part inthe replacement procedure.

h...16

16 Another Suspected Module/Interface?

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

17 Replacement Procedure for the Next Suspected Module/Interface

Go to the replacement procedure for the next suspected module/interface. h...Procedure: 3.x

18 Call TAC

END

32 A30808-X3247-M326-5-7620



A30808-X3247-M326-5-7620 33



3.4 ACDCP

1 Identify the Error Message

Does the error message report an AC/DC error or a rectifier error? Y h...3.3 "AC/DC"

N h...3.15 "DCBCTRL"

END

iACDCP is a functional part of DCBCTRL and cannot be replaced separately. AC/DC orrectifier errors are also reported via the object ACDCP.

34 A30808-X3247-M326-5-7620



3.5 ACT



– Module(s) ??

– BTS-no ??

– Rack-no ??



Use the logical address to find the mounting location of the module(s). ......(see 4.3)

2 Autorecovery (EAUTOREC) enabled?

Is the attribute Autorecovery (EAUTOREC) enabled? Y h...3N h...6

If you have no information on this attribute, continue with “N”.

3 Quick Module Replacement

iThe module ACT consists of: ACTA, ACTC and ACTPThe ACTC can be changed only together with the DC Panel.


A30808-X3247-M326-5-7620 35



1. Disconnect all cables on ACTA and ACTP, see HW:BTSE Modules, ACT forthe appropriate module description.

2. Loosen the screws of the ACTA and ACTP modules.

3. Take out the ACTA and ACTP modules.

4. Select the modules with a functional HW / SW state compatible to that of themodules which are being replaced.

5. Check the DIP Switch settings against the replaced module, see HW:BTSEModules, ACT for the appropriate module description.

6. Insert the prepared modules.

7. Attach the prepared modules by tightening the screws.


– Replacement successful? h...4– Replacement unsuccessful? h...13

4 Mark the Replaced Module as defective


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

socket.


6 Connect the LMT to the BTSE

Plug the LMT cable into the corresponding socket. ...... (see Fig. 4.6)

Start LMT Login - Procedure (refer to LMT description).

7 Lock Suspected Module

b BSS


BSS-EQUIPMENT

BTSEP

BTSEP<no>

RACK

RACK<no>

ACT

ACT<no>

LOCK ACT

Was the module replacement successful?All LEDs must signal normal operation (no red LEDs may be on).Call OMC to make sure that the BTSE has gone back to normal operation.

36 A30808-X3247-M326-5-7620




1. Disconnect all cables on ACTA and ACTP, see HW:BTSE Modules, ACT forthe appropriate module description.

2. Loosen the screws of the ACTA and ACTP modules.

3. Take out the ACTA and ACTP modules.

4. Select the modules with a functional HW / SW state compatible to that of themodules which are being replaced.

5. Check the DIP Switch settings against the replaced module, see HW:BTSEModules, ACT for the appropriate module description.

6. Insert the prepared modules and attach them by tightening the screws.


9 Run Test for Replaced Module

b BSS


BSS-EQUIPMENT

BTSEP

BTSEP<no>

RACK

RACK<no>

ACT

ACT<no>

PERFTEST ACT

The test outcome can be examined in the “Message Viewer” window. Is the testoutcome as follows?

– Test Outcome = passed h...10– Test Outcome = failed h...13



A30808-X3247-M326-5-7620 37



11 Unlock Suspected Module

b BSS


BSS-EQUIPMENT

BTSEP

BTSEP<no>

RACK

RACK<no>

ACT

ACT<no>

UNLOCK ACT


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


13 Reinsert the Replaced Module


h...14

14 Next Suspected Module

Is one of the suspected modules not yet replaced? Y h...15N h...16

15 Replacement Procedure for the next Suspected Module

Go to the replacement procedure for the next suspected module. h...Procedure: 3.x

16 Unsuccessful module replacement

Call TAC.

END

38 A30808-X3247-M326-5-7620



3.6 BATTERY

The fault message indicates the address of the corresponding DCBCTRL.

In BS-240 II / 240XL II the battery is not configured as managed object. To make batteryalarms visible, Environmental Alarms have to be configured (see ITMN:BTSE BS-240 /240 II / 240XL / 240XL II, Creating the Alarm Configuration (ENVABTSE)).



– Module(s) ??

– BTS-no ??

– Rack-no ??





Plug the LMT cable into the corresponding socket. ......(see Fig. 4.6)



b BSS


BSS-EQUIPMENT

BTSEP

BTSEP<no>

RACK

RACK<no>

BATTERY

BATTERY<no>

LOCK BATTERY

4 Module replacement

!ESD precautions must be taken when pulling and inserting a module. Refer to1.5.1 "ESD Precautions"

A30808-X3247-M326-5-7620 39



1. Disconnect the battery cables coming from AC/DC converters, see HW:BT-SE Frames, F:Battery for the appropriate module description.

2. Disconnect the batteries by removing pre-fabricated short wire bridges.

3. Remove the air vent kit.

4. Open both fixing straps.

5. Remove the affected module.

6. Select a module of the same manufacturer to that of the module which isbeing replaced (check also DIP switches for manufacturer on DCBCTRL).


8. Setup the 4 batteries on the battery tray.

9. Close and tighten both fixing straps.

10. Setup the air vent kit and route the outlet tube through the cable feedingmodule.

11. Connect the batteries by pre-fabricated short wire bridges.

12. Connect the battery cables coming from AC/DC converters.

5 Run Test for replaced module

b BSS


BSS-EQUIPMENT

BTSEP

BTSEP<no>

RACK

RACK<no>

BATTERY

BATTERY<no>

PERFTEST BATTERY


– Test Outcome = Pass h...6– Test Outcome = Fail h...10


!Pay attention to the sequence of the steps to avoid shorts.

40 A30808-X3247-M326-5-7620




For updating the remote inventory data, see to procedure “Remote InventoryData Update” in this manual.

h...Procedure: 3.42


b BSS


BSS-EQUIPMENT

BTSEP

BTSEP<no>

RACK

RACK<no>

BATTERY

BATTERY<no>

UNLOCK BATTERY

9 End of fault clearance procedure



10 Reinsert the replaced module


h...11





13 Unsuccessful module replacement

Call TAC.

END

A30808-X3247-M326-5-7620 41



3.7 BPORT

1 Go to Procedure h...3.1 "Abis"

END

iBPORT errors are reported via the object Abis.

42 A30808-X3247-M326-5-7620



A30808-X3247-M326-5-7620 43



3.8 COBA Without CORE Redundancy

Flow Chart and Additional Information:

The following flow chart gives an overview of the fault clearance procedure. Addtionalinformation to the steps is included behind the flow chart, followed by the steps in detail.

!A mix of module types COBA2P8 / COSA6P16 with module types COBA4P12 /COSA4P12 in one rack is not allowed - even in the status “power off”.

!These modules are equipped with electrostatically sensitive components and aresusceptible to damage by electrostatic discharge. Follow ESD precautions when re-moving and inserting modules. Refer to 1.5.1 "ESD Precautions".

!When the COBA4P12 is inserted, a module COSA4P12 or COREXT must also beinstalled. Check if one of these modules is installed and insert if necessary.

iThis procedure describes the replacement of a COBA4P12 with a COBA4P12 or thereplacement of a COBA2P8 with a COBA2P8 without CORE redundancy.For the replacement of a COBA2P8 with a COBA4P12 or COBA with redundancy,please see:

– 3.9 "COBA With CORE Redundancy"– 3.10 "COBA2P8 - COBA4P12 Without CORE Redundancy"– 3.11 "COBA2P8 - COBA4P12 With CORE Redundancy"

iModule COBA may be removed while the power is on.

iAfter the completion of this replacement procedure, it is necessary to perform the pro-cedure 3.41 "Remote Inventory Data Restoration" as mentioned in step 18.

44 A30808-X3247-M326-5-7620



Fig. 3.1 Flow Chart for COBA Replacement Procedure without CORE Redundancy

Fault ClearanceProcedure Start(LMT Phase 2)

Requested Logon(LMT Phase 1)

SW Downloadand Activation(LMT Phase 2)

COBAReplacement

BTSEP FlashEPROM Format

6

8

7

3-5

1,2Steps

BTSEReconfiguration

9-12

Connection to BSC(LMT Phase 3)

Reinsertment;Next Module Check

or TAC Call

FaultClearance

Successful?

yes

no

13,14

15

Module Markingas Defective

Fault ClearanceProcedure Finish

Remote InventoryData Restoration

Procedure 3.39

17

18

19

16

A30808-X3247-M326-5-7620 45



Additional Information:

1 Interpret the Fault Message ...... (see 5.4)


– Module(s) ??

– BTS-no ??

– Rack-no ??



Use the logical address to find the mounting location of the module(s). ...... (see Fig. 4.6)

2 Log on LMT

Connect the LMT to the BTSE.

3 Switch off COBA module

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

4 Replace COBA

Step Information

6 After the insertion of the new COBA, the system will automatically log offand request to log on again. After the logon, the BTSE is then in phase 1.

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

9 After the COBA replacement, the BTSE specific data base will be lost. Thismakes it necessary to reconfigure the BTSE. Usually, a backup copy of theconfiguration is stored with the site specific documentation. If there is nobackup, you must reconfigure the BTSE by hand.

14 The BTSE is now in phase 3. The BSC will start the alignment with theBTSE.

18 It is necessary to rebuild the inventory data that was stored on the removedCOBA, using a backup IDF file or by hand.

Tab. 3.1 Additional Information for COBA Replacement without CORE Redundancy

!ESD precautions must be taken when pulling and inserting a module. Referto 1.5 "Module Replacement Instructions"

46 A30808-X3247-M326-5-7620



1. Only for COBA2P8 replacement: Remove the COSA (if present).

2. Remove the COBA.

3. Select a module with a functional HW/SW state compatible to that of themodule which is being replaced: same COBA type as before, i.e. same typeas COSA (if present).

4. Only for COBA2P8: Check the DIP Switch settings against the replaced mod-ule, see HW:BTSE Modules, COBA for the appropriate module description.

5. Insert new COBA (same model type).

6. Only for COBA2P8 replacement: Insert the module COSA (if one wasinstalled).

5 Switch on COBA module

Switch on the replaced COBA with the corresponding breaker on the DC Panel.

The boot process starts. Wait a few minutes until the boot process is finished(green LED:ACT is on).

6 Log on

b Local Log on at NE Btsep

UserName:<user>

Password:<password>

Ok

7 Format BTSEP Flash EPROM

b BSS


BSS-EQUIPMENT

BTSEP

BTSEP<no>

FORMAT BTSEP FLASH

8 Download and Activate the SW

Download and activate the SW. Afterwards, log on again (the BTSE is then inphase 2). Refer to ...

i....ITMN:BTSEBS-240 / 240 II/ 240XL/ 240XL II

9 Reconfigure the BTSE

Is a backup copy of the site specific configuration available? Y h...11N h...10

iFor COBA4P12 replacement: This process will take a few minutes. Pleasewait until the process has finished.

A30808-X3247-M326-5-7620 47



10 Reconfigure the BTSE by hand

Repeat all tasks for the BTSE installation as described in the ITMN:BTSE. i ... ITMN:BTSEBS-240 / 240 II/ 240XL/ 240XL II

Afterwards, continue with step ... h...13

11 Copy the Backup Script Files to the BKBTS\BTSPLUS Directory

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

12 Restore the HW Configuration

b To restore the HW configuration:

1. Select “File” -> “Backup BTS” from the menu or click on the correspondingicon in the tool bar. The “Backup BTS” window opens and the restore proce-dure is ready to start.

2. Click on the “Restore” button in the “Backup BTS” window or select “File” ->“Restore”.

3. Select the correct configuration, e.g. “Backup 1”, and confirm by clicking“Ok”.

4. After the restoration procedure you can choose to repeat it or go on workingwith the LMT Click “Ok” to finish the process.

13 Connect BTS Site Manager to the BSC

b BSS


BSS-FUNCTIONAL

BTSM

BTSM:<no>

CONNBSC BTSM

14 Log on

b Local Log on at NE Btse

UserName:<user>

Password:<password>

Ok

48 A30808-X3247-M326-5-7620



15 Result of Module Replacement

The module replacement was successful if the LEDs signal normal operation, ifthere are no relevant active alarms, and if the object details for the COBA are asfollows:

Was the module replacement successful? Y h...17N h...16

16 Unsuccessful Module Replacement

– Remove the currently inserted module and reinsert the old (replaced) modulebecause it was probably not defective.

– If there is another suspected module/interface in the fault message, performthe replacement procedure of the next suspected module.

h...“Procedure 3.x”

– Otherwise, call TAC and proceed with step ... h...19


18 Restore the Remote Inventory Data

For the remote inventory data restoration, please see procedure ... i....3.41 "RemoteInventory DataRestoration"

Afterwards, continue with the now following step.

19 Finish Fault Clearance Procedure

– Check for other alarms and continue with the according replacementprocedure if necessary.

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

– Close the BTSE door.

END

Availability Status Null

Operational State Enabled

Administrative State Unlocked

A30808-X3247-M326-5-7620 49



3.9 COBA With CORE Redundancy


The following flow chart gives an overview of the fault clearance procedure. Additionalinformation to the steps is included behind the flow chart, followed by the steps in detail.



!When the COBA4P12 is inserted, a module COSA4P12 or COREXT must also be in-stalled. Check if one of these modules is installed and insert if necessary.

iThis procedure describes the replacement of a COBA4P12 with a COBA4P12 or thereplacement of a COBA2P8 with a COBA2P8 with CORE redundancy.For other COBA replacements see:

– 3.8 "COBA Without CORE Redundancy"– 3.10 "COBA2P8 - COBA4P12 Without CORE Redundancy"– 3.11 "COBA2P8 - COBA4P12 With CORE Redundancy"


iImportant:The data of both COBAs must be consistent and equal. If the data of both COBAs arenot consistent and equal, proper operation of the BTSE is not guaranteed in case of anautomatic switch due to a COBA/COSA failure.


50 A30808-X3247-M326-5-7620



Fig. 3.2 Flow Chart for COBA Replacement Procedure with CORE Redundancy,Part I


COBAReplacement

COBA Status Switch;Inactive COBA

Switch Off

COSA Removal(if present)

7,8

6

1,2

Steps

BTSE BackupFile Generation

3

IDT File Uploadfrom BTSE

Inactive COBADetermination

4

5

6

replaced COBAmust be active

continue on next page ...


9

ITMN:BTSE BS-240 /240 II / 240XL / 240XL II

A30808-X3247-M326-5-7620 51



Fig. 3.3 Flow Chart for COBA Replacement Procedure with CORE Redundancy,Part II



17

19

18

15

13,14

12

10

11

HWConfiguration

Connection to BSC(LMT Phase 3)

COBASwitch On


or TAC Call

FaultClearance

Successful?

yes

no




Procedure 3.39

20

... continued from previous page

16

52 A30808-X3247-M326-5-7620






– Module(s) ??

– BTS-no ??

– Rack-no ??




2 Log on LMT

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

Step Information

3 After the COBA replacement, the BTSE specific data base for this COBA islost and it is necessary to reconfigure the BTSE. Therefore, backup filesthat are generated from the redundant COBA can be used.

4 After the COBA replacement, the Remote Inventory Data are lost and mustbe rebuilt with a backup IDF file. The Remote Inventory Data have to beloaded to the LMT PC from the BTSE.

7 The replaced COBA must be active. The formerly redundant (active) COBAis now inactive.

9 With the switch of the COBA status, the BTS site manager will automaticallybe disconnected from the BSC and request to log on again. After the logon,the BTSE is then in phase 1.

11 After the COBA replacement, the BTSE specific data base for this COBA islost and it is necessary to download and activate the SW again. It is neces-sary to log on again afterwards. The BTSE is then in phase 2.

14 The BTSE is now in phase 3. The BSC will start the alignment with theBTSE.


Tab. 3.2 Additional Information for COBA Replacement with CORE Redundancy

A30808-X3247-M326-5-7620 53



3 Generate a BTSE Backup File

Perform the procedure “BTS Backup Files Generation” described in the ITMN. i ... ITMN:BTSEBS-240 / 240 II/ 240XL/ 240XL II

4 Upload IDT File from BTSE

b BSS


BSS-EQUIPMENT

BTSEP

BTSEP<no>

REMINV

REMINV<no>

UPLLIDF REMINV

DESTDIR=<path>

FILE=<file name>

OVERWRITE=YES

5 Determine the Inactive COBA Module

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 Evolution.If the value OVERWRITE=YES is selected, a former version of an uploaded IDTfile will be overwritten.

Example: <path>=C:\...\LMT<version>\Idf\Upload; <file name> =btse.idtThe extension “idt” is recommended.

Check the LEDs “FLOC” on both COBAs, see HW:BTSE Modules, COBA:The COBA, on which the LED “FLOC” is not on, is the inactive (suspected)COBA. Also, the blinking of the other LEDs at the active COBA is higher fre-quent than at the inactive COBA.

At the LMT, the inactive COBA is marked with a blue indicator:

54 A30808-X3247-M326-5-7620



Proceed with the inactive COBA module.

6 Replace COBA

1. Only for COBA2P8 replacement: Remove the module COSA (if present).

2. Remove the affected module (inactive COBA).

3. Select a module with a functional HW/SW state compatible to that of themodule which is being replaced: same COBA type as before.

4. Only for COBA2P8: Check the DIP switch settings against the replaced mod-ule, see HW:BTSE Modules, COBA for the appropriate module description.

5. Insert new module (same COBA type; the insertion starts the boot process).

6. Only for COBA2P8 replacement: Insert the module COSA (if one wasinstalled).

7. Wait a few minutes until the boot process is finished (green LED ”ACT” is on),see HW:BTSE Modules, COBA for the appropriate module description.

!ESD precautions must be taken when removing and inserting a module.Refer to 1.5 "Module Replacement Instructions"

A30808-X3247-M326-5-7620 55



7 Switch the COBA Status of the Replaced COBA from Inactive to Active

Switch the inactive COBA to active status to avoid an “automatic redundancyswitch”.

b BSS


BSS-EQUIPMENT

BTSEPs

BTSEP<no>

RACK

RACK<no>

COBA

COBA<no>

SWITCH COBA

8 Switch off the Inactive COBA

Switch off the inactive (previously redundant) COBA with the correspondingbreaker on the DC panel to avoid an “automatic redundancy switch”.

9 Log on

b Local Logon at NE Btsep

UserName:<user>

Password:<password>

Ok


b BSS


BSS-EQUIPMENT

BTSEP

BTSEP<no>

FORMAT BTSEP FLASH



i ... ITMN:BTSEBS-240 / 240 II/ 240XL/ 240XL II

iFor COBA4P12 replacement: This process will take a few minutes. Pleasewait until the process has finished.

56 A30808-X3247-M326-5-7620










b BSS


BSS-FUNCTIONAL

BTSM

BTSM:<no>

CONNBSC BTSM

14 Log on

b Local Logon at NE Btse

UserName:<user>

Password:<password>

Ok







A30808-X3247-M326-5-7620 57






h... “Procedure 3.x”




For the remote inventory data restoration, please see procedure ... and startwith step 5.

i ...3.41 "RemoteInventory DataRestoration"


19 Switch on the COBA that was Switched off before

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





END

58 A30808-X3247-M326-5-7620



A30808-X3247-M326-5-7620 59



3.10 COBA2P8 - COBA4P12 Without CORE Redundancy





iThis procedure describes the replacement of a COBA2P8 with a COBA4P12 withoutCORE redundancy.For other COBA replacements, please see:

– 3.8 "COBA Without CORE Redundancy"– 3.9 "COBA With CORE Redundancy"– 3.11 "COBA2P8 - COBA4P12 With CORE Redundancy"

!When the COBA4P12 is inserted, a module COSA4P12 or COREXT must also be in-stalled. Check if one of these modules is installed and insert if necessary. If the BTS isequipped with a COSA6P16 module, it must be replaced with a COSA4P12 orCOREXT module as part of the COBA replacement. See also 3.13 "COSA" for details.



60 A30808-X3247-M326-5-7620



Fig. 3.4 Flow Chart for COBA2P8 with COBA4P12 Replacement Procedurewithout CORE Redundancy, Part I




COSA Removal(if present)


5

7

6

2,3

1

Steps

BTSEReconfiguration

8-12

Connectionto BSC

(LMT Phase 3)

13,14


COBAReplacement

2-4

COSA or COREXTInsertion

3,4

A30808-X3247-M326-5-7620 61



Fig. 3.5 Flow Chart for COBA2P8 with COBA4P12 Replacement Procedurewithout CORE Redundancy, Part II


1 Log on LMT

Connect the LMT to the BTSE.


or TAC Call

FaultClearance

Successful?

yes

no

15



Procedure 3.39

17

19


18

16


Step Information

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

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

8 After the COBA replacement, the BTSE specific data base will be lost. Thismakes it necessary to reconfigure the BTSE. Usually, a backup copy of theconfiguration is stored with the site specific documentation. If there is no back-up, the BTSE must be reconfigured by hand.

11 In the script file “Script3p.lmt”, the command “Create BPORT” has to be modi-fied if the requested value of the “LIMP” attribute is different to the defaultvalue.

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


Tab. 3.3 Additional Information for COBA2P8 Replacement with COBA4P12,without CORE Redundancy

62 A30808-X3247-M326-5-7620



2 Power Off COBA2P8 (and COSA6P16 if present)

Switch off the COBA (and COSA if present) with the corresponding breaker(s)on the DC Panel.

3 Replace COBA2P8 with COBA4P12

1. Remove the COSA6P16 (if present).

2. Remove the COBA2P8.

3. Select the COBA4P12 module and check the DIP switch, see HW:BTSEModules, COBA .

– Check the DIP switch setting on the COBA4P12. It is possible to changethe external clock synchronization with the DIP switch setting.

4. Select the COSA4P12 or COREXT.

5. Insert the new modules.

4 Switch on COBA and COSA or COREXT, respectively

Switch on the replaced COBA and COSA or COREXT with the correspondingbreakers on the DC panel.

The boot process starts.

5 Log on


UserName:<user>

Password:<password>

Ok

!When the COBA4P12 is inserted, a module COSA4P12 or COREXT mustalso be installed. Check if one of these modules is installed and insert if nec-essary.If a COSA6P16 is already installed, it must be replaced by a COSA4P12 orCOREXT module as part of the COBA replacement. See also 3.13 "COSA"for details.

!ESD precautions must be taken when removing and inserting a module. Re-fer to 1.5.1 "ESD Precautions".

iWait a few minutes until the boot process is finished. For the COBA2P8, thebooting process is signaled by red and green flashing LEDs. The green LED“ACT” will be on when the process is finished.

A30808-X3247-M326-5-7620 63




b BSS


BSS-EQUIPMENT

BTSEP

BTSEP:<no>

FORMAT BTSEP FLASH



i ... ITMN:BTSEBS-240 / 240 II/ 240XL/ 240XL II

8 Reconfigure the BTSE

Is a backup copy of the site specific configuration available? Y h...10N h...9

9 Reconfigure the BTSE by hand

Repeat all tasks for the BTSE installation as described in the ITMN: BTSE. i ... ITMN:BTSEBS-240 / 240 II/ 240XL/ 240XL II

Afterwards, continue with step ... h...13

10 Copy the backup script files to the BKBTS\BTSPLUS directory

Copy the 6 backup scritp files “script*p.lmt” from the disk to the harddisk of theLMT PC e.g., C:\LMT<version>\BKBTS\BtsPlus\Backup1.

11 Change Backup Script File “Script3p.lmt” if necessary

iThis process will take a few minutes. Please wait until the process hasfinished.

iThis step is only necessary if the required lineImpedance setting islmp75Ohm and does therefore not correspond with the default values. Theoperator is responsible for the correct setting of the lineImpedance attribute.

64 A30808-X3247-M326-5-7620



The default values are:

– lmp100or120Ohm for COBA4P12

– AccDIP for COBA2P8

When replacing the COBA2P8 with a COBA4P12, the default value is automati-cally changed from AccDIP to lmp100or120 Ohm.

If the value lmp75Ohm is required for the COBA4P12, the script file“Script3p.lmt” must be changed:

b To edit the script file:

1. Open the file “Script3p.lmt” with a text editor like Notepad.The script files were saved in step 10 to the LMT PC, e.g.C:\...\LMT<version>\BKBTS\BtsPlus.

2. Modify the command “Create BPORT”. The attribute LIMP has to be set to“Imp75Ohm”.

3. Save the file as “Script3p.lmt”.








b BSS


BSS-FUNCTIONAL

BTSM

BTSM:<no>

CONNBSC BTSM

14 Log on


UserName:<user>

Password:<password>

Ok

A30808-X3247-M326-5-7620 65













For the remote inventory data restoration, please see procedure ... i ...3.41 "RemoteInventory DataRestoration"






END




66 A30808-X3247-M326-5-7620



A30808-X3247-M326-5-7620 67



3.11 COBA2P8 - COBA4P12 With CORE Redundancy





iThis procedure describes the replacement of a COBA2P8 with a COBA4P12 withCORE redundancy.For other COBA replacements, please see:

– 3.8 "COBA Without CORE Redundancy"– 3.9 "COBA With CORE Redundancy"– 3.10 "COBA2P8 - COBA4P12 Without CORE Redundancy"

!When the COBA4P12 is inserted, a module COSA4P12 or COREXT must also be in-stalled. Check if one of these modules is installed and insert if necessary.If the BTS is equipped with COSA6P16 modules, they must be replaced withCOSA4P12 or COREXT modules as part of the COBA replacement. See also3.13 "COSA" for details.


iImportant:The data of both COBAs must be consistent and equal. If the data of both COBAs arenot consistent and equal, proper operation of the BTSE is not guaranteed in case of anautomatic switch due to a COBA/COSA failure.

68 A30808-X3247-M326-5-7620



Fig. 3.6 Flow Chart for COBA2P8 with COBA4P12 Replacement Procedure withCORE Redundancy, Part I



Backup Script FileModification

BTSE BackupFile Generation


7

10

9

2

1Steps


COBA andCOSA (or COREXT)

Replacement

4-6


8

IDT File Uploadfrom BTSE

3

only one COBApower on

HWConfiguration

11

ITMN:BTSE BS-240 /240 II / 240XL / 240XL II

12,13IDF Evolution Start;

IDF File Open

14,15 nob_RIU File Export;Download to BTSE

A30808-X3247-M326-5-7620 69



Fig. 3.7 Flow Chart for COBA2P8 with COBA4P12 Replacement Procedure withCORE Redundancy, Part II


or TAC Call

FaultClearance

Successful?

yes

no

27



29

30

28


20,21

22

BTSM Activation;Requested Logon

(LMT Phase 2)

HW Configurationnob_RIU Download

23IDT File Upload

from BTSE

Steps 12-19Repetition forsecond COBA

fromStep 19

24Uploaded IDF

File Open

25 IDF File Export

for Backup

26Other COBA

Power On

18,19 Other COBA PowerOn; First COBA

Power OFF

Automatic SW Downloadfrom first (active) COBA

16,17 BSC Connection;Requested Logon

(LMT Phase 1)

70 A30808-X3247-M326-5-7620




1 Log on LMT


2 Generate a BTSE Backup File

Perform the procedure “BTS Backup Files Generation” described in the ITMN. i....ITMN:BTSEBS-240 / 240 II/ 240XL/ 240XL II

Step Information

2 After the COBA replacement, the BTSE specific data base is lost and it is nec-essary to reconfigure the BTSE. Therefore, backup files that are generatedfrom the redundant COBA can be used.

3 After the COBA replacement, the Remote Inventory Data are lost and must berebuilt with a backup IFD file. The Remote Inventory Data have to be loadedto the LMT PC from the BTSE.

5 If no COSA boards exist, COREXT boards need to be inserted.

7 With the switch off of the COBA modules, the BTS site manager will automati-cally be disconnected from the BSC and request to log on again. The BTSE isthen in phase 1.

9 After the COBA replacement, the BTSE specific data base for this COBA islost and it is necessary to download and activate the SW again. It is neces-sary to log on afterwards. The BTSE is then in phase 2.

10 In the script file “Script3p.lmt”, the command “Create BPORT” has to be modi-fied if the requested value of the “LIMP” attribute is different to the defaultvalue.

14 Only the nob_RIU-part has to be exported for the download to the BTSE.

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

21 After the activation of the BTSM, the BTSE will automatically request to switchto log on. The BTSE is then in phase 2.

23 The Remote Inventory Data that are stored in the BTSE (IDT file) must be up-loaded to the LMT PC in order to create an up-to-date IDF file for backup.

25 An IDF file must be created for backup.

Tab. 3.4 Additional Information for COBA2P8 Replacement with COBA4P12, withCORE Redundancy

A30808-X3247-M326-5-7620 71




b BSS


BSS-EQUIPMENT

BTSEP

BTSEP<no>

REMINV

REMINV<no>

UPLLIDF REMINV

DESTDIR=<path>

FILE=<file name>

OVERWRITE=YES

4 Power Off COBA2P8 / COSA6P16 modules

Switch off both COBA and COSA modules with the corresponding breakers onthe DC Panel.

5 Replace Both Pairs of COBA2P8 and COSA6P16 Modules with COBA4P12/ COSA4P12

1. Remove all the modules COBA2P8 / COSA6P16.

2. Select the COBA4P12 modules.

– Check the external clock synchronization and adjust if necessary with theDIP switch on the COBA4P12, also see HW:BTSE Modules, COBA .

3. Select the COSA4P12 (or COREXT) modules.

4. Insert the new modules.

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 Evolution.If the value OVERWRITE=YES is selected, a former version of an uploaded IDTfile will be overwritten.

Example: <path>=C:\...\LMT<version>\Idf\Upload; <file name> =btse.idtThe extension “idt” is recommended.

iIf no COSA boards exist, COREXT boards need to be inserted.

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

72 A30808-X3247-M326-5-7620



6 Power On one Pair of Modules COBA4P12 / COSA4P12

Switch on one COBA and COSA module with the corresponding breakers onthe DC panel.

The boot process starts.

7 Log on


UserName:<user>

Password:<password>

Ok

8 Format BTSEP Flash EPROM for the New COBA Modules

b BSS


BSS-EQUIPMENT

BTSEP

BTSEP:<no>

FORMAT BTSEP FLASH

9 Download and Activate the SW for the first COBA


i....ITMN:BTSEBS-240 / 240 II/ 240XL/ 240XL II

10 Change Backup Script File “Script3p.lmt” if necessary

iWait a few minutes until the boot process is finished. The booting process issignaled by red and green flashing LEDs. The green LED “ACT” will be onwhen the process is finished.

iThis process will take a few minutes. Please wait until the process hasfinished.

iThis step is only necessary if the required lineImpedance setting islmp75Ohm and does therefore not correspond with the default values. Theoperator is responsible for the correct setting of the lineImpedance attribute.

A30808-X3247-M326-5-7620 73



The default values are:

– lmp100or120Ohm for COBA4P12

– AccDIP for COBA2P8

When replacing the COBA2P8 with a COBA4P12, the default value is automati-cally changed from AccDIP to lmp100or120 Ohm.

If the value lmp75Ohm is required for the COBA4P12, the script file“Script3p.lmt” must be changed:

b To edit the script file:

1. Open the file “Script3p.lmt” with a text editor like Notepad.The script files were saved in step 2 to the LMT PC, e.g.C:\...\LMT<version>\BKBTS\BtsPlus.

2. Modify the command “Create BPORT”. The attribute LIMP has to be set to“Imp75Ohm”.

3. Save the file as “Script3p.lmt”.







12 Start IDF Evolution

b To start the IDF Evolution, select “IDF GSM” -> “IDF Editor” from the Windowsprogram menu.

13 Open IDF File

b To open the IDF file:

1. Select “File” -> “Open” from the menu of the IDF Evolution.

2. Enter path and file name of the IDF file or select the file from the list in theappearing window.

3. Double-click on the file name or click on the “Open” button after selecting thefile name.

74 A30808-X3247-M326-5-7620



14 Export nob_RIU File

b To export the nob_RIU data:

1. Select “Export” > “NOB” from the menu.

2. A window opens in which you can edit the file name and select the directoryin which the file is saved. By default, the file name is composed of the “SalesUniqueName” with the extension “.nob”. Edit the file name and select thesource directory or confirm the default name and directory by clicking on the“Save” button.

3. The nob_RIU data are exported to the NOB file. The selected destinationpath of this file is displayed in an attention window. Confirm by clicking on the“OK” button.

4. A question window is displayed: “Create BTS_NRIU for download?” Click onthe “Yes” button.

15 Download nob_RIU File to BTSE

Change to the LMT Evolution main window.

b BSS


BSS-EQUIPMENT

BTSEP

BTSEP:<no>

REMINV

REMINV:<no>

DNLIDFD REMINV

SRCDIR=<source directory>

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


b BSS


BSS-FUNCTIONAL

BTSM

BTSM:<no>

CONNBSC BTSM

A30808-X3247-M326-5-7620 75



17 Log on


UserName:<user>

Password:<password>

Ok

18 Power On Remaining Pair of Modules COBA4P12 / COSA4P12

Switch on the remaining (second) pair of COBA/COSA modules with thecorresponding breakers on the DC panel.

19 Power Off Active (first) Pair of Modules COBA4P12 / COSA4P12

With the corresponding breakers on the DC Panel, switch off the first pair ofCOBA and COSA modules that has been reconfigured before.

20 Activate BTSM

b BSS


BSS-FUNCTIONAL

BTSM

BTSM:<no>

ACTIVATE BTSM

NAME=BTSM:0

21 Log on


UserName:<user>

Password:<password>

Ok

22 Restore the HW Configuration and Download the nob_RIU File to theBTSE

Repeat all steps 12 to 19 as described before and continue with the followingstep.

h...12

iWait a few minutes until the boot process is finished and the SW from thefirst (active) COBA is automatically downloaded. The booting and download-ing process is signaled by red and green flashing LEDs. The green LED“ACT” will be on when the process is finished.

76 A30808-X3247-M326-5-7620



23 Upload IDT File from BTSE for Backup

b BSS


BSS-EQUIPMENT

BTSEP

BTSEP:<no>

REMINV

REMINV:<no>

UPLLIDF REMINV

DESTDIR=<path>

FILE=<file name>

OVERWRITE=YES

Additional Information: The attributes DESTDIR and FILE are optional. If nospecial path or file name is entered, the file is uploaded to the default directory:C:\...\LMT<version>\IDF\upload,OVERWRITE=<yes> of the IDF Evolution. If theattribute OVERWRITE=<yes> is selected, a former version of an uploaded IDTfile will be overwritten.

24 Open the Uploaded File

Change to the IDF Evolution main window.

b Open the uploaded file:

– Select “File” -> “Open” in the 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.

25 Export IDF File for Backup

b To export the Remote Inventory Data for backup:

1. Select “Export” -> "IDF" from the menu.

2. Select the destination path in the appearing window, preferably “A:\”. The filename is automatically composed of the “SalesUniqueName” with theextension “.idf”.

3. Click on the “Save” button.

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

26 Power On Remaining Pair of Modules COBA4P12 / COSA4P12

Switch on the remaining pair of COBA/COSA modules with the correspondingbreakers on the DC panel.

Wait a few minutes until the boot process is finished (green LED “ACT” is on).

A30808-X3247-M326-5-7620 77
















END




78 A30808-X3247-M326-5-7620



A30808-X3247-M326-5-7620 79



3.12 COREXT

The full range of 4 Abis- and 12 CU-Interfaces of the COBA4P12 is available only, if theassociated COREXT module is plugged in. The module COREXT is a passive HW-module, which is unknown by the SW.


A flow chart of the procedure is given for a better overview. Additional information to thesteps is included behind the flow chart, followed by the steps in detail.

iA new BTS is delivered by factory including the COREXT card. Installation with theCOREXT module is strongly recommended.

iIf a single module COBA2P8 is replaced by a COBA4P12:The COREXT module has to be installed too if the BTS type supports a COSA module.A COSA4P12 module is necessary if the BTSE supports an additional extension rack(e.g. BS-240XL with extension rack).

80 A30808-X3247-M326-5-7620



Fig. 3.8 Flow Chart for COREXT Replacement Procedure


FaultClearance

Successful?


CU Unlocking

1,2

Steps

CU Locking3

COREXTReplacement

CU Test

4

5

9

7 Reinsertment;Next Module Check

or TAC Call

yes

no



10

8

6

Step Information

7 The fault clearance was successful if the LEDs signal normal operation (nored LED PA on CU), if the test outcome was “pass”, and if there are no rele-vant active alarms.

Tab. 3.5 Additional Information for COREXT Replacement

A30808-X3247-M326-5-7620 81





– Module(s) ??

– BTS-no ??

– Rack-no ??



Use the logical address to find the mounting location of the module(s).

2 Log on LMT


3 Lock CU 8 - 11

b BSS


BSS-EQUIPMENT

BTSEP

BTSEP:<no>

RACK

RACK:<no>

CU

CU:<no>

LOCK CU


1. Remove the COREXT.

2. Select a COREXT module with a functional HW state compatible to that ofthe module which is being replaced.

3. Insert the new module.

! “Loss of Board” Alarms from CU:08 till CU:11” refer to a faulty COREXTmodule. Also SELIC alams are possible.

!ESD precautions must be taken when removing and inserting a module. Re-fer to 1.5.1 "ESD Precautions".

82 A30808-X3247-M326-5-7620



5 Run Test for CU 8 - 11

b BSS


BSS-EQUIPMENT

BTSEP

BTSEP:<no>

RACK

RACK:<no>

CU

CU:<no>

PERFTEST CU

6 Unlock CU 8 - 11

b BSS


BSS-EQUIPMENT

BTSEP

BTSEP:<no>

RACK

RACK:<no>

CU

CU:<no>

UNLOCK CU


Was the module replacement successful, i.e. do the COBA and the CUs signalnormal operation? Y h9

N h8




h...“Procedure 3.x”


!During this test a test signal with maximum power is transmitted for a duration ofone timeslot.

A30808-X3247-M326-5-7620 83





– Check for other alarms and continue with the according replacement proce-dure if necessary.



END

84 A30808-X3247-M326-5-7620



3.13 COSA


A flow chart of the procedure is given for a better overview. Additional information to thesteps is included behind the flow chart, followed by the steps in detail.

iIn order not to loose ongoing calls, it is necessary to perform a SHUTDOWN commandat the Operation & Maintenance Center (OMC):- on the TRXs related to the CUs 8..23- on the SUBTSLB objects (subpool(s)) configured on the Abis lines 2..7Therefore, it is recommended to call the OMC to perform this procedure. Otherwise, allinvolved traffic will be lost.

iModule COSA may be removed while the power is on. Then the module must belocked before its replacement, otherwise a reset of the core will happen.

iIn combination with a COBA4P12: Either a COSA4P12 or a COREXT must be installed.


A30808-X3247-M326-5-7620 85



Fig. 3.9 Flow Chart for COSA Replacement Procedure


1,2Steps

4, 5

7

6

3

COSAReplacement

TRXShutdown by

the OMC?

yes

noCU Locking

COSA Locking

8COSA Test

9COSA Unlocking

15

16

13

10


or TAC Call

FaultClearance

Successful?

yes

no



TRXShutdown by

the OMC?

14

yes

11,12

noCU Unlocking

86 A30808-X3247-M326-5-7620






– Module(s) ??

– BTS-no ??

– Rack-no ??




2 Log on LMT


3 TRX Shutdown by the OMC?

Are the TRX related to the carrier units 8..23 and the Abis lines 2..7 shut downby the OMC? Y h...6

N h...4

Step Information

3 In order not to loose ongoing calls, it is necessary to perform a SHUT-DOWN command at the Operating & Maintenance Center (OMC):- on the TRXs related to the carrier units 8..23- on the SUBTSLB objects (subpool(s)) configured on the Abis lines 2..7

4 CU is the object for carrier units CU, ECU, or GCU. In case of FlexCU, theobject is FCUMAIN.

10 If the carrier units 8..23 have been locked before at the BTSE (instead ofTRX SHUTDOWN by the OMC), they must get unlocked again. If the TRXwere shut down by the OMC, the carrier units return automatically to normaloperation when the COSA is replaced.

Tab. 3.6 Additional Information for COSA Replacement

A30808-X3247-M326-5-7620 87



4 Lock CUs 8..23

b BSS


BSS-EQUIPMENT

BTSEP

BTSEP<no>

RACK

RACK<no>

CU

CU<no>

LOCK CU

5 Next CU

Is one of the CUs not yet locked? Y h...4N h...6

6 Lock the COSA module

b BSS


BSS-EQUIPMENT

BTSEP

BTSEP<no>

RACK

RACK<no>

COSA

COSA<no>

LOCK COSA



iIf the redundant COSA is removed from its slot, the redundant COBAperforms a reset. This is normal and not a failure.

88 A30808-X3247-M326-5-7620



1. Remove the COSA.

2. Select a COSA with a functional HW/SW state compatible to that of the mod-ule which is being replaced: same model type.

3. Check the DIP Switch settings against the replaced module, see HW:BTSEModules, COSA for the appropriate module description.

4. Insert new COSA (same model type; the insertion starts the boot process).

5. Wait a few minutes till the boot process is finished (red LED:RCOSA is on),see HW:BTSE Modules, COSA for the appropriate module description.

8 Run Test for Replaced COSA

b BSS


BSS-EQUIPMENT

BTSEP

BTSEP<no>

RACK

RACK<no>

COSA

COSA<no>

PERFTEST COSA

9 Unlock the COSA module

b BSS


BSS-EQUIPMENT

BTSEP

BTSEP<no>

RACK

RACK<no>

COSA

COSA<no>

UNLOCK COSA

10 TRX Shutdown by the OMC?

Were the TRX related to the carrier units 8..23 and the Abis lines 2..7 shut downby the OMC? Y h...13

N h...11

A30808-X3247-M326-5-7620 89



11 Unlock CUs 8..23

b BSS


BSS-EQUIPMENT

BTSEP

BTSEP<no>

RACK

RACK<no>

CU

CU<no>

UNLOCK CU

12 Next CU

Is one of the CUs not yet unlocked? Y h...11N h...13


The flashing, green LED “ACT” (ACTIVE) indicates a running OperatingSystem.

Was the module replacement successful? Y h15N h14








– Check for other alarms and continue with the according replacement proce-dure if necessary.



END

90 A30808-X3247-M326-5-7620



3.14 CU



– Module(s) ??

– BTS-no ??

– Rack-no ??




2 Interpret the Alarm Type

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

– VSWR Alarm

– Cable Problem

– Transceiver Problem

Y h...Procedure:3.44

N h...3

iModule CU may be removed while the power is on.

iThe module CU may also be an EDGE CU (ECU) or a GMSK CU (GCU).

iIt is possible to use CUs, ECUs, GCUs or FlexCUs, but please note the following:Since the GSM 1800 GCU has more RF output power than the GSM 1800 CU, mixedcell configurations might result in slight changes of some performance counters andCU dependent coverage. It is not recommended to use the antenna hopping mode inthis configuration.For more information on the RF output power of the various CU types, please refer toTED:BSS BS-240/241, TED:BSS BS-240/241 II,TED:BSS BS-240XL or TED:BSS BS-240XL II, whichever applicable.

A30808-X3247-M326-5-7620 91







1. Disconnect all semi-rigid/flexi cables.Attention: Mark the normal- and the diversity- path!


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

4. Partly insert the prepared module. Make sure that it does not yet come intocontact with the back plane connectors by leaving a distance of about 2 cm(.75’’), between the module and the back plane.

5. Connect all semi-rigid/flexi cables (use a torque spanner).

6. Insert the prepared module completely.

– Replacement successful h...5– Replacement not successful h...14


h...6




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

iIf there was contact beteen the module and the back plane connectors be-fore all semi-rigid/flexi cables were connected, pull the module again about2 cm (.75’’) out of the rack until it is no longer connected to the back plane.

Was the module replacement successful?All LEDs must signal normal operation (no red LEDs must be on).Call OMC to make sure that the BTSE has gone back to normal operation.

92 A30808-X3247-M326-5-7620







b BSS


BSS-EQUIPMENT

BTSEP

BTSEP:<no>

RACK

RACK:<no>

CU

CU:<no>

LOCK CU


1. Disconnect all semi-rigid/flexi cables.Attention: Mark the normal and the diversity path!






The main purpose of the test is to check the receivers, which cannot be super-vised completely during normal operation. The power amplifier is supervisedduring normal operation. A fault will therefore be detected immediately.



A30808-X3247-M326-5-7620 93



b BSS


BSS-EQUIPMENT

BTSEP

BTSEP:<no>

RACK

RACK:<no>

CU

CU:<no>

PERFTEST CU





b BSS


BSS-EQUIPMENT

BTSEP

BTSEP:<no>

RACK

RACK:<no>

CU

CU:<no>

UNLOCK CU

13 Check LED PA on the CU

– The LED PA is not on h...18– The LED PA is red h...14

Wait a few seconds, until the boot process is finished (green LED:OK and SWare flashing), see HW:BTSE Modules, CU for locating the appropriate moduledescription.

94 A30808-X3247-M326-5-7620





h...15






Call TAC.

18 Update the Remote Inventory Data

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

i....Procedure:3.42




END

A30808-X3247-M326-5-7620 95



3.15 DCBCTRL

In BS-240 II / 240XL II the DCBCTRL is not configured as managed object.

To make DCBCTRL alarms visible, Environmental Alarms have to be configured (seeITMN:BTSE BS-240 / 240 II / 240XL / 240XL II, Creating the Alarm Configuration(ENVABTSE)).



– Module(s) ??

– BTS-no ??

– Rack-no ??



Use the logical address to find the mounting location of the module(s). ...... (see 4.3)





iModule DCBCTRL may be removed while the power is on.


96 A30808-X3247-M326-5-7620





3. Check the module settings against the replaced module, see HW:BTSEModules, DCBCTRL for the appropriate module description.











b BSS


BSS-EQUIPMENT

BTSEP

BTSEP:<no>

RACK

RACK:<no>

ACDCP

ACDCP:<no>

LOCK ACDCP




A30808-X3247-M326-5-7620 97





3. Check the module settings against the replaced module, see HW:BTSEModules, DCBCTRL for the appropriate module description.


9 Run test for replaced (suspected) module

b BSS


BSS-EQUIPMENT

BTSEP

BTSEP:<no>

RACK

RACK:<no>

ACDCP

ACDCP:<no>

PERFTEST ACDCP





b BSS


BSS-EQUIPMENT

BTSEP

BTSEP:<no>

RACK

RACK:<no>

ACDCP

ACDCP:<no>

UNLOCK ACDCP

98 A30808-X3247-M326-5-7620








h...14






Call TAC.

END

A30808-X3247-M326-5-7620 99



3.16 DIAMCO



– Module(s) ??

– BTS-no ??

– Rack-no ??






– VSWR Alarm

– Cable Problem



N h...3

iDILNA

DIDCTMA

This MO of the DIAMCO supplies the RX path. There are two managedobjects of this type per module and they have to be handled separately

There are two managed objects each of this type per module and theyhave to be handled separately. The DIDCTMA offers the DC powersupply for the TMA. It has to be created only if the TMA is installed.

The managed object DILNA must be locked before replacement!DIDCTMA must be locked, only if an TMA is installed!

Note: The DIAMCO- Module contains two DIAMCOs (i.e., togetherfour MOs), which could belong to two different cells!At the replacement of the DIAMCO a functioning cell could break downshort-term!

iModule DIAMCO may be removed while the power is on!

100 A30808-X3247-M326-5-7620







1. Disconnect all semi-rigid/flexi and antenna cables. In certain cases a couplerfor power monitoring may be used. Be careful not to mix up the connectionsfor the input and the monitoring output when reconnecting the cables!



4. Check the DIP Switch settings against the replaced module, see HW:BTSEModules, DIAMCO for locating appropriate module description.

5. Partly insert the prepared module. Make sure that it does not yet come intocontact with the back plane connectors by leaving a distance of about 2 cm(.75’’), between module and backplane.

6. Connect all semi-rigid/flexi and antenna cables (use a torque spanner)


8. The red alarm LEDs must not be on after module insertion!The green LED “OK” is on!If a TMA is connected: the green LED “TMA OK” is on!If LEDs are switched incorrectly, check the antenna connection.

9. Loosen the fastening screws on the corresponding CU.

10. Pull out the corresponding CU about 2 cm (.75’’), without disconnecting thesemi-rigid/flexi cables.

11. Insert the corresponding CU completely.



h...6


iIf there was contact beteen the module and the backplane connectors be-fore all semi-rigid/flexi cables were connected, pull the module again about2 cm (.75’’) out of the rack until it is no longer connected to the backplane.


A30808-X3247-M326-5-7620 101









8 Check whether a TMA is in use or not.

If Switch 1 is in the MUCO position, then the MOs are DIDCTMA and DILNA

If Switch 1 is in the AMCO position, then the MO is DILNA.

9 Lock all of the two objects DILNA and DIDCTMA of the suspected DIAMCO

b BSS


BSS-EQUIPMENT

BTSEP

BTSEP:<no>

RACK

RACK:<no>

<MO>

<MO>:<no>

LOCK <MO>

10 Second DILNA or DIDCTMA object, if created

Are either the DILNA or DIDCTMA objects not yet locked? Y h...9N h...11


Check DIP Switch of suspected DIAMCO, see HW:BTSE Modules, DIAMCO forlocating the appropriate module description.


102 A30808-X3247-M326-5-7620






4. Check the DIP Switch settings against the replaced module, see HW:BTSEModules, DIAMCO for the appropriate module description.


6. Connect all semi-rigid/flexi and antenna cables (use a torque spanner).

7. The red alarm LEDs must not be on after module insertion!The green LED “OK” is on!In case of TMA is connected: the green LED “TMA OK” is on!If LEDs are switched incorrectly: check antenna connection.

12 Run the test for DILNA (and DIDCTMA if necessary) objects of the re-placed module

b BSS


BSS-EQUIPMENT

BTSEP

BTSEP:<no>

RACK

RACK:<no>

<MO>

<MO>:<no>

PERFTEST <MO>

The MO (Managed Object) can be: DILNA or DIDCTMA.



13 Second DILNA or DIDCTMA object, if created

Are either the DILNA or DIDCTMA objects not yet tested? Y h...12N h...14

A30808-X3247-M326-5-7620 103




15 Unlock the DILNA and DIDCTMA objects of the Suspected Module

b BSS


BSS-EQUIPMENT

BTSEP

BTSEP:<no>

RACK

RACK:<no>

<MO>

<MO>:<no>

UNLOCK <MO>

16 Second DILNA and DIDCTMA objects

Are either the DILNA and DIDCTMA objects not yet unlocked? Y h...15N h...17






h...19






Call TAC.

END

104 A30808-X3247-M326-5-7620



A30808-X3247-M326-5-7620 105



3.17 DIDCTMA

1 Go to Procedure h...3.16 "DIAMCO"

END

iDIDCTMA is a functional part of DIAMCO and cannot be replaced separately.

106 A30808-X3247-M326-5-7620



A30808-X3247-M326-5-7620 107



3.18 DILNA

1 Go to Procedure h...3.16 "DIAMCO"

END

iDILNA is a functional part of DIAMCO and cannot be replaced separately.

108 A30808-X3247-M326-5-7620



3.19 DIPLEXER



– Module(s) ??

– BTS-no ??

– Rack-no ??






– VSWR Alarm

– Cable Problem



N h...3




iModule DIPLEXER may be removed while power is on.

iNote for the Quick Module Replacement Procudure:The enabled attribute Autorecovery is not neccessary for the replacement of the mod-ule DIPLEXER, but the activation of this attribute is necessary to guarantee a properinitialisation of the corresponding CUs after their reinsertion.

A30808-X3247-M326-5-7620 109




1. Disconnect all coaxial cables, see HW:BTSE Modules, DIPLEXER for the ap-propriate module description.

2. Loosen the screws of the affected module.

3. Pull the affected module.



6. Attach the prepared module by tightening the screws.

7. Connect all coaxial cables (use a torque spanner).

8. Loosen the fastening screws on all corresponding CU.

9. Pull out all corresponding CU about 2 cm (.75’’) without disconnecting thesemi-rigid/flexi cables.

10. Insert all corresponding CUs completely.



h...6









110 A30808-X3247-M326-5-7620



8 Lock All Relevant CUs

Relevant CUs are all CUs which are connected over FICOM and HPDU to thesuspected DIPLEXER.

b BSS


BSS-EQUIPMENT

BTSEP

BTSEP:<no>

RACK

RACK:<no>

CU

CU:<no>

LOCK CU

9 Next CU

Is there one relevant CU not yet locked? Y h...8N h...10

10 Lock the Relevant TMA

b BSS


BSS-EQUIPMENT

BTSEP

BTSEP:<no>

RACK

RACK:<no>

TMA

TMA:<no>

LOCK TMA

A30808-X3247-M326-5-7620 111



11 Lock the Relevant DIDCTMA

b BSS


BSS-EQUIPMENT

BTSEP

BTSEP:<no>

RACK

RACK:<no>

DIDCTMA

DIDCTMA:<no>

LOCK DIDCTMA

112 A30808-X3247-M326-5-7620




1. Disconnect all coaxial cables, see HW:BTSE Modules, DIPLEXER for the ap-propriate module description.






7. Connect all coaxial cables.

13 Unlock the Relevant DIDCTMA

b BSS


BSS-EQUIPMENT

BTSEP

BTSEP:<no>

RACK

RACK:<no>

DIDCTMA

DIDCTMA:<no>

UNLOCK DIDCTMA

14 Unlock the Relevant TMA

b BSS


BSS-EQUIPMENT

BTSEP

BTSEP:<no>

RACK

RACK:<no>

TMA

TMA:<no>

UNLOCK TMA


A30808-X3247-M326-5-7620 113



15 Unlock All Relevant CUs

b BSS


BSS-EQUIPMENT

BTSEP

BTSEP:<no>

RACK

RACK:<no>

CU

CU:<no>

UNLOCK CU

16 Next CU

Is there one relevant CU not yet unlocked? Y h...15N h...17

17 Check LED PA on all relevant CUs








h...21



Wait a few seconds, until the bootprocess is finished (green LED:OK and SWare flashing), see HW:BTSE Modules, CU for the appropriate module descrip-tion.

114 A30808-X3247-M326-5-7620






Call TAC.

END

A30808-X3247-M326-5-7620 115



3.20 DUAMCO



– Module(s) ??

– BTS-no ??

– Rack-no ??






– VSWR Alarm

– Cable Problem



N h...3




iDULNADUVSWRDUDCTMA

There are three managed objects each of this type per module andthey have to be handled separately.The managed objects DULNA and DUVSWR must be locked beforereplacement! DUDCTMA must be locked, only if an TMA is installed!

iModules may be removed while the power is on.

iThe module DUAMCO may also be an FDUAMCO (Flexible DUAMCO).

116 A30808-X3247-M326-5-7620






3. Select a module with a functional HW / SW state compatible to that of themodule which is being replaced. For information on DUAMCO, FDUAMCOhardware compatibility, refer to HW:BTSE Modules, Tab. “DUAMCO / FDU-AMCO Hardware Compatibility”.

4. Check the DIP Switch settings against the replaced module, see HW:BTSEModules, DUAMCO / FDUAMCO for the appropriate module description.


6. Connect all semi-rigid/flexi and antenna cables (use a torque spanner)..


8. The red alarm LEDs must not be on after module insertion!The green LED “POWER” is on!If the TMA is connected: the green LED “TMA” is on!If LEDs are switched incorrectly, check the antenna connection.






!All DUAMCO / FDUAMCO modules which are used for one cell must havethe same variant.ESD precautions must be taken when pulling and inserting a module. Referto 1.5.1 "ESD Precautions".

iIf there was contact beteen the module and the backplane connectors be-fore all semi-rigid/flexi cables were connected, pull the module again about2 cm (.75’’) out of the rack until it is no longer connected to the backplane.


A30808-X3247-M326-5-7620 117









8 Check whether a TMA is in use or not.

If Switch 1 is in the MUCO position, then the MOs are DULNA, DUVSWR andDUDCTMA.

If Switch 1 is in the AMCO position, then the MOs are DULNA and DUVSWR.

9 Lock the three objects DULNA, DUVSWR and DUDCTMA of both parts ofthe DUAMCO / FDUAMCO

b BSS


BSS-EQUIPMENT

BTSEP

BTSEP:<no>

RACK

RACK:<no>

<MO>

<MO>:<no>

LOCK <MO>

10 Next DULNA, DUVSWR or DUDCTMA object if created

Is one of the DULNA, DUVSWR or DUDCTMA objects not yet locked? Y h...9N h...11


Check DIP Switch of suspected DUAMCO / FDUAMCO (hide behind plate), seeHW:BTSE Modules, DUAMCO / FDUAMCO for locating the appropriate mod-ule description.

!All DUAMCO / FDUAMCO modules which are used for one cell must havethe same variant.ESD precautions must be taken when pulling and inserting a module. Referto 1.5.1 "ESD Precautions".

118 A30808-X3247-M326-5-7620





3. Select a module with a functional HW / SW state compatible to that of themodule which is being replaced. For information on DUAMCO/FDUAMCOhardware compatibility, refer to HW:BTSE Modules, DUAMCO / FDUAMCO .

4. Check the DIP Switch settings against the replaced module, see HW:BTSEModules, DUAMCO / FDUAMCO for the appropriate module description.


6. Connect all semi-rigid/flexi and antenna cables (use a torque spanner).

7. The red alarm LEDs must not be on after module insertion!The green LED “POWER” is on!In case of TMA is connected: the green LED “TMA” is on!If LEDs are switched not correct: check antenna connection

12 Run the test for all DULNA, DUVSWR and DUDCTMA objects of the re-placed module

b BSS


BSS-EQUIPMENT

BTSEP

BTSEP:<no>

RACK

RACK:<no>

<MO>

<MO>:<no>

PERFTEST <MO>

The MO (Managed Object) can be: DULNA; DUVSWR or DUDCTMA.



13 Next DULNA, DUVSWR or DUDCTMA object, if created

Are either the DULNA, DUVSWR or DUDCTMA objects not yet tested? Y h...12N h...14

A30808-X3247-M326-5-7620 119




15 Unlock the DULNA, DUVSWR and DUDCTMA objects of the SuspectedModule

b BSS


BSS-EQUIPMENT

BTSEP

BTSEP:<no>

RACK

RACK:<no>

<MO>

<MO>:<no>

UNLOCK <MO>

16 Next DULNA, DUVSWR and DUDCTMA objects

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



Close the the BTSE door.



h...19





120 A30808-X3247-M326-5-7620




Call TAC.

END

A30808-X3247-M326-5-7620 121



3.21 DUBIAS



– Module(s) ??

– BTS-no ??

– Rack-no ??






– VSWR Alarm

– Cable Problem



N h...3




iModule DUBIAS may be removed while power is on.

122 A30808-X3247-M326-5-7620




Relevant CUs are all CUs which are connected over FICOM and HPDU to thesuspected DUBIAS.

b BSS


BSS-EQUIPMENT

BTSEP

BTSEP:<no>

RACK

RACK:<no>

CU

CU:<no>

LOCK CU

5 Next CU



b BSS


BSS-EQUIPMENT

BTSEP

BTSEP:<no>

RACK

RACK:<no>

TMA

TMA:<no>

LOCK TMA

A30808-X3247-M326-5-7620 123




b BSS


BSS-EQUIPMENT

BTSEP

BTSEP:<no>

RACK

RACK:<no>

DIDCTMA

DIDCTMA:<no>

LOCK DIDCTMA

124 A30808-X3247-M326-5-7620




1. Disconnect all coaxial cables, see HW:BTSE Modules, DUBIAS for the ap-propriate module description.






7. Connect all coaxial cables.


b BSS


BSS-EQUIPMENT

BTSEP

BTSEP:<no>

RACK

RACK:<no>

DIDCTMA

DIDCTMA:<no>

UNLOCK DIDCTMA


b BSS


BSS-EQUIPMENT

BTSEP

BTSEP:<no>

RACK

RACK:<no>

TMA

TMA:<no>

UNLOCK TMA


A30808-X3247-M326-5-7620 125




b BSS


BSS-EQUIPMENT

BTSEP

BTSEP:<no>

RACK

RACK:<no>

CU

CU:<no>

UNLOCK CU

12 Next CU







h...Procedure: 3.42






h...18


126 A30808-X3247-M326-5-7620








Call TAC.

END

A30808-X3247-M326-5-7620 127



3.22 DUDCTMA

1 Go to Procedure h...3.20 "DUAMCO"

END

iDUDCTMA is a functional part of DUAMCO / FDUAMCO and cannot be replaced sep-arately.

128 A30808-X3247-M326-5-7620



A30808-X3247-M326-5-7620 129



3.23 DULNA


END

iDULNA is a functional part of DUAMCO / FDUAMCO and cannot be replaced separate-ly.

130 A30808-X3247-M326-5-7620



A30808-X3247-M326-5-7620 131



3.24 ECU

1 Go to Procedure h...3.14 "CU"

END

iECU is a Carrier Unit for the EDGE technology.

132 A30808-X3247-M326-5-7620



3.25 FAN



– Module(s) ??

– BTS-no ??

– Rack-no ??








b BSS


BSS-EQUIPMENT

BTSEP

BTSEP:<no>

RACK

RACK:<no>

FANP

FANP:<no>

LOCK FANP


iModule FAN may be removed while power is on.


A30808-X3247-M326-5-7620 133



1. Remove the affected module (press the two levers up)see HW:BTSE Mod-ules, FAN for the appropriate module description.

2. Insert the new module.


b BSS


BSS-EQUIPMENT

BTSEP

BTSEP:<no>

RACK

RACK:<no>

FANP

FANP:<no>

PERFTEST FANP






h...Procedure: 3.42

!Caution when pulling out the FAN. After the switch off, the rotor is stillrunning for a few seconds. Watch your fingers!

134 A30808-X3247-M326-5-7620




b BSS


BSS-EQUIPMENT

BTSEP

BTSEP:<no>

RACK

RACK:<no>

FANP

FANP:<no>

UNLOCK FANP





h...11






Call TAC.

END

A30808-X3247-M326-5-7620 135



3.26 FlexCU

The FlexCU is a complete two-carrier unit with standard CU footprint. The HMOFCUMAIN (Flexible Carrier Unit MAIN Part) represents the part of the Flexible CarrierUnit which is common to both carriers in a FlexCU.

This procedure covers the fault messages FCUMAIN and FCUTR.

The module CU may be removed while power is on.



– Module(s) ??

– BTS-no ??

– Rack-no ??




!WarningThese modules are equipped with electrostatically sensitive components and aresusceptible to damage by electrostatic discharge. Follow ESD precautions when re-moving and inserting modules. Refer to Chapter 1.5 "Module Replacement Instruc-tions".

iImportantAvoid the loss of calls.If you lock or remove modules in the TX/RX path of the BTSE, calls may be lost.To avoid the loss of calls, please follow the instructions in Chapter 1.5.2 "Avoiding theLoss of Calls".

iImportantAvoid reduced quality.In case of locking a CU in a cell with enabled Antenna Hopping, the concerned CU isblocked at once but Antenna Hopping is blocked only after 9.6 s. During this time thequality is reduced.To avoid this, switch off Antenna Hopping before locking the CU.

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

136 A30808-X3247-M326-5-7620





– VSWR Alarm

– Cable Problem



N h...3

3 Autorecovery (EAUTOREC) Enabled?



A30808-X3247-M326-5-7620 137




1. Disconnect all semi-rigid/flexi cables. Attention: Mark all normal- and alldiversity- paths!


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

4. Partly insert the prepared module. Make sure that it does not yet come intocontact with the back plane connectors by leaving a distance of about 2 cm(.75’’) , between module and back plane.

5. Connect all semi-rigid/flexi cables (use a torque spanner)







Plug the LMT cable into the corresponding socket. ...... (see 4.4)



iIf there was contact between the module and the back plane connectorsbefore all semi-rigid/flexi cables were connected, pull the module about 2 cm(.75’’) out of the rack again until it is no longer connected to the back plane.


138 A30808-X3247-M326-5-7620



8 Lock FCUMAIN of the Suspected Module

b BSS


BSS-EQUIPMENT

BTSEP

BTSEP:<no>

RACK

RACK:<no>

FCUMAIN

FCUMAIN:<no>

LOCK FCUMAIN

9 Lock FCUTR(s) of the Suspected Module

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

b BSS


BSS-EQUIPMENT

BTSEP

BTSEP:<no>

RACK

RACK:<no>

FCUTR

FCUTR:<no>

LOCK FCUTR

Repeat this command for the second FCUTR if created.


1. Disconnect all semi-rigid/flexi cables. Attention: Mark all normal and all di-versity paths!






A30808-X3247-M326-5-7620 139



11 Run Test for FCUMAIN of the Replaced Module

The main purpose of the test is to check the receivers, which cannot be super-vised completely during normal operation. The poweramplifier is supervisedduring normal operation, so a fault will be detected immediately.

b BSS


BSS-EQUIPMENT

BTSEP

BTSEP:<no>

RACK

RACK:<no>

FCUMAIN

FCUMAIN:<no>

PERFTEST FCUMAIN




13 Unlock FCUMAIN of the Suspected Module

b BSS


BSS-EQUIPMENT

BTSEP

BTSEP:<no>

RACK

RACK:<no>

FCUMAIN

FCUMAIN:<no>

UNLOCK FCUMAIN

140 A30808-X3247-M326-5-7620



14 Run Test for the Even Numbered FCUTR of the Replaced Module

If two FCUTRs are created per module and the FlexCU operates in the4RxTxDiv mode, the even-numbered instance of the FCUTR (master) may af-fect the behavior of the odd-numbered FCUTR (slave) during the test. In orderto avoid this, the even-numbered FCUTR must be in the state “enabled” beforethe odd-numbered FCUTR is tested. Therefore, the even-numbered FCUTRmust be tested prior to the odd-numbered one.

b BSS


BSS-EQUIPMENT

BTSEP

BTSEP:<no>

RACK

RACK:<no>

FCUTR

FCUTR:<no 2k>

PERFTEST FCUTR

The test outcome can be examined in the “Message Viewer” window. If the testoutcome is “fail”, more information is given such as “Proposed Repair Action”etc.

15 Unlock Even Numbered FCUTR of the Replaced Module

b BSS


BSS-EQUIPMENT

BTSEP

BTSEP:<no>

RACK

RACK:<no>

FCUTR

FCUTR:<no 2k>

UNLOCK FCUTR

16 Run Test for the Odd Numbered FCUTR of the Replaced Module (ifcreated)



A30808-X3247-M326-5-7620 141



b BSS


BSS-EQUIPMENT

BTSEP

BTSEP:<no>

RACK

RACK:<no>

FCUTR

FCUTR:<no 2k+1>

PERFTEST FCUTR

The test outcome can be examined in the “Message Viewer” window. If the testoutcome is “fail”, more information is given such as “Proposed Repair Action”etc.

17 Unlock Odd Numbered FCUTR of the Replaced Module (if created)

b BSS


BSS-EQUIPMENT

BTSEP

BTSEP:<no>

RACK

RACK:<no>

FCUTR

FCUTR:<no 2k+1>

UNLOCK FCUTR

18 Check LED PA on the FlexCU




h...20

Wait a few seconds, until the bootprocess is finished (green LED:OK and SWare flashing), see HW:BTSE Modules, FlexCU for the appropriate module de-scription.

142 A30808-X3247-M326-5-7620



20 Another Probable Cause?

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

21 Fault Clearance Procedure for the Next Suspected Module/Interface

Go to the fault clearance procedure for the next suspected module/interface. h...Procedure: 3.x


Call TAC.

23 Update the Remote Inventory Data

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

i....Procedure:3.42

24 Prepare End of Fault Clearance



END

A30808-X3247-M326-5-7620 143



3.27 FCUMAIN

1 Go to Procedure h...3.26 "FlexCU"

END

iFCUMAIN is a functional part of the FlexCU.

144 A30808-X3247-M326-5-7620



A30808-X3247-M326-5-7620 145



3.28 FCUTR

1 Go to Procedure h...3.26 "FlexCU"

END

iFCUTR is a functional part of the FlexCU.

146 A30808-X3247-M326-5-7620



A30808-X3247-M326-5-7620 147



3.29 FDUAMCO


END

iThe FDUAMCOis a flexible DUAMCO, it is switchable from 2:2 to 4:2 configuration.

148 A30808-X3247-M326-5-7620



3.30 FICOM



– Module(s) ??

– BTS-no ??

– Rack-no ??






– VSWR Alarm

– Cable Problem



N h...3




iFVSWRP

FTNFP

Is one of the two managed objects of the FICOM and it occurs onlyonce per Base module (not in Expansion modules).

There are two managed objects, of this type, per module and theyhave to be handled separately.

All managed objects must be locked before replacement!

iModules may be removed while power is on.

A30808-X3247-M326-5-7620 149




1. Disconnect all semi-rigid/flexi and antenna cables and all expansion cables(between the different modules) from the suspected module. In certain casesa coupler for power monitoring may be used. Be careful not to mix up the con-nections for the input and the monitoring output when reconnecting the ca-bles!

2. Pull the affected module.



5. Connect all semi-rigid/flexi and antenna cables and all expansion cables (be-tween the different modules) (use a torque spanner).


7. The alarm LEDs must not be on after module insertion! If the LED is on,check the antenna connection.




– Replacement successful h...5– Replacement unsuccessful h...20


h...6




!All FICOM modules which are used for one cell must have the same variant.ESD precautions must be taken when pulling and inserting a module. Referto 1.5.1 "ESD Precautions".

iIf there was contact between the module and the backplane connectorsbefore all semi-rigid/flexi and antenna cables were connected, pull the mod-ule about 2 cm (.75’’) out of the rack again until it is no longer connected tothe backplane.


150 A30808-X3247-M326-5-7620






8 Lock the FVSWRP object of the Suspected Module, if it is a Base module

b BSS


BSS-EQUIPMENT

BTSEP

BTSEP:<no>

RACK

RACK:<no>

FVSWRP

FVSWRP:<no>

LOCK FVSWRP

9 Lock the FTNFP objects of the Suspected Module and all FTNFP objectsbehind them

b BSS


BSS-EQUIPMENT

BTSEP

BTSEP:<no>

RACK

RACK:<no>

FTNFP

FTNFP:<no>

LOCK FTNFP

10 Second FTNFP object

Is there a second FTNFP object created and not locked? Y h...9N h...11


!All FICOM modules which are used for one cell must have the same variant.ESD precautions must be taken when pulling and inserting a module. Referto 1.5 "Module Replacement Instructions".

A30808-X3247-M326-5-7620 151



1. Disconnect all semi-rigid/flexi and antenna cables and all expansion cables(between the different modules) from the suspected module. In certain casesa coupler for power monitoring may be used. Be careful not to mix up theconnections for the input and the monitoring output when reconnecting thecables!




5. Connect all semi-rigid/flexi, antenna, and expansion cables between thedifferent modules (use a torque spanner).

6. The alarm LEDs must not be on after module insertion! If LED is on: checkantenna connection.

12 Run the test for FVSWRP object of the replaced module, if it is a Basemodule

b BSS


BSS-EQUIPMENT

BTSEP

BTSEP:<no>

RACK

RACK:<no>

FVSWRP

FVSWRP:<no>

PERFTEST FVSWRP



152 A30808-X3247-M326-5-7620



13 Run the test for FTNFP objects of the replaced module

b BSS


BSS-EQUIPMENT

BTSEP

BTSEP:<no>

RACK

RACK:<no>

FTNFP

FTNFP:<no>

PERFTEST FTNFP




Is there a second FTNFP object to be tested? Y h...13N h...15


16 Unlock the FVSWRP object of the Suspected Module, if it is a Base module

b BSS


BSS-EQUIPMENT

BTSEP

BTSEP:<no>

RACK

RACK:<no>

FVSWRP

FVSWRP:<no>

UNLOCK FVSWRP

A30808-X3247-M326-5-7620 153



17 Unlock all FTNFP objects

b BSS


BSS-EQUIPMENT

BTSEP

BTSEP:<no>

RACK

RACK:<no>

FTNFP

FTNFP:<no>

UNLOCK FTNFP


Has a second FTNFP object been created and not unlocked? Y h...17N h...19






h...21






Call TAC.

END

154 A30808-X3247-M326-5-7620



3.31 Filtermat

The filter mat must be changed annually.

In a very dirty environment the mat must be changed semi-annually.

1 Replacement

1. Hang out the spring bar and pull out the mat (see Fig. 4.1).

2. Select a new filtermat with the same characteristics.

3. Insert the new mat and hang in the spring bar.

2 End of procedure


END

A30808-X3247-M326-5-7620 155



3.32 FTNFP

1 Go to Procedure h...3.30 "FICOM"

END

iFTNFP is a functional part of FICOM and cannot be replaced separately.

156 A30808-X3247-M326-5-7620



A30808-X3247-M326-5-7620 157



3.33 FVSWRP

1 Go to Procedure h...3.30 "FICOM"

END

iFVSWRP is a functional part of FICOM and cannot be replaced separately.

158 A30808-X3247-M326-5-7620



A30808-X3247-M326-5-7620 159



3.34 GCU

1 Go to Procedure h...3.14 "CU"

END

iGCU is a Carrier Unit for the GMSK technology only.

160 A30808-X3247-M326-5-7620



3.35 HPDU



– Module(s) ??

– BTS-no ??

– Rack-no ??






– VSWR Alarm

– Cable Problem



N h...3




iModule HPDU may be removed while power is on.

A30808-X3247-M326-5-7620 161




Relevant CUs are all CUs which are connected over FICOM to the suspectedHPDU.

b BSS


BSS-EQUIPMENT

BTSEP

BTSEP:<no>

RACK

RACK:<no>

CU

CU:<no>

LOCK CU

5 Next CU



b BSS


BSS-EQUIPMENT

BTSEP

BTSEP:<no>

RACK

RACK:<no>

TMA

TMA:<no>

LOCK TMA

162 A30808-X3247-M326-5-7620




b BSS


BSS-EQUIPMENT

BTSEP

BTSEP:<no>

RACK

RACK:<no>

DIDCTMA

DIDCTMA:<no>

LOCK DIDCTMA

A30808-X3247-M326-5-7620 163




1. Disconnect all coaxial cables, see HW:BTSE Modules, HPDU for locating theappropriate module description.






7. Connect all Coaxial cables .


b BSS


BSS-EQUIPMENT

BTSEP

BTSEP:<no>

RACK

RACK:<no>

DIDCTMA

DIDCTMA:<no>

UNLOCK DIDCTMA


b BSS


BSS-EQUIPMENT

BTSEP

BTSEP:<no>

RACK

RACK:<no>

TMA

TMA:<no>

UNLOCK TMA


164 A30808-X3247-M326-5-7620




b BSS


BSS-EQUIPMENT

BTSEP

BTSEP:<no>

RACK

RACK:<no>

CU

CU:<no>

UNLOCK CU

12 Next CU



– The LED PA is not on h...14– The LED PA is on h...17




h...Procedure: 3.42






h...18


A30808-X3247-M326-5-7620 165








Call TAC.

END

166 A30808-X3247-M326-5-7620



A30808-X3247-M326-5-7620 167



3.36 LAPDLE


END

iThis error message indicates a problem with the connection to the BSC.

168 A30808-X3247-M326-5-7620



3.37 OVPT

This fault clearance procedure also applies to the optional module “ABISCON”.



– Module(s) ??

– BTS-no ??

– Rack-no ??







3 Lock BTS site manager

b BSS


BSS-FUNCTIONAL

BTSM

BTSM:<no>

LOCKREQUEST BTSM

iModule OVPT may be removed while power is on.

iModule OVPT is the interface module between the BSC and the BTSE (for the outdoorversions in common with WAVEs,NTs or CSUs). Therefore, if a failure of the Abis linkis reported, the OVPT must be considered.

!When the OVPT fails, the PCM-line is also broken for all subsequent BTSE in the eventof a multidrop configuration.

A30808-X3247-M326-5-7620 169



4 Disconnect BTS site manager from BSC / switch Phase 3 to Phase 2

b BSS


BSS-FUNCTIONAL

BTSM

BTSM:<no>

DISCBSC BTSM

5 Logon


UserName:<user>

Password:<password>

Ok

The BTSE is now in phase 2.


1. Disconnect all cables from terminal block or coaxial connectors and note theirpositions, see HW:BTSE Modules, OVPT for the appropriate module descrip-tion.

2. Dismantle all cables from clamping saddle.






8. Connect all cables to terminal block or coaxial connectors, use your notes.

7 Check Modules visually

Check modules WAVEs, NTs or CSUs if existent or the connection to the BSCfor WAVEs, NTs or CSUs, see OEM manuals, for BSC: MMN:BSC).



170 A30808-X3247-M326-5-7620



9 Start the connection to the BSC / switch from Phase 2 to Phase 3

b BSS


BSS-FUNCTIONAL

BTSM

BTSM:<no>

CONNBSC BTSM

10 Logon


UserName:<user>

Password:<password>

Ok

The BTSE is now in phase 3.






h...13






Call TAC.

END

A30808-X3247-M326-5-7620 171



3.38 PCM Line


END

iPCM Line errors are reported via the object Abis.

172 A30808-X3247-M326-5-7620



A30808-X3247-M326-5-7620 173



3.39 Rectifier

1 Go to Procedure h...3.3 "AC/DC"

END

iThe rectifier is a functional part of AC/DC and cannot be replaced separately.

174 A30808-X3247-M326-5-7620



A30808-X3247-M326-5-7620 175



3.40 Remote Inventory Data Creation

After replacing the module COBA, it is necessary to rebuild the inventory data that wasstored on the removed COBA. Usually, a backup IDF file is available for this purpose,which is stored on site with the site specific documentation. The following procedure de-scribes how to enter the data by hand if there is no backup IDF file.



Fig. 3.10 Flow Chart for Remote Inventory Data Creation

Remote InventoryData Exportfor Backup

IDF EvolutionStart

nob_RIU FileExport

6

7

5

4

3

2

Steps

Downloadnob_RIU to BTSE

Remote InventoryData Creation Fin-

IDF

IDF

IDF

IDF

IDF

LMT

Upload IDF Filefrom BTSE

1

8

LMT

Remote InventoryData Creation

from nob_RIU units

IDT FileOpen

176 A30808-X3247-M326-5-7620




1 Upload IDT File from the BTSE

b BSS


BSS-EQUIPMENT

BTSEP

BTSEP<no>

REMINV

REMINV<no>

UPLLIDF REMINV

(DESTDIR=<path>)

(FILE=<file name>)

OVERWRITE=YES

Additional Information: The attributes DESTDIR and FILE are optional. If nospecial path or file name is entered, the file is uploaded to the default directoryof the IDF Evolution. If the attribute OVERWRITE=<yes> is selected, a formerversion of an uploaded IDT file will be overwritten.


b To start the IDF Evolution select “IDF GSM” -> “IDF Editor” from the Windowsprogram menu.

Step Information

1 The remote inventory data that is stored in the BTSE as IDT file must be up-loaded to the LMT PC. This file contains the remote inventory data of theob_RIU modules.

4 The data can be entered manually or automatically via the 2D-Code Reader.

5 An IDF file for backup must be created.

6 The nob_RIU data must be attached to the remote inventory data stored inthe BTSE (IDT file). In order to attach the nob_RIU data to the IDT file, theymust be exported into a NOB file.

Tab. 3.7 Additional Information for Remote Inventory Data Creation

A30808-X3247-M326-5-7620 177



3 Open IDT File

b To open the IDT file:

1. Select “File” -> "Open" from the menu.

2. Select the uploaded file from the list in the appearing window; e.g.:<C:...\LMT<version>\Idf\Upload\BTSE.idt>.

3. Double-click on the file name or click on the "Open" button.

4 Create the Remote Inventory Data of the nob_RIU Units

b To create the Remote Inventory Data of the nob_RIU units:

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

2. Click on the appearing “Create” button.

3. Select the network entity type (“Ney Type”), the Functional Address and Typeof the module you want to create (“FunctionalAddress:FunctionalAd-dressType”), and the equipment position (“SBS_Equipment_Position”).

4. Click on the “Inventory” button.

5. A pop-up window opens in which you can enter the data by hand, or click onthe “Scan” button to use the 2D-Code Reader.

6. If the 2D-Code Reader is used for the first time, select the serial port in theappearing window.

7. To start the scanning process, press the button on the 2D-Code Reader. Thedata will be inserted into the corresponding fields.

8. Confirm the data by clicking on the “OK” button.

9. Select “File” -> “Save” from the menu.

10. Repeat these steps for the next module you want to create.

5 Export Remote Inventory Data for Backup

b To export the Remote Inventory data for backup:


2. Select the destination path in the appearing window, preferably “A:\”. The filename is automatically composed of the “SalesUniqueName” with the exten-sion “.idf”.


4. Put the disk with the backup file of the inventory data to the site specific doc-umentation.

178 A30808-X3247-M326-5-7620



6 Export Nob_RIU Data


1. Select “Export” -> “NOB” from the menu.

2. A window opens in which you can edit the file name and select the directoryin which the file is saved. By default, the file name is composed of the “Sale-sUniqueName” with the extension “.nob”. Edit the file name and select thesource directory or confirm the default name and directory by clicking on the“Save” button.


4. A question window is displayed: “Create BTS_NRIU for download?” Confirmby clicking on the “Yes” button. An attention window is displayed that informsyou on the destination path and file name to which the BTS_NRIU downloadis saved. Confirm by clicking on the “OK” button.

7 Download the nob_RIU File to the BTSE

Change to the LMT evolution window.

b BSS


BSS-EQUIPMENT

BTSEP

BTSEP<no>

REMINV

REMINV:<no>

DNLIDFD REMINV

SRCDIR=<source directory> (see below)

SRCDIR: enter the source directory in which the exported NOB file was saved.

8 Finish Remote Inventory Data Creation

Return to the corresponding procedure. h...“Procedure 3.x”

END

A30808-X3247-M326-5-7620 179



3.41 Remote Inventory Data Restoration



iIt is necessary to rebuild the inventory data that was stored on the removed COBA us-ing a backup IDF file. Usually, a backup of the IDF is stored on site with the site specif-ic information. If there is no backup file, the data can be extracted from the BSC IDF filevia TAC, or can be restored manually.

180 A30808-X3247-M326-5-7620



Fig. 3.11 Flow Chart for Remote Inventory Data Restoration

On-site Backup FileCopy to LMT PC

nob_RIU to BTSEDownload

IDF FileOpen

nob_RIU FileExport

IDF EvolutionStart

Upload IDF Filefrom BTSE

9

11

10

8

7

6

5

Steps

2Manual nob_RIUs

CreationIDF filesfrom TAC

Uploaded FileOpen

IDF File Exportfor Backup

Return toCOBA Replacement

Procedure

IDF

LMT

IDF

IDF

LMT

IDF

IDF

3 4

Remote InventoryData Availability?

1

12

Procedure3.38

A30808-X3247-M326-5-7620 181





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

2 Create all nob_RIUs manually

For the creation of the inventory data for all nob_RIUs, refer to procedure ... ......3.40 "RemoteInventory DataCreation"

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

3 Extract BTSE Data from BSC IDF

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

Continue with step.. h...5

4 Copy IDF File to LMT PC

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


b To start the IDF Evolution select “IDF GSM” -> “IDF Editor” from the Windowsprogram menu.

6 Open IDF File

b To open the IDF file:

1. Select “File” -> “Open” from the menu of the IDF Evolution.

2. Enter path and file name of the IDF file or select the file from the list in theappearing window.

3. Double-click on the file name or click on the “Open” button after selecting thefile name.

Step Information

7 Only the nob_RIU part has to be exported for the download to the BTSE.

9 The Remote Inventory Data that are stored in the BTSE (IDT file) must beuploaded to the LMT PC in order to create an up-to-date IDF file for backup.

Tab. 3.8 Additional Information for Remote Inventory Data Restoration

182 A30808-X3247-M326-5-7620



7 Export nob_RIU File


1. Select “Export” > “NOB” from the menu of the IDF Evolution.

2. A window opens in which you can edit the file name and select the directoryin which the file is saved. By default, the file name is composed of the “SalesUniqueName” with the extension “.nob”. Edit the file name and select thesource directory or confirm the default name and directory by clicking on the“Save” button.


4. A question window is displayed: “Create BTS_NRIU for download?” Click onthe “Yes” button.

8 Download nob_RIU File to BTSE


b BSS


BSS-EQUIPMENT

BTSEP

BTSEP:<no>

REMINV

REMINV:<no>

DNLIDFD REMINV

SRCDIR=<source directory>

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

A30808-X3247-M326-5-7620 183




b BSS


BSS-EQUIPMENT

BTSEP

BTSEP:<no>

REMINV

REMINV:<no>

UPLLIDF REMINV

DESTDIR=<path>

FILE=<file name>

OVERWRITE=YES

Additional Information: The attributes DESTDIR and FILE are optional. If nospecial path or file name is entered, the file is uploaded to the default directory:C:\...\LMT<version>\IDF\upload,OVERWRITE=<yes> of the IDF Evolution. If theattribute OVERWRITE=<yes> is selected, a former version of an uploaded IDTfile will be overwritten.

10 Open the Uploaded File

Change to the IDF Evolution main window.

b Open the uploaded file:

– Select “File” -> “Open” in the 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.

11 Export IDF File for Backup

Now you must create an IDF file for backup.

b To export the Remote Inventory Data for backup:





12 Finish Remote Inventory Data Restoration

Return to the according COBA replacement procedure.

END

184 A30808-X3247-M326-5-7620



3.42 Remote Inventory Data Update

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


A flow chart of the procedure is given for a better overview. Comments to the steps areincluded after the flow chart, followed by the steps in detail.

Fig. 3.12 Flow Chart for Remote Inventory Data Update

Download nob_RIUto BTSE

IDT fileOpen

Export nob_RIUfile

IDF EvolutionStart

Upload IDT filefrom BTSE

6

8

7

5

4

3

2

Steps


IDF

LMT

IDF

IDF

LMT

Remote InventoryData Editing

IDF

Remote InventoryData Export

IDF

Fault ClearanceProcedure Start

1

A30808-X3247-M326-5-7620 185




1 Upload IDT-File from BTSE

b BSS


BSS-EQUIPMENT

BTSEP

BTSEP<no>

REMINV

REMINV<no>

UPLLIDF REMINV

(DESTDIR=<path>)

(FILE=<file name>)

OVERWRITE=YES


b To start the IDF Evolution select “IDF GSM ” -> “IDF Editor” from the Windowsprogram menu.

Step Information

1 The remote inventory data must be uploaded to the LMT PC.

5 An IDF file for backup must be created. This IDF file replaces the IDF filedelivered with the rack. It contains the modified data of the BTSE.

6 The nob_RIU data must be downloaded to the BTSE. In order to downloadthem, you must export the nob_RIU data again into a NOB file.

Tab. 3.9 Additional Information for Remote Inventory Data Update

The attributes DESTDIR and FILE are optional. If no special path or file name isentered, the file is uploaded to the default directory: C:\...\LMT<ver-sion>\IDF\upload,OVERWRITE=<yes> of the IDF Evolution.If the value OVERWRITE=<yes> is selected, a former version of an uploadedIDT-file will be overwritten.

186 A30808-X3247-M326-5-7620



3 Open IDT File

b To open the IDT file:

1. Select “File” -> "Open" from the menu.

2. Select the uploaded file from the list in the appearing window; e.g.:<C:...\LMT<version>\Idf\Upload\BTSE.idt>.

3. Double-click on the file name or click on the "Open" button.

4. Select “View” -> “nob_RIUs” from the menu to get a list of all nob_RIUs.

4 Edit Remote Inventory Data of the Replaced nob_RIU Unit

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

The data can be edited manually or automatically via the 2D-Code Reader.

b To edit the Remote Inventory Data of the nob_RIU units:

1. Select the I-Record Inventory Data of the unit you need to edit and click theright mouse button.

2. Click on the appearing “Edit” button.

3. Edit the data manually, or click on the “Scan” button to use the 2D-CodeReader.

4. If the 2D-Code Reader is used for the first time, select the serial port in theappearing window.

5. To start the scanning process, press the button on the 2D-Code Reader.

6. The data are inserted into the corresponding fields.Confirm the data byclicking on the “OK” button.

7. Select “File” -> “Save” from the menu.

5 Export Remote Inventory Data for Backup

b To export the Remote Inventory data for backup:

1. Select “Export” > "IDF" from the menu.




A30808-X3247-M326-5-7620 187



6 Export Nob_RIU Data


1. Select “Export” -> “NOB” from the menu.

2. A window opens in which you can edit the file name and select the directoryin which the file is saved. By default, the file name is composed of the“SalesUniqueName” with the extension “.nob”. Edit the file name and selectthe source directory or confirm the default name and directory by clicking onthe “Save” button.


4. A question window is displayed: “Create BTS_NRIU for download?” Confirmby clicking on the “Yes” button. An attention window is displayed that informsyou on the destination path and file name to which the BTS_NRIU downloadis saved. Confirm by clicking on the “OK” button.

7 Download the nob_RIU File to the BTSE


b BSS


BSS-EQUIPMENT

BTSEP

BTSEP:<no>

REMINV

REMINV:<no>

DNLIDFD REMINV

SRCDIR=<source directory> (see below)

SRCDIR: enter the source directory in which the exported NOB file was saved.

8 Finish Fault Clearance




END

188 A30808-X3247-M326-5-7620



3.43 TMA



– Module(s) ??

– BTS-no ??

– Rack-no ??






– VSWR Alarm

– Cable Problem



N h...3




iModule TMA may be removed while power is on.

A30808-X3247-M326-5-7620 189




Relevant CUs are all CUs which are connected over FICOM/DUAMCO /FDUAMCO to an antenna at the same mast of the suspected TMA.

b BSS


BSS-EQUIPMENT

BTSEP

BTSEP:<no>

RACK

RACK:<no>

CU

CU:<no>

LOCK CU

5 Next CU



b BSS


BSS-EQUIPMENT

BTSEP

BTSEP:<no>

RACK

RACK:<no>

TMA

TMA:<no>

LOCK TMA



190 A30808-X3247-M326-5-7620



1. Disconnect all Coaxial cables, see HW:BTSE Modules, TMA for the appro-priate module description.

2. Unmount the affected TMA.


4. Mount the TMA.

5. Connect all cables .

6. Check correct connection to BTSE and antenna.


b BSS


BSS-EQUIPMENT

BTSEP

BTSEP:<no>

RACK

RACK:<no>

TMA

TMA:<no>

PERFTEST TMA




b BSS


BSS-EQUIPMENT

BTSEP

BTSEP:<no>

RACK

RACK:<no>

TMA

TMA:<no>

UNLOCK TMA

A30808-X3247-M326-5-7620 191




b BSS


BSS-EQUIPMENT

BTSEP

BTSEP:<no>

RACK

RACK:<no>

CU

CU:<no>

UNLOCK CU

11 Next CU







h...Procedure: 3.42






h...17


192 A30808-X3247-M326-5-7620








Call TAC.

END

A30808-X3247-M326-5-7620 193



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

Examples for Alarms in the TX/RX Path

RF power reflected into power stage

Cell 0,1,2: Antenna System TX

FICOM_VSWRP: VSWR alarm Low or High

DUAMCO (FDUAMCO, COAMCO): RX alarm Low or High

DIAMCO: RX alarm Low or High

TMA: RX alarm Low or High

1 Cable connections fastened correctly?

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

2 Fasten cable connections

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

3 Check the LED VSWR or ALARM on the Suspected Module

Do the LED switch off after a few seconds? Y h...4N h...6

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 inthe fault message. Afterwards - if the error is still there - to take the other modules inthe TX/RX path into consideration.

iTo make sure that no calls are lost, check whether the corresponding TRX is shutdown before cables/modules are disconnected. If the TRX is still in use, call the OMCto have it shut down. For more information, refer to 1.5.2 "Avoiding the Loss of Calls".

iNo specific alarm exists for a defective COAMCO module. Check the LEDs POWER /ALARM at the COAMCO module. Red LED lights signal a defective COAMCO module.

194 A30808-X3247-M326-5-7620



4 Check the LEDs OK and SW on CU

Do the LEDs switch to on after a few seconds? Y h...5N h...6

5 Additional check only if an LMT is present, otherwise continue with thenext StepGet active alarms

b BSS


BSS-EQUIPMENT

BTSEP

BTSEP<no>

GETACTIVEALARMS BTSEP

Look at the LMT browser window.

Does the alarm still appear? Y h...6N h...7

6 Return to 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.

Besides the modules mentioned previously in this procedure, the Diplexer,DUBIAS, HPDU and antenna can be additional suspected modules for alarmsregarding the TX/RX path.

h...Procedure: 3.x

7 Prepare end of fault clearance


END

A30808-X3247-M326-5-7620 195



4 Tables, Lists and Figures

196 A30808-X3247-M326-5-7620



A30808-X3247-M326-5-7620 197



4.1 Hardware Architecture

Fig. 4.1 BS-240 II

spring bars

198 A30808-X3247-M326-5-7620



Fig. 4.2 BS-240XL

A30808-X3247-M326-5-7620 199



Fig. 4.3 Functional Blocks for BS-240 and BS-240 II

200 A30808-X3247-M326-5-7620



Fig. 4.4 Functional Blocks for BS-240XL and BS-240XL II

A30808-X3247-M326-5-7620 201



Fig. 4.5 Functional Blocks of BS-240XL and BS-240XL II Base Rack with COBA4P12 and COREXT Modules

iNote: The functional blocks shown in Figures 4.3, 4.4, and 4.5 above have to be con-sidered as examples only. They show the logical connections of the modules but nottheir accurate number.The diagram in Figure 4.5 is valid for the BS-240 XL and the BS-240 XL II .The BS-240 and the BS-240 II each holds up to 8 CUs per rack, the BS-240 XL andthe BS-240 XL II each holds up to 12 CUs per rack.

202 A30808-X3247-M326-5-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).

For setting the correct rack number, please refer to the Hardware Manual (see HW:BT-SE Modules, ACTP).

A30808-X3247-M326-5-7620 203



4.3 Front View of the BS-240 Rack

Fig. 4.6 BS-240 Base Rack Design and Configuration (example)

LMTDCP OVPT

CO

BA

0

CO

BA

1C

OS

A0

CO

SA

1

BS-240

HPDU#0 HPDU#1

FANP 0 FANP 1

FANP 2 FANP 3

FANP 4 FANP 5

DIA

MC

O 0

DIA

MC

O 1

With core redundancy:The active COBA andCOSA can be the leftpair or the right pair. Theleft pair is always COBA0 and COSA 0, the rightpair is COBA 1 andCOSA 1, independent onthe status.

CU

1/ F

lexC

U 1

CU

0/ F

lexC

U 0

CU

4/ F

lexC

U 4

CU

5/ F

lexC

U 5

(F)D

UA

MC

O 0

FIC

OM

0or

CO

AM

CO

0

(F)D

UA

MC

O 1

FIC

OM

1or

CO

AM

CO

1

(F)D

UA

MC

O 2

FIC

OM

2or

CO

AM

CO

2

(F)D

UA

MC

O 3

FIC

OM

3or

CO

AM

CO

3

CU

6/ F

lexC

U 6

CU

7/ F

lexC

U 7

CU

2/ F

lexC

U 2

CU

3/ F

lexC

U 3

Hardware ManagedObjects (HMO) areshown in Tab. 4.1(FlexCU), Tab. 4.2(ACOM) andTab. 4.3 (MUCO).

204 A30808-X3247-M326-5-7620



Fig. 4.7 BS-240 Extension Rack Design and Configuration (example)

DCP

BS-240

HPDU#0 HPDU#1

FANP 0 FANP 1

FANP 2 FANP 3

FANP 4 FANP 5

DIA

MC

O 0

DIA

MC

O 1

CU

1/ F

lexC

U 1

CU

0/ F

lexC

U 0

CU

2/ F

lexC

U 2

CU

4/ F

lexC

U 4

CU

7/ F

lexC

U 7

CU

6/ F

lexC

U 6

CU

5/ F

lexC

U 5

CU

3/ F

lexC

U 3

(F)D

UA

MC

O 0

FIC

OM

0or

CO

AM

CO

0

(F)D

UA

MC

O 1

FIC

OM

1or

CO

AM

CO

1

(F)D

UA

MC

O 2

FIC

OM

2or

CO

AM

CO

2

(F)D

UA

MC

O 3

FIC

OM

3or

CO

AM

CO

3


A30808-X3247-M326-5-7620 205



Fig. 4.8 BS-240 Service1 Rack Design and Configuration (example)

BS-240

DCP

DC

BC

TR

L 0

DC

BC

TR

L 1

AC/DC#05

AC/DC#04

AC/DC#03

AC/DC#02

AC/DC#01

AC/DC#00

AC/DC#15

AC/DC#14

AC/DC#13

AC/DC#12

AC/DC#11

AC/DC#10

All Batteries arecreated in Rack 3.

FANP 0 FANP 1

FANP 2 FANP 3

AC+DC Distribution

BatteryBatteryBatteryBattery

Hardware ManagedObjects (HMO) areshown in Tab. 4.4(DCBCTRL).

206 A30808-X3247-M326-5-7620



Fig. 4.9 BS-240 Service2 Rack Design and Configuration (example)

BS-240

DCP

FANP 0 FANP 1

LE#00

LE#01

LE#02

LE#03

LE#04

LE#05

LE#06

LE#07

LE#08

LE#09

LE#10

LE#11



A30808-X3247-M326-5-7620 207



Fig. 4.10 24 Carrier BTSE BS-240 (examples)

Rack 2Extension Rack


Rack 0Base Rack

Rack 3Service Rack

Rack 4...7Service Rack

TMA

76

54

32

10

TMA

76

54

32

10

TMA

76

54

32

10

208 A30808-X3247-M326-5-7620



4.4 Front View of the BS-240 II Rack

Fig. 4.11 BS-240 II Base Rack Design and Configuration (example)

LMTDCP OVPT

BS-240 II

HPDU#0 HPDU#1

FANP 0 FANP 1

FANP 2 FANP 3

FANP 4 FANP 5

DIA

MC

O 0

DIA

MC

O 1

CU

1/ F

lexC

U 1

CU

0/ F

lexC

U 0

CU

2/ F

lexC

U 2

CU

4/ F

lexC

U 4

CU

7/ F

lexC

U 7

CU

6/ F

lexC

U 6

CU

5/ F

lexC

U 5

CU

3/ F

lexC

U 3

CO

BA

0

CO

BA

1C

OS

A0

CO

SA

1

(F)D

UA

MC

O 0

FIC

OM

0or

CO

AM

CO

0

(F)D

UA

MC

O 1

FIC

OM

1or

CO

AM

CO

1

(F)D

UA

MC

O 2

FIC

OM

2or

CO

AM

CO

2

(F)D

UA

MC

O 3

FIC

OM

3or

CO

AM

CO

3



A30808-X3247-M326-5-7620 209



Fig. 4.12 BS-240 II Extension Rack Design and Configuration (example)

DCP

BS-240 II

HPDU#0 HPDU#1

FANP 0 FANP 1

FANP 2 FANP 3

FANP 4 FANP 5

DIA

MC

O 0

DIA

MC

O 1

CU

2/ F

lexC

U 2

CU

7/ F

lexC

U 7

CU

6/ F

lexC

U 6

CU

3/ F

lexC

U 3

CU

1/ F

lexC

U 1

CU

0/ F

lexC

U 0

CU

4/ F

lexC

U 4

CU

5/ F

lexC

U 5

(F)D

UA

MC

O 0

FIC

OM

0or

CO

AM

CO

0

(F)D

UA

MC

O 1

FIC

OM

1or

CO

AM

CO

1

(F)D

UA

MC

O 2

FIC

OM

2or

CO

AM

CO

2

(F)D

UA

MC

O 3

FIC

OM

3or

CO

AM

CO

3


210 A30808-X3247-M326-5-7620



Fig. 4.13 BS-240 II Service1A Rack Design and Configuration (example)

BS-240 II

ADP

DCP:LEBREAKV1

DCBCTRL

AC/DC#0

AC/DC#5

AC/DC#4

AC/DC#3

AC/DC#2

AC/DC#1

FANP 0 FANP 1

LE#00

LE#01

LE#02

LE#03

LE#04

LE#05




A30808-X3247-M326-5-7620 211



Fig. 4.14 BS-240 II Service2 Rack Design and Configuration (example)

BS-240 II

DCP:LEBREAK2V1

FANP 0 FANP 1

LE#00

LE#01

LE#02

LE#03

LE#04

LE#05

LE#06

LE#07

LE#08

LE#09

LE#10

LE#11



212 A30808-X3247-M326-5-7620



Fig. 4.15 24 Carrier BTSE BS-240 II (examples)



Rack 0Base Rack

Rack 3Service Rack

Rack 4...7Service Rack

TMA

76

54

32

10

TMA

76

54

32

10

TMA

76

54

32

10

A30808-X3247-M326-5-7620 213



4.5 Front View of the BS-240XL Rack

Fig. 4.16 BS-240XL Base Rack Design and Configuration (example)

iOne additional ACOM (FICOM, (F)DUAMCO, or COAMCO) can be installed instead oftwo DIAMCOs in both Base Rack and Extension Rack.

DCP OVPTLMT

BS-240XL

HPDU#0 HPDU#1

FANP 0 FANP 1

FANP 2 FANP 3

FANP 4 FANP 5

FANP 6 FANP 7

DIA

MC

O 0

DIA

MC

O 1

DIA

MC

O 2

DIA

MC

O 3

CU

2/ F

lexC

U 2

CU

7/ F

lexC

U 7

CU

6/ F

lexC

U 6

CU

3/ F

lexC

U 3

CU

1/ F

lexC

U 1

CU

0/ F

lexC

U 0

CU

4/ F

lexC

U 4

CU

5/ F

lexC

U 5

CU

9/ F

lexC

U 9

CU

8/ F

lexC

U 8

CU

11

/ Fle

xCU

11

CU

10

/ Fle

xCU

10

CO

BA

0

CO

BA

1C

OS

A0

CO

SA

1

(F)D

UA

MC

O 0

FIC

OM

0or

CO

AM

CO

0(F

)DU

AM

CO

1F

ICO

M 1

or C

OA

MC

O 1

(F)D

UA

MC

O 2

FIC

OM

2or

CO

AM

CO

2(F

)DU

AM

CO

3F

ICO

M 3

or C

OA

MC

O 3



214 A30808-X3247-M326-5-7620



Fig. 4.17 BS-240XL Extension Rack Design and Configuration (example)

DCP

BS-240XL

HPDU#0 HPDU#1

FANP 0 FANP 1

FANP 2 FANP 3

FANP 4 FANP 5

FANP 6 FANP 7

DIA

MC

O 0

DIA

MC

O 1

DIA

MC

O 2

DIA

MC

O 3

CU

2/ F

lexC

U 2

CU

7/ F

lexC

U 7

CU

6/ F

lexC

U 6

CU

3/ F

lexC

U 3

CU

1/ F

lexC

U 1

CU

0/ F

lexC

U 0

CU

4/ F

lexC

U 4

CU

5/ F

lexC

U 5

CU

9/ F

lexC

U 9

CU

8/ F

lexC

U 8

CU

11

/ Fle

xCU

11

CU

10

/ Fle

xCU

10

(F)D

UA

MC

O 0

FIC

OM

0or

CO

AM

CO

0

(F)D

UA

MC

O 1

FIC

OM

1or

CO

AM

CO

1

(F)D

UA

MC

O 2

FIC

OM

2or

CO

AM

CO

2

(F)D

UA

MC

O 3

FIC

OM

3or

CO

AM

CO

3


A30808-X3247-M326-5-7620 215



Fig. 4.18 BS-240XL Service1 Rack Design and Configuration (example)

DCP

DC

BC

TR

L 0

AC/DC#05

AC/DC#04

AC/DC#03

AC/DC#02

AC/DC#01

AC/DC#00

DC

BC

TR

L 1

AC/DC#15

AC/DC#14

AC/DC#13

AC/DC#12

AC/DC#11

AC/DC#10

BS-240XL

FANP 0 FANP 1

FANP 2 FANP 3

AC+DC Distribution

Battery BatteryBatteryBattery




216 A30808-X3247-M326-5-7620



Fig. 4.19 BS-240XL Service2 Rack Design and Configuration (example)

DCP

BS-240XL

FANP 0 FANP 1

LE#00

LE#01

LE#02

LE#03

LE#04

LE#05

LE#06

LE#07

LE#08

LE#09

LE#10

LE#11




A30808-X3247-M326-5-7620 217



Fig. 4.20 24 Carrier BTSE BS-240XL (examples)


Rack 0Base Rack

Rack 3Service1 Rack

Rack 4...7Service2 Rack

11

TMA

109

87

65

43

21

0

11

TMA

109

87

65

43

21

0

218 A30808-X3247-M326-5-7620



4.6 Front View of the BS-240XL II Racks

Fig. 4.21 BS-240XL II Base Rack Design and Configuration (example)

DCP OVPTLMT

BS-240XL II

HPDU#0 HPDU#1

FANP 0 FANP 1

FANP 2 FANP 3

FANP 4 FANP 5

FANP 6 FANP 7

(F)D

UA

MC

O 5

(F)D

UA

MC

O 4

With core redundancy:The active COBA andCOSA can be the leftpair or the right pair. Theleft pair is always COBA0 and COSA 0, the rightpair is COBA 1 andCOSA 1, independenton the status.

CU

2/ F

lexC

U 2

CU

7/ F

lexC

U 7

CU

6/ F

lexC

U 6

CU

3/ F

lexC

U 3

CU

1/ F

lexC

U 1

CU

0/ F

lexC

0C

U 4

/ Fle

xCU

4C

U 5

/ Fle

xCU

5

CU

9/ F

lexC

U 9

CU

8/ F

lexC

U 8

CU

11

/ Fle

xCU

11

CU

10

/ Fle

xCU

10

CO

BA

0

CO

BA

1C

OS

A0

CO

SA

1

(F)D

UA

MC

O 0

or C

OA

MC

O 0

(F)D

UA

MC

O 3

or C

OA

MC

O 3

(F)D

UA

MC

O 1

or C

OA

MC

O 1

(F)D

UA

MC

O 2

or C

OA

MC

O 2

Hardware ManagedObjects (HMO) areshown in Tab. 4.1(FlexCU) andTab. 4.2 (ACOM).

A30808-X3247-M326-5-7620 219



Fig. 4.22 BS-240XL II Extension Rack Design and Configuration (example)

DCP

BS-240XL II

HPDU#0 HPDU#1

FANP 0 FANP 1

FANP 2 FANP 3

FANP 4 FANP 5

FANP 6 FANP 7

CU

2/ F

lexC

U 2

CU

7/ F

lexC

U 7

CU

6/ F

lexC

U 6

CU

3/ F

lexC

U 3

CU

1/ F

lexC

U 1

CU

0/ F

lexC

U 0

CU

4/ F

lexC

U 4

CU

5/ F

lexC

U 5

CU

9/ F

lexC

U 9

CU

8/ F

lexC

U 8

CU

11

/ Fle

xCU

11

CU

10

/ Fle

xCU

10

(F)D

UA

MC

O 0

or C

OA

MC

O 0

(F)D

UA

MC

O 3

or C

OA

MC

O 3

(F)D

UA

MC

O 1

or C

OA

MC

O 1

(F)D

UA

MC

O 2

or C

OA

MC

O 2

Hardware ManagedObjects (HMO) areshown in Tab. 4.1(FlexCU) andTab. 4.2 (ACOM).

(F)D

UA

MC

O 5

or C

OA

MC

O 5

(F)D

UA

MC

O 4

or C

OA

MC

O 4

220 A30808-X3247-M326-5-7620



Fig. 4.23 BS-240XL II Service1A Rack Design and Configuration (example)

ADP

DCP:LEBREAKV1

DCBCTRL

BS-240XL II

FANP 0 FANP 1

LE#00

LE#01

LE#02

LE#03

LE#04

LE#05

AC/DC#0

AC/DC#5

AC/DC#4

AC/DC#3

AC/DC#2

AC/DC#1





A30808-X3247-M326-5-7620 221



Fig. 4.24 BS-240XL II Service2 Rack Design and Configuration (example)

DCP:LEBREAK2V1

BS-240XL II

FANP 0 FANP 1

LE#00

LE#01

LE#02

LE#03

LE#04

LE#05

LE#06

LE#07

LE#08

LE#09

LE#10

LE#11




222 A30808-X3247-M326-5-7620



Fig. 4.25 24 Carrier BTSE BS-240XL II (examples)


Rack 0Base Rack

Rack 3Service1 Rack

Rack 4...7Service2 Rack

11

TMA

109

87

65

43

21

0

11

TMA

109

87

65

43

21

0

A30808-X3247-M326-5-7620 223



4.7 Corresponding Hardware Managed Objects (HMO)

* Only in BS240XL and BS240XL II

iHMOs with names identical to those of their modules are not explicitly listed.Example: The HMO of the COBA 1 is called COBA 1.

Module Type Module Number Hardware ManagedObjects (HMO)

FlexCU FCU 0 FCUMAIN 0FCUTR 0,1

FCU 1 FCUMAIN 1FCUTR 2,3







FCU 8* FCUMAIN 8FCUTR 16,17




Tab. 4.1 Possible Modules and their Hardware Managed Objects (HMO) for FlexCU

iCU, GCU, or ECU can also be installed instead of FlexCU.The HMOs are then all called CU 0..x.

224 A30808-X3247-M326-5-7620



** Only in BS240XL II


(F)DUAMCO (F)DUAMCO 0 DUDCTMA 0,1DULNA 0,1DUVSWR 0,1

(F)DUAMCO 1 DUDCTMA 2,3DULNA 2,3DUVSWR 2,3



(F)DUAMCO 4** DUDCTMA 8,9DULNA 8,9DUVSWR 8,9

(F)DUAMCO 5** DUDCTMA 10,11DULNA 10,11DUVSWR 10,11

FICOM FICOM 0 FTNFP 0,1FVSWRP 0

FICOM 1 FTNFP 2,3FVSWRP 1



Tab. 4.2 Possible Modules and their Hardware Managed Objects (HMO) for ACOM

iThe module COAMCO has no HMOs.

A30808-X3247-M326-5-7620 225



*** Only in BS240XL

**** Only in BS240 and BS240XL


DIAMCO DIAMCO 0 DIDCTMA 0,1DILNA 0,1

DIAMCO 1 DIDCTMA 2,3DILNA 2,3

DIAMCO 2*** DIDCTMA 4,5DILNA 4,5

DIAMCO 3*** DIDCTMA 6,7DILNA 6,7

Tab. 4.3 Possible Modules and their Hardware Managed Objects (HMO) for MUCO


DCBCTRL DCBCTRL 0 ACDCP 0

DCBCTRL 1**** ACDCP 1

Tab. 4.4 Possible Modules and their Hardware Managed Objects (HMO) forDCBCTRL

iACDCP 0 / ACDCP 1 is dependent on the DIP switch setting, see HW:BTSE Modules,DCBCTRL for the appropriate module description.

226 A30808-X3247-M326-5-7620



4.8 TX/RX Paths of Some Configuration Examples

This chapter shows diagrams of the TX/RX paths of 3 configuration examples. For eachconfiguration a table is given which lists some details on possible failures, their possibleeffects and how they can be detected.

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

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 andfurther details that cannot be taken into account here.The occurrence frequency of the errors is not considered and may differ considerably.

- VSWR MonitoringExamples of corresponding alarms:Combining Equipment:Error ID <no> – DUAMCO: 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

- Sleeping Cell DetectionBSC alarm: Transceiver Problem (Specific Problem: No call incell within a predefined time frame)

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

A30808-X3247-M326-5-7620 227



Fig. 4.26 TX/RX Paths of Configuration with FICOM, DIAMCO, HPDU, DUBIAS, TMA

FICOM (F)DUAMCO

CU

HPDU

DUBIAS

1

3

8 9

10

12

14

13

15

16

11

2

3

5

7

6

TMA

14

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

*

TMA

CU11

4 4

Configuration withone TX antenna.Note:Configurations withadditional TXantennas for thesame cell are alsopossible.

Hardware ManagedObjects (HMO) arelisted in Tab. 4.1(FlexCU) andTab. 4.2 (ACOM).

*

228 A30808-X3247-M326-5-7620



No. Failure Cause Effect Detected by...

1 TX/RX antenna defect, cable dis-rupted

VSWR Alarm (dependant onattenuation 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-RX path interruption insideTMA

reduced diversity gain TMA Alarm;Online RF Loopback;RX Diversity Alarm

5 RF cable damaged betweenDUBIAS and HPDU

VSWR Alarm;reduced coverage area;reduced diversity gain;

VSWR monitoring;Online RF Loopback;RX Diversity Alarm

6 RF cable damaged betweenDUBIAS and DIAMCO

reduced diversity gain Online RF Loopback;RX Diversity Alarm;TMA Alarm

7 RF cable damaged betweenHPDU and FICOM

VSWR Alarm;reduced coverage area;

VSWR monitoring;Online RF Loopback;

8 FICOM: mistuned TNF operation and maintenance SWdisables carrier due to FICOMred tuning alarm

TNF monitoring

9 RF path interruption insideFICOM

coverage area reduced to zerofor carriers behind interruptionpoint

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

10 RF cable damaged betweenFICOM and CU (HPA)

SW disables carrier due to VSWRAlarm

VSWR monitoring of HPA/CU;Online RF Loopback if VSWRmonitoring fails (if BasebandHopping is activated a thresholdmust be exceeded)

Tab. 4.5 Failure Causes in the TX/RX Path, Configuration with FICOM, DIAMCO, HPDU, DUBIAS, TMA

A30808-X3247-M326-5-7620 229



11 Failure inside CU (HPA) (isolatornot properly soldered)

SW disables CU due to VSWRAlarm

VSWR monitoring;Online RF Loopback is possible ifVSWR monitoring fails (if Base-band Hopping is activated athreshold must be exceeded)

12 RX antenna defect, cable disrupt-ed

reduced sensitivity RX Diversity Alarm

13 RX antenna out of bearing reduced RX sensitivity;no RX signal

RX Diversity Alarm

14 RX feeder cable poorly assem-bled or disrupted

reduced sensitivity due to the lossof one RX branch

RX Diversity Alarm

15 RF path interruption insideDIAMCO


LNA Alarm;RX Diversity Alarm;Online RF Loopback

16 RF cable damaged betweenDIAMCO and CU


RX Diversity Alarm


Tab. 4.5 Failure Causes in the TX/RX Path, Configuration with FICOM, DIAMCO, HPDU, DUBIAS, TMA

230 A30808-X3247-M326-5-7620



Fig. 4.27 TX/RX Paths of Configuration with DUAMCO / FDUAMCO

1

3

5

2

CU6


CU6

(F)DUAMCO4

Hardware ManagedObjects (HMO) arelisted in Tab. 4.1(FlexCU) andTab. 4.2 (ACOM).

A30808-X3247-M326-5-7620 231





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








4 RF-TX path interruption insideDUAMCO / FDUAMCO;

RF-RX path interruption insideDUAMCO / FDUAMCO

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 betweenDUAMCO / FDUAMCO and CU;

RF-RX path interruption betweenDUAMCO / FDUAMCO and CU

SW disables carrier due to VSWRAlarm

VSWR monitoring of HPA/CU;Online RF Loopback if VSWRmonitoring fails (possibleexception if Baseband Hopping isactivated);RX Diversity Alarm

6 Failure inside CU (HPA) (isolatornot properly soldered)

SW disables CU due to VSWRAlarm

VSWR monitoringOnline RF Loopback if VSWRmonitoring fails (possibleexception if Baseband Hopping isactivated)

Tab. 4.6 Failure Causes in the TX/RX Path, Configuration with DUAMCO / FDUAMCO

232 A30808-X3247-M326-5-7620



Fig. 4.28 TX/RX Paths of Configuration with DIPLEXER

DIPLEXER

1 2

3

4 5

FICOM (F)DUAMCO

CU CU CU CU


See Configuration Examplewith (F)DUAMCO

See Configuration Examplewith FICOM etc.

Hardware ManagedObjects (HMO) arelisted in Tab. 4.1(FlexCU) andTab. 4.2.

A30808-X3247-M326-5-7620 233





VSWR Alarm (dependant onattenuation figures);reduced sensitivity;reduced coverage area








4 RF cable damaged betweenDIPLEXER and FICOM

VSWR Alarm;reduced coverage area;coverage area reduced to zero

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

5 RF cable damaged betweenDIPLEXER and DUAMCO /FDUAMCO

VSWR Alarmreduced coverage area;coverage area reduced to zero;reduced diversity gain

VSWR monitoring;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

Tab. 4.7 Failure Causes in the TX/RX Path, Configuration with DUAMCO / FDUAMCO, FICOM, DIPLEXER

234 A30808-X3247-M326-5-7620



A30808-X3247-M326-5-7620 235



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 theswImages is stopped.

This check is only performed in the load phase.

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.

Test Report in Case of a Failed VAM Check:

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

Test Report:

name = BTSETEST:<no>testOutcome = <fail or aborted>testTermination = <normal or aborted>MOT = RACK:<no>/<Module>:<no>executedPhases

(...)

Proposed Repair Action(...)

Other Information = H’01 H’00 H’00 H’00 H’00 H’00 H’00 H’00

END OF OUTPUT FOR JOB <no>

236 A30808-X3247-M326-5-7620



Meaning of Other Information:

All other bytes are not used.

If the first byte of the string “Other Information” is H’01, the result of the VAM check isnegative. In this case, it has to be checked whether the HW version of the replacedmodule is supported by the actual SW version according to the stock list/release note.If the HW version is not supported, the module must be replaced by one with a support-ed HW version.

5.2 State/Status Attributes of BTSE Managed Objects

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

Other Information = H’01 H’00 H’00 H’00 H’00 H’00 H’00 H’00⇑01 VAM check failed02 board recovery (2x PROC_ID)03 no startup04 board failed05 board deleted06 board power off

State/Status Attribute State/Status Explanation

Administrative State(AST)

This state informs whether or not the MO is permitted to provideservice.

Locked The related MO is not permitted to provide service, but is addres-sable for maintenance tasks and fully operable (it can, for exam-ple, be tested). This state can be brought about via the LMT“Lock” command.Note: at the BTSE, only HMOs can be locked/unlocked.

Shutting Down The MO is currently shutting down, i.e. ongoing calls are not in-terrupted, but no new calls are permitted.This state cannot be brought about via LMT at the BTSE.

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

Operational State(OST)

This state informs whether or not the MO is able to provide ser-vice.

Enabled (ena) The MO is able to provide service.(Exception: The MOs “RACK”, “BTSE” and “ENVABTSE” arealways “Enabled”, even if, for example, a service rack is notinstalled.)

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

Tab. 5.1 State/Status Attributes of BTSE MOs

A30808-X3247-M326-5-7620 237



Alarm Status (ALS) This status reports the severity level of active alarms. If morethan one alarm is active, the level of the alarm with the highestseverity level is reported.

Critical At least one active alarm with severity level “critical”(see 5.3.3.1).

Major At least one active alarm with severity level “major” (see 5.3.3.2).

Minor At least one active alarm with severity level “minor” (see 5.3.3.3).

Cleared No active alarms.

Availability Status This status reports details on AST or OST.

In Test (tst) Intrusive test under progress.

Failed (fail) MO is defective/not operable.

Power Off (pof) The power of the MO is switched off.

Degraded (deg) The service is degraded.

Off Line (ofl) The creation of the MO is in progress.

Dependency (Dep) The MO cannot operate because of another MO on which it de-pends.

Not Installed (noi) The MO is not installed.

Null Value (nul) Value after the creation of an MO (+Disabled/Locked).Certain processes still in progress (e.g. alignment).MO TRX: transient failure of a HMO.

Procedural Status(PRS)

This status reports whether or not the MO performs an initializa-tion 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 “Enabled”/AST “Un-locked”. The MO provides service.

Cold Standby The MO is able to provide service but it is either not active or it islocked.

State/Status Attribute State/Status Explanation

Tab. 5.1 State/Status Attributes of BTSE MOs

238 A30808-X3247-M326-5-7620



5.3 BTSE Alarm Information

On each BTSE board a local alarm queue for 30 alarms is available. Every 100 ms 1alarm is sent to the COBA. If currently more alarms are generated, the queue gets fulland a reset is performed on the board. After the board is restarted, a corresponding Fail-ure Event Report is sent.

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

1. Managed object class

2. Managed object instance

3. Error information

– probable cause value

– event type

– perceived severity

– trend indication

– immediate defense action

– threshold information

– proposed repair action

– error description

– additional information

5.3.1 Probable Cause Value

Probable cause of the fault or error. The probable cause is taken out of a predefined setof values, defined for each event type.

5.3.2 Event Types

Errors are classified in the following categories (so called “event types”):

5.3.2.1 Equipment Errors– detected by hardware check or application software

5.3.2.2 Processing Errors– detected by online software checks and audits

5.3.2.3 Communication Errors– detected by protocols

5.3.2.4 Quality of Service ErrorsThey depend on:

– traffic overload conditions

– excessive instability of the hardware

– loss of hardware components

A30808-X3247-M326-5-7620 239



5.3.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.3.3 Perceived Severity

The severity level indicates to what extent the functionality of the BTSE is affected. Thefollowing values are used:

5.3.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, if an equipment related managed object MO breaks down completely.

5.3.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, ifthere is a severe degradation in the capability of the equipment related managed object(MO).

5.3.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.3.3.4 WarningThe warning severity level indicates the detection of a potential or impending service af-fecting fault, before any significant effects have been detected. Actions should be takento further diagnose (if necessary) and correct the problem in order to prevent it from be-coming a fault causing more severe interference to services.

5.3.4 Trend Indication

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

5.3.5 Immediate Defense Action

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

240 A30808-X3247-M326-5-7620



5.3.6 Threshold Information

5.3.7 Proposed Repair Action

Suggested repair actions. Consult also the corresponding user manual.

5.3.8 Error Description

Detailed description of the error and its probable cause.

5.3.9 Additional Information

A fixed length buffer contains additional information concerning the detected fault/error.This information depends on the error.

5.4 Fault Messages

5.4.1 Fault Messages at the Radio Commander

Fig. 5.1 Fault Messages at the Radio Commander

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

A30808-X3247-M326-5-7620 241



5.4.2 Fault Messages at the LMT

JOB: <no>

PC Time&Date:<Time> <Date>

NE Time&Date:<Time> <Date>

USER: <Name>

SW RELEASE: <Release>

COMMAND RESULT: Operation successful

FAILURE EVENT REPORT:

NAME = <modul>:<no>

Event Type = Communication Failure Event

Event Time = <Time> <Date>

Probable Cause = Transmitter Error

Specivic Problems = 10270 - Loss of signal

Severity = Major

Trend Indication = More Severe

Notification Identifier = 322

Proposed Repair Actions_1 = 185 - Collect infor for assistance

Proposed Repair Actions_2 = 181 - Test the addressed card

Originator = 1281

Additional Words =

Octets 01 to 16: H’6d63 H’6e61, H’6c72, H’6d66 H’0746 H’0106 H’1a19

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

Software Version = <Version>


5.5 BTSE Components

5.5.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.5.2 Numbering of BTSE Components

5.5.2.1 General Rules

Relative Numbering

In general, the relative numbering (i.e. logical numbering) of the units starts with the fig-ure zero (0). That means that the first of a set of devices, modules or racks / shelters isassigned the number 0; the next one the number 1 in sequence, etc.

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

242 A30808-X3247-M326-5-7620



5.5.2.2 Specific Rules

Rack Numbering

The first rack in a BTSEplus is called Base Rack and is assigned the number 0. If addi-tional space is required for transceivers and combining equipment, the base rack is ex-tended by an Extension Rack. Altogether, beside one Base Rack, two Extension Racks(one Extension Rack for BS-240XL / 240XL II), a maximum of 5 Service Racks can beinstalled for one BTSEplus.

The rule for numbering of the racks is shown in the table below. Note, that the numberingof the Service Racks always begins with the number 3, even, if the Extension Racks 1or 2 does not exist.

Slot Numbering Inside the Racks or Shelters

In a rack, slot numbers are defined for accommodation of CUs, ACOMs and MUCOs.There are 8 CU slots (0...7), 4 ACOM slots (0...3) and 2 MUCO slots (0, 1) in the BS-240/ 240 II and 12 CU slots (0...11), 4 ACOM slots (0...3) and 4 MUCO slots (0...3) in theBS-240XL / 240 II. Additionally, in the Base Rack, 4 CORE slots are defined for housingthe core units and their redundant units. Slot numbering in the Base Rack and the Ex-tension Rack is equal for CUs, ACOMs and MUCOs.

The HPDU 0 is located at the left and the HPDU 1 at the right side on top of the rack.

Figure Fig. 4.10 shows, as an example, the arrangement of a BTSEplus with one BaseRack (Rack 0), 2 Extension Racks (Rack 1 and 2) and 2 Service Racks (Rack 3 and 4).

5.5.3 Remote Inventory Data

The function “Remote Inventory” of the Siemens Base station System performs elec-tronic, non-volatile storing of the complete, individual product identification data (PID) ofeach inventoried object.

Modules that have inventory data on board are called ob_RIUs (on-board Remote In-ventory Units). The PID of these ob_RIUs is automatically loaded to the inventory datafile (IDF).

In order to include inventory data of objects without a non volatile storage (e. g. frames,racks, OEM components), the data of these so called nob_RIUs (not on-board RemoteInventory Units) are entered into an inventory data table (IDT) via the LMT and the offlinetool “IDF Evolution”. These data are stored on the COBA as a nob_RIU file (NOB). Sup-plemented with a footer and header, the IDT can be exported and stored as an inventorydata file (IDF) for backup purposes.

Rack Numbering Type of Rack

0 Base Rack

1 Extension Rack

2 Extension Rack (not BS-240XL / 240XL II)

3 Service 1 Rack with AC/DC modules

4...7 Service 2 Rack with Link Equipment and Backup Batteries

Tab. 5.2 Rack Numbering

A30808-X3247-M326-5-7620 243



In the event of the replacement of a nob_RIU component, the NOB file must be updatedmanually and the backup IDF file with the inventory data, which is stored on site, mustbe updated as well.

In case of a COBA replacement, the inventory data that was stored on the removedCOBA must be rebuilt. This can be done by using the backup IDF file.

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

The following list shows all nob_RIU components:

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

ACDC-m/n 3 0...11 AC/DC

BATTERY-m/n 3...7 0...2 F:BATTERY

DCP-m/n 0 0 DCP:RSHB

DCP-m/n 1...2 0 DCP:RSHE

DCP-m/n 3 0 DCP:RSHSB

DCP-m/n 4...7 0 DCP:RSHSS

DUBIAS-m/n 0...2 0...1 DUBIAS

EMIPB-m/n 0 0 EMIP:B

EMIPE-m/n 1...2 0 EMIP:E

EMIPS-m/n 3...7 0...5 EMIP:S

FACDC-m/n 3 0 F:AC/DC1

FACDC-m/n 3 1 F:AC/DC2

FACOM-m/n 0...2 0 F:ACOM

FAN-m/n 0...7 0...7 FAN

FCORECU-m/n 0 0 F:CORECU

FFAN-m/n 3...7 0...3 F:FAN

FNT-m/n 3...7 0...7 F:NT

FRXCU-m/n 0...2 0...2 F:RXCU

HEATER-m/n 0...7 0...2 HEATER

HEX-m/n 0...7 0...2 HEX

HPDU-m/n 0...2 0...1 HPDU

MEF-m/n 0...7 0 MEF

MKAIRBUF-m/n 0...7 0...3 MK:AIRBUF

MKAIRDUCT-m/n 0...7 0...2 MK:AIRDUCT

MKBATTERY-m/n 4...7 0...2 MK:BATTERY

MKBUS-m/n 0...7 0 MK:BUS

MKCARB-m/n 0 0 MK:CARB

MKCARE-m/n 1...2 0 MK:CARE

Tab. 5.3 List of nob_RIUs

244 A30808-X3247-M326-5-7620



5.6 Diagnostics / Test

5.6.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

The successful replacement of analog modules can only be verified by reactivating theBTSE.

MKCARS-m/n 3 0 MK:CARS

MKCARS2-m/n 4...7 0 MK:CARS2

MKCASHB-m/n 0 0 MK:CASHB

MKCASHE-m/n 1...2 0 MK:CASHE

MKCASHS-m/n 3 0 MK:CASHS

MKCASHS2-m/n 4...7 0 MK:CASHS2

MKEMC-m/n 1...7 0 MK:EMC

MKFLOOR-m/n 0...7 0 MK:FLOOR

MKHPDU-m/n 1...2 0...1 MK:HPDU

MKLE-m/n 3...7 0...3 MK:LE

MKOCT-m/n 3...7 0...3 MK:OCT

MKOPEXAL-m/n 0 0 MK:OPEXAL

MKPOWER-m/n 0...7 0 MK:POWER

MKSMOKE-m/n 0...7 0 MK:SMOKE

MSUAC-m/n 3 0 MSUAC

MSUDC-m/n 0...7 0 MSU:DC

OVPT-m/n 0, 3...7 0...1 M:OVPT

RACK-m/n 0...70...1, 3...7

00

R/SH:BS8x (BS-240 /240 II)R:BS120 (BS-240XL /240XL II)

TMA-m/n 0...2 0...15 TMAx

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

Tab. 5.3 List of nob_RIUs

A30808-X3247-M326-5-7620 245



5.6.2 Requirements for Starting the BTSE Module Test

The module test is controlled by the LMT; therefore the LMT must be plugged in at theplug position and the user logged on. The principle sequence is as follows:

– change the administrative state from unlocked to locked

– start the module test

– change the administrative state from locked to unlocked

The requisite command sequence is as follows:

5.6.2.1 Lock the BTS Site Manager (only relevant for some modules)BSS


BSS-FUNCTIONAL

BTSM

BTSM<no>

LOCKREQUEST BTSM

NAME=BTSM:0

LOCKREQUEST BTSM:NAME=BTSM:0;

5.6.2.2 Change the BTSE from Phase 3 to Phase 2 (only relevant for somemodules)BSS


BSS-FUNCTIONAL

BTSM

BTSM<no>

DISCBSC BTSM

NAME=BTSM:0

DISCBSC BTSM:NAME=BTSM:0;

5.6.2.3 Lock the Suspected Module (all modules)BSS


BSS-EQUIPMENT

BTSEP

BTSEP<no>

RACK

RACK<no>

<module>

<module><no>

246 A30808-X3247-M326-5-7620



LOCK <module>

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

5.6.2.4 Run the Test for the Replaced ModuleBSS


BSS-EQUIPMENT

BTSEP

BTSEP<no>

RACK

RACK<no>

<module>

<module><no>

PERFTEST <module>

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

Explanation of the test parameters:

Refer to the manual CML:BS-4x/240/241/240XL.

System Response

Example for Test Report

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

PERFTEST ACK BTSEP :

name = BTSEP:<no>MOT = RACK:<no>/<MO>:<no>t0 = BTSETEST: <no>


JOB: <no>PC Time&Date = <time> <date>NE Time&Date = <time> <date>USER NAME: <user>

A30808-X3247-M326-5-7620 247



5.6.2.5 Unlock the Suspected Module (all modules)BSS


BSS-EQUIPMENT

BTSEP

BTSEP<no>

RACK

RACK<no>

<module><no>

UNLOCK <module>

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

5.6.2.6 Change the BTSE from Phase 2 to Phase 3 (only relevant for somemodules)BSS

SW RELEASE: <no>COMMAND RESULT: <command result>

Test Report:

name = BTSETEST:<no>test Outcome = <test outcome> (see below)testTermination = NormalMOT = RACK:<no>/<MO>:<no>executedPhases

phaseId = PreliminaryTests<MO>phaseId = CheckAlarmStatus<MO>phaseId = EndTest<MO>


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

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

Failed Phases = <no>Additional Words

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

248 A30808-X3247-M326-5-7620




BSS-FUNCTIONAL

BTSM

BTSM<no>

CONNBSC BTSM

NAME=BTSM:0

CONNBSC BTSM:NAME=BTSM:0;

5.6.2.7 Unlock the BTS Site Manager (only relevant for some modules)BSS


BSS-FUNCTIONAL

BTSM

BTSM<no>

UNLOCKREQUEST BTSM

NAME=BTSM:0

UNLOCKREQUEST BTSM:NAME=BTSM:0;

A30808-X3247-M326-5-7620 249



6 AbbreviationsABISCON Abis Connector Board

AC/DC AC/DC Converter

ACOM Antenna Combiner

ACT Alarm Collection Terminal

ACTA ACT Alarm Board

ACTC ACT Connection Board

ACTM ACT for the Base Rack/Shelter

ACTP ACT Processor Board

ADP AC/DC Panel

BSC Base Station Controller

BSS Base Station System

BTS Base Transceiver Station

BTSE Base Transceiver Station Equipment

CAN Controller Area Network

COBA Core Basis

COSA Core Satellite

CSU Channel Service Unit

CU Carrier Unit

DIAMCO Dual Integrated Amplifier Multicoupler

DUAMCO Duplexer Amplifier Multicoupler

DUBIAS Duplexer Bias Path

ECU EDGE Carrier Unit

EDGE Enhanced Data Rates for GSM Evolution

EMI Electro Magnetic Interference

ESD Electrostatic Sensitive Device

FAN Fan Unit

FDUAMCO Flexible DUAMCO

FlexCU Flexible Carrier Unit

GCU GMSK CU

GMSK Gaussian Minimum Shift Keying

GSM Global System for Mobile Communication

HMO Hardware related Managed Object

HPDU High Power Duplexer

HW Hardware

IDF Inventory Data File

IDT Inventory Data Table

ITMN Installation & Test Manual

LAPD Link Access Protocol for D-channel

LE Link Equipment

LED Light Emitting Diode

250 A30808-X3247-M326-5-7620



LMT Local Maintenance Terminal

MO Managed Object (e.g. functional part of a module)

MOT Managed Object Under Test

N No

no number

NOB nob_RIUs only

nob_RIU not on-board Remote Inventory Data

NT Network Termination

ob_RIU on-board Remote Inventory Data

OMC Operation and Maintenance Center

OS Operating System

OVPT Overvoltage Protection and Tracer

PID Product Identification Data

RC Radio Commander

SBS Siemens Base Station

TAC Technical Assistance Center

TMA Tower Mounted Amplifier

VAM Version Attachment Mechanism

VSWR Voltage Standing Wave Ratio

Y Yes

A30808-X3247-M326-5-7620 251



7 IndexAAutorecovery 20

Ccode key 19compatibility 235configuration 203–222CORE Redundancy 43, 49, 59, 67

EEAUTOREC 20

FFault and Test Management 14

Llevers 18Local Fault Clearance 14

NNumbering

Rack / Shelter 207, 212, 217, 222, 242Relative 241Slot 242

RRadio Commander 14

SSpanner 18

TTAC 15tools 18

Wwrist strap 16

252 A30808-X3247-M326-5-7620



bs240mt.pdf

Documents

Transcript of bs240mt.pdf