Vous êtes sur la page 1sur 5

TROUBLESHOOTING PROCEDURE OF FOTS

1. RETRIEVE INFORMATION
OBJECTIVE
To check all modules state and abnormal condition occurred on multiplexer.
States to be concerned are as follow
a! Current alarm " E#ent $o%
&'efer Operation & Maintenane !etion ".1!
b! (erformance )onitorin%
&'efer Operation & Maintenane !etion ".#!
c! *uto )essa%es " Command $o%
&'efer Operation & Maintenane !etion "."!
*ll states must be checked b+ CI, at appropriate -E and -)S.
#. ALARM CHEC$

OBJECTIVE
To know real multiplexer problem situation from the be%innin% of trouble occurred
until recent time. all alarm messa%es are shown in table $ist of indication. &'efer to
Operation & Maintenane !etion 1%.#.1!
*larms are classified into
a! Operatin% S+stem
b! S+nchroni/ation
c! Traffic
d! (acka%e
e! E0uipment
f! 1irmware
%! -etwork
*ll states must be checked b+ CI, at appropriate -E and -)S.
". TROUBLESHOOTING

Trouble occurred in )ultiplexer can be di#ided into 2 cate%ories
a! -E3s 4ardware
b! Improper cross5connect
".1. NE&! Har'(are Tro)*+e

4ardware trouble occurred when e0uipment is dama%ed with 6fail alarm
indication7 shown on the module.
This trouble can be checked #isuall+ or #ia CI,.
".#. I,proper Cro!!-onnet Tro)*+e
Improper cross5connect trouble occurred when there is mismatched cross5connect
database between actual &-E3s side! and reference &-)S or multiplexer3s side!.
This trouble can be checked b+ execute 6#erif+7 cross5connect database in -)S.
.. Tro)*+e!/ootin0 F+o(/art
This section shows the troubleshootin% flowchart procedures.
..1. U-No'e Tro)*+e!/ootin0 Proe')re
..#. SMS-11%V an' SMS 2%%V Tro)*+e!/ootin0 Proe')re
..". SMS #1%%A Tro)*+e!/ootin0 Proe')re

Vous aimerez peut-être aussi