TAP-110: Trouble Clearing 365-575-102
Page2of4 Issue8.0,July2002
2.
NOTE:
If the provisioning is not completed properly (ALL appropriate
Cross-Connections provisioned in each NE of a signal’s path) before an
OC-3c or OC-12c service/signal is applied, then the incoming (from OC3)
STS LOP,orincoming (from OC12) STS LOP will be produced. As a
contrast, before deleting any of the Cross-Connections in an OC-3c or
OC-12c signal’s path, the signal must have been previously removed.
NOTE:
Under very unusual circumstances, a stuck sts1-all STS LOP alarm may
occur. If this happens, use the FAULT-System-Reset command (after
clearing any other alarms first) to clear this invalid alarm.
Refer to the Active Alarms and Status Report (FAULT-Retrieve-Alarm)
and determine the type of incoming signal failure.
Is the incoming signal failure an incoming (from OC3) STS LOP,orincoming
(from OC12) STS LOP?
If NO, then go to Step 3.
If YES, then initiate a Trouble Report to the source of the failed incoming
signal indicating the type of failure. And, ask that they verify that all
Cross-Connections for the signal path have been provisioned correctly.
If the source of the failed incoming signal returns a Trouble Report indi-
cating “no trouble found,” then follow the prescribed operating proce-
dures to fault isolate the cable/fiber carrying the failed incoming signal.
Reference: DLP-535
To Next Page
Loading...
Need help?
General