Cisco Cisco Prime Optical 9.6 Developer's Guide
Cisco Prime Optical 9.6.3 GateWay/CORBA Programmer Reference Guide
OL-28047-01
78
close other sessions. To avoid this exception, the NMS must invoke the destroy method on
iterators.
2.2.6.4.9 EXCPT_USERLABEL_IN_USE
This exception indicates that the userLabel uniqueness constraint cannot be met.
2.2.6.4.10 EXCPT_STRICT_MERGE_FAILED
This exception is raised when an OSS issues an upgrade request to merge circuits with a STRICT
MERGE operation type. The OSS uses this exception to issue the upgrade request with a LOOSE
MERGE operation type.
2.2.7 Provisioning Subnetwork Connections
SNC provisioning must be within a multilayer subnetwork scope, which means the aEnd and the
zEnd of an SNC must be in the same multilayer subnetwork.
Prime Optical defines the method multiLayerSubnetwork::MultiLayerSubnetworkMgr_I::
Prime Optical defines the method multiLayerSubnetwork::MultiLayerSubnetworkMgr_I::
createAndActivateSNCFromUserLabel for SNC provisioning.
2.2.7.1 SNC Provisioning on OC-n or Electrical Equipment
Prime Optical supports SNC provisioning on OC-n or electrical cards for ONS 15310 CL, ONS
15310 MA SONET, ONS 15310 MA SDH, ONS 15327, ONS 15454 SONET, ONS 15454 SDH, and
ONS 15600 SONET NEs.
CTPs are used as the endpoints to create the SNC.
CTPs are used as the endpoints to create the SNC.
2.2.7.2 SNC Provisioning on Ethernet Equipment
ONS 15310 CL, ONS 15310 MA SONET, ONS 15310 MA SDH, ONS 15327, ONS 15454 SONET,
ONS 15454 SDH, CPT 200/600 SONET, and CPT 200/600 SDH managed elements support
Ethernet equipment. SNCs can be created on this equipment to carry Ethernet traffic. The TMF
standard supports only SONET, SDH, DWDM, and ATM; it does not support Ethernet at this
time.
Provisioning SNCs on E-series, G-series, and ML-series equipment supported by the ONS 15310
Provisioning SNCs on E-series, G-series, and ML-series equipment supported by the ONS 15310
CL, ONS 15310 MA SONET, ONS 15310 MA SDH, ONS 15327, ONS 15454 SONET, and ONS 15454
SDH is different from creating SNCs on SONET or PDH equipment. For SNCs on Ethernet
naming conventions.
The three modes supported for SNC provisioning on Ethernet equipment are:
• Single-card mode—E-series cards; VLANs can be associated during creation.
The three modes supported for SNC provisioning on Ethernet equipment are:
• Single-card mode—E-series cards; VLANs can be associated during creation.
• Multicard mode—E-series cards; VLANs can be associated during creation.
• Linear-card mode—E-series, G-series, and ML-series cards.
To obtain available source and destination FTPs for SNC provisioning, use the following
To obtain available source and destination FTPs for SNC provisioning, use the following
methods:
• managedElementManager::ManagedElementManager_I:: getAllSrcFTPsForSNCProvisioning
• managedElementManager::ManagedElementManager_I:: getAllSrcFTPsForSNCProvisioning