User guide

3-195
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
EXCPT_ENTITY_NOT_FOUND - Raised when mlVlanName references an ML VLAN object that does not
exist.
Compliance
CTM-defined.
3.10.16 createL2Topology
Synopsis
void createL2Topology(
in multiLayerSubnetwork::L2TopoCreateData_T createData,
out multiLayerSubnetwork::L2Topology_T l2Topo)
raises(globaldefs::ProcessingFailureException);
Description
This interface provides a way to create an L2 topology, including all the optical SNCs associated with
it. The user must associate ML VLANs using the interface method defined in 3.10.1 createMLVLAN,
page 3-180. CTM creates an L2 topology within the same MultiLayerSubnetwork. If the NMS specifies
the L2 topology createData with MEs belonging to a different MultiLayerSubnetwork, CTM returns the
ProcessingFailureException EXCPT_UNABLE_TO_COMPLY.
CTM supports point-to-point, hub-and-spoke, Resilient Packet Ring (RPR), and 802.17 RPR topologies.
However, CTM supports the creation of only RPR, 802.17 RPR, and point-to-point topologies. CTM
treats a hub-and-spoke topology as multiple point-to-point topologies.
This is an asynchronous operation. CTM returns this method after all requests for creating the underlying
SNCs are complete. CTM autodiscovers an L2 topology based on the L1 SNCs created. CTM generates
OCE for all the L1 SNCs created. CTM also generates L2 topology OCE after the L2 Topology is
autodiscovered.
To create an RPR or 802.17 RPR topology, you must specify the complete list of ML-series and/or ML2
(L2/L3) equipment names to involve in the topology. RPR consists of all ML-series equipment or all
ML2 (L2/L3) equipment or a combination of ML and ML2 (L2/L3) equipment. To create a point-to-point
topology, you must specify the end TPs of the underlying L1 SNC.
During the L2 topology creation, if any part of the underlying L1 SNC creation fails, CTM generates a
processing failure exception. However, CTM autodiscovers the L2 topology in INCOMPLETE state if
any SNC was created before the failure occurred. Either the NMS creates the remaining L1 SNCs that
failed, using the interface described in 3.9.16 createAndActivateSNCFromUserLabel, page 3-138 to
complete the L2 topology, or the NMS deletes the L2 topology and recreates it using this operation.
For RPR topologies, the NMS must specify all the equipment to involve, in cyclical order and in pairs.
There are three different scenarios:
All SNCs in the RPR are CCAT. In this case, only SNCCreateDataList_T is populated and
VCATSNCCreateDataList_T is empty. For example, if the NMS is trying to create an RPR topology
involving three ML-series cards (M1, M2, and M3), the NMS must specify a three-element array of
SNCCreateData_T. The first element’s aEnd will specify the M1 equipment name and the zEnd 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.
All SNCs in the RPR are VCAT. In this case, only VCATSNCCreateDataList_T is populated and
SNCCreateDataList_T is empty. For example, if the NMS is trying to create an RPR topology
involving three ML-series cards (M1, M2, and M3), the NMS must specify a three-element array of
VCATSNCCreateData_T. The first element’s aEnd will specify the M1 equipment name and zEnd