BSC TC Maintenance (Alcatel)

ALCATEL BSC / TC MaintenanceALCATEL BSC / TC Maintenance

Training manual8 AS 902001403 VH ZZA Ed 01

Edition 2004

© All rights reserved. Passing on and copying of this document, use and communication of its contents not

permitted without written authorization from Alcatel

© Alcatel University - 8AS 902001403 VH ZZA Ed.01 Page 0.2

Note : Please print this document with comments pages


ALCATEL 9120 Base Station Controller MaintenanceALCATEL 9120 Base Station Controller MaintenanceS1 Local maintenance principle

DefinitionsManaged objectsSBL operator commandsSBL state descriptionSBL hierarchy

S2 BSC local maintenanceTelecom and O&M SBLTransmission SBL at BSC sideLEDs and AlarmsBSC terminal descriptionBSC terminal functions Definition

S3 BSC local maintenancePlatform Hardware IdentificationBSC terminal practice and BSS software overview SBL practice Replace an RIT using the appropriate BSC task procedureAnalyse fault messages using the alarm dictionaryAnalyse the BTS software download

S4 TC G2 local maintenanceTransmission SBL at TC sideTC G2 LEDs and AlarmsTC G2 terminal descriptionTC G2 terminal functions

S5 TC G2 local maintenancePlatform Hardware IdentificationSBL practice Check the transmission equipment settingsReplace an RIT using the appropriate TC task procedureAnalyse fault messages using the alarm dictionary

ALCATEL 9125 TC MaintenanceALCATEL 9125 TC Maintenance1 Getting started2 Transcoder supervision

Alarm monitoringCheck logical parametersCheck SW versionCheck remote inventoryExercises

3 Hardware module replacementReplace MT120Software downloadReplace transcoder Fan casetteExercises

Contents


Page intentionally left blank


Self assessment of the objectives

Instructional objectives Yes (or Globally

yes)

No (or globally

no) Comments

1 To be able to use the BSC terminal

2 To be able to retrieve and analyze the

alarm messages

3 To be able to handle the Security Blocks

4 To be able to Change a Replaceable Item

using the relevant task procedure

5 To be able to Start-up a BSC System

6 To be able to Identify the preventive

maintenance tasks

Contract number :

Course title :

Client (Company, centre) :

Language : English dates from : to :

Number of trainees : Location :

Surname, First name :

Did you meet the following objectives ?Tick the corresponding box

Please, return this sheet to the trainer at the end of the training


Instructional objectivesYes (orGlobally

yes)

No (orglobally

no)Comments

Self assessment of the objectives (continued)

Thank you for your answers to this questionnaire

Other comments

© Alcatel University - 8AS 902001403 VH ZZA Ed.01 Page 1

© Alcatel University - 8AS 902001403 VT ZZA Ed.01

ALCATEL 9120 Base Station ControllerALCATEL 9120 Base Station Controller

Maintenance


© Alcatel University - 8AS 902001403 VT ZZA Ed.01 Page 1. 2

BSC DescriptionCourse content

S1: Local maintenance principle

S2: BSC local maintenance

Telecom & transmission

S3: BSC local maintenance

Practice

S4: TC local maintenance

Telecom & transmission

S5: TC local maintenance

Practice


Session 1

Local maintenance principle




S1: Local maintenance principleObjective and program

Objective : To be able to describe the purpose of local maintenance and to define local maintenance vocabulary

Program: Definitions

Managed Objects

SBL operator commands

SBL state description

SBL hierarchy



S1: Local maintenance principleDefinitions

Telecom functionsThe GSM network allows call handling between MS/MS, MS/PLMN, PLMN/MS

The call management is handled by Telecom functions

Operating and maintenance functionsDeploy, operate, upgrade the network is made through the O&M function

The 3 O&M major functions are0 Configuration management0 Fault management0 Performance management



S1: Local maintenance principleDefinitions

Several BSS terminals are available :

0 OMC-R : supervises and controls the whole BSS0 BSC local terminal : supervises and controls BSC, TC, BTS’s, and

transmission SBL’s0 Transmission terminal : supervises and control local transmission

equipment (BSC & TC site)0 BTS local terminal : supervises and controls one BTS0 TC terminal : configuration and alarm reporting for Alcatel 9125 TC0 IMT terminal : supervises and controls the MFS

Since release B6.2 transmission SBLs are no more handled by the Transmission Terminal, but by the BSCTerminal. The Transmission Terminal is only used to configure, read transmission boards files, collect alarms, and perform tests and measurements (local use).

During this course we are going to learn how to use the BSC and the Transmission terminal.



S1: Local maintenance principleManaged objects

Security block

An SBL is a set of circuit which performs a set of coherent functions

If one function is lost, the whole SBL is lost too

More than one SBL may share the same RIT

One SBL may be built on different RIT

Some SBL’s are logical, they can’t be mapped on any hardware

The definition of a RIT is given on the next page.



S1: Local maintenance principleManaged objects

Replaceable item

A RIT is the lowest assembly piece such as boards, DC/DC converter.

A RIT may contain different SBL’s

Repair block

A Repair Block is the smallest number of SBL’s that must be taken out of service during board replacement to ensure that the faulty RIT is correctly repaired without endangering other SBL



S1: Local maintenance principleSBL operator commands

Maintenance operator commands

Reset : It allows to kill and set up a functionality in sequence

0 Purpose• Escape from a situation where the behaviour is doubtful• This command may be seen as a combination of Disable and Init

0 Impact• SW and DATA downloading.• The context is lost (calls / signalling)





Restart : It allows to restart a functionality

0 Purpose• Build up a function supported by SW without SW download

0 Impact• Context is kept





Init : It allows to set up a functionality. This command applies to an SBL which was disabled before

0 Purpose• Reactivate the functionality of a target SBL

0 Impact• When the initialisation has been successfully achieved, the SBL should be able to handle its

functionality





Disable : It allows to kill the functionality of an SBL

0 Purpose• Inhibit the functionality of a target SBL and filters alarms• The Wait Traffic Clear parameter introduce a delay into the command execution• The traffic may be stopped in a clean way

0 Impact• The context is lost (calls / signalling)




DISABLE

1 BOOTSTRAP

2 SELF-TESTS

3 SOFTWARE DOWNLOADING

4 SOFTWARE START-UP

5 NON-DESTRUCTIVE TESTS

6 CONFIGURATION DOWNLOADING /DATA BASE SYNCHRONISATION

