Traumt PDF

Maintenance
Transcoding and Rate Adaption Unit

MMN:TRAU
A30808-X3247-L420-2-7620
MMN:TRAU
Maintenance
Important Notice on Product Safety

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

Wichtiger Hinweis zur Produktsicherheit
LEBENSGEFAHR - BEACHTEN SIE ALLE INSTALLATIONSHINWEISE.
Das System entspricht den Anforderungen der EN 60950 / IEC 60950. Alle an das System angeschlossenen Gerte mssen die zutreffenden Sicherheitsbestimmungen erfllen.
In diesen Anlagen stehen die Netzversorgungsleitungen unter gefhrlicher Spannung. Einige
Komponenten knnen auch eine hohe Betriebstemperatur aufweisen.
Nichtbeachtung der Installations- und Sicherheitshinweise kann zu schweren Krperverletzungen oder Sachschden fhren.
Deshalb darf nur geschultes und qualifiziertes Personal das System installieren und warten.
Caution:
This equipment has been tested and found to comply with EN 301489. Its class of conformity is
defined in table A30808-X3247-X910-*-7618, which is shipped with each product. This class also
corresponds to the limits for a Class A digital device, pursuant to part 15 of the FCC Rules.
These limits are designed to provide reasonable protection against harmful interference when the
equipment is operated in a commercial environment.
This equipment generates, uses and can radiate radio frequency energy and, if not installed and used
in accordance with the relevant standards referenced in the manual Guide to Documentation, may
cause harmful interference to radio communications.
For system installations it is strictly required to choose all installation sites according to national and
local requirements concerning construction rules and static load capacities of buildings and roofs.
For all sites, in particular in residential areas it is mandatory to observe all respectively applicable
electromagnetic field / force (EMF) limits. Otherwise harmful personal interference is possible.
Trademarks:
All designations used in this document can be trademarks, the use of which by third parties for their own purposes
could violate the rights of their owners.
Copyright (C) Siemens AG 2003 .

Issued by the Information and Communication Mobile Group
Hofmannstrae 51
D-81359 Mnchen
Technical modifications possible.
Technical specifications and features are binding only insofar as
they are specifically and expressly agreed upon in a written contract.
A30808-X3247-L420-2-7620
Maintenance
MMN:TRAU
Issues
Change indications (Ind.):
N = new;
G = modified;
Document
MMN:TRAU . . . . . . . . . .
A30808-X3247-L420-2-7620
Title
0 = deleted;
Page(s)
1...124
Issue/Ind.
2
MMN:TRAU
Maintenance
A30808-X3247-L420-2-7620
Maintenance
MMN:TRAU
Reason for Update

Summary:
Second Edition for Release BR 7.0
Details:
Chapter / Section
Reason for Update
3.6
New Remote Inventory file for TRAU-HC
Issue History
Issue
Date of Issue
Reason for Update
07/2003
First Edition for New Release BR 7.0
12/2003
Second Edition for Release BR 7.0
A30808-X3247-L420-2-7620
MMN:TRAU
Maintenance
A30808-X3247-L420-2-7620
Maintenance
MMN:TRAU
Contents
1
1.1
1.2
1.3
1.4
1.5
1.6
1.7
How to Use this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Structure of the Maintenance Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Symbols used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fault Clearance Principle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fault Clearance Guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Module Replacement Instructions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fault Management Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Procedures references . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tasklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
3
3.1
3.2
3.3
3.4
3.5
3.6
3.7
Fault Clearance Procedures for Modules and Interfaces . . . . . . . . . . . . . .

Diagnostic Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BSCI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Module Check Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MSCI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PWRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Remote Inventory Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TRAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
37
39
41
45
49
53
55
67
4
4.1
4.2
4.3
4.4
4.5
4.6
4.7
4.8
Hardware Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Rack Connections for TRAU standard . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Rack Connections for TRAU_High-Capacity . . . . . . . . . . . . . . . . . . . . . . .
Fuse and Alarm Panel for TRAU_standard . . . . . . . . . . . . . . . . . . . . . . . .
Temperature Sensor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Lamp Panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DC-Panel of the TRAU-HC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Jumpers Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
71
77
78
79
80
81
82
83
85
5
5.1
5.2
5.3
5.4
Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Alarm Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Alarm Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Failure Event Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
General Diagnostic Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
A30808-X3247-L420-2-7620
13
13
14
15
16
18
20
24
103
103
104
110
114
MMN:TRAU
Maintenance
A30808-X3247-L420-2-7620
Maintenance
MMN:TRAU
Illustrations
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
1.1
1.2
1.3
1.4
1.5
3.1
3.2
3.3
3.4
3.5
3.6
3.7
3.8
3.9
4.1
4.2
4.3
4.4
4.5
4.6
4.7
4.8
4.9
4.10
4.11
4.12
4.13
4.14
4.15
4.16
4.17
4.18
4.19
4.20
4.21
4.22
4.23
4.24
Fig. 4.25
Fig. 5.1
Fig. 5.2
A30808-X3247-L420-2-7620
Structure of the MMN:TRAU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Used Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Fault Clearance Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
ESD Symbol. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
General Maintenance flow chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Delete nob_Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Create nob_Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Edit nob_Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Attach nob_RIU file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Remove reduntant nob_RIUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Export nob_RIUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Download of the nob_RIU file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
TRAU Standard rack remote inventory files. . . . . . . . . . . . . . . . . . . . . . 60
TRAU_H-C Remote Inventory file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Front view of the TRAU rack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Front view of the TRAU rack in fire resistance cabinet . . . . . . . . . . . . . 73
TRAU-High Capacity version rack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
TRAU-HC module with two TRAUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
TRAU Rack Cabling Access Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
TRAU-HC top view: Rach Cabling Access Panel (RCAP). . . . . . . . . . . 78
TRAU_Standard Fuse and Alarm Panel . . . . . . . . . . . . . . . . . . . . . . . . 80
Lamp Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
DC-Panel of the TRAU-HC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
TRAU Power Supply Module Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Jumpers Setting for BSCIB Module (75 ohm) (S30861-Q352-X1) . . . . 85
BSCI PCM Monitoring Points. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Jumpers Setting for BSCIV3 Module (75 ohm) (S30861-Q352-X101) . 87
Jumpers Setting for BSCIV4 Module (75 Ohm) (S30861-Q415-X1) . . . 88
Jumpers Setting for BSCIV4 module (120 Ohm) (S30861-Q415-X1) . . 89
Jumpers Setting for BSCIV4 Module (100 Ohm) (S30861-Q415-X1) . . 90
Jumper Setting for MSCI Module (S30861-Q351-X1) . . . . . . . . . . . . . . 92
MSCI PCM MonitoringPoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Jumpers Setting for MSCIV2 Module (75 Ohm) (S30861-Q416-X1) . . . 94
Jumpers Setting for MSCIV2 Module (120 Ohm) (S30861-Q416-X1) . . 95
Jumpers Setting for MSCIV2 Module (100 Ohm) (S30861-Q416-X1) . . 96
Jumpers Setting for TRAC Module (S30861-Q350-X1). . . . . . . . . . . . . 98
Jumpers Setting for TRACV3 Module (S30861-Q354-X101) . . . . . . . . 99
Jumpers Setting for TRACV5 Module (S30861-Q413-X1 up to Issue 6). .
100
Jumpers Setting for TRACV5 Module (S30861-Q413-X1 from Issue 7) . .
101
Alarm Event Handling Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Alarm Ceased Handling Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
MMN:TRAU
Maintenance
Fig. 5.3
Fig. 5.4
10
TRAU Maintenance Entity Graph with TPWR. . . . . . . . . . . . . . . . . . . . 108

TRAU Maintenance Entity Graph without TPWR . . . . . . . . . . . . . . . . . 109
A30808-X3247-L420-2-7620
Maintenance
MMN:TRAU
Tables
Tab. 1.1
Tab. 2.1
Tab. 3.1
Tab. 3.2
Tab. 3.3
Tab. 4.1
Tab. 4.2
Tab. 4.3
Tab. 4.4
Tab. 4.5
Tab. 4.6
Tab. 4.7
Tab. 5.4.1
A30808-X3247-L420-2-7620
Relationship between alarms and replacement procedure . . . . . . . . . . 24

Fuse Electrical Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
List of nob-RIUs for TRAU Standard . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
List of nob-RIUs for TRAU_H-C. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
TRAUs numbering for Remote Inventory . . . . . . . . . . . . . . . . . . . . . . . 61
Left TRAUs PCM lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Right TRAUs PCM lines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Remote Alarms lines of the TRAUs_Left . . . . . . . . . . . . . . . . . . . . . . . . 79
Remote Alarms lines of the TRAUs_Right. . . . . . . . . . . . . . . . . . . . . . . 79
Anomaly Conditions Notified by LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Description of BSCI Monitoring Points. . . . . . . . . . . . . . . . . . . . . . . . . . 86
Description of MSCI Monitoring Points . . . . . . . . . . . . . . . . . . . . . . . . . 93
New Phase Identifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
11
MMN:TRAU
12
Maintenance
A30808-X3247-L420-2-7620
Maintenance
MMN:TRAU
1 How to Use this Manual

1.1
Structure of the Maintenance Manual

The following diagram gives an overview of the structure of this manual and the purpose
of its chapters.
Chapter 1
Introduction
Basic information on this manual
Basic information on fault clearance
Guidelines
General replacement Instructions
Preparatory work if relevant
(Important information to make your work

efficient and safe)
Chapter 2
Task List
Information on routine tasks that need to be
carried out
(General Maintenance)
Chapter 3
Fault Clearance Procedures for Modules

and Interfaces
Fault clearance procedures for modules
and interfaces in alphabetical order
Concluding procedure Remote Inventory
Data Update that some fault clearance
procedures require (if necessary, links are
provided to this concluding procedure)
(Main Part for Fault Clearance Tasks)
Chapter 4
Tables, Lists and Figures

Information on replaceable modules,
e.g. LEDs, connectors etc.
Overview of the HW architecture as
additional information
(Reference Chapter)
Chapter 5
Appendix
Basic required knowledge in more detail,
e.g. fault messages
(Reference Chapter)
Chapter 6
Abbreviations
(Reference Chapter)
Fig. 1.1
Structure of the MMN:TRAU
A30808-X3247-L420-2-7620
13
MMN:TRAU
Maintenance
1.2
Symbols used
The following symbols are used throughout this manual:
Symbol
Meaning
Warning; the notes given here are to be followed with care.

Non-observance can lead to personal injury or property damage.
ESD (Electrostatic Sensitive Device) precautions to be taken
Use LMT to enter commands
Reference to another step in the procedure or to another procedure
Reference to another chapter in the document or to another document
Reference to another procedure. Return after finishing.
Fig. 1.2
14
Note; important information
Used Symbols
A30808-X3247-L420-2-7620
Maintenance
1.3
MMN:TRAU
Fault Clearance Principle

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

The following diagram gives an overview of the fault clearance procedure (detailed
description below):
1. System Integrated Routine Test Detects a Fault
2. Fault Message Displayed at Radio Commander:

Information for example on
probable cause
suspected modules(s)/interface(s)
location ...
Fault and Test

Management at the
OMC via Radio
Commander
3.
Local Fault
Clearance at the
TRAU Necessary?
Content of this Manual
Local Fault
Clearance
at the TRAU
4. Fault Clearance Procedure for the Suspected

Module or Interface
7.
5.
Fault
Clearance N
Successful?
6.
Another
Probable
Cause?
8. Call
TAC
9. End of Fault Clearance: Faulty Modules are Sent to Repair Depot

Fig. 1.3
16
Fault Clearance Overview
A30808-X3247-L420-2-7620
Maintenance
MMN:TRAU
Fault Clearance Guidelines

(The numbering refers to the above diagram.)
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 Radio Commander (RC) must verify
whether a local fault clearance at the TRAU is required (see Radio Commander
documentation).
For the local fault clearance at the TRAU:
Make sure that all spare parts that might be required to clear the fault are available
at the site.
For general module replacement instructions see also "1.5 Module Replacement
Instructions".
4. Interpret the fault message and go to the fault clearance procedure of the suspected
module or interface, localize the fault and clear it according to the corresponding
procedure in chapter "3 Fault Clearance Procedures for Modules and Interfaces".
5. As described in the corresponding procedure, verify whether the fault clearance was
successful:
Was the outcome of the hardware test pass?
Are there any relevant pending alarms?
Do the LEDs signal normal operation?
6. If the fault should still exist and the replaced module was not the fault cause, check
whether there is another probable cause.
7. If there is another probable cause, reinsert the recently replaced original module and
go to the corresponding fault clearance procedure for the next suspected module or
interface.
8. It should be possible to clear most faults that may occur in the TRAU by following
the fault clearance procedures described in this manual. However, if the fault should
still exist after considering all probable causes, contact the Technical Assistance
Center (TAC). Here you will obtain help from specially trained troubleshooting
experts.
9. End of fault clearance. Pack and tag all faulty modules for transport to a repair depot.
Write a fault report in which the following information is given in detail:
A30808-X3247-L420-2-7620
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
17
MMN:TRAU
Maintenance
1.5
1.5.1
Module Replacement Instructions

ESD Precautions
Fig. 1.4
ESD Symbol
All modules are to be handled with extreme care as each contains a number of electrostatically sensitive components.
All integrated modules may contain electrostatically sensitive devices (ESDs). All
modules are marked with the ESD symbol.
The following precautions are to be taken:
Personnel should avoid wearing synthetic clothing and shoes with plastic soles, as
these foster the build-up of electrostatic charges.
Before handling modules, personnel should be freed of electrostatic charge. For this
reason personnel should always put on a grounded wrist strap before changing a
module.
Before touching modules, printed circuits or components, the wrist strap must be
connected to the ground potential of the rack by means of a flexible lead integrating a
high-value discharge resistor. The discharging socket in the holder of the special tool for
changing modules must be used for connecting the wrist strap to the ground potential.
This holder is located on the right vertical strut of the module side of the rack. Note that
the conducting parts of the split pin should not be touched when plugging it in (bypassing the discharge resistor).
IMPORTANT:
Modules with the ESD symbol are to be handled with extreme care. Static or external
voltage can lead to long-term damage in the modules.
In general, the printed circuits and components of the modules should not be touched.
Modules should be held only by their edges.
Removed modules are to be placed in covers made of conductive plastic (provided) and
then stored or sent off in special transport boxes or cases bearing the ESD symbol.
To prevent further damage, faulty modules are to be treated with as much care as new
ones.
All tools, measuring devices and metal objects that come in contact with removed
modules are to be discharged to the ground potential before being used.
To summarize:
a) ESDs should not be allowed to touch electrostatically charged or chargable objects.
18
A30808-X3247-L420-2-7620
Maintenance
MMN:TRAU
b) ESDs should only come in contact with high-value discharging material ("gentle"
discharging), i.e. should not undergo "harsh" discharging with, for example, a metal
plate.
c) ESDs should be set down on grounded surfaces only (flexible bases with a
grounding connection for servicing purposes).
d) ESDs should only be transported in authorised packaging. A grounded wrist strap
must be put on before removing ESDs.
e) ESDs should not be brought near strong DC electrical fields, e.g. cathode-ray
tubes/monitors (safety distance at least 10 cm (3.9)).
f)
Maintenance personnel should check the discharge resistance of the wrist straps at
regular intervals.
g) Even discharges that are considerably lower than the detection limit can damage or
destroy ESDs!
1.5.2
Removing and Inserting Modules

