365-575-102 DetailedLevelProcedure:
Issue 8.0, July 2002 Page 1 of 2
DLP-543
STS3 (or STS1) Path Trace Monitor for Non-DS3
Signals
Overview: This procedure is used to monitor non-DS3 signals at the destination
node and at any intermediate node(s). [The path trace is a "tag" on a path in the
network.] The non-DS3 signals could be an STS1, OC3, OC3c, OC12, OC12c,
STS-12, STS-12c, or any other SONET signal. The monitor arrangement accesses
the path trace byte (J1) of the SONET signal. The SONET signal is provisioned at its
source (network element) and may be either inside an FT-2000 ring or outside an
FT-2000 ring. This procedure can be performed from any network element in an
FT-2000 network.
1. Do you wish to verify the path trace byte for a DS3 or non-DS3 signal?
For a DS3 signal,thengotoDLP-532.
If a non-DS3 signal, then continue with Step 2.
2. If required, condition the craft interface terminal (CIT) and connect it to the
local FT-2000 network element.
Reference: DLP-501
3. From office records or work instructions, determine the path(s) to be
monitored.
4. Establish a login to the network element, if required, for the first path to be
verified. (To establish a remote login, refer to DLP-524.)
NOTE:
A "tag" or path trace may be verified at one or at all of the intermediate
network elements and/or at the destination network element.
5. From office records, identify a DS3 circuit pack that is ready for service BUT IS
NOT carrying service (AUTO state). This slot (STS3) or port (STS1) and
circuit pack will be used as an STS3 (or STS1) path trace monitor. To verify
theslotorportstate,youcanusetheFAULT-Retrieve-State-LS
command.
6. At the CIT, select CONFIGURATION-Enter-Crossconnection-STS3 (or
STS1) command and enter a drop cross-connection (tributary-to-slot). The
drop must be from the incoming tributary of the 1-way circuit. Another DS3
circuit pack would be required if monitoring a 2-way circuit.
To Next Page
Loading...
Need help?
General