Cisco Cisco Prime Optical 10.3 Developer's Guide
Cisco Prime Optical 10.3 GateWay/CORBA Programmer Reference Guide
477
Use Case Description
The EMS must validate the data provided by the NMS and disassociate the requested MFDs
from the specified FD. If the EMS cannot disassociate the specified MFDs, an appropriate
exception is raised. Best effort is not supported. The operation also disassociates the fdEdge
CPTPs that are associated to the MFDs to be disassociated. After the disassociation, the EMS
verifies the server layer connectivity between the associated MFDs using the FD Connectivity
State attribute.
The following describes how the system requests to disassociate MFDs from an existing FD:
The EMS must validate the data provided by the NMS and disassociate the requested MFDs
from the specified FD. If the EMS cannot disassociate the specified MFDs, an appropriate
exception is raised. Best effort is not supported. The operation also disassociates the fdEdge
CPTPs that are associated to the MFDs to be disassociated. After the disassociation, the EMS
verifies the server layer connectivity between the associated MFDs using the FD Connectivity
State attribute.
The following describes how the system requests to disassociate MFDs from an existing FD:
1. The NMS sends the request to the EMS to disassociate MFDs from an existing FD.
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 FD is unknown to the EMS, an Entity Not Found exception is raised.
c. If one or more of the specified MFDs were not previously associated to the FD, an Unable To
b. If the specified FD is unknown to the EMS, an Entity Not Found exception is raised.
c. If one or more of the specified MFDs were not previously associated to the FD, an Unable To
Comply exception is raised.
d. If one or more of the specified MFDs is carrying traffic, an Object In Use exception is raised.
e. If any fdEdge CPTPs cannot be disassociated from the MFDs that are being disassociated (the
e. If any fdEdge CPTPs cannot be disassociated from the MFDs that are being disassociated (the
PortTPRoleState attribute of the CPTPs is set to assigned), no fdEdge CPTPs are disassociated
and an Unable To Comply exception is raised.
and an Unable To Comply exception is raised.
f. If any of the MFDs could not be disassociated, no MFD is disassociated and an Unable To
Comply exception is raised.
3. If the request is valid, the EMS:
a. Disassociates the specified MFDs from the FD.
b. Replies with a success indication.
c. Sends an attribute value change notification to the notification service using the
b. Replies with a success indication.
c. Sends an attribute value change notification to the notification service using the
MatrixFlowDomain attribute of the FD. The notification includes the complete list of MFD
names that are associated to the FD.
names that are associated to the FD.
d. Verifies the server layer connectivity between the associated MFDs. The FD Connectivity State
attribute is modified accordingly (fully connected, not fully connected, or unknown).
4. If the FD Connectivity State attribute is modified, the EMS sends a state change notification to the
notification service.
5. If the request is successful:
a. The requested MFDs are disassociated from the FD.
b. The corresponding fdEdge CPTPs are also disassociated from the FD.
c. If the request fails, there is no change in the system or the MFD association to the FD.
b. The corresponding fdEdge CPTPs are also disassociated from the FD.
c. If the request fails, there is no change in the system or the MFD association to the FD.
Limitations
Notification changes are not sent.
Notification changes are not sent.
4.5.4 EVC FDFr Provisioning Interfaces
This section describes the following interfaces:
•
•
•
•
4.5.4.1 createAndActivateFDFr
Synopsis