Individual fault-clearance procedures given for each fault in the relevant manual must
be followed when changing a suspect module.
Check whether the modules contain switches, jumpers or solder straps. If so, their
settings must be checked and corrected if necessary, following the guidelines in the
manual.
Modules are to be changed with extreme care. Inappropriate handling of modules can
destroy contacts or printed circuits.
a) Removing a module
The module can now be pulled by hand from the guide rail in the frame.
b) Inserting a module
The conductive wrist strap must be put on before changing a module. It must then be
connected via the flexible lead to the discharging socket in the tool holder.
Push the replacement module into the guide rails in the frame. Check that the module
has been correctly inserted into the lower rail as well as into the upper.
The faceplate of the correctly inserted module must be level with those of the adjacent
modules.
Push back the module in the guide rails until it encounters some resistance; this is overcome by lightly pressing by hand. The module's strip connectors (module connectors)
are centered on the blade contact strips in the module frame.
A30808-X3247-L420-2-7620
19
MMN:TRAU
Maintenance
1.6
Fault Management Procedure

The following list of test equipment is recommended for use in the trouble-shooting
procedures provided in this section. Make sure that equipment needed is on hand and
properly operating.
Local Maintenance Terminal (LMT)

Digital Multimeter - Fluke Model 8062A with Y8134 test lead kit, or equivalent; used
for precision DC and AC measurement, requiring 4-1/2 digits.
Antistatic wrist strap
Miscellaneous hand tools.
Be aware of the fact that a copy of each suspected faulty module is available on the site.
20
A30808-X3247-L420-2-7620
Maintenance
Fig. 1.5
MMN:TRAU
General Maintenance flow chart
A30808-X3247-L420-2-7620
21
MMN:TRAU
Maintenance
In the following an explanation of the above diagram is given.

1. Test the Alarm Lamp Integrity
Before performing any operation on the TRAU rack, check for all alarm lamp integrity. Use the LAMP TEST switch located on the TRAU front panel (see Hardware
Equipment section).
2. Verify the Lamp Status
Illuminated lamps should be consistent with the suspected module signalled in the
original fault message.
Therefore:
the lamps on the lamp panel should signal an alarm condition; (see Hardware
Equipment section)
one or more lamps on the alarm panel should be on (see Hardware Equipment
section)
3. Connect the LMT to the TRAU
Plug the LMT cable into the corresponding socket.
Perform the LOGON procedure (see OGL:LMT).
The LMT tree is now displayed on the screen.
4. Get the Equipment Alarms
LMT tree:
MANAGED-ELEMENT--> BSS-EQUIPMENT--> TRAUE
Command:
GETACTIVEALARMS TRAUE
Name:
TRAUE:<instance>
Attributes:
EVTYP = EQUIPMENT_FAILURE_EVENT
Submit
GETACTIVEALARMS
TRAUE:NAME=TRAUE:<instance>,EVTYP=EQUIPMENT_FAILURE _EVENT;
The LMT shows the list of all the modules (possibly faulty modules) which issued an
Equipment Failure Event; for each of them keep track of the related possible cause
of fault.
5. Check the Possible Faulty Modules
For all the possible faulty modules (from previous step), do the following from LMT:
LMT tree:
Command:
GET TRAUE
Name:
TRAUE:<instance>
Attributes:
REQATTL:<value>
Submit
GET TRAUE:NAME=TRAUE:<Instance>,REQATTL=value
22
A30808-X3247-L420-2-7620
Maintenance
MMN:TRAU
LMT tree:
MANAGED-ELEMENT--> BSS-EQUIPMENT--> TRAUE -->

