Cisco Cisco Prime Optical 9.6 Guia Do Programador
Cisco Prime Optical 9.6.3 GateWay/CORBA Programmer Reference Guide
OL-28047-01
523
EXCPT_ENTITY_NOT_FOUND - Raised when the fdName attribute references an object
that does not exist.
that does not exist.
EXCPT_UNABLE_TO_COMPLY - Raised when the EMS is unable to execute the request
because at least one of the parameters, although valid, cannot be set.
because at least one of the parameters, although valid, cannot be set.
EXCPT_USERLABEL_IN_USE - Raised when the userLabel uniqueness constraint is
not met.
not met.
EXCPT_NE_COMM_LOSS - Raised when communication is lost to an ME involved in
this operation, which prevents the creation of an MFD or CPTP.
this operation, which prevents the creation of an MFD or CPTP.
Relevant Data Structures
FDModifyData_T
String
userLabel
boolean
forceUniqueness
String
owner
String
networkAccessDomain
LayeredParameters_T[] transmissionParams
NameAndStringValue_T[] additionalModificationInfo
Use Case Description
The following describes how the system requests to modify an FD:
1. The NMS sends the request to the EMS to modify an FD.
The following describes how the system requests to modify an FD:
1. The NMS sends the request to the EMS to modify an FD.
2. The EMS validates the request:
a. If the syntax is incorrect, an Invalid Input exception is raised.
b. If the specified FD is unknown to the EMS, an Entity Not Found exception is raised.
c. If user label uniqueness is required, the EMS checks the user label for uniqueness. If an
FD object with the same user label exists, a User Label In Use exception is raised.
d. If the EMS cannot satisfy any attribute that must be modified, an Unable To Comply
exception is raised.
3. If the request is valid:
a. If the FD already has all the required information, the EMS does not send any
notifications to the notification service.
b. If the FD does not have the required information, the EMS modifies the FD attributes as
requested.
c. The EMS replies with a success indication.
4. If the EMS makes a change, the appropriate notification is sent to the notification service.
Limitations
• The failedAttributes parameter is not supported.
Limitations
• The failedAttributes parameter is not supported.
• Notification changes are not sent.