DLP-544
: Detailed Level Procedure 363-206-305
Page 2 of 4 Issue 3, June 2000
DDM-2000 F
IBER
R
EACH
W
IDEBAND
S
HELF
NOTE:
Trace strings are case sensitive. Be sure to match capticals and lower
case entries in the trace (
trc
) message at the near end with the expected
trace (
exptrc
) message at the far end.
From office records, determine the path trace character string for each STS-1
path to be traced (path is between the source and destination network
elements
6. Use set-trace-sts1:
address
:exptrc=
ExpectedIncomingPathTrace
,
trc=
OutgoingPathTrace
command to provision the near-end Expected
Incomng Path Trace (
exptrc
) string and near-end Outgoing Path Trace (
trc
)
string.
7. Establish remote login to the far-end STS-1 terminating network element.
Reference:
DLP-522
8. Use set-trace-sts1:
address
:exptrc=
ExpectedIncomingPathTrace
,
trc=
OutgoingPathTrace
command at the far end to provision the Expected
Incoming Path Trace (
exptrc
) string the same as you did for the
trc
string at the
near end terminating element. Provision the Outgoing Path Trace (
trc
) string
the same as you did for the
exptrc
string at the near-end terminating element.
9. Use
rtrv-trace-sts1:
address
command to retrieve the provisioned
transmit and receive path trace string for the STS-1 channel being tested.
10. Did the STS-1 Path Trace Report indicate Status:
GOOD?
If
YES
, proceed to
Step 14
.
If
NO
, continue with
Step 11
.
11. Did the STS-1 Path Trace Report indicate Status: MISMATCH?
If
YES
, proceed to
Step 13
.
If
NO
, continue with
Step 12
.
12. Indications are that there is no incoming path trace message (Status:
UNAVAILABLE). Verify that both terminating nodes are using
BBG4B DS3
circuit packs. Verify cross connections and terminating addresses at all nodes.
Repeat this test from
Step 9
.
To Next Page
Loading...