User guide

2-44
Cisco Transport Manager Release 9.2 GateWay/CORBA User Guide and Programmer Manual
OL-20937-01
Chapter 2 NE- and CTM-Specific Details
2.2.7 Provisioning Subnetwork Connections
CTP naming is identical to OCHNC SNCs: CTM GateWay/CORBA determines whether to create an
OCHNC or OCHCC, depending on the layer. See 2.2.5.4 Connection Termination Point, page 2-31 for
the CTP details.
OCHCC must be bidirectional.
CTM supports different sizes corresponding to possible payload types of transponder and muxponder
client ports. A specific layer must be defined for each payload type.
OCHCC is either unprotected or protected. Protected is created only on protected transponder or
muxponder cards where there is a protected trunk port.
Note To create OCHCC, you must create patchcord links at an optical channel layer between the transponders,
muxponders, or ITU-T line cards and DWDM ports.
OSPF-detected links between GCC terminations on transponder or muxponder cards are indicated at the
Optical_Transport_OTUk layer.
When an OCHCC circuit is created, unless transponder cards are directly connected by a trunk-to-trunk
patchcord link, an additional OCH trail tunnel circuit is created automatically.
The following method is defined for protected OCHCC circuits when it is necessary to specify
constraints for both working and protected routes:
multiLayerSubnetwork::MultiLayerSubnetworkMgr_I::
createAndActivateProtectedOchccFromUserLabel
2.2.7.4.2 OCHNC Circuit Provisioning
CTM supports OCHNC circuit provisioning on the following WDM cards for ONS 15454 SONET and
ONS 15454 SDH NEs:
• 40-SMR1-C
• 40-SMR2-C
• AD_1B_CARD_EQPT
• AD_1C_CARD_EQPT
• AD_2C_CARD_EQPT
• AD_4B_CARD_EQPT
• AD_4C_CARD_EQPT
• AMP_PORT_EQPT
• DMX32_L_CARD_EQPT
• DMX32_O_CARD_EQPT
• DMX32_R_CARD_EQPT
• DMX40_LINE_CARD_EQPT
• MMU_CARD_EQPT
• MUX_DMX_PORT_EQPT
• MUX_DMX4_CARD_EQPT
• MUX32_O_CARD_EQPT
• MUX40_LINE_CARD_EQPT