7 FUNCTION START-UP

INIT

RESTART

RESET




Tests operator commands

Verify

0 Purpose• It allows to check a working SBL which behaviour is doubtful• WTC parameter is included• May be seen as the combination of Disable & Diagnostic tests & Init• Only applies to processors SBL• Stops on going calls in a clean way

0 Impact• Inhibit the functionality of a target SBL• Filters alarms• The context is lost (calls / signalling)





Diagnostic tests

0 Purpose• Check before / after performing a repair action that SBL is working or not• SBL must not be in service• Only applies to processor SBL• Stops on going calls in a clean way

0 Impact• SW is downloaded and all its data are initialised





Extension tests

0 Purpose• Check equipment before commercial service• Performed with SBL’s in the Non Equipped state• Permits loop tests between MSC-TC and BSC-TC

0 Impact• None if TC Time slot has been disabled at MSC side




1 BOOTSTRAP

2 SELF-TESTS

3 SOFTWARE DOWNLOADING

4 SOFTWARE START-UP

5 NON-DESTRUCTIVE TESTS

6 CONFIGURATION DOWNLOADING /DATA BASE SYNCHRONISATION

7 FUNCTION START-UP

EXT & DIAG TESTS

VERIFY



S1: Local maintenance principleSBL state description

Human operationOPR (Operator)0 The object is subject to an operator intervention0 It cannot perform its functions

Level of serviceIT (In traffic)0 The object is ready to perform all its functions0 The provided service is acceptable

FIT (Faulty in traffic)0 The object is ready to perform its functions in a degraded mode0 A non fatal error has been detected0 The provided service is acceptable




Level of serviceFLT (Faulty out of service)0 A fatal error has been detected0 The service is unavailable0 The provided object has the capability to recover autonomously

FOS (Forced out of service)0 A fatal error has been detected0 The service is unavailable0 The provided object has not the capability to recover autonomously

UT (Under test)0 The object is being tested by automatic processes0 The service is momentary unavailable




Inhibition due to system administrationSOS (Software out of service)0 The object can not performed its functions because a parent object is out of

service

EF (External fault)0 The object can not performed its functions because an other co-operating

item is out of service

Configuration managementNEQ (Non equipped)

WTC (Wait for traffic clear)0 This state is linked with the WTC timer parameter0 Corresponding SBL can not be selected for new transactions0 The traffic still goes on until the WTC timer expires




Configuration managementMSD (Maintenance seized)0 This state indicates that a test operator action is running on the

corresponding SBL

MSD AUTO (Autonomous maintenance seized)0 This state indicates that an action autonomously trigged by the system is

running on the corresponding SBL



S1: Local maintenance principleSBL hierarchy

The hierarchy between SBL defines their logical dependence

There are three types of dependenceNo logic0 If A is out of service B is SOS

Logical OR0 If A AND B are out of service then C is SOS

Logical AND0 If A OR B are out of service then C is SOS

A

B

OR

A B

C

AND

A B

C


Session 2

BSC local maintenance

Telecom & Transmission




S2: BSC local maintenanceObjective and program

Objective: To be able to describe the BSC terminal and BSC SBL for local equipment management and troubleshooting

Program: Telecom and O&M SBL

Transmission SBL at BSC side

LEDs and Alarms

BSC terminal description

BSC terminal functions



S2: BSC local maintenance Telecom and O&M SBL

SBL’s identification (1)0 ACH : A channel0 ATR : A trunk0 BATTERY : battery0 BC RACK BUS : broadcast rack bus0 BC SYS BUS : broadcast system bus0 BSC : base station controller0 BSS_TEL : BSS telecom capability (all cells)0 BTS OM (*) : BTS operation and maintenance capability0 BTS TEL (*) : BTS telecom capability (one cell per sector)0 CLK GEN : clock generator0 CLK REP : clock repeater0 CONV : converter0 CPR : central processor

• * : logically associated with BTS, managed by BSC

ACH : provides a 64 kbps data path which flows between the MSC and the BSC. The channels are used as:

•PCM speech and data channels

•N7 channels.

ATR : provides a 2 Mbps link from the MSC to the BSC. The link carries up to 31 A-Channels (up to 30 PCMs, 1 N7 (optional), 1 X.25 (optional)).

BC_RACK_BUS : distributes each paging message to all boards within the required rack. The rack is determined by the destination LAC.

BC_SYS_BUS : distributes each paging message to all BCLA Rack boards

BTS_TEL : this is the radio channel management part of a given BTS. It also provides the radio signal preprocessing (Mode A) needed to support the RR session (error rate, power control, handover, timing advance, etc.).

CPR :

Layer 1:support of HDLC controller (which supports the LAPB), interface to the internal switch.

Signalling: X.25 Layers 2 and 3 protocol, OSI high layer protocol (CMISE and FTAM)

Radio Channel Management: centralised radio channel resource management, telecom supervision to control the overload procedure and handles the reset procedure (initiated by MSC or BSC).




SBL’s identification (2)0 DISC : solid state disk0 DTC : digital trunk controller0 GSL : GPRS signalling link0 N7 : number 7 signalling link0 OML (*) : operations and maintenance signalling link0 RSL (*) : radio signalling link0 RS232 : RS232 connection0 SWITCH : network switch0 TCU : Terminal control unit0 TR OM (**) : transmission operation and maintenance capability0 X25 : X25 link

• ** : logically associated with TSC, managed by BSC

DTC :

Layer 1: supports Digital Trunk Control (G703),Supports HDLC Controller (support MTP) , extracts clock information on received A-Trunks interface to the internal switch.

signalling: N7 MTP and SCCP protocols, terrestrial Channel Management: MSC/BSC channel blocking/unblocking.

Radio Channel Management: receives and forwards paging commands and performs the paging group calculation, performs the SCCP mobile user function, controls intra-BSC handovers, controls the assignment of channels by the MSC, distinguishes between transparent and non-transparent messages and routes the transparent messages to the correct TCU.

GSL : Carries GPRS signalling between MFS and BSC

N7 : Carries (between BSS and MSC) the signalling information associated with the traffic channels contained in the A-Channel. The signalling is arranged according to the CCITT Recommendation Q700.

RSL : Carries through the BSC-BTS path, the routing information associated with the traffic channels contained in one BSC-BTS 2 Mbps link. The signalling is arranged according to a LAPD protocol. There is one RSL for one FU/TRX .




SBL‘s layout & hierarchy

