TAP-120: Trouble Clearing 365-575-102
Page2of4 Issue8.0,July2002
NOTE:
After clearing the condition identified in Step 3, continue the trouble clearing
procedure using TAP-102 at the network element that initially reported the inc.
(from OC48) DCC failure or the incoming DCC failure condition.
4. Find the condition identified in Step 3 in Table A of TAP-102 and go to the indi-
cated TAP to clear that condition [ignoring the inc. (from OC48) DCC
failure or incoming DCC failure condition throughout the remainder of
thetroubleclearingprocedure].
5. STOP! YOU HAVE COMPLETED THIS PROCEDURE.
6. From office records, determine which network element is the source of the
failed DCC input.
NOTE:
The source of the failed DCC input is the other FT-2000 End Terminal in a
point-to-point network, or the first (adjacent) FT-2000 Add/Drop-Rings
Terminal in the indicated direction.
7. At the source of the failed DCC input, use the CIT to obtain an Active Alarms
and Status Report.
NOTE:
You may not be able to log in to the network element sending the failed
DCC input. If you cannot log in to that network element, you will need
assistance there to continue with this procedure.
8. Referring to the report obtained in Step 7, are there any conditions other than
inc. (from OC48) DCC failure or incoming DCC failure listed?
NOTE:
It is possible that an inc. (from OC48) DCC failure or an
incoming DCC failure will also be observed at this network element.
If so, you MUST ignore the inc. (from OC48) DCC failure or the
incoming DCC failure condition in the Active Alarms and Status
Report.
If YES, then continue with Step 9.
If NO, then continue with Step 12.
9. Referring to the report obtained in Step 7, identify the topmost condition other
than the inc. (from OC48) DCC failure or the incoming DCC fail-
ure condition.
NOTE:
While following the instructions in the procedure(s) to which you will now be
sent, you MUST ignore the inc. (from OC48) DCC failure or the
To Next Page
Loading...
Need help?
General