Download Print this page

Cisco ONS 15454 SDH Manual page 37

Hide thumbs Also See for ONS 15454 SDH:

Advertisement

Chapter 11 Circuits and Tunnels
All connections from the master circuit and at least one connection from the other selected circuits must
be used in the resulting circuit for the merge to succeed. If a merge fails, the master circuit and all other
circuits remain unchanged. When the circuit merge completes successfully, the resulting circuit retains
the name of the master circuit.
11.19 Reconfigured Circuits
You can reconfigure multiple circuits, which is typically necessary when a large number of circuits are
in the PARTIAL state. When reconfiguring multiple circuits, the selected circuits can be any
combination of DISCOVERED, PARTIAL, DISCOVERED_TL1, or PARTIAL_TL1 circuits. You can
reconfigure VCTs, VCA circuits, VLAN-assigned circuits, VCAT circuits, CTC-created circuits, and
TL1-created circuits. The Reconfigure command maintains the names of the original cross-connects.
Use the CTC Tools > Circuits > Reconfigure Circuits command to reconfigure selected circuits. During
reconfiguration, CTC reassembles all connections of the selected circuits into circuits based on path size,
direction, and alignment. Some circuits might merge and others might split into multiple circuits. If the
resulting circuit is a valid circuit, it appears as a DISCOVERED circuit. Otherwise, the circuit appears
as a PARTIAL or PARTIAL_TL1 circuit.
If CTC cannot reconfigure all members in a VCAT circuit, the reconfigure operation fails for the entire
Note
VCAT circuit and it remains in the PARTIAL or PARTIAL_TL1 status. If CTC does reconfigure all
members in a VCAT circuit, the VCAT circuit may still remain in the PARTIAL or PARTIAL_TL1
status. This occurs if the ports defined in the VCAT termination do not match the source/drop ports of
the member circuits or if one or two VCAT terminations are missing.
Note
PARTIAL tunnel and PARTIAL VLAN-capable circuits do not split into multiple circuits during
reconfiguration.
11.20 Server Trails
A server trail is a non-DCC (logical or virtual) link across a third-party network that connects two CTC
network domains. A server trail allows A-Z circuit provisioning when no DCC is available. You can
create server trails between two distant optical or EC-1 ports. The end ports on a server trail can be
different types (for example, an OC-3 port can be linked to an OC-12 port). Server trails are not allowed
on DCC-enabled ports.
The server trail link is bidirectional and can be VT1.5, VT2, STS1, STS-3c, STS-6c, STS-12c, STS-48c,
or STS-192c; you cannot change an existing server trail to another size. It must be deleted and recreated.
A circuit provisioned over a server trail must match the type and size of the server trail it uses. For
example, an STS-3c server trail can carry only STS-3c circuits and not three STS-1 circuits.
There is no OSPF or any other management information exchange between NEs over a server trail.
Note
78-18119-01
11.19 Reconfigured Circuits
Cisco ONS 15454 SDH Reference Manual, R8.5
11-37

Advertisement

loading