TR_O&M** BTS_O&M* BTS_TEL*

These SBLs are at the same level as the BSC SBL. They are reported to the OMC-R as isolated SBLs.

BSS_TEL

BSC

TCU DTC CPR

GSL ATRDISC

X25

RS232

BC_SYS_BUS

BC_RACK_BUS

SWITCH CONV BATTERY CLK-GENCLK-GEN

CLK-REP

ACHN7

LAPD

OML*

LAPD

TSL**

LAPD

RSL*

* = BTS SBLs, ** = TSC SBLs. All these SBLs are managed by the BSC. Note that the TSL is routed via the first TCUC in

each cabinet which is connected to the BIUA PBA with Q1 address 2. ACH = A-Trunk Channel ATR = A-Trunk

TCU :

Layer 1: supports proprietary interface (to FU), known as Base Station (BS) -trunks, supports HDLC controller (support of LAPD), interface to the internal switch.

Signalling: LAPD L2 signalling, radio signalling link control (towards FUs), O&M link (towards OMU), terrestrial channel management (BSC-BTS channel allocation).

Radio Channel Management: receives random access channel request on Abis interface, sends broadcast and paging messages on Abis interface, manages DCCH resources (allocation, link supervision, channel release, power control), selects outgoing SCCP routing on A-interface, taking into account the best signalling spread over N7 links, sets start time and timing advance on all channel allocations, processes measurements for handover requests, processes measurements for power control, routes transparent messages to the correct SCCP, connects BS-channel to the switch, on connection request, manages channel configuration (if modified), manages frequency hopping (if modified), handles trace-invocation.

Those explanations are valid for Telecom functions. For O&M functions please refer to BSS reference guide.

.



S2: BSC local maintenance Transmission SBL at BSC side

SBL’s identification

0 ABIS HWAY TP : abis highway termination point0 ATER HWAY TP : sub multiplexer highway termination point0 BSC ADAPT : base station controller adapter0 BTS ADAPT : base transceiver station adapter0 SM ADAPT : sub multiplexer adapter0 TC 16 : 16 channels transcoder function 0 TC TS : transcoder time slot (*)0 TSC : transcoder sub multiplexer controller

• (*) not seen by the BSC terminal

Abis-HWAY-TP : Provides a G703/G704 link between BSC and BTS. The multiplexing scheme depends on the BTS network topology (ring/star) and on the BTS configuration (number of FUs installed, channels rate, etc.). The mapping is produced by a configuration tool. It carries speech and data.

ATER-HWAY-TP : G703/G704 link multiplexing A-trunks (the multiplexing sheme can be either 3 or 4 A-trunks per submultiplexer highway).

BSC-ADAPT : Multiplexes BS-trunks onto an Abis highway. The number of multiplexed BS-trunks is configurable on the BSC-BTS interface at the BSC site.

BTS-ADAPT : Demultiplexes Abis channels from an Abis highway. The number of demultiplexed Abis channels is configurable on the BSC-BTS interface at the BTS site.

SM-ADAPT : Performs the multiplexing of Ater links.

TC16 : Performs the transcoding between the PSTN coding (64 kbps channel) and the GSM/DCS coding (13 kbps) for 16 channels.




S2: BSC local maintenance Transmission SBL at BSC side

Transmission SBL‘s layout & hierarchy

ATER-HWAY_HP

ATER-HWAY_TP

SM-ADAPT*

SM-ADAPT*

TC-ADAPT*

TC16 TC16

A-PCM-TP*

ABIS-HWAY_TP*

ABIS-HWAY_TP*BTS-ADAPT*

BSC-ADAPT*

DTC

1…6

1…2

1…4

1…4

SBL are hierarchically associated in a father / child relationship

SBL B is assigned to SBL A by using the CONF relationship forA B SBL B within the HW configuration report (“ “) means more than 1.

* means the box represents several instances of the SBL



S2: BSC local maintenance LEDs and Alarms

LEDs flashing convention

=

=

=

LED Off

LED On

LED Flashing

Front mounted LEDs

=

=

=

LED Off

LED On

LED Flashing

Side mounted LEDs

= Not Relevant




CPRC / TCUC / DTCCPower on - Reset LED states

Operational (Flashing LEDs indicate OBC is active)

PBALED

4

3

2

1




Slaves CPRC / TCUC / DTCCLoading LEDs

Awaiting loading

Loading slave PBAs and operational

Loading

PBALED

4

3

2

1




BCLA SYSStatus LEDs

LED 4

LED 5

LED 2

LED 1

LED 3

PBA None

Selected Reference clock

Local Ater 1 Ater 2 Ater 3

Error Condition (note 1)

(note 2)

ExternalBCLA is Master

BCLA is Slave

Operational States

ON for the following errors :- reference failure- PLL out of control range- Broadcast signal failure

Note 2 : LED 4 flashing indicates one of the following :Flashing rate = 1s On / 1s OffPower on : the PBA is initialised and a time out is started to get the PLL locked on to the local oscillator.

Flashing rate = 150 ms On / 150 ms OffError after power on : the PLL locked on time out has expired and either the POOR state still exists or a reference failure has been detected. The PBA does not start the normal function and waits until the poor and / or reference failure disappears. Normally, the PBA must be repaired.

Flashing rate = 300 ms On / 300 ms OffTest mode

Flashing rate = 600 ms On / 600 ms OffThe PBA is forced to “local oscillator” by means of a plug on the backpanel.




BCLA RACKStatus LEDs

PBALED

4

3

2

1

A B

Selected systemclock

Operational states

(note 2)

(note 1)

Errorcondition

Note 1 : LED 4 is ON for the following errors :- reference failure- PLL out of control range- Broadcast signal failure- Clock drivers disabled

Note 2 : LED 4 flashing indicates one of the following :Flashing rate = 1s On / 1s OffPower on

Flashing rate = 150 ms On / 150 ms OffError after power on : the PLL locked on time out has expired and either the POOR state still exists or a reference failure has been detected. The PBA does not start the normal function and waits until the poor and / or reference failure disappears. Normally, the PBA must be repaired.

Flashing rate = 300 ms On / 300 ms OffTest mode




TSCA / ASMB / BIUA

Status leds

LED 3 on : service alarm

LED 4 on : prompt maintenance alarm

Operational (Flashing LEDs indicate OBC is active)

PBALED

4

3

2

1



S2: BSC local maintenance BSC terminal description

Hardware requirements (minimum)

