User guide

3-196
Cisco Transport Manager Release 9.2 GateWay/CORBA User Guide and Programmer Manual
OL-20937-01
Chapter 3 Using CTM GateWay/CORBA Interfaces
3.10.16 createL2Topology
will specify the M2 equipment name. The second element’s aEnd will specify the M2 equipment
name and zEnd will specify the M3 equipment name. The third element’s aEnd will specify the M3
equipment name and zEnd will specify the M1 equipment name.
• Mix of CCAT and VCAT SNCs in the RPR. In this case, both VCATSNCCreateDataList_T and
SNCCreateDataList_T are populated and all the equipment in the two arrays is in cyclical order.
For example, if the NMS is trying to create an RPR topology involving three ML-series cards (M1,
M2, and M3) and the SNC between M1-M2 and M3-M1 is of type CCAT and M2-M3 is of type
VCAT, the NMS must specify:
– A two-element array of SNCCreateData_T with the first element’s aEnd specifying the M1
equipment name and the zEnd specifying the M2 equipment name, and the second element’s
aEnd specifying the M3 equipment name and zEnd specifying the M1 equipment name.
– A one-element array of VCATSNCCreateData_T with the first element’s aEnd specifying the
M2 equipment name and zEnd specifying the M3 equipment name.
For point-to-point topologies, the NMS specifies either CCATSNCCreateData_T or
VCATSNCCreatedata_T. For creating CCAT point-to-point topologies, CCATSNCCreateData_T is
populated and VCATSNCCreateData_T is empty. For creating VCAT point-to-point topologies,
VCATSNCCreateData_T is populated and CCATSNCCreateData_T is empty.
In addition to specifying SNC creation parameters using the SNCCreateData_T structure for each SNC
in the L2 topology, the NMS can provide a partial or complete list of managed elements, or of both end
PTPs of a topological link that is included or excluded in the SNC route during SNC creation. The NMS
can specify only one type of object name list during the SNC creation. CTM returns a processing failure
exception if the NMS-specified list is not homogeneous. CTM returns a processing failure exception
with EXCPT_ENTITY_NOT_FOUND as the error reason if any one of the specified managed elements
or PTPs does not exist. If the NMS specifies a PTP list, CTM verifies whether the PTPs are specified in
pairs and each PTP in a pair is associated with each end PTP of the same topological link. CTM uses the
first PTP of a pair as the aEnd of the topological link and uses the second PTP of the same pair as the
zEnd of the topological link. CTM attempts to route the SNC from aEnd PTP of a PTP pair to zEnd PTP
of the same pair on a topological link. CTM returns a processing failure exception if the SNC cannot be
routed from the specified aEnd PTP to the zEnd PTP of a topological link. The NMS then must
interchange the aEnd and zEnd PTPs specified, provide a different PTP pair, or delete the PTP pair from
the include or exclude list. CTM returns a processing failure exception if at least one PTP is not
associated with a topological link. The NMS must ensure that the sequence of the object name list
conforms to the sequence of the objects existing in the network. CTM returns a processing failure
exception if the sequence is nonconforming.
CTM does not support the creation of L2 topologies in which SNCs have more than one source point and
destination endpoint in SNCCreateData_T.aEnd or SNCCreateData_T.zEnd.
CTM does not support 802.17 RPR topology creation if the circuit size entered is not compatible with
the bandwidth values entered. CTM returns a processing failure exception if the circuit size and
bandwidth values are incompatible. Refer to the Cisco Transport Manager Release 9.2 User Guide for
compatibility between circuit size and bandwidth.
CTM supports the creation of L2 topologies containing VCAT SNCs. For point-to-point topologies,
either the CCAT SNC or VCAT SNC is specified. RPR topologies can consist of both CCAT and VCAT
SNCs.