Boards Locations

8/12/2019 Boards Locations

1/29

SMMMAINT

OPERATING / MAINTENANCE SHEETE10B SMMMAINT

FUNCTION : MAINTENANCE STATION - SMM

SUB-FUNCTION : MAINTAINING THE SMM

1 PURPOSESMMMAINT explains how to carry out maintenance on maintenance stations (SMMs).

2 WHEN TO USE SMMMAINTUse SMMMAINT :

- When the following alarms appear:

For this alarm... see...

"SMM SWITCHOVER" section 6.1

"DISK POWER SUPPLY" section 6.2

"STREAMER POWER SUPPLY" section 6.3

"STANDBY SMM OOS" section 6.4

"CONVERTER" section 6.5

"SAI HARDWARE" section 6.6

"OPTION NON STANDARD" section 6.7

"SAI SOFTWARE" section 6.8

- In the following cases:

If you want to... see...

set the SMM to BLOM section 5.4

run a LOCAVAR test on an SMM section 5.3

repair an SMM component section 7

start the SMM in manual mode section 5.1

carry out an SMM switchover section 5.2

ascertain the SMM startup options Appendix A

3BW36141AAAXREAHA Ed. 03 1 / 29
http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-


2/29

SMMMAINT

If you want to... see...

ascertain the equivalence between an RTOS ob-ject and physical line units

Appendix B

have a view of the ACCSG board Appendix C

have a view of the DACLE1 daughter board Appendix D

have a view of power distribution in the OCB2 83 Appendix E

react when there is no operational subsystem section 5.5

3 WARNING

CAUTION: IF THE PROCEDURE leads you to replace a board

TAKE NOTE OF THE PRECAUTIONS TO BE FOLLOWED for extract-ing and inserting a board. These precautions are described inthe Co rrecti ve maintenance management operator guideMCGOP.

4 OVERVIEW To carry out maintenance on SMMs:

a) Execute the procedure for the alarm (see section 6).b) If necessary, refer to Appendix B to identify the faulty equipment.

c) Repair the equipment (see section 7).

d) End.

5 INDIVIDUAL ACTIONS

5.1 How to start the SMM in manual modeTo start the SMM in manual mode:

a) Raise physical switch I1 on the ACCSG board of both SMMs.

b) Switch over subsystems A and B:

use the CTIBSC (see FOP CTIBSC) on the OM console, or

raise switch V2 on the ACCSG board of the worker subsystem (ACCSG LED D1 on) (see Appendix C).

c) Complete the startup option after the following message appears on the support console:

***** OM INITIALISATION ? (OPTION;) *****

2 / 29 3BW36141AAAXREAHA Ed.03
http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-


3/29

SMMMAINT

==>Note : The startup options are described in Appendix A.

d) Lower physical switches I1 to enable a future startup in automatic mode for startup in NORON ,RITON or INION mode.

e) End.

5.2 How to perform an SMM switchoverTo perform an SMM switchover:

a) Switch over subsystems A and B:

use the CTIBSC command (see FOP CTIBSC) on the WAM terminal, or

raise switch V2 on the ACCSG board of the worker subsystem (ACCSG LED D1 on) (see

Appendix C).b) End.

5.3 How to run a LOCAVAR test on the standby SMMTo run a LOCAVAR test on the SMM:

a) Set the SMM to BLOM.

b) Execute the SETSCH: TEST; command (see FOP SETSCH) on the WAM terminal.

c) End.

5.4 How to set the SMM to BLOM standby To set the SMM to BLOM:

a) Execute the SETSCH: BLOM; command (see FOP SETSCH) on the WAM terminal.

b) End.

5.5 How to react when no subsystem is operating When no subsystem is operating, the total failure interface is activated and no "SYSTEME PRET" mes-sage is generated.

To react when no subsystem is operating:

a) Attempt an SMM switchover by activating reset switch V2 on the worker subsystem (the one forwhich LED D1 on the ACCSG board is lit).

b) Check the history of alarms on printout or in the TI-PGS log and look for a hardware alarm relatingto the SMM.



4/29

SMMMAINT

If... then...

an alarm is present and has not been repaired a) Block the SMM:

1) lower physical switches V1 on bothSMMs

2) momentarily set physical switches V2 upon both SMMs to perform a reset

b) Repair the faulty board (see section 6)

c) Restart the SMM:

1) raise physical switches V1 on bothSMMs

2) momentarily set physical switches V2 upon both SMMs to perform a reset

there are no alarms that have not been dealt with momentarily set physical switches V2 up on bothsubsystems to perform a reset

c) Reload the system from the streamer (see FEX SMDKRST2).

d) End.



5/29

SMMMAINT

6 DEALING WITH ALARMS

6.1 "SMM SWITCHOVER" ALARMTo react to the "SMM SWITCHOVER" alarm:

a) Check the messages output on the WAM te rminal:

If... then...

