User guide

3-164
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.33 createRoll
Parameters
For details about the Roll_T structure, see 3.8.28 getAllRolls, page 3-111.
CTM support for RollCreateData_T is as follows:
• multiLayerSubnetwork::RollType_T rollType
Supported.
• multiLayerSubnetwork::RollMode_T rollMode
Supported.
• globaldefs::NamingAttributesList_T sncNames
Supported. This refers to the name of the SNC to roll partially or fully. If two SNCs are specified,
the first SNC will be the RollFromSNC and the second SNC will be the RollToSNC.
• globaldefs::NamingAttributesList_T fixCTPs
Supported. This refers to the fully qualified name of the CTP of the SNC. This CTP is the fixed point
of the roll. In cases where the rollType is DUAL, there will be two fixed points in the roll. The first
fixCTP indicates the first fixed point in the roll object and the second fixCTP indicates the second
fixed point of the roll.
• globaldefs::NamingAttributesList_T rollFromCTP
Supported. This refers to the fully qualified name of the CTP of the SNC. This CTP is either the
source or destination or any other associated CTP of the SNC. In cases where the rollType is DUAL,
the first element in the array indicates the first rollFromCTP point and the second element in the
array indicates the second rollFromCTP point.
Note If the rollFromCTP can be determined from the fixed CTP, the value is ignored.
• globaldefs::NamingAttributesList_T rollToCTP
Supported. This refers to the fully qualified name of the CTP where the roll occurs. In cases where
the rollType is DUAL, the first element in the array indicates the first rollToCTP point and the
second element in the array indicates the second rollToCTP point.
• subnetworkConnection::ResourceList_T neTpInclusions
Supported. CTM expects a list of managed element names or PTP names of the endpoint of a
topological link or CTP name pair representing the endpoints of the span to include in the
subnetwork connection route. For complete manual routing, CTM expects the list of all CTPs of the
links (OCH Trail circuit links, if any) to which the circuit must be routed. If the OSS specifies a CTP
pair in the neTpInclusions, the entire path for the subnetwork connection must be specified.
• subnetworkConnection::ResourceList_T neTpSncExclusions
Supported. CTM expects a list of managed element names or PTP names of the endpoint of a
topological link representing the endpoints of the span to exclude in the subnetwork connection
route.
• subnetworkConnection::StaticProtectionLevel_T staticProtectionLevel
CTM supports the following for the subnetwork connection that is created as part of the roll creation:
Name Type Input/Output Description
rollCreateData multiLayerSubnetwork::RollCreateData_T In Structure describing the roll to create.