BSMS/TRAC/TPWR
Command:
GET BSMS/TRAC/TPWR
Name:
BSMS/TRAC/TPWR:<instance>
Attributes:
REQATTL:<value>
Submit
GET
BSMS/TRAC/TPWR:NAME=BSMS/TRAC/TPWR:<Instance>,REQATTL=value
The LMT shows the state of each specified module. Keep track of the operational
state and the availability status for each module.
6. Find the Suspected module
Keeping in mind the output described above, take into account the modules for
which:
the OPERATIONAL STATE is DISABLED
the PROBABLE CAUSE description includes the word Hardware in the Alarm Event
List
the AVAILABILITY STATUS is FAILED.
These modules are called suspected modules.
7. Replace the Suspected Modules
The TRAU rack is protected by a front cover. This must be removed in order to
access the modules. To do this, remove the screws on the cover.
To remove a module, pull the levers on the module itself - pull up the top levers and
pull down the bottom ones - then extract the module. To restore a removed module
to its site, insert the module then push the levers - push down the top levers and
push up the bottom ones.
If the alarm originates from line interface card, as MSCI or BSCI and is LOSS OF
SIGNAL or LOSS OF SIGNAL ON LINK A/B, in detail signal absent (LOS), LFA
alarm present, eer alarm present (BER), RAI alarm present, check the jumpers
on the faulty card are conforming the line impedence requirement (see "4.8 Jumpers
Setting"); as well as the cable connector concerning the line number in failure state
is correctly inserted and not damaged (see IMN:TRAU manual).
After a check of cables and connectors, proceede with the replace of the suspected
modules following the procedures described in the "3 Fault Clearance Procedures
for Modules and Interfaces" chapter.
A30808-X3247-L420-2-7620
23
MMN:TRAU
Maintenance
1.7
Procedures references
The following table shows the TRAU alarms in the first column, the relative severity in
the second column and gives informations how to solve the problem.
FAULT
PROBLEM
SEV.
FIRST CHECK OR STEP REPLACEMENT PROCEDURE
Equipment
failure
TRAC
1045 TRAC
diagnostic
failure
minor
TRAC card (see

chp."3.7 TRAC")
1047 TRAC
diagnostic
online failure
minor
see the automatic diagnostic test result
1009 TRAC
timing loss
minor
1077 TRAC
HW fault
minor
TRAC card (see

chp."3.7 TRAC")
1081 TRAC
fail to load
minor
TRAC card (see

chp."3.7 TRAC")
1086 TRAC
link failure
minor
1088 TRAC
card failure
minor
1089 DSP fail

to load
minor
TRAC card (see

chp."3.7 TRAC")
TRAC card (see

chp."3.7 TRAC")
TRAC card (see
chp."3.7 TRAC")
TRAC card (see

chp."3.1 Diagnostic
Procedure")
BSCI
1006 PLL
permanent
failure
major
BSCIcard (see
chp."3.2 BSCI")
1007 BSCI
HW fault
major
BSCIcard (see
chp."3.2 BSCI")
1020 PCMS
circuit alarm
major
BSCIcard (see
chp."3.2 BSCI")
1100 BSCI
card failure
major
BSCIcard (see
chp."3.2 BSCI")
MSCI
Tab. 1.1
24
Relationship between alarms and replacement

procedure
A30808-X3247-L420-2-7620
Maintenance
FAULT
PROBLEM
MMN:TRAU
SEV.
1021 PCMA
circuit alarm
major
1059 MSCI
HW fault
major
1078 MSCI
sync 8KHz
failed
major
1079 MSCI
DIGA faulted
major
MSCI card (see

chp."3.4 MSCI")
MSCI card (see
chp."3.4 MSCI")/
BSCIcard (see
chp."3.2 BSCI")
Interface
(MSCI,BSCI)
1042 BSMS
diagnostic
failure
major
MSCI card (see

chp."3.4 MSCI")/
BSCIcard (see
chp."3.2 BSCI")
1012
major
protected
memory illegal
write attempt
1082 flash
EPROM not
valid
major
1089 DSP fail

to load
minor
TRAC card (see

chp."3.1 Diagnostic
Procedure")
TPWR
1052 TPWR
diagnosti
failure
major
PWRS card (see

chp."3.5 PWRS")
1074 TPWR
fault
major
PWRS card (see

chp."3.5 PWRS")
Line interface
failure
011 loss of
signal
critical
cables,connections of the
PCMT/PCMS line
Tab. 1.1
A30808-X3247-L420-2-7620
MSCI/BSCI card (see

chp."3.1 Diagnostic
Procedure")

procedure
25
MMN:TRAU
Maintenance
FAULT
PROBLEM
SEV.
018 loss of
signal on link
A
minor
PCMT/PCMS line
MSCI/BSCI card (see

chp."3.1 Diagnostic
Procedure")
019 loss of
signal on link
B
minor
PCMT/PCMS line
BSCI/MSCI card (see

chp."3.1 Diagnostic
Procedure")
012 AIS alarm major
problem in other station

equipment(BTS/MSC)
:call TAC
020 AIS alarm

on link A
minor

equipment(BTS/MSC)
:call TAC
021 AIS alarm

on link B
minor

equipment(BTS/MSC)
:call TAC
Loss of
synchronization
1097 bad PLL warning
input synchronisation

equipment (BTS/MSC)
:call TAC
Database
inconsistency
1019 invalid
database
warning
warning
1023 TRAC
DBA refused
minor
test the TRAC card (see

chp."3.1 Diagnostic
Procedure")
1091 datamajor
base inconsistency
BRINGUP
automatic restore
1102 probable database

inconsistency
automatic restore
warning
Input parameter out of

range
Tab. 1.1
26

procedure
A30808-X3247-L420-2-7620
Maintenance
MMN:TRAU
FAULT
PROBLEM
SEV.
1015 input
parameter out
of range
warning
warning
call TAC
warning
call TAC
warning
call TAC
1044 invalid
warning
message data
call TAC
1048 invalid
RTE header
field value
warning
call TAC
1060 MSCI
SW error
warning
call TAC
1080 TRAC
unexpected
message
warning
call TAC
warning
call TAC
1024 system
call unsuccessful
warning
warning
call TAC
1028 function
call unsuccessful
warning
call TAC
Invalid pointer
1114 invalid
pointer
warning
Message not
expected
1014 unexpected
message
Message out
of sequence
1033
message out
of sequence
warning
System call
unsuccessful
Tab. 1.1
A30808-X3247-L420-2-7620

procedure
27
MMN:TRAU
Maintenance
FAULT
PROBLEM
SEV.
1066
message not
sent
warning
call TAC
1067 invalid
DB call
warning
call TAC
1096 system
call unsuccessful minor
major
test the MSCI/BSCI card

(see chp."3.1 Diagnostic
Procedure")
1037 timeout
expired
warning
warning
call TAC
1075 TRAC
keep alive
alarm
major

chp."3.1 Diagnostic
Procedure")
1087 DSP
TSYNC
expired
warning
ASUB lines is disconnected or problem in BTS or

network :call TAC
1090 DSP
keep alive
alarm
minor

chp."3.1 Diagnostic
Procedure")
1104 BSCI
keep alive
alarm
major
test the BSCI card (see

chp."3.1 Diagnostic
Procedure")
1105 MSCI
keep alive
alarm
major
test the MSCI card (see

chp."3.1 Diagnostic
Procedure")
warning
call TAC
minor

chp."3.1 Diagnostic
Procedure")
Timeout
expaired
Equipment
failure
Variable out of
range
1029 variable
out of range
Watch dog
timer expired
1003 TRAC
WDT timeout
Tab. 1.1
28

procedure
A30808-X3247-L420-2-7620
Maintenance
MMN:TRAU
FAULT
PROBLEM
SEV.
1005 BSCI
WDT warning
warning
call TAC
1004 BSCI
WDT timeout
major
test the BSCI card (see

chp."3.1 Diagnostic
Procedure")
warning
call TAC
2001 ASUB
transient
failure
warning
call TAC
2003 LPDL
link down
critical
different LAPD timeslot in

BSC and TRAU :_call
TAC
015 remote
alarm
major
outgoing stream,interface card (MSCI/BSCI)
test the BSCI/MSCI card

Procedure")
026 remote
alarm on link
A
minor

Procedure")
027 remote
alarm on link
B
minor

Procedure")
016 higher
major
BER threshold
exceeded
cables,connections and
line interface cards

Procedure")
017 lower
minor
BER threshold
exceeded

Procedure")
System
resource overload
1115 unable
to run test
LAPD link
protocol
failure
Remote alarm
indication
Transmission
error
Tab. 1.1
A30808-X3247-L420-2-7620

procedure
29
MMN:TRAU
Maintenance
FAULT
PROBLEM
SEV.
028 higher
minor
BER threshold
exceeded on
link A

Procedure")
029 higher
minor
BER threshold
exceeded on
link B

Procedure")
030 lower
minor
BER threshold
exceeded on
link A

Procedure")
031 lower
minor
BER threshold
exceeded on
link B

Procedure")
ISO probable
cause
1010 HW not
compatible
with internal
power
warning
HW configuration,cards
version
1031 TRAC is
not compatible with
actual configuration
minor
version
1036 BSCI
HW version
not valid for
PCM type
major
version
1038 MSCI
HW version
not valid for
PCM type
major
version
1103 PWR
offrequest
pending
warning
lock the related equipment
2002 unexpected TEI
critical
wrong LAPD parameters

: call TAC
Congestion
Tab. 1.1
30

procedure
A30808-X3247-L420-2-7620
Maintenance
MMN:TRAU
FAULT
PROBLEM
SEV.
1098 T interface message

lost
warning
call TAC
1083 Flash
EPROM must
be formatted
major
call TAC
1108 formatting flash

EPROM
major
ip appen after Lock

BSMS command
1109 invalid
file format
warning
call TAC
critical
sense point
minor
line interface card of the
alarmed PCM line
MSCI card (see

chp."3.4 MSCI")/
BSCIcard (see
chp."3.2 BSCI")
022 loss of
minor
frame alignment on link A
alarmed PCM line
MSCI card (see

chp."3.4 MSCI")/
BSCIcard (see
chp."3.2 BSCI")
023 loss of
minor
frame alignment on link B
alarmed PCM line
MSCI card (see

chp."3.4 MSCI")/
BSCIcard (see
chp."3.2 BSCI")
014 loss of
CRC alignment
major
alarmed PCM line
MSCI card (see

chp."3.4 MSCI")/
BSCIcard (see
chp."3.2 BSCI")
024 loss of
minor
CRC alignment on link A
alarmed PCM line
MSCI card (see

chp."3.4 MSCI")/
BSCIcard (see
chp."3.2 BSCI")
Corrupt data
Enclosure
open door
5001 open
door alarm
Loss of frame
013 loss of
frame alignment
Tab. 1.1
A30808-X3247-L420-2-7620

procedure
31
MMN:TRAU
Maintenance
FAULT
PROBLEM
SEV.
025 loss of
minor
CRC alignment on link B

alarmed PCM line
MSCI card (see

chp."3.4 MSCI")/
BSCIcard (see
chp."3.2 BSCI")
Out of
memory
1040 memory
not available
warning
call TAC
1041 mailbox
cannot be
created
warning
call TAC
1093 empty
RTE pool
restart
warning
call TAC
1094 emty
message pool
warning
call TAC
1113 memory
overflow
warning
call TAC
1016 AR
procedural
error
warning
call TAC
1017 RTE
interrupt loop
warning
call TAC
1018 standby
alignement
failed
warning
call TAC
1034 scheduler blocked
warning
call TAC
1035 initializa- warning

tion updated
call TAC
1043 initializa- warning

tion failure
call TAC
1046 file
system error
warning
call TAC
1049 internal
link failure
warning
call TAC
Software error
Tab. 1.1
32

procedure
A30808-X3247-L420-2-7620
Maintenance
FAULT
PROBLEM
MMN:TRAU
SEV.
1053 BSMS
procedural
error
major

Procedure")
1068 timer
cannot be set
warning
call TAC
1084 standby
not aligned
warning
call TAC
1099 RTE
processing
failure error
warning
call TAC
1107 BSCI
reset cause
warning
call TAC
1110 peripheral loading

error
warning
call TAC
1111 deleted
current task
warning
call TAC
1112 deleted
current init
function
warning
call TAC
Software
program
abnormally
terminated
Tab. 1.1
A30808-X3247-L420-2-7620

procedure
33
MMN:TRAU
34
Maintenance
A30808-X3247-L420-2-7620
Maintenance
MMN:TRAU
2 Tasklist
2.1
Preventive Maintenance
No preventive maintenance is required for the TRAU.
2.2
Cleaning the Rack
Dust and dirt can cause troubles to the hardware. Make sure that the contents of the TRAU rack is clean.
Use a dry brush to remove dust.
2.3
Replaceable Fuses
Electrical data of fuses that can be replaced are the following:
DATA
TYPE OF FUSE
Rated Current
10 A
Voltage Drop
200 mV
Breaking Capacity
500 A / 250 V / 50 Hz
Fuse Type
quick
Rated Voltage
250 Vmax
Tab. 2.1
Fuse Electrical Data
Mechanical dimensions are the same for all types of fuses: 5 mm (0.2)(diameter) x 20 mm
(0.79)(length)
A30808-X3247-L420-2-7620
35
MMN:TRAU
36
Maintenance
A30808-X3247-L420-2-7620
Maintenance
MMN:TRAU
3 Fault Clearance Procedures for Modules and

Interfaces
A30808-X3247-L420-2-7620
37
MMN:TRAU
38
Maintenance
A30808-X3247-L420-2-7620
Maintenance
3.1
MMN:TRAU
Diagnostic Procedure
This procedure describes the TRAU diagnostic procedure (refer to Appendix for more
details).
If both procedures are required at the same time, the first diagnostic is executed
followed by the second. Perform Test commands will be queued and executed sequentially.
If the BSMS is not redundant, the Perftest Trau command on the TRAC object is
accepted but the BSCI LoopTest will not be executed even if it has been included.
In the Test Report, the Proposed Repair Action field displays the BSCI cards and the
MSCI cards to be replaced.
The object under test be in Locked state (except TPWR module).
The
Start the Test
Enter the following command:

LMT tree:
Command:
PERFTEST TRAUE
Name:
TRAUE:<instance>
Attributes:
MORT = <pathname> where pathname=BSMS, TPWR, TRAC
Submit
Perftest TRAUE:NAME=<instance>,MORT=<pathname>;
It is possible to perform a test on the single module. The LMT tree is the
following:
LMT tree:
MANAGED-ELEMENT--> BSS-EQUIPMENT--> TRAUE --> module where

module=BSMS, TRAC, TPWR,
Command:
PERFTEST module
Name:
module:<instance>
Submit
Perftest module:NAME=<module>:<instance>;
For output detailed information
......"5.4
General
Diagnostic
Structure"
The System output depends on the fact that the test is activated on a faulty (Response
1) or working (Response 2) module.
A30808-X3247-L420-2-7620
39
MMN:TRAU
Maintenance
If the test has been activated on a faulty module

Otherwise return to the calling procedure.
h ... 2
h ... 3
System Response 1 - Faulty Module
START TEST FAIL: Go to the module replace procedure:

"3.2 BSCI", "3.4 MSCI", "3.7 TRAC", "3.5 PWRS"
If the test pass after the substitution of the faulty module
h ... 4
If the test failed repeat this test on the other module if there is a falty one
Otherwise call TAC
System Response 2 - Working Module
START TEST PASS: Exit to calling
Record the Reported Additional Info
The Additional Info fields report data useful to the factory to locate the faulty
component on the substituted board.
END
40
A30808-X3247-L420-2-7620
Maintenance
3.2
MMN:TRAU
BSCI
Module initialization is performed by Diagnostic execution.
If both BSCI copies must be replaced, repeat this procedure for each module one at a
time: install the second module only after the first has been successfully installed.
DO NOT EXECUTE!
The following operational sequence causes the TRAU crash:
1. BSMS0 providing service, BSMS1 hot standy-by (or vice versa);
2. Format BSCI stand-by;
3. Extract the BSCI active;
4. Start the software download with the remained copy by means of the LMTTRAU;
5. Once the first download is terminated and the second one is taking place (PH1 Software installation) insert the BSCI previously extracted.
If both the BSCI copies are out of service, they have to be replaced with new modules
and a Bring-Up procedure has to be executed (follow the instructions contained in
ITMN:TRAU manual).
Check the cables
2
b
If the alarm originates from Line Interface Card, as MSCI or BSCI, and is LOSS OF
alarm present, eer alarm present (BER), RAI alarm present, check the jumpers on
the faulty card are conforming the line impedence requirement (see "4.8 Jumpers
Setting"); as well as the cable connector concerning the line number in failure state is
correctly inserted and not damaged (see IMN:TRAU manual).
Lock the Module before Substitution

LMT tree:
MANAGED-ELEMENT--> BSS-EQUIPMENT--> TRAUE--> BSMS
Command:
LOCK BSMS
Name:
BSMS:<instance>
Submit
LOCK BSMS:NAME=BSMS:<instance>;
System Response:
The command is acknowledged (ACK)
A30808-X3247-L420-2-7620
41
MMN:TRAU
Maintenance
Important Notice
If the configuration is with modules powered by the TRAU power supply (PWRS)
If the configuration is with modules powered by the on board DC/DC converter
or in case of TRAU High Capacity
4
b
h ... 4
h ... 6
Lock the PWRS (Module Y) Corresponding to the Module to Replace

LMT tree:
MANAGED-ELEMENT--> BSS-EQUIPMENT--> TRAUE--> TPWR
Command:
LOCK TPWR
Name:
TPWR:<Y>
Attributes:
None
Submit
LOCK TPWR:NAME=TPWR:<Y>;
The modules connected to the PRWS-Y which has been switched off are put into the
"disabled" state.
System Response:
Pull down the OFF REQ Switch on the PWRS Module Y

If the PWRS module Y is not in the locked state, it will not switch off.
System Response:
SYSTEMINFOREPORT:NAME=PWRS:Y
INFORMATION IDENTIFIER=POWER KEYLOCK SWITCH OFF
The red LED on module PWRS is switched on, if power is switched off.
Replace the Module
Follow the recommended instructions (see "1.5 Module Replacement

Instructions") and according to the rack structure (see "4 Hardware Equipment")
Important Notice
42
h ... 8
h ... 10
A30808-X3247-L420-2-7620
Maintenance
MMN:TRAU
Pull up the OFF REQ Switch on PWRS Module Y

The modules connected to PWRS-Y (which has been switched on) remain in a
"disabled dependency" state because PWRS-Y is LOCKED.
System Response:
SYSTEM INFOREPORT:NAME=PWRS:Y
INFORMATIONIDENTIFIER:POWER KEYLOCK SWITCH ON
9
b
Unlock the PWRS (Module Y) Corresponding to the Module to Replace

LMT tree:
Command:
UNLOCK:TPWR
Name:
TPWR:<instance>
Attributes:
None
Submit
UNLOCK TPWR:NAME=TPWR:<instance>;
System Response:
A30808-X3247-L420-2-7620
43
MMN:TRAU
10
b
Maintenance
Start the Test on BSCI Module

LMT tree:
Command:
PERFTEST TRAUE
Name:
TRAUE:<instance>
Attributes:
MOT = BSMS:copy
Submit
Perftest TRAUE:NAME=TRAUE:<instance>,MOT=<BSMS:copy>;
following:
LMT tree:
MANAGED-ELEMENT--> BSS-EQUIPMENT--> TRAUE --> BSMS
Command:
PERFTEST BSMS
Name:
BSMS:<instance>
Submit
Perftest BSMS:NAME=BSMS<copy>;
11
b
If the start test pass.
h ... 11
If the test result is FAIL and another module is in alarmed status and not
replaced yet, reinsert the old replaced module, because its possible the fault is
in other part.
h ... END
Unlock the BSMS

LMT tree:
Command:
UNLOCK:BSMS
Name:
BSMS:<instance>
Attributes:
None
Submit
UNLOCK BSMS:NAME=BSMS:<instance>;
System Response:
END
44
A30808-X3247-L420-2-7620
Maintenance
3.3
MMN:TRAU
Module Check Procedure

Module xxx is either missing or not correctly inserted in the rack.
If the missing module is a PWRS, the whole nob_RIU file must be modified through the
IDF Editor Tool, in order to insert the missing inventory data, and then this new file
version must be downloaded with LMT-TRAU. (See "3.6 Remote Inventory Data".)
Check if module xxx is physically inserted in the rack
If module XXXX is missing and BSCI or MSCI type, switch off his power supply
unit
h ... 2
Otherwise
h ... 4
Insert module xxx in its slot in the rack
h ... 9
Insert the module carefully by sliding it along the rail, then push the levers - push
down the top levers and push up the bottom ones.
Important Notice
h ... 4
h ... 6
Only for the configuration with modules powered by the TRAU power supply

LMT tree:
Command:
LOCK TPWR
Name:
TPWR:<Y>
Attributes:
None
Submit
"disabled" state.
System Response:
A30808-X3247-L420-2-7620
45
MMN:TRAU
Maintenance

System Response:
Extract the module xxx from the rack
Pull the levers on the module - pull up the top levers and pull down the bottom
ones -, then extract the module.
Insert the same module xxx
Insert the module carefully by sliding it along the rail, then push the levers - push
down the top levers and push up the bottom ones.
Important Notice
h ... 9
h ... 11

System Response:
10
b

LMT tree:
Command:
UNLOCK TPWR
Name:
TPWR:<instance>
Attributes:
None
Submit
System Response:
46
A30808-X3247-L420-2-7620
Maintenance
11
b
MMN:TRAU
Start the Test on BSCI Module

LMT tree:
Command:
PERFTEST TRAUE
Name:
TRAUE:<instance>
Attributes:
MOT = BSMS:copy
Submit
following:
LMT tree:
Command:
PERFTEST BSMS
Name:
BSMS:<instance>
Submit

If the test result is FAIL
h ... END
h ...PROC: BSCI
h ...PROC: MSCI
END
A30808-X3247-L420-2-7620
47
MMN:TRAU
48
Maintenance
A30808-X3247-L420-2-7620
Maintenance
3.4
MMN:TRAU
MSCI
There is a particular condition for this module. Before replacing the module, it is necessary to verify if the MSCI is missing or not correctly inserted in the rack (Module Check
Procedure). If the alarm condition persists, try to replace the module with the procedure
described in this section.
Module initialization is performed by Diagnostic execution.
If both MSCI copies must be replaced, repeat this procedure for each module: install the
second module only after the first has been successfully installed.
If both the MSCI copies are out of service, they have to be replaced with new modules
and a Bring-Up procedure has to be executed (follow the instructions contained in
ITMN:TRAU manual).
Check the cables
2
b
If the alarm originates from Line Interface Card, as MSCI or BSCI, and is LOSS OF
alarm present, eer alarm present (BER), RAI alarm present, check the jumpers on
the faulty card are conforming the line impedence requirement (see "4.8 Jumpers
Setting"); as well as the cable connector concerning the line number in failure state is
correctly inserted and not damaged (see IMN:TRAU manual).

LMT tree:
Command:
LOCK BSMS
Name:
BSMS:<instance>
Submit
LOCK BSMS:NAME=BSMS:<instance>;
System Response:
Important Notice
A30808-X3247-L420-2-7620
h ... 4
h ... 6
49
MMN:TRAU
Maintenance
Only for the configuration with modules powered by the TRAU power supply

LMT tree:
Command:
LOCK TPWR
Name:
TPWR:<Y>
Attributes:
None
Submit
"disabled" state.
System Response:

System Response:
Replace the Module

Important Notice
50
h ... 8
h ... 10
A30808-X3247-L420-2-7620
Maintenance
MMN:TRAU
System Response:
9
b

LMT tree:
Command:
UNLOCK:TPWR
Name:
TPWR:<instance>
Attributes:
None
Submit
System Response:
10
b
Start the Test on MSCI Module

LMT tree:
Command:
PERFTEST TRAUE
Name:
TRAUE:<instance>
Attributes:
MOT = BSMS:copy
Submit
following:
LMT tree:
Command:
PERFTEST BSMS
Name:
BSMS:<instance>
Submit
h ... 11
in other part.
h ... END
A30808-X3247-L420-2-7620
51
MMN:TRAU
11
b
Maintenance
Unlock the BSMS

LMT tree:
Command:
UNLOCK:BSMS
Name:
BSMS:<instance>
Attributes:
None
Submit
UNLOCK BSMS:NAME=BSMS:<instance>;
System Response:
END
52
A30808-X3247-L420-2-7620
Maintenance
3.5
MMN:TRAU
PWRS
Module PWRS may be removed while power is off!
This procedure is not valid in case of TRAU High Capacity or in case of modules
powered by the on board DC/DC converter supply.
If the missing module is a PWRS, the whole nob_RIU file must be modified through the
IDF Editor Tool, in order to insert the missing inventory data, and then this new file
version must be downloaded with LMT-TRAU. (See "3.6 Remote Inventory Data".)

LMT tree:
Command:
LOCK TPWR
Name:
TPWR:<Y>
Attributes:
None
Submit
LOCK TPWR:<Y>;
"disabled" state.
System Response:
System Response:
Switch off the PWRS Module by pressing the red button. Use a pointed
tool such as a pencil
System Response:
1. All the lamps on the module switch off.
A30808-X3247-L420-2-7620
53
MMN:TRAU
Maintenance
Replace the Module

Switch on the PWRS module by pressing the black "OI" switch
System Response:
The red lamp on the module switches on.

System Response:
7
b

LMT tree:
Command:
UNLOCK TPWR
Name:
TPWR:<instance>
Attributes:
None
Submit
UNLOCK TPWR:NAME=<instance>;
System Response:
Update the RI file
Edit the RI-data by the IDF Editor Tool , update the Nob_Riu object file, export
and then download into BSC.
h ..."3.6 Remote
Inventory Data"
END
54
A30808-X3247-L420-2-7620
Maintenance
3.6
MMN:TRAU
Remote Inventory Data

With BR5.0 for each rack, the RLC provides one diskette which includes an inventory
data file that contains all inventory objects contained in the rack.
The file name is composed of the serial number of the rack (where / is replaced by _)
with the extension IDF.
For a new ob_RIU object installation, the system automatically provides the inventory
data after physical recovery of the module. No administration of inventory data is
required. Of course it makes sense to upload the latest version of the IDF for backup
purposes.
The following describes the procedure for handling the RI File.
Fig. 3.1
A30808-X3247-L420-2-7620
Delete nob_Record
55
MMN:TRAU
56
Maintenance
Fig. 3.2
Create nob_Record
Fig. 3.3
Edit nob_Record
A30808-X3247-L420-2-7620
Maintenance
MMN:TRAU
Fig. 3.4
Attach nob_RIU file
Fig. 3.5
Remove reduntant nob_RIUs
A30808-X3247-L420-2-7620
57
MMN:TRAU
58
Maintenance
Fig. 3.6
Export nob_RIUs
Fig. 3.7
Download of the nob_RIU file
A30808-X3247-L420-2-7620
Maintenance
MMN:TRAU
Functional Address
Functional Address Type
TPWR-0/0
M:PWRS
TPWR-0/1
M:PWRS
TPWR-1/0
M:PWRS
TPWR-1/1
M:PWRS
TPWR-2/0
M:PWRS
TPWR-2/1
M:PWRS
TPWR-3/0
M:PWRS
TPWR-3/1
M:PWRS
TRAU-RACK
R:TRAU
TRAU-SHELF-0
F:TRAU
TRAU-SHELF-1
F:TRAU
TRAU-SHELF-2
F:TRAU
TRAU-SHELF-3
F:TRAU
EARTHQUAKE-0
MK:EQ4
FIREPROT-0
MK:FG
TRAU-SHELF-0
F:TRAUV2
TRAU-SHELF-1
F:TRAUV2
TRAU-SHELF-2
F:TRAUV2
TRAU-SHELF-3
F:TRAUV2
MADPC-0
M:ADPC
MADPC-1
M:ADPC
MADPC-2
M:ADPC
MADPC-3
M:ADPC
EXTRAAD-0
EXTRAAD
EXTRAAD-1
EXTRAAD
EXTRAAD-2
EXTRAAD
EXTRAAD-3
EXTRAAD
Tab. 3.1
A30808-X3247-L420-2-7620
List of nob-RIUs for TRAU Standard
59
MMN:TRAU
Maintenance
GLOBAL ALARMS
POWER 0
10A
F
POWER 1
LOCAL
TERMINAL
10A
F
P
W
R
S
0
3
T
R
A
C
1
T
R
A
C
2
T
R
A
C
5
P
W
R
S
1
18
24
30 36 40 44 48 52 58 64
71
M
S
C
I
0
B
S
C
I
1
B
S
C
I
0
M
S
C
I
1
GLOBAL ALARMS
POWER 0
T
R
A
C
3
T
R
A
C
4
LOCAL
TERMINAL
10A
F
M
S
C
I
0
BSC
LINK
ALARM
B
S
C
I
1
B
S
C
I
0
M
S
C
I
1
T
R
A
C
3
T
R
A
C
4
T
R
A
C
5
T
R
A
C
0
T
R
A
C
1
T
R
A
C
2
18
24
30 36 40 44 48 52 58 64
GLOBAL ALARMS
POWER 0
10A
F
P
W
R
S
1
POWER 1
LOCAL
TERMINAL
LAMP
TEST
BSC
LINK
ALARM
P
W
R
S
0
T
R
A
C
0
T
R
A
C
1
T
R
A
C
2
18
24
30 36 40 44 48 52 58 64
M
S
C
I
0
B
S
C
I
1
B
S
C
I
0
M
S
C
I
1
GLOBAL ALARMS
POWER 0
10A
F
T
R
A
C
3
T
R
A
C
4
T
R
A
C
5
P
W
R
S
1
LOCAL
TERMINAL
10A
F
LAMP
TEST
BSC
LINK
ALARM
P
W
R
S
0
T
R
A
C
0
T
R
A
C
1
T
R
A
C
2
T
R
A
C
5
P
W
R
S
1
18
24
30 36 40 44 48 52 58 64
71
M
S
C
I
0
B
S
C
I
0
B
S
C
I
1
M
S
C
I
1
T
R
A
C
3
T
R
A
C
4
OPDS
Fig. 3.8
60
HI
71
CRITICALMAJOR MINOR
POWER 1
EF
71
CRITICALMAJOR MINOR
10A
F
BC
LAMP
TEST
CRITICALMAJOR MINOR
POWER 1
BSC
LINK
ALARM
T
R
A
C
0
10A
F
P
W
R
S
0
LAMP
TEST
CRITICALMAJOR MINOR
MN
TRAU Standard rack remote inventory files
A30808-X3247-L420-2-7620
Maintenance
MMN:TRAU
Functional Address
TRAU-RACK
R:TRAU
TRAU-SHELF-0
F:TRAU
TRAU-SHELF-1
F:TRAU
TRAU-SHELF-2
F:TRAU
TRAU-SHELF-3
F:TRAU
EARTHQUAKE-0
MK:EQ4
EXTRAAD
EXTRAAD
EQAD
MK:EQAD
FANB
FANB
ADC-0/0
M:ADC
ADC-0/1
M:ADC
ADC-0/2
M:ADC
ADC-0/3
M:ADC
ADC-0/4
M:ADC
ADC-0/5
M:ADC
ADC-0/6
M:ADC
ADC-0/7
M:ADC
Tab. 3.2
List of nob-RIUs for TRAU_H-C
TRAU number
Remote Inventory allocation
BC
EF
HI
MN
PQ
ST
VW
YZ
Tab. 3.3
Functional Address type
TRAUs numbering for Remote Inventory
The numbering of the TRAUs start from the top of the rack and left side of the shelf.
A30808-X3247-L420-2-7620
61
MMN:TRAU
Maintenance
T
FANB
Shelf 0
BC
EF
Remote inventory location
Shelf 1
HI
MN
Shelf 2
PQ
ST
Shelf 3
VW
Fig. 3.9
62
YZ
TRAU_H-C Remote Inventory file
A30808-X3247-L420-2-7620
Maintenance
MMN:TRAU
Upload the Iventory Data Table from the TRAU
The user must enter the "Upload idf file" command in order to create a copy of
the file on the local LMT.

LMT tree:
MANAGED-ELEMENT--> BSS EQUIPMENT--> TRAUE --> REMINV
Command:
UPLLIDF REMINV
Attributes:
NAME=REMINV:<Instance>
DESTDIR = <..\idf\upload>
FILE ="trau.idt"
OVERWRITE = <overwrite>
Submit
UPLLIDF REMINV:NAME=REMINV:<Instance>:DESTDIR=<../idf/upload>,FILE=trau.idt,OVERWRITE=YES;
Open the IDT File
The operations decribed below are implemented on the local LMT. (Refer to the
OGL:LMT for detailed instructions relating to the IDF Editor).
Start the IDF Editor from the LMT window and open the uploaded IDT file by
choosing "File --> Open" men.
To delete a nob_Record file
To create a new nob_Record file
To attach nob_RIU file
To edit the RI-data from the replaced Unit
Delete a nob_Record file
Select the S-Record, open the "Delete" dialog box by clicking the right mouse
button to delete the S-Record.
If no additional modifications are necessary
Create a new nob_Record file
Select the N-Record, open the "Create" dialog box by clicking the right mouse
button and create a new nob_RIU object.
A30808-X3247-L420-2-7620
h ... 3
h ... 4
h ... 5
h ... 6
......Fig. 3.1
h ... 7
......Fig. 3.2
h ... 7
63
MMN:TRAU
5
b
Maintenance
Attach nob_RIU file to actually loaded IDF or IDT

To create a new nob_RIU file coming from the RLC disk, enter the following
command:
Command: <File: Attach>
Input:
<NOB file to be attached>
Result:
The inventory objects of the <NOB file to be attached> are

attached to the loaded IDF or IDT. The number of attached
objects is displayed after command execution.
......Fig. 3.4
The nob_RIU records are shown in bold letters.
h ... 7
Edit the RI-data from the replaced Unit
Start the IDF-Editor and open the uploaded IDT file by choosing <File: Open>.
The following window appears, where all the RI-records are seen. The nob_RIU
records are shown in bold letters.
Move the mouse cursor to the I-record to be changed and press the right
mouse-button. The edit functionality is enabled.
......Fig. 3.3
Remove all redundant nob_RIUs
After importing IDFs coming from the RLC or after replacing a card that originally was a nob_RIU against another card that now has inventory data on
board, the same board would be reported twice.

Command: <File: Remove nob_RIUs>
Input:
8
b
<none>
......Fig. 3.5
Export nob_RIU file

Command: <Export: NOB>
Input:
<new filename>
(default filename is kept from the "SalesUniqueName" field of the
IDF)
Result:
nob_RIU part of modified IDF/IDT is saved for further proceeding
A copy of this NOB file is saved in the c:\LMT_root\..\idf\download directory,

where it can be accessed only by the LMT during the "Download nob_RIU"
command.
64
......Fig. 3.6
A30808-X3247-L420-2-7620
Maintenance
MMN:TRAU
Download of the nob_RIU file
This step must be executed if the operator wants to transfer the file modified on
the local LMT to the TRAU.

LMT tree:
MANAGED-ELEMENT--> BSS EQUIPMENT--> TRAUE --> REMINV
Command:
DNLIDFD REMINV
Attributes:
NAME=REMINV:<Instance>
SRCDIR = <..\idf\download>
Submit
DNLIDF REMINV:NAME=REMINV<Instance>:SRCDIR=<..\idf\download>;
......Fig. 3.7
END
A30808-X3247-L420-2-7620
65
MMN:TRAU
66
Maintenance
A30808-X3247-L420-2-7620
Maintenance
3.7
MMN:TRAU
TRAC
Module initialization is performed by the Diagnostic execution.
i
i
The currently examined module will be indicated as Y in this procedure. Start with Y = 0
To replace one or more TRAC modules while the TRAU is running in connection with
the BSC handling telephone service, see the Chap. 3.17 on the ITMN:TRAU manual.

LMT tree:
MANAGED-ELEMENT--> BSS-EQUIPMENT--> TRAUE--> TRAC
Command:
LOCK TRAC
Name:
NAME=TRAC:<instance>
Submit
Lock TRAC:NAME=TRAC:<instance>;
System Response:
Replace the Module

A30808-X3247-L420-2-7620
67
MMN:TRAU
3
b
Maintenance
Start the Test on TRAC Module

LMT tree:
Command:
PERFTEST TRAUE
Name:
TRAUE:<instance>
Attributes:
MOT = TRAC:copy
Submit
Perftest TRAUE:NAME=TRAUE:<instance>,MOT=<TRAC:copy>;
following:
LMT tree:
MANAGED-ELEMENT--> BSS-EQUIPMENT--> TRAUE --> TRAC
Command:
PERFTEST TRAC
Name:
TRAC:<instance>
Submit
Perftest TRAC:NAME=TRAC<copy>;
4
b
h ... 4
in other part.
h ... END
Unlock the Module after Substitution

LMT tree:
MANAGED-ELEMENT--> BSS-EQUIPMENT--> TRAUE--> TRAC
Command:
UNLOCK TRAC
Name:
TRAC:<instance>
Attributes:
None
Submit
UNLOCK TRAC:NAME=TRAC:<instance>;
System Response:
68
A30808-X3247-L420-2-7620
Maintenance
MMN:TRAU
Update the RI file
Edit the RI-data by the IDF Editor Tool , update the Nob_Riu object file, export
and then download into BSC.
h ..."3.6 Remote
Inventory Data"
END
A30808-X3247-L420-2-7620
69
MMN:TRAU
70
Maintenance
A30808-X3247-L420-2-7620
Maintenance
MMN:TRAU
4 Hardware Equipment
The TRAU rack houses up to four TRAU subracks, each processing 120 channels. The
TRAU configuration is modular on the basis of the number of transcoders that may be
installed.
Fig. 4.1 shows the TRAU rack fully equipped and the single module location inside the
subracks.
They are:
1 to 4 TRAU subracks (position BC, EF, HI, MN)

1 to 4 TRAU Fuse and Alarm Panel (TFAP) (position A, D, G, L)
one LAMP Panel ( position T)
Fans unit (position H).
Fig. 4.2 shows the TRAU in fire resistance cabinet.

Fig. 4.3 and Fig. 4.4 show the new high capacity version of the TRAU rack.
A30808-X3247-L420-2-7620
71
MMN:TRAU
Maintenance
CRITICALMAJOR MINOR
POWER 1
LOCAL
TERMINAL
10A
F
P
W
R
S
0
3
T
R
A
C
2
T
R
A
C
5
P
W
R
S
1
18
24
30 36 40 44 48 52 58 64
71
M
S
C
I
0
B
S
C
I
0
B
S
C
I
1
GLOBAL ALARMS
POWER 0
M
S
C
I
1
T
R
A
C
5
P
W
R
S
1
18
24
30 36 40 44 48 52 58 64
71
B
S
C
I
0
B
S
C
I
1
GLOBAL ALARMS
POWER 0
T
R
A
C
3
T
R
A
C
4
LAMP
TEST
BSC
LINK
ALARM
M
S
C
I
1
T
R
A
C
0
T
R
A
C
1
T
R
A
C
2
T
R
A
C
5
P
W
R
S
1
18
24
30 36 40 44 48 52 58 64
71
M
S
C
I
0
B
S
C
I
0
B
S
C
I
1
GLOBAL ALARMS
POWER 0
10A
F
T
R
A
C
3
T
R
A
C
4
LAMP
TEST
LOCAL
TERMINAL
10A
F
BSC
LINK
ALARM
M
S
C
I
1
T
R
A
C
0
T
R
A
C
1
T
R
A
C
2
T
R
A
C
5
P
W
R
S
1
18
24
30 36 40 44 48 52 58 64
71
M
S
C
I
0
HI
CRITICALMAJOR MINOR
POWER 1
EF
CRITICALMAJOR MINOR
LOCAL
TERMINAL
10A
F
T
R
A
C
2
M
S
C
I
0
BC
LAMP
TEST
BSC
LINK
ALARM
T
R
A
C
1
POWER 1
P
W
R
S
0
T
R
A
C
4
T
R
A
C
0
10A
F
T
R
A
C
3
CRITICALMAJOR MINOR
LOCAL
TERMINAL
10A
F
P
W
R
S
0
M
S
C
I
1
T
R
A
C
1
POWER 1
BSC
LINK
ALARM
T
R
A
C
0
10A
F
P
W
R
S
0
LAMP
TEST
GLOBAL ALARMS
POWER 0
10A
F
B
S
C
I
0
B
S
C
I
1
T
R
A
C
3
T
R
A
C
4
MN
O
OPDS
Fig. 4.1
72
Front view of the TRAU rack
A30808-X3247-L420-2-7620
Maintenance
MMN:TRAU
GLOBAL ALARMS
POWER 0
10A
F
POWER 1
LOCAL
TERMINAL
10A
F
P
W
R
S
0
3
T
R
A
C
0
T
R
A
C
1
18
24
LAMP
TEST
CRITICALMAJOR MINOR
M
S
C
I
0
BSC
LINK
ALARM
B
S
C
I
0
M
S
C
I
1
T
R
A
C
4
T
R
A
C
5
P
W
R
S
1
30 36 40 44 48 52 58 64
71
T
R
A
C
2
B
S
C
I
1
CRITICALMAJOR MINOR
POWER 1
LOCAL
TERMINAL
10A
F
BSC
LINK
ALARM
M
S
C
I
1
P
W
R
S
0
T
R
A
C
0
T
R
A
C
1
T
R
A
C
2
T
R
A
C
5
P
W
R
S
1
18
24
30 36 40 44 48 52 58 64
71
M
S
C
I
0
B
S
C
I
0
LOCAL
TERMINAL
10A
F
T
R
A
C
3
T
R
A
C
4
BSC
LINK
ALARM
M
S
C
I
1
T
R
A
C
0
T
R
A
C
1
T
R
A
C
2
T
R
A
C
5
P
W
R
S
1
18
24
30 36 40 44 48 52 58 64
71
M
S
C
I
0
B
S
C
I
0
B
S
C
I
1
GLOBAL ALARMS
POWER 0
10A
F
T
R
A
C
3
T
R
A
C
4
HI
LAMP
TEST
CRITICALMAJOR MINOR
POWER 1
LOCAL
TERMINAL
10A
F
BSC
LINK
ALARM
M
S
C
I
1
P
W
R
S
0
T
R
A
C
0
T
R
A
C
1
T
R
A
C
2
T
R
A
C
5
P
W
R
S
1
18
24
30 36 40 44 48 52 58 64
71
M
S
C
I
0
B
S
C
I
0
B
S
C
I
1
T
R
A
C
3
T
R
A
C
4
OPDS
Fig. 4.2
EF
LAMP
TEST
CRITICALMAJOR MINOR
POWER 1
P
W
R
S
0
B
S
C
I
1
GLOBAL ALARMS
POWER 0
10A
F
BC
LAMP
TEST
GLOBAL ALARMS
POWER 0
10A
F
T
R
A
C
3
MN
Front view of the TRAU rack in fire resistance cabinet
A30808-X3247-L420-2-7620
73
MMN:TRAU
Fig. 4.3
74
Maintenance
TRAU-High Capacity version rack
A30808-X3247-L420-2-7620
Maintenance
Fig. 4.4
MMN:TRAU
TRAU-HC module with two TRAUs
A30808-X3247-L420-2-7620
75
MMN:TRAU
76
Maintenance
A30808-X3247-L420-2-7620
Maintenance
4.1
MMN:TRAU
Rack Connections for TRAU standard
Fig. 4.5
A30808-X3247-L420-2-7620
RGB
PM2
PP1
PP0
to GND
-48 +to
-48
LW6
GW6
LW3 GW3
to GND
Temp. Sensors
DW6
AW6
DW3 AW3
PM3
The Fig. 4.5 shows the rack connections blocks.
TRAU Rack Cabling Access Panel
77
MMN:TRAU
Maintenance
4.2
Rack Connections for TRAU_High-Capacity

The shows the rack connection blocks for the TRAU_High-Capacity.
Fig. 4.6
TRAU-HC top view: Rach Cabling Access Panel (RCAP)
TRAU backpanel
(PCM0 connector)
RCAP connector
module 0 - TRAU 0
LINK 0
module 1 - TRAU 2
LINK 2
module 2 - TRAU 4
LINK 4
module 3 - TRAU 6
LINK 6
Tab. 4.1
Left TRAUs PCM lines
TRAU backpanel
(PCM1 connector)
module 0 - TRAU 1
LINK 1
module 1 - TRAU 3
LINK 3
module 2 - TRAU 5
LINK 5
Tab. 4.2
78
RCAP connector
Right TRAUs PCM lines
A30808-X3247-L420-2-7620
Maintenance
MMN:TRAU
TRAU backpanel
(PCM1 connector)
module 3 - TRAU 7
Tab. 4.2
RCAP connector
LINK 7
Right TRAUs PCM lines
TRAU DC-panel
(REM-AL-L
connector)
RCAP connector
module 0 - TRAU 0
AW 0
module 1 - TRAU 2
AW 2
module 2 - TRAU 4
AW 4
module 3 - TRAU 6
AW 6
Tab. 4.3
Remote Alarms lines of the TRAUs_Left
TRAU DC-panel
(REM-AL-R
connector)
module 0 - TRAU 1
AW 1
module 1 - TRAU 3
AW 3
module 2 - TRAU 5
AW 5
module 3 - TRAU 7
AW 7
Tab. 4.4
4.3
RCAP connector
Remote Alarms lines of the TRAUs_Right
Fuse and Alarm Panel for TRAU_standard

The TRAU subsystem allows for the display of the notified alarms. Fig. 4.7 shows the
complete layout of the alarm and fuse panel.
Each alarm panel contains the connectors for the LMT, the alarm relays which drive the
Remote Alarm indication, the four alarm LEDs, and the pushbutton for LEDs testing. The
alarms are generated by the BSCI and ORid to drive the LEDs.
Three summary LEDs represent the alarm status (Minor, Major, Critical) and display the
alarm type. A summary of the LED layout is shown in Fig. 4.7.
These LEDs represent, in an OR logic way, the possible alarm statuses. They are the
sum (OR) of all the TRAU alarms, i.e. each LED shows the OR of the TRAU alarms
which are at a certain severity level.
A30808-X3247-L420-2-7620
79
MMN:TRAU
Maintenance
The switching on of one of these LEDs signals a minor, major or critical severity alarm
(refer to chapter "5 Appendix" for more details):
a RED LED for a CRITICAL alarm,
a ORANGE LED for a MAJOR alarm,
a YELLOW LED for a MINOR alarm.
The fourth LED displays whether the LAPD link through which the BSC controls the
TRAU is in a faulty status.
10A
F
POWER 1
CRITICAL
4.4
MAJOR
MINOR
BSC
LINK
ALARM
LOCAL
TERMINAL
10A
F
Fig. 4.7
LAMP
TEST
GLOBAL ALARMS
POWER 0
TRAU_Standard Fuse and Alarm Panel
Temperature Sensor
Two temperature sensors are mounted on the top of the rack (RCAP): each one of them
controls a copy of the Power Suppliers.
When the temperature increases, the temperature sensor contact closes and the relevant supplier goes out of service (OFF).
If during normal operations, the equipment internal temperature reaches the 72C
threshold, the Copy 0 temperature sensor contacts close and the suppliers of the relevant copy go out of service (OFF).
Copy 0
TS 72C close
Suppliers OFF
Copy 0 will restore (opening of the temperature sensor (TS) contacts and suppliers
returning in service (ON)) when the temperature reaches the 63C threshold.
If the temperature reaches 78C, the Copy 1 temperature sensor contacts close and the
suppliers of the relevant copy go out of service (OFF).
Copy 1
80
TS 78C close
Suppliers OFF
A30808-X3247-L420-2-7620
Maintenance
MMN:TRAU
At this point there is no power supply in the equipment and Copy 0 and Copy 1 will
restore (opening of temperature sensor (TS) contacts and suppliers returning in service
(ON)) when the temperature returns to 63C threshold.
Each Temperature Sensor is tested singularly by means of a heating board adjusted to:
72C
78C
63C
for Copy 0 power suppliers

for Copy 1 power suppliers
the contact reopens
A tester can be used to verify whether the contact is open or closed.
4.5
Lamp Panel
On the top of the TRAU rack, three global lamps indicate that an alarm condition exists
on any of the installed TRAU subracks. Fig. 4.8 shows the TRAU lamps panel.
MINOR
ALARM
Fig. 4.8
A30808-X3247-L420-2-7620
MAJOR
ALARM
CRITICAL
ALARM
Lamp Panel
81
MMN:TRAU
Maintenance
4.6
DC-Panel of the TRAU-HC

The philosophy of the lamp panel is the same of the TRAU_Standard (see 4.3).
The only difference is that the power 0 and power 1 fuses are been replaced by two
magnetothermic switches (as shown in Fig. 4.9) that feed the frame below.
Fig. 4.9
82
DC-Panel of the TRAU-HC
A30808-X3247-L420-2-7620
Maintenance
4.7
i
MMN:TRAU
Power Supply
This section is not valid in case of the TRAU High Capacity
On the power panel three LEDs, a key and two switches (red and black) are provided.
1
IS
OS
AL
ON
OFF
REQ.
RED
BLACK
M1 +12.3
M2 +5.3
M3 PPW
ON
Fig. 4.10
A30808-X3247-L420-2-7620
TRAU Power Supply Module Panel
83
MMN:TRAU
Maintenance
Explanation of the LEDs displayed in Fig. 4.10 (pos. 1 and 3):
"IS" green LED is on whenever the power supply is on and the provided voltage is
correct;
"OS AL" red LED will switch on in the event of an "out of service" or anomaly in the
power supply;
"ON" green LED is on whenever the power supply is on.
The OFF REQ key controls the on/off status of the regulated output voltages, and must
be in the upper position to allow the system to work. It must be set in the lower position
to obtain any "out of service" request.
Explanation of the buttons displayed in Fig. 4.10 (pos 2):
The red button controls the magnetic switch, and must be pressed to interrupt the
primary power supply; to avoid undesirable manual interruptions, the user must use
a pointed device to switch the red button.
The black button must be pressed to switch on the primary power.
Normal power control (emergency breaker in ON position):

To switch on the power supply, the following procedure must be performed:
1. Set OFF REQ key in the upper position. The IS and ON LEDs will switch on and
OS AL led will switch off.
To switch off the power supply, the following procedure must be performed:
1. Set the OFF REQ key in down position. The OS AL led will switch on, and the IS
and the ON leds will switch off.
Emergency power control:
To switch on the power supply, the following procedure must be performed:
1. Press the black button. The OS AL LED will switch on.
2. Set the OFF REQ key in the upper position. The IS and ON LEDs will switch on and
the OS AL LED will switch off.
To switch off the power supply, the following procedure must be performed:
1. Set the OFF REQ key in down position;
2. Press the red switch. The OS ALL LED will switch off.
Tab. 4.5 summarizes the anomaly conditions notified by the setting of the LEDs.
MEANING
LEDS CONDITIONS
IS
ON
Out of service (manual off request), or

Out range of the input battery, or
Output below the nominal voltage, or
Output over the nominal voltage
OFF
ON
OFF
Emergency breake in the off condition

(manual or automatic)
OFF
OFF
OFF
Output overload or short circuit
OFF
ON
ON
Tab. 4.5
84
ALL/OS
Anomaly Conditions Notified by LEDs
A30808-X3247-L420-2-7620
Maintenance
4.8
4.8.1
MMN:TRAU
Jumpers Setting
BSCI Module
SZ8
SZ9
SZ7
SZ11
SZ10
SZ12
SZ2
SZ4
SZ20
SZ13
SZ14
SZ15
SZ19
SZ17
SZ16
SZ18
SZ5
SZ3
SZ6
SZ21
SZ1
TR7
TR8
TR9
Fig. 4.11
Jumpers Setting for BSCIB Module (75 ohm) (S30861-Q352-X1)
A30808-X3247-L420-2-7620
85
MMN:TRAU
Maintenance
Note 1:
Note 2:
Note 3:
The configuration of jumpers SZ7 to SZ18 is related to the 75 ohm

unbalanced coax cable physical interface. In the event of a 120 ohm
balanced interface, the configuration must be inverted (OPEN <->
CLOSED) except for SZ12 and SZ15. Jumper TR8-TR9 is soldered.
The last type of this module, BSCIV3 (S30861-Q352-X101), is mandatory in CEE countries instead of BSCIB (S30861-Q352-X1), which can
be used only in EXTRA CEE countries. BSCIV3 (S30861-Q352-X101)
has SZ21 positioned in a vertical way, rather than horizontal.
On the BSCI module front there are two plugs to monitor the PCM
Lines. Each line has a monitoring point on both the transmitting side and
the receiving side.
B
S
C
I
Fig. 4.12
RX
TX
BSCI PCM Monitoring Points
PCM Line 0
PCM Line 1
Tab. 4.6
86
TX
RX
Description of BSCI Monitoring Points
A30808-X3247-L420-2-7620
Maintenance
MMN:TRAU
SZ8
SZ9
SZ7
SZ11
SZ10
SZ12
SZ2
SZ4
SZ20
SZ13
SZ14
SZ15
SZ19
SZ17
SZ16
SZ18
SZ5
SZ3
SZ6
SZ21
SZ1
TR7
TR8
TR9
Fig. 4.13
Jumpers Setting for BSCIV3 Module (75 ohm) (S30861-Q352-X101)
A30808-X3247-L420-2-7620
87
MMN:TRAU
Maintenance
SZ1001
SZ1002
SZ1000
SZ1003
SZP1
SZOTP
SZPLL
SZD1
SZMS1
SZ4
SZD3
SZ3
3 2 1
TR1
SZ6
SZD2
SZ5
SZ1
SZ2
SZ10
TR4
1 2 3
SZ9
SZ12
SZ11
SZ7
SZ8
SZCPU
Fig. 4.14
88
Jumpers Setting for BSCIV4 Module (75 Ohm) (S30861-Q415-X1)
A30808-X3247-L420-2-7620
Maintenance
MMN:TRAU
SZ1001
SZ1003
SZ1002
SZ1000
SZP1
SZOTP
SZPLL
SZD1
SZMS1
SZ4
SZD3
SZ3
3 2 1
TR1
SZ6
SZD2
SZ5
SZ1
SZ2
SZ10
TR4
SZ9
1 2 3
SZ12
SZ11
SZ7
SZ8
SZCPU
Fig. 4.15
Jumpers Setting for BSCIV4 module (120 Ohm) (S30861-Q415-X1)
A30808-X3247-L420-2-7620
89
MMN:TRAU
Maintenance
SZ1001
SZ1002
SZ1000
SZ1003
SZP1
SZOTP
SZPLL
SZD1
SZMS1
SZ4
SZD3
3 2
SZ3
TR1
SZ6
SZD2
SZ5
SZ1
SZ2
SZ10
1 2
SZ9
TR4
SZ12
SZ11
SZ7
SZ8
SZCPU
Fig. 4.16
90
Jumpers Setting for BSCIV4 Module (100 Ohm) (S30861-Q415-X1)
A30808-X3247-L420-2-7620
Maintenance
MMN:TRAU
Note 1: Configuration 1: BSCIV4 powered by the TRAU Power Supply

Modules
SZ1000
OPEN
SZ1001
CLOSED
SZ1002
CLOSED
SZ1003
OPEN
SZP1
CLOSED
Configuration 2: BSCIV4 powered by the on board DC/DC
Converter Power Supply (it is represented in the figure)
SZ1000
CLOSED
SZ1001
OPEN
SZ1002
OPEN
SZ1003
CLOSED
SZP1
OPEN
This configuration must be used only in respect of the following
conditions:
a) TRAU shelf in last version (Front Door)
b) TRAU shelf equipped with all TRACV5 cards
c) Both the MSCI copies must be MSCIV2 cards and must be
strapped as described in Configuration 2 of Note 1 of MSCIV2
jumpers setting description.
If these conditions are matched, then the TRAU Power Supply
Modules must not be inserted in their relative slots and both the
BSCIV4 copies must be strapped with Configuration 2.
Note 2: The BSCIV4 is mandatory for USA
A30808-X3247-L420-2-7620
91
MMN:TRAU
Maintenance
4.8.2
MSCI Module
SZ8
SZ7
SZ9
SZ5
SZ4
SZ6
SZ11
SZ10
SZ12
SZ14
SZ13
SZ15
SZ20
SZ19
SZ21
SZ17
SZ16
SZ18
1
SZ1
2 3
TR16
SZ40
SZ23
SZ22
SZ24
SZ41
SZ26
SZ25
SZ27
SZ32
SZ31
SZ33
SZ29
SZ28
SZ30
SZ35
SZ34
SZ36
TR14
TR13
SZ38
SZ37
SZ39
Fig. 4.17
92
TR15
Jumper Setting for MSCI Module (S30861-Q351-X1)
A30808-X3247-L420-2-7620
Maintenance
Note 1:
Note 2:
MMN:TRAU
The configuration of jumpers SZ4 to SZ39 is related to the 75 ohm

unbalanced coax cable physical interface. In the event of 75 ohm
balanced, SZ9, SZ15, SZ21, SZ27, SZ33, SZ39 must be inverted
(CLOSED -> OPEN). In the event of 120 ohm balanced interface, the
configuration must be inverted (OPEN <-> CLOSED) except for SZ6,
SZ12, SZ18, SZ24, SZ30 and SZ36. Jumper TR13-TR14 is soldered.
On the MSCI module front, there are six plugs to monitor the PCM
Lines. Each line has a monitoring point on both the transmitting side and
the receiving side.
M
S
C
I
Fig. 4.18
TX
RX
RX
TX
TX
RX
RX
TX
TX
RX
RX
TX
MSCI PCM MonitoringPoints
Not used
PCM Line 0
PCM Line 1
PCM Line 2
PCM Line 3
Not used
Tab. 4.7
A30808-X3247-L420-2-7620
Description of MSCI Monitoring Points
93
MMN:TRAU
Maintenance
SZ2
SZ31
SZ33
SZ1
SZ34
1
SZ15
SZ3
SZ19
SZ4
SZ35
SZ24
SZ5
SZ23
SZ16
SZ6
SZ20
SZ7
SZ26
SZ8
SZ25
SZ17
SZ9
SZ21
SZ32
SZ10
SZ28
SZ11
SZ27
SZP1
1
SZ18
SZ12
SZ22
SZ13
SZ30
Fig. 4.19
94
SZ29
SZ14
Jumpers Setting for MSCIV2 Module (75 Ohm) (S30861-Q416-X1)
A30808-X3247-L420-2-7620
Maintenance
MMN:TRAU
SZ2
SZ31
SZ33
SZ1
SZ34
1 2
SZ15
SZ3
SZ19
SZ4
SZ35
SZ24
SZ5
SZ23
1 2
SZ16
SZ6
SZ20
SZ7
SZ26
SZ8
SZ25
1 2
SZ17
SZ9
SZ21
SZ32
SZ10
SZ28
SZ11
SZ27
SZP1
1 2
SZ18
SZ12
SZ22
SZ13
SZ30
Fig. 4.20
SZ29
SZ14
A30808-X3247-L420-2-7620
95
MMN:TRAU
Maintenance
SZ2
SZ31
SZ33
SZ1
SZ34
1 2 3
SZ15
SZ3
SZ19
SZ4
SZ35
SZ24
SZ5
SZ23
1 2 3
SZ16
SZ6
SZ20
SZ7
SZ26
SZ8
SZ25
1 2 3
SZ17
SZ9
SZ21
SZ32
SZ10
SZ28
SZ11
SZ27
SZP1
1 2 3
SZ18
SZ12
SZ22
SZ13
SZ30
Fig. 4.21
96
SZ29
SZ14
A30808-X3247-L420-2-7620
Maintenance
MMN:TRAU
Note 1: Configuration 1: MSCIV2 powered by the TRAU Power Supply

Modules
SZ1
CLOSED
SZ2
CLOSED
SZ31
CLOSED
SZ33
OPEN
SZ34
OPEN
Configuration 2: MSCIV2 powered by the on board DC/DC
Converter Power Supply (it is represented in the figure)
SZ1
OPEN
SZ2
OPEN
SZ31
OPEN
SZ33
CLOSED
SZ34
CLOSED
This configuration must be used only in respect of the following
conditions:
a) TRAU shelf in last version (Front Door)
b) TRAU shelf equipped with all TRACV5 cards
c) Both the BSCI copies must be BSCIV4 cards and must be
strapped as described in Configuration 2 of Note 1 of BSCIV4
jumpers setting description.
If these conditions are matched, then the TRAU Power Supply
Modules must not be inserted in their relative slots and both the
MSCIV2 copies must be strapped with Configuration 2.
Note 2: The MSCIV2 is mandatory for USA
A30808-X3247-L420-2-7620
97
MMN:TRAU
Maintenance
4.8.3
TRAC Module
TR33-TR34
TR4-TR1
JB 1 5 JC
TR30
JA 1
TR8-TR5
5 1
TR31
TR11-TR9
JD 1 5 JF
TR38
5 1
TR19-TR17
TR39
1
2
TR16-TR13
TR40
3
JE 1 5 JH
5 1
TR28-TR25
5 JG
TR32
TR37
TR21-TR24
Fig. 4.22
Jumpers Setting for TRAC Module (S30861-Q350-X1)

Note 1:
98
Jumpers TR4-TR1, TR8-TR5, TR11-TR9, TR16-TR13, TR19-TR17,

TR21-TR24, TR28-TR25, TR33-TR34 are made with a tin drop
A30808-X3247-L420-2-7620
Maintenance
MMN:TRAU
SZ1
SZ3
SZ6
SZ5
SZ2
SZ4
Fig. 4.23
Jumpers Setting for TRACV3 Module (S30861-Q354-X101)
A30808-X3247-L420-2-7620
99
MMN:TRAU
Maintenance
SZ2
SZ9
SZ3
SZ1
SZ7
SZ6
SZ10
SZ12
SZ13
SZ4
SZ5
Fig. 4.24
100
Jumpers Setting for TRACV5 Module (S30861-Q413-X1 up to Issue 6)
A30808-X3247-L420-2-7620
Maintenance
MMN:TRAU
SZ2
SZ9
SZ3
SZ1
SZ7
SZ6
SZ10
SZ12
SZ13
SZ4
SZ5
Fig. 4.25
Jumpers Setting for TRACV5 Module (S30861-Q413-X1 from Issue 7)
A30808-X3247-L420-2-7620
101
MMN:TRAU
102
Maintenance
A30808-X3247-L420-2-7620
Maintenance
MMN:TRAU
5 Appendix
5.1
Alarm Handling
An alarm notifies the Radio Commander (RC) of fault conditions. Alarms can occur at
any point in the TRAU subsystem provided with a hardware (HW) or software (SW)
detector to recognize the fault, and with an event-generating software.
Following the general alarm philosophy, alarm reports specify:
the fault severity level;

the anomaly type.
In general, the principle applies when an error is still detectable. Whenever this condition
disappears (presumably following the intervention of a user), the TRAU detects it and
communicates an end-of-alarm event to the BSC and to the LMT; however, up to then
the malfunction is present and detectable. In the TRAU, two types of malfunction deviate
from this principle:
processing-type errors (generally due to software errors) which, although having

variable severity levels which at times result in very serious effects, are not easy to
locate.
minor malfunctions, which generate warning alarms and do not require discussion
about alarm removal.
The TRAU spontaneously informs the BSC and the LMT of any change of status and
configuration concerning its devices.
The TRAU subsystem provides three different severity levels:
Critical
Major
Minor
The Critical level is reached when the subsystem is out of order.

The Major level specifies the presence in the subsystem of a fault that makes the
subsystem itself drop significantly. The immediate intervention of a user is required to
clear the fault and resume service.
The Minor level specifies that the fault in the subsystem does not lower its functionality
(for instance, a backup module is now working). In other words, a section of the
subsystem is lowered, but it is still able to work without effect on the service. User intervention is required.
The severity level of the FER emitted by object instance of BSMS, TRAC, TPWR where,
as consequence of the fault, the object goes into a disabled state can be set by the operator.
The default severities are:
BSMS -> MAJOR

TRAC -> MINOR
TPWR -> MAJOR
Five types of anomalies are defined depending on the functional part of the subsystem
that is actually damaged:
A30808-X3247-L420-2-7620
Quality of Service
103
MMN:TRAU
Maintenance
Communication
Equipment
Processing
Environmental
A Quality of Service alarm refers to a service downgrading.

Communication alarms refer to the procedures/processes that are devoted to the
communication exchange between subsystem elements. Generally speaking, the
following failures are taken into account:
system link LAPD faults;

network connection faults that do not originate from the hardware.
Equipment alarms refer to hardware failures. Alarms of this kind are detected and analized by the maintenance procedures in order to clear them by means of the provided
redundancy. In this case, the alarm display reports the generating function together with
the related severity.
With each of these types of anomalies software tails (System Tails) are associated that
contain a short outline description of various error messages relating to the error
concerned.
Processing alarms are associated with software errors.
Environmental alarm are associated with a condition relating to an enclosure in which
the equipment resides.
5.2
Alarm Reporting
Every system of the PLMN network reports any malfunctions occurring during its operation to a local operator and to a remote control center (OMT). These malfunctions
include a large variety of types, from hardware faults to recurrent software errors and
from air condition faults to back-up battery faults.
104
A30808-X3247-L420-2-7620
Maintenance
MMN:TRAU
CENTRALIZED DATA BASE
LOCAL DATA BASE

ERROR COUNTER
TABLES
DEFENCE ACTION
DESCRIPTION
TABLES
FAULT
COUNTER_DESCR.
LOW_THRESH
UP_THRESH
*ERROR COUNTER
*IMMEDIATE_ACT
*LOW_THRESH_ACT
*UP_THRESH_ACT
CALL
DETECTOR
ERROR_TYPE
PROBABLE_CAUSE
SEVERITY
SM_ACTIV
(none, disable, recover)
ERROR_COUNTER
UP_THRESH
ERROR
ERROR
COLLECTOR
PROCESSOR
OUTPUT
MESSAGE
I/O
MESSAGE
MESS A
CLASS_ID
ME_ID
ERROR_ID
ADDITIONAL_INFO
ORIGINATOR
Fig. 5.1
MESS A+
ACTIVE
ALARM
LIST
Alarm Event Handling Overview

The TRAU system is a network element of the PLMN and can be remotely controlled via
the RC, therefore the Alarm Reporting activity, by means of which the TRAU keeps RC
informed on its own malfunction-related events, plays a key role. In the TRAU, the Alarm
Reporting function has been developed, in compliance with the applicable GSM recommendations.
The SBS TRAU Alarm Reporting feature handles two different event types: fault detection and fault ceased detection. The two figures reported in this subsection describe
the operational sequence in the two different cases.
The fault detector detects a fault and sends the message labeled as "MESS. A" to the
error collector. This block obtains other information, related to the received message,
in the local data base; it takes the appropriate defensive actions if required and sends
the message "MESS. A+" to the error processor. The error processor obtains other
information in the centralized data base, sends the "Output Message" to OMT/LMT and,
updates the active alarm list.
A30808-X3247-L420-2-7620
105
MMN:TRAU
Maintenance
as
OUTPUT
MESSAGE
FAULT
CEASED
DETECTOR
ERROR
CEASED
COLLECTOR
CALL
MESSAGE
ERROR
CEASED
PROCESSOR
I/O
B
CLASS_ID
ME_ID
ERROR_ID
ACTION
(report,enable)
Fig. 5.2
Alarm Ceased Handling Overview

As in the previous case, the fault ceased detector detects a ceased fault and sends
the message labeled as "B" to the error ceased collector. This block checks the
consistency of the message fields and sends the same message to the error ceased
processor. This block deletes the error from the active alarm list and sends the output
message to OMT/LMT.
The Alarm Reporting function is used on BSMS by the centralized Error Reporting
manager. It receives messages from the error collector and performs the following
functions:
1. Formats and sends the failure event message to the LMT and OMT (via the I/O and
the Event Forwarding Discriminator functions)
2. Formats and sends the failure event message to the File System (via the I/O and the
Log Control functions);
3. Manages the error ceased messages.
The State that is currently used on the SBS-TRAU system is strongly derived from the
one proposed by GSM. The model used includes two fields:
The ADMINISTRATIVE STATE is the only state that the user can alter by using maintenance commands.
106
A30808-X3247-L420-2-7620
Maintenance
MMN:TRAU
LOCKED: the object is not allowed to perform its functions without the intervention of the user
UNLOCKED: the object can freely perform all its functions.
SHUTTING_DOWN: the object is gradually changing its administrative state
from UNLOCKED to LOCKED.
The OPERATIONAL STATE is used to indicate whether an object is able to work or
not. It specifies the object's operational mode.
ENABLED: the object is in service. It may be used or not, depending on
system needs.
DISABLED: the object is out of service. It cannot be used to perform its operations.
The TRAU system is logically structured as a tree (see Fig. 5.3). The nodes indicate the
objects (logical and physical) in which the system itself is sub-divided. The structure indicates the functional and operational dependence of several objects (sub-ordinate
objects) from others.
The autodiagnostic procedures of the TRAU system are able to identify the defective
module and the possible malfunctioning objects within the module. The same procedures can place the objects in the operative DISABLE state. As a consequence of this
action, the sub-ordinate objects are also placed in the operative DISABLE state. The
user must pay attention to this, and by means of the procedure shown in the following
section, look at the MEG tree (see Fig. 5.3 and Fig. 5.4) in order to identify the source
of the error.
From Release BR5.5 forwards, there are two possible MEGs depending on the value of
the TypeOfTraue attribute:
1. When the TypeOfTraue attribute is WITH_TPWR, the TRAU is powered by two
TPWR devices: each one powers one copy of BSCI/MSCI (BSMS), while the TRACs
are powered by the two power supplies in parallel. Each TPWR (0/1) is modelled as
a managed object which has the BSMS objects (0/1) as subordinate. This case is
shown in Fig. 5.3.
2. When TypeOfTraue is WITHOUT_TPWR, the TPWR is not used and it is deleted
from the TRAU database. The 3 devices (BSCI, MSCI and TRACs) extract the
needed voltage from the 48 V. This case is shown in Fig. 5.4.
Note that: if the TRAU cards (BSCI V4, MSCI V2, TRAC V5) are configured with jumpers
setting in order to work with their on board power supplies (in this way the board derives
the power directly from the 48V source), but the TypeOfTraue has the value
WITH_TPWR, then from the TRAU O&M point of view, the TPWR object is present and
is always ENABLE even if the TPWR cards are extracted from the rack or they are
powered off! This situation means that at the RC side the TPWR icons (for that TRAU)
will be present and displayed in GREEN. This situation is due to the fact that the boards
jumper settings and the value of TypeOfTraue are not consistent; moreover, in this case
(boards SELF-POWERED) the TRAU hardware simulates the presence of the TPWR
cards so from the software point of view, the TPWR cards are present and always
working properly. The TPWR hardware simulation is necessary for backwards software
compatibility. The consistency between the jumpers setting and the value of
TypeOfTraue is a duty of the Operator; the TRAU maintains the service without outage
even in event of inconsistency. The following table will be helpful to keep the Consistency:
A30808-X3247-L420-2-7620
107
MMN:TRAU
Maintenance
Is TPWR cards
present in the
RACK?
Yes
Yes
Yes
Yes
No
No
TypeOfTraue
value
Boards Jumpers
Setting:
O&M Result
WITH_TPWR
WITH_TPWR
WITHOUT_TPWR
WITHOUT_TPWR
WITH_TPWR
WITHOUT_TPWR
NO SELF-POWERED
SELF-POWERED
NO SELF-POWERED
SELF-POWERED
SELF-POWERED
SELF-POWERED
CONSISTENCY
INCONSISTENCY
INCONSISTENCY
INCONSISTENCY
INCONSISTENCY
CONSISTENCY
TPWR 0
TPWR 1
BSMS 0
BSMS 1
TRAUE
ENVA
TRAU
PCMT
TRAC
PCMST
(2)
(1)
SYNCT
TSLT
LAPD
1) If the TRAC is not spare

2) if the SYNC law is BSC
Fig. 5.3
108
TRAU Maintenance Entity Graph with TPWR
A30808-X3247-L420-2-7620
Maintenance
MMN:TRAU
TRAUE
ENVA
BSMS 1
BSMS 0
TRAU
PCMT
TRAC
PCMST
(2)
(1)
SYNCT
TSLT
LAPD
1) If the TRAC is not spare

2) if the SYNC law is BSC
Fig. 5.4
TRAU Maintenance Entity Graph without TPWR

Performing a service removal command ( LOCK ) the STATUS MANAGER first
removes from service the leaf objects, then level by level all the superordinates. The
command ends when, at least, the target object is put out of service.
The command related STATE CHANGED EVENT REPORT is sent only on the target
object and only if the object's state is really changed.
To be able to perform criticity checks on duplicated objects the STATUS MANAGER use
particular entity called BOND.
A BOND instance is a counter that holds the number of bonded objects that are currently
out of service. A critical alarm is sent to the RC for a BOND object whenever all the
underlying objects (both redundant units) are out of service.
A30808-X3247-L420-2-7620
109
MMN:TRAU
Maintenance
5.3
Failure Event Message

This type of message is sent to the I/O device (OMT and/or LMT), when an error occurs.
The message is formatted using information, from the message received from the error
collector and from the protected database of the Error Task. More specifically, the
failure event message to be sent to the I/O module (in other words to the OMT and/or to
the LMT) includes the following information:
Date/Time
NAME
Event Type
Event Time
Probable Cause
Specific Problems
Severity
Trend Indication
Notification Identifier
Correlated Notification
Identifier
Related MO
Proposed Repair Actions
Additional Text
Originator
Additional Words
Software Version
NAME:
110
<object mnemonic+object address>

This field identifies the object. Note that the mnemonic is
followed by a structured numbering (address) that univocally
identifies an object in the BSC.
Event Type: this parameter categorizes the alarm. Five basic categories of
alarm are specified:
Communication Failure Event (COM LED): a failure event of this type
concerns the procedure and/or processes that are used to transport information from one point to another. In principle, the following communication
failure event is communicated: malfunctions related to all links of the BSC
system (SS7, LAPD and X.25); problems resulting in blocking the switching
network (not due to hardware causes); and malfunctions resulting in
blocking at least one level 3 radio automaton. These malfunctions are
generated by the protocols of their respective links whenever they detect a
problem, by the level 3 radio function and/or by the function controlling the
network connections whenever a block is detected in call establishment.
According to this definition, for example, the objects of the protocol links
and the level 3 radio manager object are objects generating this failure
event.
A30808-X3247-L420-2-7620
Maintenance
MMN:TRAU
Quality of Service Events (QOS LED): a failure event of this type

concerns the degradation of the quality of service in the BSC. Such a failure
event will be generated by level 3 radio whenever the quality of service
offered to the mobile user drops below the preset warning threshold. It is
not easy to identify the objects that could generate such a failure event,
because they don't make reference to any specific physical object.
For example, the process that manages level 3 radio could be regarded as
the object that can generate this type of event. Together with the event, the
status of the automaton that experienced the abormal situation could also
be specified.
Equipment Failure Events (EQP LED): an event of this type is associated
with hardware faults and is the most traditional form. It appears in the form
of hardware malfunctions that are reported and analyzed by the maintenance procedures in order to take the necessary remedies based on the
redundancies which the BSC system is equipped with. As far as the local
display is concerned, for these failure events information on their severity
are given as well as information enabling to locate the faulty unit that generated them.
For example, there is a lamp to indicate a network unit (the NTW LED) and
another one to indicate an LICD line module unit (the LINE LED), and
another to indicate the processing units. All of these failures are equipment
failure events and, for every unit, the object shall select the related lamp.
Processing Failure Event: this category of failure events includes all software-type errors and is a category that one would like to get rid of, because
these errors are due to programming errors. These failure events and the
information reported by them are necessary to remove the error.
Environmental Failure Events (ENV LED): this type of failure event is
associated with environmental problems on the site where the BSC is
located. The BSC has the capabilty of detecting these causes via a number
of sense points connected to environmental sensors.
Event Time: This attribute identifies the time of detection of the fault.
Probable
This parameter defines further qualifications as to the probable
Cause:
cause of the alarm.
Specific
This Failure Event attribute provides further refinement to the
Problem:
Probable Cause attribute.
Severity:
this parameter defines five severity levels providing an indication of their serverity as it is perceived. The five levels, from the
least to most severe, are:
Cleared: this severity level indicates the clearing of one or more previously
reported alarms. This alarm clears all alarms for this managed object that
have the same Alarm Type and Probable Cause. It is reported as an "Error
Ceased Message".
Warning: this level indicates that the object has reported a potential or
pending "error" that has not yet affected the functionality of the BSC. It is
just a prompt to take the necessary actions to diagnose and correct the
problem as soon as possible before it becomes more severe. For a failure
event of such a low severity, an end-of-alarm event might be unnecessary;
in any case, neither the status nor the instance having generated it are
retained (it could not be polled by RC), nor will it be displayed by any visual
indicator (i.e. LEDs).
A30808-X3247-L420-2-7620
111
MMN:TRAU
Maintenance
112
Minor: this level indicates that the object has reported such an error as not
to degrade its functionality (for example, its backup has been switched into
service) or, better, indicates that a functional part of the BSC is degraded,
but is still in a position to perform its functions without affecting the service
too much.
Major: this level indicates that the object has reported such an error as to
render it severly degraded or, better, indicates that a functional part of the
BSC system is severly degraded.
Critical: this level indicates that the object reported such an error as to put it
totally out of service or, better, indicates that a functional part of the BSC is
completely unavailable.
Trend Indica- this parameter indicates how the degradation of the features of
tion:
a component part is evolving. Its value can be the followings:
the Not Applicable trend indication is printed if the associated
severity for the object in question is INDETERMINATE or
WARNING.
the NoChange trend indication is printed if the associated
severity for the object in question isnt changed from the
severity of those associated to previously reported Failure
Event relevant the same object and still active (i.e. no related
error ceased message was generated).
the LessSevere trend indication is printed if the associated
severity for the object in question is less severe of the severity
of those associated to previously reported Failure Events relevant the same object and still active (i.e. no related error ceased
message was generated).
the LessSevere-noChange trend indication is printed if the
associated severity for the object in question is less severe or of
equal severity of those associated to previously reported Failure
Events relevant the same object and still active (i.e. no related
error ceased message was generated).
the MoreSevere trend indication is printed if the associated
severity for the object in question is more severe of those associated to previously reported Failure Events relevant the same
object and still active (i.e. no related error ceased message was
generated).
Notification this attribute identifies unambiguously the Failure Event.
Identifier:
Correlated
this attribute identifies the notification to which this Failure Event
Notification: is considered to be correlated. Since the failure Event Reports
are father event for the Notification Identifier correlations, the
Correlated Notification information are shown only for the
Failure Enet Report output during an Alarm Alignment (RC) or a
Get Pending Alarm Command (LMT)
Proposed
this attribute identifies the repair action suggested to the operRepair
ator for the fault resolution.
Actions:
A30808-X3247-L420-2-7620
Maintenance
MMN:TRAU
Additional
Text:
For the alarms generated by the ENVA objects, the operator

shall be able to define his own alarm text and also to define
the severity associated to each ENVA objects instance
indipendent from the alarm text. The Additional Text string
defined by the operator represents a description of the environmental event. This field is always present in a Failure Event
Report, but is meaningful only for the ENVIRONMENTAL
Failure Events: in all other type of failure events is output as
Null String.
Originator:
It is an integer number that identifies the software module originating the Failure Event.
Additional
aaaa-oooo are hex values that are helpful for a detailed descripWords:
tion of the error. This part is of particular usefulness for the software designer to analyse the error cause and so take proper
actions to solve the problem.
Software
Its the BSC software version files (if we are on BSC Local
Version:
Terminal).
The following is a real example of error message:
ALARM REPORTING --> SYSTEM BROADCAST
16:00:03 17/02/2000
21:34:24 17/02/2000
*** INFORMATION ***
FAILURE EVENT REPORT:
NAME=DISK:1
Event Type = Equipment Failure Event
Event Time = 17/02/2000 16:00:03
Probable Cause: Equipment Failure
Specific Problems = PLL_FAILURE
Trend Indication: More Severe
Notification Identifier = 05
Proposed Repair Actions = 1 NoAction
Additional Text = Null String
Originator: 4305
Additional Words =
H003c H0335 H0000 H0000 H0000
H0000 H0000 H0000 H0000 H0000
H0000 H0000 H0000 H0000 H0000
Additional Info:
Software Version: 02-06-01-01-00-00_10-05-00
A30808-X3247-L420-2-7620
113
MMN:TRAU
Maintenance
5.4
General Diagnostic Structure

When the operator enters data from the Local Maintenance Terminal or enters a test
command from the O&M Center, two activities are performed: a "status consistency
check" and a "phase controller activation". The former addresses the initial conditions
control, while the latter is involved in monitoring the execution of the diagnosis sections
called "phases".
A diagnostics is subdivided into phases: the single phase is a test on a hardware section
functionality that can be executed individually and can provide an indication of what the
problem is as precisely as possible.
The result of the phase takes into account both the particular hardware components
inspected by the phase and the general interface of the diagnostic tests.
Some phases are always present and common to all diagnosis:
start phase:
end phase:
abort phase:
to correctly set the card to support the rest of diagnostic tests;

to restore the working conditions of the hardware to the previous
successfully executed phase!
It is always performed as the last phase, unless an abort occurred,
also if the termination is induced by an operator.
resets the hardware, without depending on what was currently
executed. These actions depend on the running phase.
The other phases that every hardware diagnostics will provide to actually prove the
device are named "working phases". They are containers for a group of test routines
forcing the single function, the single alarm or a particular internal hardware interface.
The soft termination, contrary to the abort one, has an operator origin, and can have two
managements: if the diagnosis is still waiting for activation, an immediate cancellation
of the test request is sufficient, while if the diagnosis is already active, the current
working phase is completed and the end phase is then executed.
The TRAU system includes a number of diagnostics which cover the following hardware
units:
BSCI (Base Station Controller Interface)

MSCI (Mobil Switching Center Interface)
TRAC (Transcoding and Rate Adaption Card)
TPWR (Trau Power supplies)
From the maintenance point of view, the main advantage of the diagnosis features is the
capability to provide the list of suspected faulty modules. Up to four modules can be
listed, sorted starting from the most probable module. Another aspect concerns the
capability of the diagnosis to provide information regarding the specific components on
a module which is responsible for the fault. Although this information is not immediately
readable, it is contained in the additional info field reported by the test output.
114
A30808-X3247-L420-2-7620
Maintenance
5.4.1
MMN:TRAU
Hardware Diagnostics
Introduction
Diagnostics are provided to check the functionality of hardware units and to locate hardware faults.
They achieve this by:
a) applying inputs to a hardware device;
b) comparing resulting outputs with expected outputs;
c) using the failing phase as the basis for fault resolution.
Every diagnostics is structured in the same way: it is divided into PHASES and each
phase into TESTS.
A TEST is a software routine that verifies the functionality of a specific hardware circuit.
A PHASE is a stand alone set of test routines, executed in a sequential manner, that
verify the same hardware device.
Every diagnostics must has:
a "start phase" to correctly initialize the device to be tested;

a variable number of "working phases" (the core of any diagnostics); each working
phase has been designed to point out a least replaceable unit (LRU).
an "end phase" to re-establish the conditions in which the device was before the
diagnostics;
an "abort phase" to clean up the system configuration in the event of an abort of the
diagnostics;
As general rule:
each diagnostics is destructive (the object has to be locked before starting a test)
with the exception of the PWRS;
the diagnostics of a specific board is incompatible with the diagnostics of the same
type of board; starting with Release BR5.0, BSMS diagnostics and TRAC diagnostics are incompatible.
Each type of hardware unit has its specific diagnostics. The results of a diagnostics of a
certain phase are different for every kind of diagnostics: normally for each test there is
a bit which indicates if the test passed or failed. The meaning of the bits depend on the
hardware device under test.
If the diagnostics runs successfully, the output provides a list of the successfully
executed phases.
If the diagnostics fails the output provides a list of the executed phases and, for each
failed phase 8 words which detail the kind of failure.
The failure of a phase can have different degrees of severity. In particular, it may happen
that the failure prevents any further diagnostic testing on the device (for instance if the
object or some part of it is not accessible, or if the processor on board does not answer).
In this case, all the remaining phases (except for the end phase) is skipped. In other
failure cases, the diagnosis continues in spite of the bad test result. In both cases, the
test outcome will be fail. The termination of the diagnosis when a phase fails is
decided at run time by the hardware diagnostic.
A30808-X3247-L420-2-7620
115
MMN:TRAU
Maintenance
5.4.2
Phase Identifier
In order to provide a better interpretable information, the following table shows at the
Operator, in the form of character strings, new Phase Identifiers that are specific for the
hardware object under test. The Phase Identifier are defined starting from the current
Working Phase.
In general, when a phase fails the next ones are skipped.
MOT
TPWR
BSMS
TRAC
New Phase Identifier
Old Phase
Dummy Test
Start Phase
Force Alarm Test
WP1
End Test
End Phase
Accessibility Test
Start Phase
BSCI Initialization Test
WP1
BSCI Serial Link Test
WP2
MSCI Global Test
WP3
End Test
End Phase
Accessibility Test
Start Phase
Initialization Test
WP1
BSCI Loop Test
WP2
End Test
End Phase
Tab. 5.4.1 New Phase Identifiers
5.4.3
TPWR Diagnostics
With the following hardware configuration:
- Backplane A30861-X223-X10
- BSCI V4
- MSCI V2
- TRAC V5
and with the TRAU High Capacity
each card derives its power supply directly from the 48 Volt. Therefore the TPWR card
is not equipped and the card test does not apply. With this configuration the sense point
and the control point on the BSCI related to the TPWR are maintaned but they not
control hardware circuits.
The TRAU power supply provides two regulated power voltages (+5,3V and +12,3V)
accepting at the input a battery voltage variable in the range -34/-73 Volt.
The power supply also contains the supervisory, monitoring and control functions
necessary to interface with the system and with maintenance personnel.
These functions include:
116
A30808-X3247-L420-2-7620
Maintenance
MMN:TRAU
The control of the on/off state of the regulated output voltages in response to the
control panel switches, the monitor of the system out of service input and detection
of an out of limits on the regulated output voltages.
An automatic shutdown if an out of limits condition occurs on the regulated output
voltages.
The presence of a system sense point signal for reporting the status of the regulated
output voltages; the presence of a system sense point signal for requesting turn off.
The response to a system control point signal which indicates subsystem in or out
of service and the response to a system control point signal which controls voltage
monitor testing.
A main interface on the control panel consisting of in out of service indicator, on/off
request, failure indicators and an emergency off circuit breaker.
The presence of a power on reset output for subsytem initialization following a power
on sequence.
The TPWR diagnostics has been implemented only with the start phase (see paragraph
5.4.2).
a) TPWR start phase
This phase is not applicable for PWRS diagnostics
b) TPWR working phase 1
OUTPUT if this phase fails:
word[0]
0 x 01
ALARM CIRCUIT ERROR
c) TPWR end phase