start of LOCAVAR test messages are output onthe WAM terminal , there is a hardware prob-lem

wait for the diagnostic reports to be output:

- If the LOCAVAR test is the subject of a di-agnostic report, the faulty equipment andthe processing subsystem go to BLOS. The"STANDBY SMM OOS" alarm appears. Dealwith the alarm (see section 6.4).

- If the LOCAVAR test is not the subject of adiagnostic report, an end of LOCAVAR testmessage with error code = 0 is output. Thestandby subsystem is reset as if the switchoverwas due to a non-hardware fault.Note : If two consecutive LOCAVAR

tests are run and find no faultsin under an hour, the sub-system is set automatically toBLOS and the "STANDBY SMMOOS" alarm appears. Dealwith the alarm (see section6.4).

- a SYSTEM post mortem dump (PMD) is gener-ated on the WAM terminal

- an APPLICATION post mortem dump (PMD)is generated on the terminal assigned tothe YSYS logical file , there is a software

problem

Carry out the procedure described in FEX SMPMD.

b) End.

6.2 "DISK POWER SUPPLY" alarmTo react to the "DISK POWER SUPPLY" alarm:

a) Check for the presence of the "SAI-HARDWARE" alarm.

b) If an alarm message concerns a converter powering a disk , repair the converter. Go to the nextstep.



6/29

SMMMAINT

c) Set the disk controller to BLOM using the SETEQP: OBJET_CD,BLOM; command (see FOPSETEQP):Note : To obtain the exact name of the "OBJET_CD" object, see appendix B.

d) Run a LOCAVAR test on the disk controller using the SETEQP: OBJET_CD,TEST; command (seeFOP SETEQP):

e) Depending on the result of the LOCAVAR test, the mirror function may be restored by replacing thedisk. (See FEX SMDKRST1):

f) End.

6.3 "STREAMER POWER SUPPLY" alarmTo react to the "STREAMER POWER SUPPLY" alarm:

a) Check that the alarm is supplemented by an "SAI-HARDWARE" alarm.

b) Analyze the alarm messages concerning the converters:

Check whether the alarm message concerns a converter powering the streamer (see AppendixE). If it does, repair the converter (see section 6.5) and go to the next step.

c) Set to BLOM the streamer controller identified in the alarm messages using the SETEQP :OB-JET_CSMR,BLOM; command (see FOP SETEQP).Note : To obtain the exact name of the "OBJET_CSMR" object, see Appendix B.

d) Run a LOCAVAR test on the streamer controller using the SETEQP: OBJET_CSMR,TEST; com-mand (see FOP SETEQP):

if the result is OK, go to the next step,

otherwise, replace the streamer.

e) Set the controller to ES using the SETEQP: OBJET_CSMR,ES; command (see FOP SETEQP).

f) End.

6.4 "STANDBY SMM OOS" alarmTo react to the "STANDBY SMM OOS" alarm:

a) Refer to the table below:

If the alarm is due to... then...

an operator command setting the procedure is finished

the presence of a converter alarm or "SAI-HARD- WARE" alarm

repair the faulty equipment (see section 7)

Note : The SMM remains unsecured until the repair is carried out and validated.

b) End.

http://-/?-http://-/?-


7/29

SMMMAINT

6.5 "CONVERTER" alarmTo react to the "CONVERTER" alarm:

a) If the alarm concerns a 5 V converter on SMMA or SMMB or the 5 V converter of the disk and

ACAJB board, repair the converter (see section 7.4).b) For all other converters, carry out the procedure indicated in the Alarm dictionary ALA283.

c) End.

6.6 "SAI HARDWARE" alarmTo react to the "SAI-HARDWARE" alarm:

a) Check for the presence of the "CONVERTER" alarm:

if there is a "CONVERTER" alarm, deal with it (see section 6.5), if there is no "CONVERTER" alarm:

1) Note down the name of the object identified as suspect in the alarm message.

2) Refer to Appendix B to obtain the equivalence between the RTOS object name and the physicalequipment.

3) Carry out the repair (see section 7).

b) End

6.7 "OPTION NON STANDARD" alarmTo react to the "OPTION NON STANDARD" alarm:

a) Check the setting for the next SMM startup using the ESYIN command (see FOP ESYIN).

b) If the OLAF setting is not NORON, assign that setting using the ESYMO command (see FOPESYMO).

c) End.

6.8 "SAI SOFTWARE" alarm"SAI SOFTWARE" alarms are transmitted via the station alarm interface (SAI). They contain additionalinformation on the source of the message. All that is covered here are alarms concerning the MSS orswitches. For other "SAI SOFTWARE" alarms, see:

- the RTOS alarms dictionary ALARTOS , when the additional information begins with the letter C,

- the TMNK alarms dictionary ALATMNK , when the additional information begins with the letter E.



8/29

SMMMAINT

