............................................................................................................................................................
4
Is the
Remote client signal failed
alarm still present?
If...
Then...
Yes
Continue with
No
STOP! End of Procedure.
............................................................................................................................................................
5
From the System View at the far-end network element, click the
Alarm List
button. Are there
inc. LOS
or
inc. Loss of Synch
alarms in the alarm list?
If...
Then...
Yes
Proceed to the appropriate procedure
to clear the alarm. Then continue with
No
Proceed to
............................................................................................................................................................
6
From the System View at the near-end network element, click the
Alarm List
button and click
Refresh
.
............................................................................................................................................................
7
Is the
Remote client signal failed
alarm still present?
If...
Then...
Yes
Continue with
No
STOP! End of Procedure.
............................................................................................................................................................
8
Important! If the far-end port is in AUTO or NMON state and
the cable was disconnected or broken, the
Remote client
signal failed
alarm/condition is still reported at the near-end
network element.
At the near-end network element, use the
Configuration
→
Equipment
command to disable the Remote Client Fail parameter for
Procedure 5-48: Clear
″
Remote client signal
failed
″
alarm
Trouble clearing procedures
....................................................................................................................................................................................................................................
5 - 1 3 8
Lucent Technologies
365-372-333 R2.1
Issue 4, June 2005