0 Pentium 233 MHz processor0 64 Mb of RAM0 At least 100 Mb free for program and data storage0 1 3½“ floppy drive0 1 CD-ROM drive0 1 serial RS232 port0 1 X25 serial communication board (*)0 1 SVGA video adapter with1024x768pixel resolution0 1 SVGA monitor0 1 PS2 or serial mouse

• see BSC terminal user guide for board compatibility




Software requirements

0 Microsoft Windows 2000 / XP operating system0 Windows BSC terminal application software0 Optional Connections for Windows software for the X.25 EICON C91 or

ACB-PCMCIA link.




Two kind of BSC connection : RS232 - X25RS232

X25 type 1 (EICON C91 X25 board)

There are two ways to connect on the BSC with the BSC terminal.

The first one is to use the RS232 link. This is done normally at the first step of the commissioning while the mini build is not yet loaded in the BSC. Anyway the “normal” way to connect the BSC terminal is to use the X25 connection.




Two kind of BSC connection : RS232 - X25X25 type 2 (ACB PCMCIA X25 board)



S2: BSC local maintenance BSC terminal functions

File menu

Standard windows menu




Command menu

This menu, the command menu is the one which is mostly used for BSC maintenance.It allows to read and change SBL states, to manage SSD content, to perform tests and to extend or reduce

BSCs and BTSs.




Utilities menu

This menu is mainly used during commissioning to transfer the mini build from PC to BSC.

It’s also possible by connecting the BSC terminal to the standby CPRC - SYS to check BTSs downloading.




View menu





Window menu





Help menu





Report window example

This is an example of a report view at the BSC terminal.

On this screen the engaged action was to read the status of the DTCC 1. This SBL (so the board) is In Traffic.


Session 3

BSC local maintenance

Practice




S3: BSC local maintenanceObjective and program

Objective: To be able to perform the main maintenance tasks

Program: Platform Hardware Identification

BSC terminal practice and BSS software overview

SBL practice

To replace an RIT using the appropriate BSC task procedure

To analyse fault messages using the alarm dictionary

Analyse the BTS software download



S3: BSC local maintenance Practice

Objective : Platform Hardware Identification

Identify how many BTS are connected to the BSC and which type

Identify the physical links between BSC/BTS

With the help of the site description document, if it exists, and looking at the DDF, identify the A-bis TSU used and the A-bis ports used

Without using the BSC terminal give the hardware status of the BSC (alarms, clocks, Common TSU)




Objective : BSC terminal practice and BSS software overview

Using the necessary software package and documents install, configure and connect the BSC terminal

Make a BSS software dump on SSD A and SSD B, check that files are identical

Identify the master files for BTS, BSC and BSS

Identify the BSS cipher and BSS software version




Objective : SBL practice (1)

Confirm the results found in previous exercise using the BSC terminal0 What kind of method are you going to use ?0 Is it possible to find the TRX number for each BTS ?0 Is it possible to find the sector number for each BTS ?

At the BSC terminal identify SBL’s0 Which kind of SBL have « BSC », « BSS », « BTS » for parents ?0 Is it possible for some SBL to have more than one parent ?0 Which ones ?

For each SBL give a quick definition





Make a drawing showing the BSC transmission SBL’s

What is the meaning of _TP SBL’s ?

List the SBL of the BSC that are in state other than IT, SOS, NEQ. Explain the results





Disable a TCU SBL0 Print out the states of the offspring SBLs and the BTS_TEL 0 What do you notice ?0 Reactivate the TCU SBL0 Check that the SBLs are IT





Deactivate the BTS_OM SBL0 Check that BTS_TEL SBL is still IT0 Reactivate BTS_OM SBL





Restart the active system CPR0 Check the LEDs states during and after the switchover0 Connect the X25 link to the new active system CPR0 Note how the LEDs react




Objective : To replace an RIT using the appropriate BSC task procedure (1)

Replace a TCUC using the task procedure0 Deactivate the SBL0 Print out the states of the SBLs supported by this RIT0 Replace the RIT0 Reactivate the SBL

TOOL : BSC Corrective Maintenance Handbook





Replace a DTCC using the task procedure0 Deactivate the SBL0 Print out the states of the SBLs supported by this RIT0 Replace the RIT0 Reactivate the SBL





Replace a CPRC SYS using the task procedure0 Deactivate the SBL0 Print out the states of the SBLs supported by this RIT0 Replace the RIT0 Reactivate the SBL





Replace a TSCA using the task procedure0 Deactivate the SBL0 Print out the states of the SBLs supported by this RIT0 Replace the RIT0 Reactivate the SBL




Objective : To analyse fault messages using the alarm dictionary (1)

Simulate a fault by removing a SWCB RIT0 Analyse the fault messages using the alarm dictionary

Be careful : there are two kind of switches in the BSC : - AS (access switch) type SWCB- GS (group switch) type SWCA

By removing a group switch a lot of CE are going to be disconnected from DSN.





Ask the instructor to disconnect a PCM interface on the BIE at the BTS side0 Analyse the fault messages using the alarm dictionary0 Note down the states of the LEDs





Remove a TCUC0 What do you notice ?0 Reactivate the TCU




Objective : Analyse the BTS software download

List the BTS files while the OMU is loading0 Connect the BSC terminal to the standby CPR (X25)0 Find the « BTS download status » sub menu0 Ask the instructor to reset the BTS from the OMC/R0 Note down the time it takes to load the BTS0 Print out a list of the BTS files


Session 4

TC G2 local maintenance

Telecom & Transmission




S4: TC G2 local maintenanceObjective and program

Objective: To be able to describe the TC terminal and transmission SBL at TC side for local equipment management and troubleshooting

Program: Transmission SBL at TC side

TC G2 LEDs and Alarms

TC G2 terminal description

TC G2 terminal functions



S4: TC G2 local maintenance Transmission SBL

SBL’s identification

0 A PCM TP : A trunk link termination point0 ATER HWAY TP : sub multiplexer highway termination point0 SM ADAPT : sub multiplexer adapter0 TC ADAPT : transcoder adapter

• please refer to BSC transmission for hierarchy mapping

A-PCM-TP : G703/G704 MSC TC link which can carry speech and data channels.

ATER-HWAY-TP : G703/G704 link multiplexing A-trunks (the multiplexing scheme can be either 3 or 4 A-trunks per submultiplexer highway).

TC-ADAPT : Performs the adaptation between MSC-TIU links and TIU-SM links.




S4: TC G2 local maintenanceLEDs and Alarms

