User guide

2-46
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
/rack=1/shelf=1/slot=4/port=5, /rack=1/shelf=1/slot=4/port=6,
/rack=1/shelf=1/slot=4/port=7, /rack=1/shelf=1/slot=4/port=8,
/rack=1/shelf=1/slot=4/port=9
Or:
The secondary source does not belong to the list of available PTPs:
/rack=1/shelf=1/slot=2/port=9
A mixed configuration, such as an OCHNC bidirectional circuit between an 80WXC card (configured
as bidirectional) and a MUX/DMX card, requires only the secondary drop on the 80WXC card. CTM
still automatically calculates the secondary source on the MUX/DMX card.
For the ONS 15454 SONET and ONS 15454 SDH R9.0 and later, OCHNC circuits support protected
optical paths. You can specify the following property within the creation data structure:
staticProtectionLevel=StaticProtectionLevel_T.FULLY_PROTECTED.
The availability of protected paths and the possibility of provisioning protected OCHNC circuits depend
on the presence of the Protection Switch Module (PSM). When configured correctly, the PSM provides
one of the available protection schemas.
If the PSM card mode is configured as STANDALONE, you cannot create OCHNC or OCHCC protected
circuits that involve the PSM card. The STANDALONE mode can be set and retrieved from the CTM
client GUI only. (In the CTM GUI, launch the NE Explorer, select the PSM card, click the Card tab, and
configure the Card Mode attribute.)
CTM GateWay/CORBA distinguishes the mode that the NE version uses.
2.2.7.5 Specifying Route Constraints for OCHxx Circuit Provisioning
For OCHCC, OCHNC, and OCH trail tunnel circuits, you can specify route constraints (NE
include/exclude constraints) in the SNCCreateData_T parameter.
For protected OCHCC circuits, constraints for the working path are specified in the SNCCreateData_T
parameter; constraints for the protected path are specified in a separate parameter. See details in the
createAndActivateProtectedOchccFromUserLabel API description.
2.2.7.6 Low-Order Circuit Provisioning Using VAP/LAP
CTM supports low-order circuit provisioning using VAP circuits on ONS 15310 CL, ONS 15310 MA
SONET, ONS 15310 MA SDH, ONS 15327, and ONS 15454 SONET NEs, and low-order aggregation
point (LAP) circuits on ONS 15454 SDH NEs. The VAP/LAP circuits must be bidirectional.
When provisioning VAP/LAP circuits, the source is treated as the STS grooming end; the destination is
treated as the VT grooming end and is used later to connect VT circuits.
The source is a CTP and the destination is an FTP. See 2.2.5 Naming Conventions, page 2-30 for naming
conventions.