This phase is not applicable for PWRS diagnostics.
5.4.4
BSMS Diagnostics
The diagnostic of the BSMS object involves the diagnostics of the BSCI and MSCI
modules.
The BSCI is the main processor of the TRAU and its task is to control it. Then, apart from
controlling itself, the BSCI controls the peripheral devices - TRACs, MSCIs and Power
Supplies.
The BSCI card interfacesthe BSC station with the TRAU station. The BSC card has
control functions for all TRAC cards and for the MSCI card directly subordinate. It comunicates with the other BSCI card to coordinate O&M actions.
It provides the following functions:
A30808-X3247-L420-2-7620
Implements an INTEL 80C186XL microprocessor running at 20 MHz.

Provides a total of 2 Mbytes of static Ram memory, parity protected.
Provides up to 128 Kbytes of erasable and programmable read only memory for
bootstrap and firmware implementation.
Provides 4 Mbytes of Flash erasable and programmable memory for storing whole
TRAU code.
Provides serial links at 64 Kb/s with all TRAC cards, with MSCI (same copy), with
BSCI (other copy) through HSCX serial controllers.
117
MMN:TRAU
Maintenance
Handles 16 sources of interrupt by 2 programmable interrupt controllers (PIC).

Provides a duplicated PCM link 2 Mb/s, 120 traffic channels interfaced to BSC.
Implements a PLL circuit and provides a Timing Generator. This circuit regenerates
the MSC line clock and provides TRAU clocks (8 MHz, 2 MHz, 64KHz) and synchronization signals (8 MHz, 4KHz).
Implements a V.11 interface with LMT (Local Maintenance Terminal) through the
ESCC2 Serial Controller.
Provides an OR function for external timing alarms coming from the TRACs and the
MSCI.
Manages power supply of the other copy.
Provides a LOOP TEST and IDLE CODE DETECTOR function for TRAU Maintenance.
The MSCI card interfaces the MSC station with the TRAU. The MSCI has control functions for mapping the PCM line connections towards MSC with the 64 Kb/s traffic channels to/from the TRACs and the 64 Kb/s transparent channels to/from the BSCI.
It also handles the lower levels of the LAPD protocol of the communication between
BSC and TRAU, while the higher levels of this protocol are handled by the BSCI.
The MSCI card provides the following functions:
Implements four PCM 2Mbit/s interfaces towards MSC