ASMC / ATBXStatus LEDs

LED 5 (green) : power on

LED 4 off : no alarm

LED 4 flashing : alarm

LED 1-3 : off during normal operation

PBALED

5

4

3

2

1

Operational No Alarms



S4: TC G2 local maintenanceLEDs and Alarms

DT16Status LEDs (operational combinations)

Red

PBA

Yellow

Red

Green

Permanently off

Permanently off

On indicates at least one call

Operational, but no call (all SPUs in

idle state)

Operational, at least one call (at

least one SPUs not in idle state)

The DT16 PBA has four LEDs. There are two red LEDs, one yellow and one green. The two red LEDs are connected in series and operate together.

The figure shows the behaviour of the DT16 LEDs during normal operating conditions.

LED Status Definition

Red (x 2) Off Normal operation (no fault).. On The 3.3 V supply voltage is either too low or not present at all.. Flashing Hardware error.

Yellow Off All DSPs are operating correctly.. On At least one DSP is in the RESET state.

Green Off All the TRAUs are in IDLE mode.. On At least one TRAU is not in IDLE mode.



S4: TC G2 local maintenance TC terminal description

Hardware & software requirementsHardware0 Pentium 233 MHz processor0 64 Mb of RAM0 Cache Memory 512 KByte0 At least 100 Mb free for program and data storage0 1 3½“ floppy drive0 1 serial RS232 port0 1 SVGA video adapter (Video RAM 4 Mbyte)0 1 SVGA monitor0 1 PS2 or serial mouse

Software0 Microsoft Windows 2000 / XP operating system



S4: TC G2 local maintenance TC terminal description

TC connection

0 BIUA0 ASMB0 ASMC

• Since B6.2 connection on TSCA board is no more available



S4: TC G2 local maintenance TC terminal functions

Services menu (ATBX)

Depending on which transmission board you are connected, the service menu may change a little bit.This menu is used to perform tests, measurements, configuration and alarms collection on ATBX (TC), ASMB

(BSC), BIUA (BSC) and ASMC (TC).



S4: TC G2 local maintenance TC terminal functions

Services menu (ASMC - ASMB - BIUA)


Session 5

TC G2 local maintenance

Practice




S5: TC G2 local maintenanceObjective and program

Objective: To be able to perform the main maintenance tasks

Program: Platform Hardware Identification

SBL practice

To check the transmission equipment settings

To replace an RIT using the appropriate TC task procedure

To analyse fault messages using the alarm dictionary



S5: TC G2 local maintenance Practice

Objective : Platform Hardware Identification

Identify the physical links between BSC/TC - TC/MSC

With the help of the site description document, if it exists, and looking at the DDF, identify the A-ter TSU used and the A-ter ports used

Without using the TC terminal give the hardware status of the TC(alarms)




Objective : SBL practice

Confirm the results found in previous exercise using the TC G2 terminal and, if necessary, the BSC terminal

At the BSC terminal identify SBL’s0 Which kind of SBL have TC for parent ?0 Is it possible for some SBL to have more than one parent ?0 Which ones ?

For each SBL give a quick definition




Objective : To check the transmission equipment settings

Connect TC terminal to ASMC board, check the time slot allocation on A-ter and A-ter Mux interfaces

Connect TC terminal to BIUA board, check the time slot allocation on A-bis interface




Objective : To replace an RIT using the appropriate TC task procedure

Replace an ASMC using the task procedure

Replace a DT16 using the task procedure

TOOL : TC Corrective Maintenance Handbook





Ask the instructor to disconnect the first A-ter Mux PCM link between BSC and TC0 Analyse the fault messages using the alarm dictionary0 Note down the states of the LEDs





Ask the instructor to disconnect the first A PCM link between TC and MSC0 Analyse the fault messages using the alarm dictionary0 Note down the states of the LEDs





Analyse the consequences of a « CRC on-off » toggle on ASMC, BIUA, ATBX boards

©Alcatel University - 8AS 902001403 VH ZZA Ed.01 Page 2.1

©Alcatel University - 8AS 902001403 VT ZZA Ed.01 Page 2.1

Alcatel 9125 TC Maintenance





1 - Getting Started

2 - Transcoder Supervision

3 - Replace MT120 Board

4 - Replace Transcoder Fan Cassette




1 - Getting Started

1 - Computer Configuration1.1 - Hardware Requirements1.2 - Software Requirements

2 - Connect / Disconnect2.1 - Connect2.2 - TC Terminal Parameters 2.3 - Communication Window2.4 - TCC Window



Getting StartedComputer Configuration

Hardware Requirements

1 - Computer Configuration

1.1 - Hardware requirements



Getting StartedComputer Configuration

Software Requirements

1.2 - Software requirements



Getting StartedConnect / Disconnect

Connection

2 - Connect / Disconnect2.1 - Connect

1 Double click on the compact TC terminal icon.2 Enter your name, then press TAB.3 Enter your password, then press TAB.4 Click on OK.

The Compact TC Terminal open and the communication window appears.




TC Terminal Parameters

2.2 - TC Terminal ParametersTo check the parameters setting from the MENU BAR, select SERIAL ⌫ SETTING.




CommunicationWindow

2.3 - Communication window

In this window you can:– Connect and disconnect from the TC rack (SERIAL ⌫

CONNECT/ DISCONNECT).– View messages in hexadecimal, TLV or decoded text.– Filter messages and alarms to reduce noise.– Create a log file to consult on site or later.

With A925 transcoder, you can access all the MT120 boards by connecting to one MT120board. With EVOLIUMTM G2 transcoder, you must connect on each MT120 board individually.

Message area: Displays the messages and alarms appearing during the connection. Message input in hexadecimal decoded: Displays messages and alarms in hexadecimal, TLV or decoded text.Filter area to filter and reduce noise in the message area.

When you select SERIAL ⌫ CONNECT:The connection messages are displayed in the communication windows. The TCC window appears.The Compact TC terminal opens a monitoring window for each MT120 board.The tittle bar of each window shows the TEI (Terminal End Identifier) of each board.

– Example MT120 25 means that the TEI for that board is 25.




TCC Window

2.4 - TCC window

In this window you can:– Locate board OVERVIEW panel.– Check Ater mux and A interfaces OVERVIEW panel.– Declare BSC CONFIGURATION panel.– Download software to MT120 boards DOWNLOAD panel.– Edit site inventory SITE INFO panel.– Check fans FAN & TEMPERATURE

