365-575-102 TroubleClearing:
Issue 8.0, July 2002 Page 1 of 2
TAP-166
Address an Unexplained Loss of Service
!
CAUTION:
This condition can be caused by an incorrectly provisioned source and/or
destination node TID and can result in a service outage under certain multiple
failure conditions.
NOTE:
For Release 4.1 and earlier, it is difficult to detect an incorrect source node TID
and/or destination node TID. The method presented here is to individually
compare the provisioned values with the work order which is normally done at
time of installation/acceptance.
NOTE:
For Release 5 and later, an incorrect provisioned source and/or destination
node TID is automatically indicated by a site provisioning conflict
condition and is documented in TAP-130.
1. At the CIT, select the CONFIGURATION-Retrieve-Map-Ring command to
obtain a Ring Map Report.
2. Compare the actual node TIDs listed on the report with the work order (instruc-
tions).
3. Do the node TIDs match (report and work order)?
If NO, then continue with Step 4.
If YES, then STOP! YOU HAVE COMPLETED THIS PROCEDURE.
4. Make the appropriate correction (node TID, cross-connection, etc.).
5. STOP! YOU HAVE COMPLETED THIS PROCEDURE.
To Next Page
Loading...
Need help?
General