Implements two PCM 2Mb/s interfaces for TRAU ring connection.
Implements a microcomputer circuit based on 80C188 microcontroller whose function is to supervise the operations and maintenance of the MSCI and to support
various comunication links:
- with the BSCI card
- with the MSCI card of the other copy
- with the MSCI cards of the other TRAUs in the TRAU ring connection
- with the BSC, via a LAPD HDLC protocol.
All the HDLC protocols are implemented in FW or SW with the support of Siemens
HSCX, serial communication link controllers for HDLC protocols.
Implements a maintenance circuit, realized into the TILT gate-array, whose function
is to generate a test pattern to be injected into the coders of the TRAC cards,
belonging to the TCHs that are idle at the moment of the test; these idle TCHs are
closed in loop by the TILT equipped in the BSCI card, so that the output of the coder
constitutes the input of the decoder in the TRACs. The TILT of the BSCI generates
a check pattern and compares it with the bit stream coming from the decoders.
Implements a 64 KBit/s Space Switch Matrix realized into the DIGA gate-array,
whose function is to route 64 Kb/s channels from one TRAU to another one through
the double ring interconnection in which a group of TRAUs belonging to the same
BSC are linked. For this purpose, two 2 Mb/s PCM lines in a double ring configuration are used. The 64 Kb/s channels of these PCM lines are used to save the control
links between the BSC and to distribute to the others the messages that belong to
them, by means of the ring interconnection drop-insert.
The BSMS diagnostic has been implemented with three working phase (see paragraph
5.4.2).
a) BSMS start phase
This phase initializes the BSMS under test.
118
A30808-X3247-L420-2-7620
Maintenance
MMN:TRAU
word[0]
0 x 04
BSCI is not powered
word[0]
0 x 02
BSCI is absent
b) BSCI working phase 1