panel.– Supervise boards temperature FAN & TEMPERATURE.– View software inventory FILE INFO.




2 - Transcoder Supervision

1 - ALARM MONITORING1.1 - Rack layout front view1.2 - Check Leds status1.3 - Overview panel1.4 - TCC tree1.5 - Analyse MT120 board alarm1.6 - Check fans and board temperature

2 - CHECK LOGICAL PARAMETERS 2.1 - View all BSCs connected to transcoder2.2 - Check hardware, QMUX, DSP configuration

– 2.2.1 - Qmux addressing principle – 2.2.2 - Config (Changeable) panel

2.3 - Check transmission configuration3 - CHECK SOFWARE VERSIONS ON MT120 BOARD

3.1 - File Info panel3.2 - MT120 SW version handling

4 - CHECK REMOTE INVENTORY DATA4.1 - Fans/Rack inventory data (site info panel)4.2 - MT120 Remote inventory data (Remote inventory panel)

5 - EXERCISES5.1 - Alarms analysing5.2 - Check logical parameters



FANU FANUFANU

FANU FANUFANU

FANU FANUFANU

FANU FANUFANU

Top Rack Unit

Empty

JSTRU

SR2

SR1

SR3

SR4

JRTC

MT

120

MT

120

MT

120

MT

120

MT

120

MT

120

MT

120

MT

120

MT

120

MT

120

MT

120

MT

120

MT

120

MT

120

MT

120

MT

120

MT

120

MT

120

MT

120

MT

120

MT

120

MT

120

MT

120

MT

120

MT

120

MT

120

MT

120

MT

120

MT

120

MT

120

MT

120

MT

120

MT

120

MT

120

MT

120

MT

120

MT

120

MT

120

MT

120

MT

120

MT

120

MT

120

MT

120

MT

120

MT

120

MT

120

MT

120

MT

120

TEI

Slotnumber

16 17 18 19 20 21 22 23 24 25 26 27

32 33 34 35 36 37 38 39 40 41 42 43

48 49 50 51 52 53 54 55 56 57 58 59

64 65 66 67 68 69 70 71 72 73 74 75

002 005 008 011 016 019 022 025 030 033 036 039

002 005 008 011 016 019 022 025 030 033 036 039

002 005 008 011 016 019 022 025 030 033 036 039

002 005 008 011 016 019 022 025 030 033 036 039

Transcoder SupervisionAlarm Monitoring

Rack LayoutFront View

1 - Alarm Monitoring1.1 - Rack layout front view

In TCIL bus MT120 uses a simplified LPD protocol. Consequently the MT120 addressing in TCIL use the TEI value.The TEI is derived from its physical location and is unique in a TC rack.

Using LAPD protocol between BSC and each MT120 board will be possible in future realease for software downloading.




LED 7

Operational Status

Check LEDs Status

1.2 - Check LEDs status




OverviewPanel

1.3 - Overview panel

Use this panel to:– Locate boards.– Check A-termux and A interfaces.– Enable fault indication RIGHT CLICK on a BOARD ⌫ FAULT INDICATION ⌫

ON ALL BOARD ON.– Reset /restart software RIGHT CLICK on a BOARD ⌫ RESTART or RESET.– Run a commissioning loop test RIGHT CLICK on a BOARD ⌫ COMMISSIONING.– To access to MT120 individual panel DOUBLE CLICK ON A BOARD.

Top area : indicatesThe PCMs-links connection status:

– GREEN and letter C: connection with PCM links.– RED and letter DC: no connection with PCM link.

For each MT120 board:– The A-termux connected.– BSC connected.– TSC connected that mean the BSC rack.– TEI number, Subrack and slot.– The software version.

Bottom area: displays where the MT120 boards are located in A925 transcoder for G2 this area is blank.Each MT120 board is allocated a number (TEI) and a color. The board numbered in italic-bold is the master (the board you are connected to).

The colors and the meaning are the following:– Green: the board is running correctly.– Yellow : the board presents minor problem(s).– Orange: the board presents fatal problem(s).– Red: the board need to be replaced.




TCC Tree

1.4 - TCC tree

If it is not on display, open the TCC tree VIEW ⌫ OVERVIEW:

The TCC TREE indicates:– On which subracks MT120 boards are located.– Under which number each board is referenced.– And depending on the color, whether each board is functioning correctly.

The colors and the meaning are the following:– Green: the board is running correctly.– Yellow : the board presents minor problem(s).– Orange: the board presents fatal problem(s).– Red : the board need to be replaced.

You can DOUBLE CLICK ON A BOARD to display its individual panel.




Analyse MT120 Board Alarms

1.5 - Analyse MT120 board alarmsIn this window, you can:

– View alarms which are specific to the board.– Download software.– Activate software.– Define BSC and Hardware configuration.– Run a commissioning loop test.– Modify the remote inventory.– Execute the board replacement software procedure.

Top area :Displays all the alarms for the board, in their order of appearance. If MT120 board is the master board (the board you are connected to) you can also see the alarms for the rack:

– A check in the active column indicates that the problem which generated the alarms has not been solved.

– A square in the Active column indicates that the problem which generated the alarm has been solved.

Bottom area :Displays all the pending alarms.

The time stamp column does not indicate when the alarm occurred, but when the Compact TC Terminal has received it.

For a full description of alarms and how to solve the problem, refer to BSC/TC Alarm dictionary.




Check Fans and Boards Temperature

1.6 - Check Fans and Boards Temperature

Use the Fan &Temperature panel to:– Test fan.– Supervise board temperature.

Top area:To test fans at different speeds.

Middle area:To view the temperature curve of a board.

Bottom area:To read the temperature of each board.To view its temperature.To select a board to view its temperature curve. ACTIVATE.

For G2 transcoder this area is blank.



Transcoder SupervisionCheck Logical Parameters

View all BSCs connected to TC

2 - Check Logical Parameters2.1 - View all BSCs connected to the Transcoder

Use the configuration panel to:– Declare BSCs.– Generate a rack inventory.

Top Area:To specify the rack number and PCM impedance.

Middle area:To view BSCs and if necessary, enter new one.

Bottom area:To generate fans/rack remote inventory.




@Qmux 16

Qmux

@Qmux 4

@Qmux 8

@Qmux 24

Qmux

@Qmux 20

@Qmux 0A-ter mux1

A-ter mux2

A-ter mux3

A-ter mux4

A-ter mux5

A-ter mux6

BSC1

Rack1

