User guide

2-45
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
• OADM_PORT_EQPT
• OPT_AMP_17_C_LINE_CARD_EQPT
• OPT_AMP_L_EQPT
• OPT_BST_E_EQPT
• OPT_BST_EQPT
• OPT_BST_L_EQPT
• OPT_PRE_EQPT
• OSC_CSM_CARD_EQPT
• OSCM_CARD_EQPT
• OSCM_PORT_EQPT
• WSS_32_CARD_EQPT
• WSS32_L_CARD_EQPT
• WSS40_LINE_CARD_EQPT
• WXC40_LINE_CARD_EQPT
This type of circuit is referred to as WDM SNC. The WDM SNC is created on a particular wavelength
channel with a direction of either east-to-west or west-to-east. WDM SNCs are unidirectional or
bidirectional. CTM GateWay/CORBA supports the creation of bidirectional OCHNC circuits on R5.0
and later NEs. You can also create two unidirectional OCHNC circuits on the same frequency, in
opposite directions.
The CTPs used in WDM SNCs are different from the CTPs used in SONET/SDH SNCs in terms of
naming and nature. See 2.2.5.4 Connection Termination Point, page 2-31 for the CTP naming
conventions. The layer rate for the CTPs and WDM SNC must be LR_Optical_Channel.
The OCHNC size is “Equipped not specific.” You can specify four possible directions:
• East-to-west unidirectional
• East-to-west bidirectional
• West-to-east unidirectional
• West-to-east bidirectional
The preceding values are added to the globaldefs::ConnectionDirection_T structure.
For OCHNC on ONS 15454 SONET and ONS 15454 SDH R7.0 and later, you do not have to specify
the east-to-west or west-to-east direction; instead, UniDir and BiDir must be used. For R8.0 NEs you
can specify route constraints (NE include/exclude constraints) in the SNCCreateData_T parameter.
When creating OCHNC bidirectional circuits on R5.x or R6.x NEs, you must specify all four circuit
endpoints: source, destination, secondary source (the source in the opposite direction), and secondary
destination (the destination in the opposite direction). For R7.x or R8.x NEs you must specify only the
source and destination in one direction, because the endpoints for the opposite direction are calculated
automatically.
However, with the 80-WXC card (introduced in R9.2), more secondary sources and secondary
destinations could be available. In such a case, you must also specify the secondary TP. If they do not
belong to the actual list of available PTPs, an EXCPT_UNABLE_TO_COMPLY exception is thrown.
For example:
The secondary destination does not belong to the list of available PTPs:
/rack=1/shelf=1/slot=4/port=1, /rack=1/shelf=1/slot=4/port=2,
/rack=1/shelf=1/slot=4/port=3, /rack=1/shelf=1/slot=4/port=4,