word[0]
Error Id
word[1]
Originator
word[2]
For Internal Use Only
word[3]
word[4]
word[5]
word[6]
word[7]
c) BSCI working phase 2

word[0]
0x00 HSCX Loop Test Failed

0x01 ESCC2 Loop Test Failed
0x02 PCM Test Failed
0x03 BSCI Ram Parity Test Failed
word[1]
word[2]
word[3]
word[4]
word[5]
word6]
word[7]
d) MSCI working phase 3

word[0]
word[1]
word2]
word[3]
word4]
word[5]
word[6]
word7]
e) BSMS end phase

This phase is meaningless for BSCI and MSCI diagnostics.
A30808-X3247-L420-2-7620
119
MMN:TRAU
Maintenance
5.4.5
TRAC Diagnostics
During the BSCI Loop Test, the standby status of the BSMS used in the TRAC loop is
temporarily changed from HOT STANDBY to COLD STANDBY.
The TRAC card performs the most important function of the TRAU, speech transcoding
and data rate adaption for 24 pairs of 16 Kb/s TCHs and 64 Kb/s PCM channels.
An Intel 80C188XL microprocessor running at 15.15 MHz implements the TRAC card
controller.
The controller is provided with 128 Kbytes of erasable and programmable read only
memory for firmware implementation and 128 Kbytes of static random access memory
downloadable code and data, as well as with serial communication links at 64 Kb/s
between the controler and both BSCI active and stand-by. The controller receives at the
start-up, through the serial link from the active copy of the BSCI card, the code to be
stored in its memory and in the memories of the DSPs. During the operation, the
controller executes all the configuration and O&M commands coming from the BSCI and
report to it all the fault and alarms detected inside the card.
The card implements a bank of 8 AT&T DSP1610 (24 AT&T DSP1617 for TRAC V3)
digital signal processors running at 29.25 MHz; each DSP handles 3 transcoders and
rate adapters and is provided with 128 Kbytes of code downloadable in a fast static
random access memory.
The line interface both with the 64 Kb/s channels coming from the MSC and the 16 Kb/s
TCHs coming from the BSC is implemented through four 60.000 gate-arrays each of
which interfaces 2 DSPs with the lines coming from the BSCIs and MSCIs, and also
provides a mail-box for the DSP and controller communications in both directions.
The controller sends towards the BSCI all the detected alarms through serial link and
also through dedicated signals.
The card provides an RS-232 interface to permit the on-line debugging function through
a serial controller and an EPROM containing factory information: code, hardware issue,
etc. This information is readable by the controller.
The TRAC diagnostics has been implemented with two working phases (see paragraph
5.4.2).
a) TRAC start phase
This phase initializes the TRAC under test.
word[0]
0 x 02
TRAC CARD under test is absent
b) TRAC working phase 1

120
word[0]
word[1]
word[2]
word3]
word[4]
A30808-X3247-L420-2-7620
Maintenance
MMN:TRAU
word[5]
word[6]
word[7]
c) TRAC working phase 2

word[0]
0x03 TRAC V3
0x05 TRAC V5
0x06 TRAC Does Not Answer
0x07 TRAC V7
0x08 BSMS Standby Not Available
0x09 Timeout Or Corrupted Message
0x0A TRAC Not In Running State
0x0B TRAC Absent
0x12 Tilt Not Configured
0x13 Diga Not Configured
0x14 MSCI Not Configured
0x15 Standby Updating
0xAAAA TRAC HW NOT COMPATIBLE WITH ACTUAL
CONFIGURATION. This add_word appears when a TRAC V1
is in the rack and the TRAU is configured to AMR. TRAC V1 is
incompatible with AMR.
word[1]...word[7]
These values are meaningful only if Word[0]=0x03 or 0x05 and

the values are the same that those specified in the TRAU Error
Manual for the Specific Problem
TRAC_DIAGNOSTIC_ONLINE_FAILURE, strating from
word Iiii to word Oooo.
d) TRAC end phase

This phase is meaningless for TRAC diagnostics.
A30808-X3247-L420-2-7620
121
MMN:TRAU
122
Maintenance
A30808-X3247-L420-2-7620
Maintenance
MMN:TRAU
Abbreviations
ACTM
ACT for the Base Rack/Shelter
BSC
Base Station Controller
BSCI
BSC interface card
BSMS
BSCI and MSCI modules
BSS
Base Station System
BTS
Base Transceiver Station
BTSE
Base Transceiver Station Equipment
DUKIT
Duplex Combiner Kit
EMI
Electro Magnetic Interference
ESCC2
Enhanced Serial Communication Controller
GSM
Global System for Mobile Communication
HMOI
Hardware Managed Object
HSCX
High Level Serial Communication Control