@Qmux 16

Qmux

@Qmux 4

@Qmux 8

@Qmux 24

Qmux

@Qmux 20

@Qmux 0A-ter mux7

A-ter mux8

A-ter mux9

A-ter mux10

A-ter mux11

A-ter mux12

BSC1

Rack2

@Qmux 16

Qmux

@Qmux 4

@Qmux 8

@Qmux 24

Qmux

@Qmux 20

@Qmux 0A-ter mux1A-ter mux2

A-ter mux3

A-ter mux4

A-ter mux5

A-ter mux6

BSC2

Rack1

Cluster A TC2

Cluster B TC3

Cluster D TC2

Check Hardware, Qmux, DSP Configurations: Qmux Adressing principle

2.2 - Check hardware, QMUX, DSP configuration– 2.2.1 - Qmux addressing principle

In this example the BSC1 is connected to two different TC (rack 1 to TC2 and rack 2 to TC3).BSC2 rack 1 is connected to TC2.The MT120 boards could be any board of the rack.The rule for qmux addressing is the following:

A-termux QMUX ADRESS1 7 13 02 8 14 43 9 15 84 10 16 165 11 17 206 12 18 24




Check Hardware, Qmux, DSP Configurations

Config. (changeable) Panel

– 2.2.2 - Config (changeable) panelIn this window, you can:

Define BSC and hardware configuration.Execute on line configuration of the board (transmission programming).Execute the board replacement software procedure.

Top area:To define which BSC the board is in connection with and the A-termux number.

Middle area:To enable Qmux and set the DSP configuration.

Bottom area :To execute on line configuration or replace a board.




Check Transmission Configuration

2.3 - Check Transmission ConfigurationIn this window you can:

– Define BSC and hardware configuration.– Execute on line configuration of the board (Transmission programming).– Execute the board replacement software procedure.

Top area :Check LAPD configuration.

Middle area :To read if CRC4 is enabled or not.

Bottom area :To Check transmission setting.

Predefined files are used:– A law or mu law.– A-termux mapping 3:1 or 4:1.– N7 or not.– X25 or not.



Transcoder SupervisionCheck SW Versions

Check the current Software Version on

MT120 Board

3 - Check the current Software Version on MT120 Board3.1 - File Info panelUse the configuration panel to:

– View the software inventory for each board of the rack.

3.2 - MT120 SW versions handlingThe MT120 is able to store 3 SW versions in its flash EPROM memory:

– V0 is store in factory in a protected area ( p).– V1 and V2 are stored on site by preload mechanism, in a non protected area of the flash. A

compressed (c) and a non compressed version are stored in flash memory (f). The MT120 uses VO at first installation or when V1 or V2 are corrupted. V1 is the running version and V2 is the previous version. The MT120 board uses V1 (current) after correct preload and activation, and uses V2 (previous) if V1 is corrupted.

For each MT120 SW a status is defined:– Current SW that is currently running the board.– Previous SW that used to run the board before the current SW.– Preloaded SW which has been downloaded but not yet been activated.– Fallback last remaining preloaded version of the current software.– Original Factory software that originally came with the board.



Transcoder SupervisionCheck Remote Inventory Data

Fans/Rack Inventory Data

(Site Info Panel)

4 - Check Remote Inventory Data4.1 - Fans/Rack inventory data (Site Info Panel)Use the configuration panel to:

– Check and if necessary, modify general site remote inventory data.– Check or modify the site information on MT120 board.

Top Area:Check and if necessary, modify general site remote inventory data.

TEI columns:To see which boards hold which site information.

Bottom area:To check which board(s) hold different information from the general site information, and what that information is.



Transcoder SupervisionCheck Remote Inventory Data

MT120 Inventory Data

(Remote Inventory Panel)

4.2 - MT120 Inventory Data (Remote Inventory Panel)Use this panel to view and, if necessary, modify the remote inventory of the MT120 board.



Exercise 1Alarm Analysing

Using the TC Terminal and the Alarm dictionary, analyze the alarms present in:

MT120 BoardFan Cassette

Locate the boards in the TC rack and check the LED Status

5 - Exercises5.1 - Alarm analysing



Using the TC Terminal, complete the diagram of the BSC - MT120 connections :

BSCRack Number 1

TranscoderRack Number 1

Exercise 2Check Logical Parameters

A-ter Mux number: Qmux TS:

X25 TS:CRC enable:

TEI:SLOT: SR

TRAU LAW

A-ter Mux mapping typeCRC enable:

X25 TS:

Qmux TS: @ Qmux:N7 TS:

BSC name:

5.2 - Check Logical Parameters



BSCRack Number 2




X25 TS:CRC enable:

TEI:SLOT: SR

TRAU LAW


X25 TS:



BSC name:




BSCRack Number 3




X25 TS:CRC enable:

TEI:SLOT: SR

TRAU LAW


X25 TS:



BSC name:




3 - Hardware Module Replacement


1 - MT120 BOARD REPLACEMENT GENERAL PROCEDURE2 - REPLACE MT120 BOARD USING REPLACEMENT COMMAND3 - MT120 BOARD MANUAL REPLACEMENT4 - SOFTWARE DOWNLOAD IN MT120 BOARD5 - REPLACE TRANSCODER FAN CASSETTE6 - EXERCISES



Launch the Replace Procedure

Hardware Module ReplacementMT120 Board Replacement General Procedure

Connect TC Terminal to any Board

Execute the Module Replacement Command

Are the Configuration Files Uploaded ?

Check that PCM Links carry any Telecom Traffic

Unbolt and Replace Board

Check the Qmux Cluster Parameters

Check the Transmission Parameters Set up the MT20 Remote Inventory

Check that PCM Links carry any Telecom Traffic

Is it the good Software Version ?

Set up the MT20 Remote InventorySet up the Fans/Rack Remote Inventory

Configure the Board for Operational Mode

Download the Generic Transmission Settings

Check Board Transmission Data

Download the SW Board

Activate the Software

Unbolt and Replace Board

Yes No

NoYes

1 - MT120 Board Replacement General Procedure



Hardware Module ReplacementReplace MT120 Board, using Replacement Command

2EXECUTE

THE MANUAL REPLACEMENT

2 Execute the Module Replacement CommandThe TC terminal uploads the configurations files (this includes the SW

version and the configurations files) in the directory c:\programfiles\Alcatel\Tcterminal\trm

Are the Configuration Filesuploaded ?

1 Connect TC terminal to any board