CAUTION: "SAI-SOFTWARE" ALARMS ALWAYS POINT TO THE SMMthat was the worker when the fault was detected.

CHECK THE SWITCH POSITIONS BEFORE TAKING ANY ACTION.

6.8.1 "SSM TEMPOR. DEGRADED" additional information

This alarm appears when disks are being controlled by an operator command which clears the mirrorfunction. It requires no operator action.

6.8.2 "SSM ABNORMAL DEGRAD." additional information

This alarm appears when temporary degradation of the MSS persists beyond the time of the operatorcommands controlling the disks.

To react to an "SSM ABNORMAL DEGRAD." alarm:

a) Restore the mirror function (see FEX SMDKRST1).

b) End.

6.8.3 "LOGICAL KEY POSITION" additional information

This alarm appears when a logical switch is incorrectly set.

To react to a "LOGICAL KEY POSITION" alarm:

a) Execute the MCLEMO command (see FOP MCLEMO).

b) End.

6.8.4 "MANUF. PRES. LOG. KEY" additional information

To react to a "MANUF. PRES. LOG. KEY" alarm:

a) Execute the MCLEMO command (see FOP MCLEMO).

b) End.

6.8.5 "PHYSICAL KEY Ix" additional information

To react to a "PHYSICAL KEY Ix" alarm:

a) Set physical switches Ix on the ACCSG boards correctly (see ACCSG board diagram in AppendixC).

b) End.

6.8.6 "AIDED START KEY" additional information

To react to a "AIDED START KEY" alarm:

a) Set the V1 physical switches on the ACCSG boards correctly (see the diagram of the ACCSG board

in Appendix C.



9/29

SMMMAINT

b) End.

6.8.7 "MANUF. PRES. PHYS. KEY" additional information

To react to a "MANUF. PRES. PHYS. KEY" alarm:

a) Raise switch V4 on the DACLE1 daughter board behind the backplane of the Xbus subracks (seethe DACLE1 daughter board diagram in Appendix D).

b) End.

6.8.8 "S-SYS. STILL MASTER" additional information

To react to a "S-SYS. STILL MASTER" alarm:

a) Raise physical switch V3 on the DACLE1 daughter board of the standby SMM (see the DACLE1board diagram in Appendix D).

CAUTION: A DACLE1 DAUGHTER BOARD ERROR may cause a du-plex shutdown of the SMM.

BE SURE TO WORK ON THE CORRECT SMM.

b) End.

7 REPAIRING SMM EQUIPMENTThis section explains the procedures for repairing equipment specific to the SMM.

Note : Boards that are not specific to the SMM are described in FEX SCCARTES.

To repair equipment:

Start "SAI HARDWARE" alarm

a) Check that the maintenance kit contains a replacement with the same interchangeability index asthe item to be replaced.

b) Look for the equivalence between the RTOS object identified as suspect in the alarm message and

the faulty item (see Appendix B).c) If there is a particular procedure for replacing the item concerned, refer to that procedure:

If the item to be replaced is... refer to...

an ACBSG or DCCBPH board section 7.1.1

an A CCSG board section 7.1.2

an ACFTD board section 7.1.3

a DATSTA and DATSTB daughter board section 7.1.4

an ACTUJ board section 7.2.1

http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-


10/29

SMMMAINT

If the item to be replaced is... refer to...

an ACRAL2 board section 7.2.2

ACJ64, DCV11 and ACV11 boards section 7.2.3

a magnetic tape unit section 7.3.1

a streamer section 7.3.2

a disk section 7.3.3

an AE12V or AE412 converter section 7.4.1

an AE5V40 converter section 7.4.2

d) If there is no particular procedure:

1) Set the standby SMM to BLOM using the SETSCH: BLOM; command (see FOP SETSCH).

2) Remove the item to be replaced using the two extractor levers at either end of the boardsfront panel.

3) Insert the replacement. The front panel should be flush with the front panels of the ad jacentboards.

4) Run a LOCAVAR test on the SMM to check that the new item is operating correctly; use theSETSCH: TEST command (see FOP SETSCH).

5) Check the end of the IAS alarm identifying the faulty board.

6) Restart the SMM in operational mode using the SETSCH: ES command (see FOP SETSCH).

7) Check that the "STANDBY SMM OOS" alarm has disappeared.

e) End.

7.1 Repairin g an item in the processing subsystem7.1.1 ACBSG or DCCBPH board

To repair the ACBSG or DCCBPH board:

a) Set the SMM concerned to BLOM using the SETSCH: BLOM; command (see FOP SETSCH).

b) Remove the item to be replaced using the two extractor levers at either end of the boards frontpanel.

c) Insert the replacement. The front panel should be flush with the front panels of the adjacent boards.

d) Run a LOCAVAR test on the SMM to check that the new item is operating correctly; use the SETSCH:TEST command (see FOP SETSCH).

e) Check the end of the "SAI-HARDWARE" alarm identifying the faulty board.

