Cisco Cisco Prime Optical 9.8 Guide Du Développeur
Cisco Prime Optical 9.8 GateWay/CORBA Programmer Reference Guide
OL-29218-01
509
The read and write attributes required to modify an MFD on the EMS are bundled in the
MFDModifyData structure, which the NMS passes to the EMS.
MFDModifyData structure, which the NMS passes to the EMS.
The following describes the MFDModifyData structure attributes:
• userLabel—Can be specified by the NMS or it can be empty.
• forceUniqueness—Specifies whether userLabel uniqueness is required for EMS MFDs. If the
• forceUniqueness—Specifies whether userLabel uniqueness is required for EMS MFDs. If the
userLabel is unique and is already in use, the operation fails.
• owner—Can be specified by the NMS or it can be empty.
• networkAccessDomain—The network access domain to which the FD is assigned.
• transmissionParameters::LayeredParameterList_T transmissionParams—A list of modified
• networkAccessDomain—The network access domain to which the FD is assigned.
• transmissionParameters::LayeredParameterList_T transmissionParams—A list of modified
connectionless parameters. As an input only, the list of parameters to be changed,
removed, or added is provided. If an entry must be removed, a hyphen (-) is specified as the
value. When the method is returned, this attribute contains the list of parameters that
could not be applied.
removed, or added is provided. If an entry must be removed, a hyphen (-) is specified as the
value. When the method is returned, this attribute contains the list of parameters that
could not be applied.
• globaldefs::NVSList_T additionalModificationInfo—Additional modification information can
be specified by the NMS. When the method is returned, this attribute contains the
parameters that could not be applied.
parameters that could not be applied.
Use Case Description
The following describes how the system requests to modify an MFD:
1. The NMS sends a request to the EMS to modify an MFD.
2. The EMS validates the request:
2. The EMS validates the request:
a. If the syntax is incorrect, an Invalid Input exception is raised.
b. If the specified MFD 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 MFD
b. If the specified MFD 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 MFD
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.
e. If the MFD already has the required information, the EMS replies with a success indication, but
no notification is generated.
3. If the request is valid:
a. If the MFD has all the required information, the EMS does not send any notifications to the
notification service.
b. If the MFD does not have the required information, the EMS modifies the MFD attributes as
requested.
c. The EMS replies with a success indication.
d. If the EMS makes a change, the appropriate notification is sent to the notification service.
d. If the EMS makes a change, the appropriate notification is sent to the notification service.
Limitations
• The failedAttributes parameter is not supported.
• Notification changes are not sent.
• Notification changes are not sent.
4.5.3 Flow Domain Provisioning Interfaces
This section describes the following interfaces: