DLP-532: Detailed Level Procedure 365-575-102
Page2of6 Issue8.0,July2002
8. If required to correct any discrepancies, use the CONFIGURATION-Set-
Path-Trace command.
Reference: DLP-531
9. Repeat Steps 6 through 8 for any additional STS-1 paths to be verified.
10. Discontinue the login at the source network element. (To discontinue a remote
login, refer to DLP-524.)
11. Establish a login to the destination network element for the first STS-1 path
to be verified. (To establish a remote login, refer to DLP-524.)
12. At the CIT, select CONFIGURATION-Retrieve-Path-Trace command and
execute to obtain a Path Trace Report. Section 11 shows example of report.
This report shows the STS-1 paths that originate or terminate at this network
element.
13. Compare the provisioned receive (PrvRx) character string(s) in the Path Trace
Report with the values determined from office records (Step 4) and make a
note of any differences. (To continue with the same example as in DLP-531,
the PrvRx and the PrvTx strings should match with "transmitting from node 3 at
Boston.")
NOTE:
A path trace mismatch will not cause an alarm or status condition. A
mismatch could be caused by missing cross-connections.
14. If required to correct any discrepancies, use the CONFIGURATION-Set-
Path-Trace command.
Reference: DLP-531
15. Repeat Steps 12 through 14 for any additional STS-1 paths to be verified.
16. Discontinue the login at the destination network element. (To discontinue a
remote login, refer to DLP-524.)
Verify Actual Receive Path Trace
17. Do you wish to verify that the actual receive path trace agrees with the
provisioned receive path trace for one or more STS-1 signals?
If YES, then continue with Step 18.
If NO, then STOP! YOU HAVE COMPLETED THIS PROCEDURE.
18. From office records, determine which FT-2000 network element is the
destination network element for the STS-1 path(s) to be verified.
19. Establish a login to the destination network element for the first STS-1 path to
be verified. (To establish a remote login, refer to DLP-524.)