f) Restart the SMM in operational mode using the SETSCH: ES command (see FOP SETSCH).

g) Check that the "STANDBY SMM OOS" alarm has disappeared.

h) Check whether the secondary memory (MSS) is degraded using the ISTMSS; command (see FOPISTMSS).

http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-


11/29

SMMMAINT

If the MSS is degraded, the fault has switched the controller of disk A0A0 or A0B0 to BLOS; de-pending on which ACBSG or DCCBPH board is faulty:

1) Set the disk controller specified in the alarm messages to BLOM using the SETEQP: OB-JET_CD,BLOM; command (see FOP SETEQP).

2) Run a LOCAVAR test on the disk controller using the SETEQP: OBJET_CD,TEST; command(see FOP SETEQP).

3) Set the controller to ES using the SETEQP: OBJET_CD,ES; command (see FOP SETEQP).

4) Reconstruct the faulty disk:

If the faulty disk is... execute the following command...

disk A (DK A0A0) RECDP :DK A0B0,DK A0A0,SYST00,SYST00DISKNAME;(see FOP RECDP)

disk B (DK A0B0) RECDP :DK A0A0,DK A0B0,SYST01,SYST01DISKNAME;(see FOP RECDP)

i) End.

7.1.2 ACCSG board

To repair the ACCSG boar d:

Note : For a view of the board see Appendix C.


b) Check that switches V3 and V4 on the associated DACLE1 daughter board are in the rest position(top position).Note : For a view of the DACLE1 daughter board, see Appendix D.

c) Lower physical switch V2 on the board to be replaced.

d) Remove the item to be replaced using the two extractor levers at either end of the boards frontpanel.

e) Lower physical switch V2 on the replacement board.

f) Insert the replacement board. The front panel should be flush with the front panels of the adjacentboards.

g) Raise physical switch V2 on the new board.

h) Run a LOCAVAR test on the SMM to check that the new board is operating correctly; use theSETSCH: TEST command (see FOP SETSCH).

i) Initialize the stations logical switches (see FEX SMCONSAS).

j) Check the end of the "SAI-HARDWARE" alarm identifying the faulty board.

k) Restart the SMM in operational mode using the SETSCH: ES command (see FOP SETSCH).

l) Check that the "STANDBY SMM OOS" alarm has disappeared.



12/29

SMMMAINT

m)End.

7.1.3 ACFTD board

To repair the ACFTD board:

a) Set the SMM concerned to BLOM using the SETSCH: BLOM; command (see FOP SETSCH).b) Remove the item to be replaced using the two extractor levers at either end of the boards front

panel.

c) Insert the replacement item. The front panel should be flush with the front panels of the adjacentboards.

d) Check the repair by activating the standby SMM in LOCAVAR mode using the SETSCH: TEST;command (see FOP SETSCH).

if the fault persists with the following di-agnostic...

then...

FTD_12G replace the DATSTA board (see section 7.1.4 )

FTD_14G replace the DATSTB board (see section 7.1.4 )

e) Run a LOCAVAR test on the SMM to check that the new item is operating correctly; use the SETSCH:TEST; command (see FOP S ETSCH).

f) Check the end of the "SAI-HARDWARE" alarm specifying the faulty board.

g) Restart the SMM in operational mode using the SETSCH: ES command (see FOP SETSCH).

h) Check that the "STANDBY SMM OOS" alarm has disappeared.i) End.

7.1.4 DATSTA and DATSTB daughter boards

Access to the DATSTA and DATSTB daughter board positions differs depending on whether the SMMis in a CA, SA or SK rack.

To replace a DATSTA or DATSTB daughter board of an SMM in an SA and SK rack:

a) Ensure that the daughter board being inserted is offered up at right angles to the backplane op-posite its slot marked by two dividers.

b) Ensure that the daughter board is positioned perfectly in the vertical plane.

CAUTION: AN OFFSET BY TWO CONNECTOR PINS in the verticalplane can cause a 5 V power supply short circuit.

HANDLE THE DAUGHTER BOARDS WITH CARE.

c) End.

To replace a DATSTA or DATSTB daughter board of an SMM in a CA rack:

http://-/?-http://-/?-http://-/?-http://-/?-


13/29

SMMMAINT

The same installation (or replacement) procedure for the daughter boards can be used (see above).It is more difficult because the daughter board positions are difficult to access (at the bottom of therack) and there is a profusion of cables. To overcome this problem, simply shut down the SMM usingthe following procedure:

Note : This procedure shuts down both SMMs which means the disks are automatically resyn-chronized when the SMMs are restarted.

a) Check the setting for the next SMM star tup using the ESYIN command (see FOP ESYIN).

b) If the OLAF setting is not NORON, assign that setting using the ESYMO command (see FOPESYMO).

c) Shut down the SMM using the CTIAR command (see FOP CTIAR).

d) Lower switches V2 on both SMMs to the permanent reset position.

e) Disconnect the two 5 V supplies to the ABLAS subrack.

f) Replace the daughter boards.g) Reconnect the two 5 V supplies.

h) Restart both SMMs by returning switches V2 to their original positions.

i) Check for alarms after the "SYSTEM READY" message.

If a "MINEURE 2 MPNA" alarm appears, clear it by following the procedure described in the Alarmdictionary ALA283. Do not replace the boards but reset them by removing and reinserting them.

j) End.

7.2 Repairing an external access unit A TELBUS unit is switched to BLOS when the LOCAVAR test detects a fault. When two successiveautomatic LOCAVAR tests end with no diagnostic report, the equipment is switched to BLOS in lessthan an hour.

Note : An "SAI-HARDWARE" alarm specifying a faulty object (unit) indicates that it is BLOS.

7.2.1 ACTUJ board

To repair an ACTUJ board:

a) If the ACTUJ board to be repaired is connected to the WAM terminal (first or second ACTUJ board):

1) Notify the users of terminals connected to the ACTUJ board that they must stop operationson those terminals.

2) Transfer the asynchronous WAM link to the ACTUJ board that is still ES (see FEX SMWAMINT).

b) Check the state of the controller associated with the board using the ISTEQP: OBJ_CTLP; com-mand (see FOP ISTEQP). For further information on the equivalence between the "RTOS objects"and the boards, see Appendix B.



14/29

SMMMAINT

c) Set the CTLP controller to BLOM using the SETEQP: OBJET_CTLP,BLOM; command (see FOPSETEQP).Note : This causes the "SAI-HARDWARE" alarm to appear on the CTLP object indicating that

it is BLOM if it was not already suspect.

Note : When the item goes BLOM or BLOS, the OM lines that are still ES become inacces-sible.

d) Replace the board concerned.

e) Run the LOCAVAR test using the SETEQP: OBJET_CTLP,TEST; command (see FOP SETEQP).

f) Set the equipment to ES using the SETEQ P: OBJET_CTLP,ES; command (see FOP SETEQP).

g) Wait for the end of the "SAI-HARDWARE" alarm on the CTLP object to be indicated by a message.

h) If the faulty unit was the child object of the CTLP (OBJ_FILS=CTLL,LIGP):

1) Set the child object to ES using the SETEQP: OBJ_FILS,ES; command (see FOP SETEQP).

2) Wait for the end of the "SAI-HARDWARE" alarm on the CTLL or LIGP object to be indicatedby a message.

3) Repeat the operation on all the previously suspect child objects.

i) Check that the terminals connected to the new ACTUJ board are operational using the INFILcommand (see FOP INFIL). Specify OPT=ETAT.Note : All the lines return automatically to ES if no SMM switchover occurs before the CTLP

is reset to ES. If they do not return to ES, execute the INFES command for those linesand complete the DV parameter (see FOP INFES).

j) End.

7.2.2 ACRAL2 board

To repair the ACRAL2 board:

a) Check the states of the lines connected to the ACRAL2 board on the WAM terminal using the IS-TEQP: LIGP ACRAL2 command (see FOP ISTEQP).

b) If the lines are BLOM, set them to ES using the SETEQP command (see FOP SETEQP).

c) Run a manual LOCAVAR test on the suspect object using the SETEQP: OBJET_XXX,TEST com-

mand (see FOP SETEQP). If the diagnostic report is confirmed, repair the ACRAL2 board.

If the diagnostic report is not confirmed, return the previously suspect object to ES.

d) Carry out the procedure in section 7.2.1 .Note : When the unit goes BLOM or BLOS, the OM lines that are still ES become inacces-

sible. Alarms concerning failure of the CVA may appear.

e) The asynchronous lines (ASL) assigned to the CVA automatically return to ES after a few minutes.

f) End.

http://-/?-http://-/?-


15/29

SMMMAINT

7.2.3 ACJ64, DCV11 and ACV11 boards

To repair the ACJ64, DCV11 or ACV11 board:

a) Carry out the procedure in section 7.2.1 .

Note : Switching the unit to BLOM or BLOS closes any existing sessions. Auto-connectedsessions on the standby link are automatically reopened. Other sessions are re-opened by the remote system operator.

b) End.

7.3 Repairing a secondary memory unit An SAI-HARDWARE alarm concerning the faulty RTOS object indicates that it is set to BLOS.

7.3.1 Magnetic tape unit

To repair the magnetic tape unit:

a) Set the tape controller to BLOM using the SETEQP: OBJET_CB,BLOM; command (see FOPSETEQP).

b) If necessary, wait for the "SAI-HARDWARE" alarm to appear if no object was declared suspect before.

c) Replace the unit concerned.

d) Run the LOCAVAR test using the SETEQP: OBJET_CB,TEST; command (see FOP SETEQP).

e) Set the unit to ES using the SETEQP: OBJET_CB,ES; command (see FOP SETEQP).

f) Wait for the end of the "SAI-HARDWARE" alarm on the tape controller object to be indicated by amessage.

g) If the faulty object is a child of the controller (OBJ_FILS=BND):

1) Set the object to ES using the SETEQP: OBJ_FILS,ES; command (see FOP SETEQP).

2) Wait for the end of the "SAI-HARDWARE" alarm on the BND object to be indicated by amessage.

3) Repeat the operation on all the previously suspect child objects.

h) End.

7.3.2 Streamer

To repair the streamer:

a) Set the streamer controller to BLOM using the SETEQP: OBJET_CSMR,BLOM; command (seeFOP SETEQP).

b) If necessary, wait for the "SAI-HARDWARE" alarm to appear if no object was previously declaredsuspect.

c) Replace the board concerned.

d) Run the LOCAVAR test using the SETEQP: OBJET_CSMR,TEST; command (see FOP SETEQP).

http://-/?-http://-/?-


16/29

SMMMAINT

e) Set the unit to ES using the SETEQP: OBJET_CSMR,ES; command (see FOP SETEQP).

f) Wait for the end of the "SAI-HARDWARE" alarm on the streamer controller object to be indicated by a message.

g) If the faulty object is a child of the controller (OBJ_FILS=SMR):

1) Set the object to ES using the SETEQP: OBJ_FILS,ES; command (see FOP SETEQP).

2) Wait for the end of the "SAI-HARDWARE" alarm on the MSR object to be indicated by a mes-sage.

h) End.

7.3.3 Disk

To repair the disk:

a) Carry out FEX SMDKRST1.

b) End.

7.4 Repairing a converter7.4.1 AE12V and AE412 converters

To repair the AE12V and AE412 converters:

a) Set the standby SMM to BLOM using the SETSCH: BLOM; command (see FOP SETSCH).

b) Replace the converter:

1) Remove the converter.

2) Wait one minute.

3) Insert the new converter.

4) Set the new converters switch to ON.

5) Check that the converters power LED c omes on normally.

c) Run a LOCAVAR test on the SMM to check that the new unit is running correctly; use the SETSCH:TEST command (see FOP SETSCH).

d) Check for the end of the IAS alarm specifying the faulty board.

e) Restart the SMM in operational mode using the SETSCH: ES command (see FOP SETSCH).

f) Check that the "STANDBY SMM OOS" alarm disappears.

g) End.

7.4.2 AE5V40 converter

To repair an AE5V40 converter:


b) Replace the converter:



17/29

SMMMAINT

1) Set the switch on the existing converter to OFF.

2) Remove the converter.

3) Wait one minute.

4) Check that the switch on the new converter is OFF.

5) Insert the new converter.

6) Set the new converters switch to ON.

7) Check that the converters power LED comes on normally.

c) Run a LOCAVAR test on the SMM to check that the new unit is operating correctly; use the SETSCH:TEST command (see FOP SETSCH).

d) Check for the end of IAS alarm specifying the faulty board.

e) Restart the SMM in operational mode using the SETSCH: ES command (see FOP SETSCH).

f) Check that the "STANDBY SMM OOS" alarm disappears.g) End.

8 RELATED DOCUMENTSSEE:

- Operator sheets: CTIAR, CTIBSC, ESYIN, ESYMO, INFES, INFIL, ISTEQP, ISTMSS, MCLEMO, RECDP,SETEQP, SETSCH.

- Operating/maintenance sheets: SCCARTES, SMCONSAS, SMDKRST1, SMDKRST2, SMPMD,SMWAMINT,

- Operator guide: Corrective maintenance management MCGOP.

- Alarm dictionary ALA283.



18/29

SMMMAINT

APPENDIX A : SMM STARTUP OPTIONSNORON: OM initialization in NORMAL mode

This is the OM functions normal initialization mode with insertion in theOCB system. All operating functions are available.

The subsequent startup option is set to NORON (standard setting).

MANON: OM initialization in manual mode

In this mode, the OM function can be initialized with all the OCB stations setto BLOM. All operating functions are available except the routine functions.The OCB should be initialized from craft terminals under operator control. After the stations are manually initialized, the operator must reset the OM

function to NORON so that all the OM functions are operational.

INION: General system initialization

In this mode, the OM function is initialized with all the OCB stations beinginitialized from the OM. When the stations have been initialized, the oper-ating functions are available.

RITON: NORON initialization with resetting of the buffer files and resumption of theexchange configuration.

In this mode, the buffer files are reset and the XASM disk archive is updatedusing the data from an operational station. The OM is aligned on the systemconfiguration. This option is used after the OM disks are reloaded.

The subsequent startup option is set to NORON (standard setting).

ALONE: OM initialization in standalone mode

In this mode, the OM can be started up on its own without being connectedto OCB control. All the OM functions resources are available except access,OCB operation and remote operation (REM).