Extended
HW
Hardware
IDF
Inventory Data File
ITMN
Installation & Test Manual
LAPD
Link Access Procedure on the D-Channel
LED
Light Emission Diode
LED
Light Emitting Diode
LMT
Local Maintenance Terminal
MEG
Maintenance Entity Graph
MOT
Managed Object Under Test
MSCI
MSC interface card
No
nob-RIU
Not On Board Remote Inventory Unit
ob_RIU
On Board Remote Inventory Unit
OMC
Operation and Maintenance Center
OMT
Operation and Maintenance terminal
OS
Operating System
PCM
Pulse Code Modulation
PLMN
Public Land Mobile Network
RC
Radio Commander
SBS
Siemens Base Station
TAC
Technical Assistance Center
TFAP
TRAU Fuse and Alarm Panel
TPWR
TRAU Power
TRAC
Transcoding and Rate Adaption Card
Yes
A30808-X3247-L420-2-7620
123
MMN:TRAU
124
Maintenance
A30808-X3247-L420-2-7620

Traumt PDF

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Traumt PDF

Hochgeladen von

Copyright:

Verfügbare Formate

Maintenance

Transcoding and Rate Adaption Unit

Important Notice on Product Safety

The same text in German:

Copyright (C) Siemens AG 2003 .

Reason for Update

Reason for Update

New Remote Inventory file for TRAU-HC

Reason for Update

First Edition for New Release BR 7.0

Second Edition for Release BR 7.0

How to Use this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Fault Clearance Procedures for Modules and Interfaces . . . . . . . . . . . . . .

Structure of the MMN:TRAU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

TRAU Maintenance Entity Graph with TPWR. . . . . . . . . . . . . . . . . . . . 108

Relationship between alarms and replacement procedure . . . . . . . . . . 24

1 How to Use this Manual

Structure of the Maintenance Manual

(Important information to make your work

Fault Clearance Procedures for Modules

(Main Part for Fault Clearance Tasks)

Tables, Lists and Figures

Structure of the MMN:TRAU

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

Use LMT to enter commands

Reference to another step in the procedure or to another procedure

Reference to another chapter in the document or to another document

Reference to another procedure. Return after finishing.

Note; important information

Fault Clearance Principle

Fault Clearance Guidelines

1. System Integrated Routine Test Detects a Fault

2. Fault Message Displayed at Radio Commander:

Fault and Test

Content of this Manual

4. Fault Clearance Procedure for the Suspected

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

Fault Clearance Overview

Fault Clearance Guidelines

name and code of the site

Module Replacement Instructions

Removing and Inserting Modules

Fault Management Procedure

Local Maintenance Terminal (LMT)

General Maintenance flow chart

In the following an explanation of the above diagram is given.

MANAGED-ELEMENT--> BSS-EQUIPMENT--> TRAUE

MANAGED-ELEMENT--> BSS-EQUIPMENT--> TRAUE

MANAGED-ELEMENT--> BSS-EQUIPMENT--> TRAUE -->

FIRST CHECK OR STEP REPLACEMENT PROCEDURE

TRAC card (see

see the automatic diagnostic test result

see the automatic diagnostic test result

TRAC card (see

TRAC card (see

1089 DSP fail

see the automatic diagnostic test result

TRAC card (see

TRAC card (see

TRAC card (see

see the automatic diagnostic test result

see the automatic diagnostic test result