Cisco Cisco Prime Optical 9.6 개발자 가이드
Cisco Prime Optical 9.6.3 GateWay/CORBA Programmer Reference Guide
OL-28047-01
511
EXCPT_USERLABEL_IN_USE - Raised when the userLabel uniqueness constraint is
not met.
not met.
EXCPT_OBJECT_IN_USE - Raised if a specified CPTP is already associated to an
existing MFD or if the MFD name specified by the NMS is already assigned to an
existing object.
existing MFD or if the MFD name specified by the NMS is already assigned to an
existing object.
EXCPT_NE_COMM_LOSS - Raised when communication is lost to the ME that contains
the MFD.
the MFD.
EXCPT_ENTITY_NOT_FOUND - Raised when one of the provided TPs does not exist.
Relevant Data Structures
MFDCreateData_T:
NameAndStringValue_T[] name
String
userLabel
boolean
forceUniqueness
String
owner
String
networkAccessDomain
NameAndStringValue_T[][]
unassignedCPTPs
LayeredParameters_T[] transmissionParams
NameAndStringValue_T[] additionalCreationInfo
The name of each MFD must be in the following format:
name="EMS";value="CompanyName/EMSname"
name="ManagedElement";value="ManagedElementName"
name="MatrixFlowDomain"; value= "MatrixFlowDomainName"
name="ManagedElement";value="ManagedElementName"
name="MatrixFlowDomain"; value= "MatrixFlowDomainName"
In Prime Optical, each ME name is unique irrespective of which network partition or network
access domain it belongs to. In this data structure, networkAccessDomain separates an ME
from another that has the same name but belongs to a different network access domain.
Use Case Description
The following describes how the system requests to create an MFD:
1. The NMS sends the request to the EMS to create an MFD with the provided parameters.
Use Case Description
The following describes how the system requests to create an MFD:
1. The NMS sends the request to the EMS to create an MFD with the provided parameters.
2. The EMS validates the request:
a. If the syntax is incorrect, an Invalid Input exception is raised.
b. If user label uniqueness is required, the EMS checks the user label for uniqueness. If an
MFD object with the same user label exists, a User Label In Use exception is raised.
c. If one of the specified TPs is unknown to the EMS, an Entity Not Found exception is
raised.
d. If at least one of the MFD parameters could not be set, an Unable To Comply exception
is raised.