This option is reserved for specific maintenance operations or when connec-tion to the exchange core subsystem is not possible (FACDET extraction, etc).

In this mode, the disabling of certain defense reactions means that the MAL-OMO macro must be executed.

At the end of the operation, the operator must reset the OM function toNORON mode so that all the OM functions are operational.



19/29

SMMMAINT

APPENDIX B : EQUIPMENT IDENTIFICATION"SAI-HARDWARE" alarm messages specify RTOS objects. The table below is designed to help you find:

- the equivalence between the RTOS object name and the unit concerned (board, converter, etc),

- the positions of the units in the racks depending on the exchanges configuration.Note : In Table 1 , the "_" characters in the name of the suspect object must be replaced by

spaces in the positioning commands. For example UT__124 becomes UT 124.

http://-/?-http://-/?-


20/29

SMMMAINT

Table 1 : Table of subsystem (SMMA or SMMB) units

Exchange configurationSuspectobject inthe alarm

message

Equivalent

unitP M G COMPACT SA COMPACT SK

For SMMA

level slot level slot level slot

CMIS123

ACJB122 ACAJB4 109 013 125 015 098 015

ACJA123 ACAJA4 109 017 125 019 098 019

UT__124 ACUTG 109 025 125 027 098 027

MC16125 ACMGS 109 029 125 031 098 031

UT__126 ACUTG 109 033 125 035 098 035

MC16127 ACMGS 109 037 125 039 098 039

CBS_12C ACBSG or DCCBPH 109 057 125 043 098 047

CBS_12D ACBSG or DCCBPH 109 063 125 049 098 053

CS__12E ACCSG 109 069 125 055 098 059

FTD_12G ACFTD 109 081 125 061 098 067

For SMMB

level slot level slot level slot

CMIS143

ACJB142 ACAJB4 185 013 098 015 125 015

ACJA143 ACAJA4 185 017 098 019 125 019

UT__144 ACUTG 185 025 098 027 125 027

MC16145 ACMGS 185 029 098 031 125 031

UT__146 ACUTG 185 033 098 035 125 035

MC16147 ACMGS 185 037 098 039 125 039

CBS_14C ACBSG or DCCBPH 185 057 098 043 125 047

CBS_14D ACBSG or DCCBPH 185 063 098 049 125 053

CS__14E ACCSG 185 069 098 055 125 059

FTD_14G ACFTD 185 081 098 061 125 067



21/29

SMMMAINT

Table 2 : Table of subsystem units

Exchange configurationSuspectobject inthe alarm

message

Equivalent

unit P M G COMPACT SA COMPACT SK

CTLP13F ACJ64/DCV11/ACV11# 147 095 098 075 098 077

CTLP13G ACJ64/DCV11/ACV11 # 147 099 098 079 098 081

CTLP13H ACTUJ 1 (WAM) 147 103 098 083 098 085

CTLP13I ACTUJ 2 (WAM) 147 109 098 089 098 091

CTLP13J ACTUJ 3 # 147 115

CTLP13K ACTUJ 4 # 147 121

CTLP13L ACRAL2 147 127 098 095 098 097

CTLP13M ACTUJ 5 # 147 131CD__12H ACDDG1 DISK CTRL 109 088 125 071 125 077

DK__A0A0 DISK 109 088 125 071 125 077

CD__14H ACDDG1 DISK CTRL 185 088 125 091 125 087

DK__A0B0 DISK 185 088 125 091 125 087

CSMR13D ACST2 STREAMER CTRL 147 071 125 111 125 097

ACSTG1 (1.2G STREAMER) 147 071 125 111 125 097

147 071 125 111 125 097

SMR_C0C0 STREAMER

CB__200 DILMK2 TAPE CTRL

BND_7072 PVDBF2 TAPE UNIT (MTU)

BND_7073 PVDBF2 MTU #

BND_7074 EMUL. MTU #

BND_7075 EMUL. MTU #

BS__10A CBS A SCSI BUS 12C/14CBS__10B CBS B SCSI BUS 12C/14C

BS__11A CBS A SCSI BUS 12D/14D

BS__11B CBS B SCSI BUS 12D/14D

Note : Boards with a # apply in some configurations only.

Note : The CMIS logical object covers the ACJA and ACJB physical objects.

Note : The board type indicates the boards family, for example ACUTG indicates both an ACUTG and an ACUTG2 board.



22/29

SMMMAINT

B.1 Identifying TELBUS secondary unitsEach board has a physical controller to which secondary objects are linked. These secondary objectsare logical controllers (microprocessors) and physical lines. The names of the secondary objects arederived from those of the physical controllers.

For example, physical lines are used to connect:

- UNIX or SUN stations,

- X.25 networks,

- modems,

- leased lines,

- etc.



23/29

SMMMAINT

Table 3 gives the equivalence between the board names in the standard configuration and the RTOSobject names associated with them.

