DLP-536: Detailed Level Procedure 365-575-102
Page4of8 Issue8.0,July2002
cross-connection. The source node TID is the TID of the node where the sig-
nal is added, whereas, the destination node TID is the TID of the node where
the signal is dropped. See Examples 1 and 2.
NOTE:
If the cross-connection just made was to a port(s) of an OC-3/OC-12 circuit
pack, you may want to provision a DCC assignment to establish DCC
connectivity with the network element at the other end of the OC-3/OC-12
line.
9. You may enter a DCC assignment on an OC-3/OC-12 line.
Reference: DLP-542
10. At the CIT (local network element), select CONFIGURA-
TION-Retrieve-Crossconnection-All and execute to obtain a
Cross-Connection Map Report (examples are shown in Volume 1, Section 11).
11. Verify that the cross-connections in the report match the instructions.
12. Steps 12 through 16 are used to verify that the source and destination node
TID provisioning has been done correctly.
Wait 2 minutes and verify that a site provisioning conflict IS NOT reported at
either of the two end NEs or any of the intermediate NE(s). It will be necessary
to individually check each NE, that is involved in the crossconnection. At the
CIT, use the FAULT-Retrieve-Alarms command.
NOTE:
Every possible combination of DRI manual switches in the path being
established should be checked. See Example 2 where a DRI manual switch at
node B would result in a new path coming from node C.
13. Make the first possible DRI manual switch in the path by using the
FAULT-Switch-Path command.
14. Wait 2 minutes and verify that a site provisioning conflict IS NOT reported at
either of the two end NEs or any of the intermediate NE(s). It will be necessary
to individually check each NE, that is involved in the crossconnection. At the
CIT, use the FAULT-Retrieve-Alarms command.
15. Repeat Steps 12 through 14 for each different remaining path.
16. Reset all DRI manual switches using the FAULT-Switch-Path:Reset com-
mand.
To Next Page
Loading...
Need help?
General