Administration and Provisioning
Issue 8.0 July 2002
8-59
â– At node 3, a 2-way add/drop cross-connection is entered by specifying:
— Source (tributary)
— Source line (line 1W)
— Source STS-3 tributary (tributary 5)
— Source node TID†‡ (node 2 TID)
— Destination (slot)
— Destination low-speed interface slot
*
(slot 7A).
â– The same 2-way add/drop cross-connection may also be entered by
specifying:
— Source (slot)
— Source low-speed interface slot* (slot 7A)
— Destination line (line 1W)
— Destination STS-3 tributary (tributary 5)
— Destination node TID
†‡
(node 2 TID).
NOTE:
While cross-connections are entered, the FT-2000 OC-48 Add/Drop-Rings
Terminal will report several trouble conditions (for example, circuit
provisioning error and path integrity failure). However,
these trouble conditions should be ignored until all the cross-connections
for a circuit have been entered. If the trouble conditions remain after all the
cross-connections have been entered, refer to the "Operation and
Maintenance (TOP)" section (Volume II).
For more information about entering cross-connections at an FT-2000 OC-48
Add/Drop-Rings Terminal, refer to the CIT Tutorial in Section 11, "Craft Interface
Terminal Usage," and the Operation Task Index in the "Operation and
Maintenance (TOP)" section (Volume II).
Figure 8-18 shows a worksheet that may be used to record STS-3
cross-connections at FT-2000 OC-48 Add/Drop-Rings Terminals in a 2-fiber
bidirectional ring.
* In the specified slot is part of a slot pair that has been provisioned for the OC-3 1+1
(Release 5 and later releases) or OC-12 1+1 (Release 7.1 and later releases) protected
mode, specifying one slot also includes the companion slot.
†In Release 4.1 and later releases, entering a question mark (?) in response to the TID
prompt will display a point-and-shoot list of available addresses in the OC-48 ring. Enter
the Retrieve-Map-Ring command to update the point-and-shoot list.
‡ If an STS-3 tributary is bridged at one or more nodes in a ring, the last node where the
low-speed signals are terminated is the destination node.
In Releases 3 and 4.0, the node ID is entered.