Table 3 : Equivalence between the board names and RTOS objects

Board name Physical controller(CTLP)

RTOS object name

Logical controller(CTLL)

RTOS object name

Physical line (LIGP)

RTOS object name

LIGP13F0

LIGP13F1

LIGP13F2

ACJ64

ACV11

DCV11

CTLP13F CTLL13F0

LIGP13F3

LIGP13G0

LIGP13G1

LIGP13G2

ACJ64

ACV11

DCV11

CTLP13G CTLL13G0

LIGP13G3

LIGP13H0(WAM lineTERME001)

CTLL13H0

LIGP13H1

LIGP13H2CTLL13H1

LIGP13H3

LIGP13H4CTLL13H2LIGP13H5

LIGP13H6

ACTUJ CTLP13H

CTLL13H3

LIGP13H7

LIGP13I0CTLL13I0

LIGP13I1

LIGP13I2CTLL13I1

LIGP13I3

LIGP13I4CTLL13I2LIGP13I5

LIGP13I6

ACTUJ CTLP13I

CTLL13I3

LIGP13I7

http://-/?-http://-/?-


24/29

SMMMAINT

Board name Physical controller(CTLP)

RTOS object name

Logical controller(CTLL)

RTOS object name

Physical line (LIGP)

RTOS object name

LIGP13J0CTLL13J0

LIGP13J1LIGP13J2CTLL13J1

LIGP13J3

LIGP13J4CTLL13J2

LIGP13J5

LIGP13J6

ACTUJ CTLP13J

CTLL13J3

LIGP13J7

LIGP13K0CTLL13K0

LIGP13K1

LIGP13K2CTLL13K1

LIGP13K3

LIGP13K4CTLL13K2

LIGP13K5

LIGP13K6

ACTUJ CTLP13K

CTLL13K3

LIGP13K7

CTLL13L0 LIGP13L0

CTLL13L1 LIGP13L2

CTLL13L2 LIGP13L4

ACRAL2 CTLP13L

CTLL13L3 LIGP13L6

LIGP13M0CTLL13M0

LIGP13M1

LIGP13m2CTLL13M1

LIGP13M3

LIGP13M4CTLL13M2

LIGP13M5

LIGP13M6

ACTUJ CTLP13M

CTLL13M3

LIGP13M7



25/29

SMMMAINT

APPENDIX C : VIEW OF THE ACCSG BOARDFigure 1 : View of the ACCSG board



26/29

SMMMAINT

APPENDIX D : VIEW OF THE DACLE1 BOARDThe DACLE1 daughter boards are behind the backplane of the X-bus subracks of the SMM on the ACCSG1 board connector.

They each have two switches:

- switch V3: subsystem always worker,

- switch V4: manufacturer present.Note : The names of the switches are not marked on the daughter board.

Figure 2 : DACLE1 daughter board switches



27/29

SMMMAINT

APPENDIX E : POWER DISTRIBUTION IN THEOCB283

E.1 P-M-G configurationOnly non-duplicated converters, which require servicing other than replacement, are shown here.

Figure 3 : SMM power supply for P-M-G configuration

Board type Power supply function Level Slot

AE5V40 5V SMMA 109 000

AE5V40 5V SMMB 185 000 AE5V40 5V DK A0A0 and ACAJB SMMA 109 146

AE5V40 5V DK A0B0 and ACAJB SMMB 185 146

AE12V 12V DK A0A0 109 128

AE12V 12V DK A0B0 185 128

Note : Replacing converters (P-M-G configurations)



28/29

SMMMAINT

E.2 Compact SA configurationOnly non-duplicated converters, which require servicing other than replacement, are shown here.

Figure 4 : SMM power supply for the Compact SA configuration


AE5V40 5V SMMA 125 000

AE5V40 5V SMMB 098 000

AE5V40 5V DKA0A0/ACAJB SMMA/SMR 190 142

AE12V 12V DK A0A0 125 136

AE12V 12V DK A0B0 125 145Note : Replacing converters (Compact SA configuration)



29/29

SMMMAINT

E.3 Compact SK configurationOnly non-duplicated converters, which require servicing other than replacement, are shown here.

Figure 5 : SMM power supply for the Compact SK configuration


AE540B 5V SMMA 098 000

AE540B 5V SMMB 125 000

AE412B 12V DK A0A0 125 138

AE412B 12V DK A0B0 125 147

Note : Replacing converters (Compact SK configuration)

The pools constitute a coupling (redundancy) between two converters. When one of the two convertersfails, all the power is supplied by the converter that is still operational.POOL P1 consists of the 5 V converter in slot 147 of SMMA and the 5 V converter in slot 148 in SMT2G.POOL P4 consists of the 5 V converters in slot 147 of the SMX and 148 of SMA2.

Date post:	03-Jun-2018
Category:	Documents
Upload:	mdrhally
View:	221 times
Download:	0 times

Boards Locations

Documents