User guide

3-138
Cisco Transport Manager Release 9.2 GateWay/CORBA User Guide and Programmer Manual
OL-20937-01
Chapter 3 Using CTM GateWay/CORBA Interfaces
3.9.16 createAndActivateSNCFromUserLabel
3.9.16 createAndActivateSNCFromUserLabel
Synopsis
void createAndActivateSNCFromUserLabel(
in subnetworkConnection::SNCCreateData_T createData,
in subnetworkConnection::GradesOfImpact_T tolerableImpact,
in EMSFreedomLevel_T emsFreedomLevel,
inout subnetworkConnection::TPDataList_T tpsToModify,
out subnetworkConnection::SubnetworkConnection_T theSNC,
out string errorReason)
raises(globaldefs::ProcessingFailureException);
Description
This interface provides a way to create and activate a subnetwork connection in one command. It is
CTM-specific and not TMF-defined. According to the TMF, the SNC name is assigned by the EMS when
it creates the SNC. However, if the NMS is to control the SNC name, it must use this method. The NMS
provides the name of the SNC in the userLabel field of the SNCCreateData input parameter. CTM uses
the userLabel value and assign it to the name of the new SNC. CTM also verifies the uniqueness of the
name. The operation fails if an SNC with the same name as the userLabel exists. This is an asynchronous
operation. Successful completion of this operation only guarantees delivery of the creation request to
CTM. Operation on CTPs of this SNC might still fail.
Optionally, you can also provide a description for the SNC by entering it in the additionalCreationInfo
field.
CTM cleans up resources if SNC creation fails. For example, if CTM fails to create the SNC on the
destination node, CTM also cleans up resources on the source node.
If the OC-n port is configured for SDH, CTM can create the SNC. CTM supports only those layer rates
supported by the NE. However, IPPM and J1 path tracing are not supported for CTPs of this SNC.
FTPs can be used as A ends and Z ends of the SNCs. A typical use of FTP is to create an SNC on Ethernet
equipment, create a tunnel SNC, or create a VAP/LAP circuit. See 2.2.7 Provisioning Subnetwork
Connections, page 2-39 for more information.
Creating SNCs between ONS 15327 nodes or ONS 15310, and between ONS 15600 nodes is identical
to creating SNCs between ONS 15454 nodes. It is also possible to create SNCs among ONS 15327,
ONS 15454, and ONS 15600 nodes.
CTM supports protection channel access (PCA). PCA SNCs are unprotected. For details about PCA, see
the NE documentation.
You can provide a description for the SNC. Enter the description in the additionalCreationInfo field.
To create a dual-ring interconnect SNC, set the staticProtectionLevel value in createData to
HIGHLY_PROTECTED. Use the CTC or CTM client to modify the Hold-off Timer attribute for this
SNC.
The following types of circuit creation are not supported:
• Monitor circuits
• STS-1 on DS1 cards and VC-4 on E1 and E1_42 cards
• DRI circuits with constraint routing
In addition to specifying SNC creation parameters using the SNCCreateData_T structure, the NMS can
provide a partial or complete list of MEs or both end PTPs of a topological link to include or exclude 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