Replacement 1

Yes No

2 - Replace MT120 Board using the Replacement Command2.1 - Replacement

– 2.1.1 - Overview•This command is used to ease the replacement procedure; the actions of the operator are limited to the strict necessary. The only constraint is that the TC terminal must be able to retrieve the current configuration of the MT120 board to replace (this includes the SW version and the configuration parameters to run the MT120 board).

– 2.1.2 - Replacement




3

5

3 CHECK THAT THE PCM LINKS CARRY ANYTELECOM TRAFFIC (Link status disconnected)

4 UNBOLT MT120 BOARD,REPLACE IT BY A NEW ONE

5 LAUNCH THE REPLACE PROCEDURE

At the end of the auto test (5 minutes) the TC terminalchecks the SW version in the MT120 board and if

necessary downloads and activates the correct version. Afterwards the TC terminal configures and sets up the

fans/rack RI

3

Replacement 2




7

8

7 CHECK THE Qmux CLUSTER PARAMETERS

8 CHECK THE MT120 BOARD

TRANSMISSION PARAMETERS

Check Board Logical Configuration

2.2 - Check board logical parameters



99 SET UP BOARD REMOTE INVENTORY

(e.g. Commissioning date, network identity...)

Set up MT120 Board Remote Inventory

Hardware Module Replacement Replace MT120 Board, using Replacement Command

2.3 - Set up MT120 board remote inventory data



1

Are the Configuration Filesuploaded ?

No

1 CHECK THAT MT120 BOARD CARRIESNO TELECOM TRAFFIC

2 UNBOLT AND REPLACE THE MT120 BOARDAs there is no disable command, carefully extract it

from the back panel

3 WAIT FOR THE END OF SELF TEST

Yes No

DOWNLOAD SWIN MT120 BOARD

4 Is it the good SW Version ?

Board Replacement

Hardware Module Replacement Replace MT120 Board, Manual Replacement

3 - MT120 Board Manual Replacement3.1 - Replace board



6

6 SET UP THE FANS/RACK REMOTEINVENTORY

5 SET UP BOARD REMOTE INVENTORY(e.g. Commissioning date, network identity...)

YesBegin

End

6


Set up BoardRemote Inventory Data


3.2 - Set up board remote inventory data–1. Open the “TCC - Site Info” window

In the TCC window, click the “Site Info” tab.The “TCC - Site Info” window shows up. SEE BEGIN

–2. Complete the site and rack/fan informationA On the bottom part of the window click the <Default> button to completethe fields with the default RI data in the “other” area of the window. B In the

“other” area complete also the following fields: SEE BEGIN–Site name: name of the site (max. 10 characters)–Rack Serial No: rack serial number–NbrFanUnitsInRack: number of fan units in the rack (max. 12)–Commissioning date: date of commissioning (YYMMDD)–First commissioning date: see NOTE (YYMMDD)

–NOTE: It is the same as commissioning date.C On the bottom of the “TCC - Site Info” window choose: Site Info text used to reload all MT120: other

–3. Update all MT120 with site and rack/fan dataA Click <Update All>B Wait for the action to complete.

–At the end of the process all the RI data can be seen in the “most used” area and all the MT120 boards are listed in the corresponding “TEI” column (no board is left in the “other” area). SEE END.



7

8 DOWNLOAD THE GENERICTRANSMISSION SETTINGS

7 CONFIGURE THE NEW MT120 BOARD FOR OPERATIONAL MODE

I.E. Enter the configuration parameters especially the BSC number and the Ater mux

number for the Qmux cluster setting

Yes

8

Set up BoardLogical Data


3.3 - Setup board logical data–They are 12 generic files 6 for A law and 6 for MU law.–For each coding 3 for 3:1 and 3 for 4:1 multiplexing type.–For each multiplexing type they are 3 files:

•no X25 (No X25 and N7).•X25 MSC (X25 at MSC and N7).•X25 TC (X25 at TC and N7).



9 CHECK BOARD TRANSMISSION DATA

Yes

9

Check Board Transmission Data


3.4 - Check board transmission data



DownloadPanel

Hardware Module Replacement Software Download in MT120 Board

4 - Software download in MT120 Board4.1 - Download panel–Use the download panel to:

– Download software.– Activate software.– Delete preloaded software.

–Top area: To select a SW to download.–Bottom area: To select board to:

– from which to download software.– On which to download, activate or delete software.

–With a G2 TC this area is blank.–TCC enable you to download software to one or several board at the same time.You can download software that is in your PC or on one board of he rack.–When you download SW that is in your PC, it is first preloaded onto a board, then block-loaded from that board onto the other board.–When you select the software (...) check the color of the board:

– White:the board can be selected for the download.– Green: the software is currently running the board.– Orange: the software has already been preloaded on the board. It is from that board that

the software will be block-loaded on to the other board.–During the download check the color of the boards:

– Yellow: the software is being downloaded.– Green: the software has successfully downloaded.– Red: failure in downloading.



CommissioningPanel


4.2 - Commissioning panel–Use the download panel to:

– Download software.– Activate software.– Run commissioning loop test.

–Top area: To select a SW to download from: – a board (BLOCK).– or PC (PRELOAD).

–Middle AREA: Display messages linked to downloading, activation or deletion of the software.–Bottom area: To select board to:

– To run a commissioning loop test on a board.



1 No

1 DOWNLOAD THE BOARDChoose the software to be downloaded.

The board to be downloaded turns in white.On the bottom part, double click on the board

to be downloaded. The selected board turns in dark blue

SUBMIT

AFTER ACTIVATION a rest takes placeAnd the board turns green

2

2 ACTIVATE THE SOFTWAREChoose the software to be activated.

The board to be downloaded turns in white.On the bottom part, double click on the board

to be activatedSUBMIT


SoftwareDownloadandActivate


4.3 - Software download and activate



1 UNBOLT THE FAN CASSETTE,REPLACE IT BY A NEW ONE

2 TEST THE FAN CASSETTE

2

Replacement and Test

Hardware Module Replacement Replace Transcoder Fan Cassette

5 - Replace Transcoder Fan Cassette



Hardware Module Replacement Exercises

1 : Replace 1 MT120 Board using the Replacement Command

2 : Replace 1 MT120 Board using Manual Replacement without Software Download

3 : Replace a Transcoder Fan Cassette

TOOL : TC Corrective Maintenance Handbook

6 - Exercises

Documents

BSC TC Maintenance (Alcatel)