User guide

3-173
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.43 createAndActivateSNCOnDRI
The structure of DRISNCCreateData_T is as follows:
struct DRISNCCreateData_T
{
subnetworkConnection::SNCCreateData_T createData,
subnetworkConnection::DRINodesList_T nodeList,
};
typedef sequence <DRINodes_T> DRINodesList_T;
The structure of DRINodes_T is as follows:
struct DRINodes_T
{
globalDefs::DRIType_T type,
boolean isSecPCA;
DriNodePairList_T nodePairList;
globaldefs::NamingAttributesList requiredRings;
}
typedef sequence <DRINodePair_T> DRINodePairList_T;
struct DRINodePair_T
{
globaldefs::NamingAttributes_T PrimaryME;
globaldefs::NamingAttributes_T SecondaryME
}
CTM support for DriNode_T structure is as follows:
• type
This field defines integer values that categorize the BLSR-DRI as traditional or nontraditional
BLSR-DRI. In CTM type = 0 means it is a dummy node, 1 = traditional. and 2 = nontraditional.
• isSecPCA
This field indicates whether or not the RIP option is supported.
• DriNodePair_T
This structure holds the primary and secondary nodes. The sDriNodePair structure is as follows:
– globaldefs::NamingAttributes_T PrimaryME—Defines the primary DRI node.
– globaldefs::NamingAttributes_T SecondaryME —Defines the secondary DRI node.
– globaldefs::NamingAttributesList requiredRings—Holds the ring information. The first name
value tuple represents EMS instance and the second one holds the BLSR ring ID.
Compliance
CTM-defined.
tpsToModify subnetworkConnection::TPDataList_T In/out CTM ignores this parameter.
theSNC subnetworkConnection::SubnetworkC
onnection_T
Out Resulting SNC, with sncState and name
set. The name is set to the user label
supplied in createData structure.
errorReason String Out Specifies the creation and/or activation
error(s), if any.
Name Type Input/Output Description