Cisco Cisco Evolved Programmable Network Manager 2.0 Developer's Guide
MTOSI Interface Details
Cisco EPN Manager 2.0.1 MTOSI API Guide for OSS Integration
102
Request parameter
Data Type
Description
beginProcessingEvent
BeginProcessingEventType
Returned if the provisioning process
takes more than default wait time for
completing the provisioning.
Note: After the response is returned,
the provisioning process runs in
background and user will be notified of
completion results using notification
producer interface.
takes more than default wait time for
completing the provisioning.
Note: After the response is returned,
the provisioning process runs in
background and user will be notified of
completion results using notification
producer interface.
cfsCreation
CfsCreationEventType
Indicates that CFS creation is
successful.
successful.
serviceCreationFailureEvent
ServiceCreationFailureEven
tType
tType
Indicates partial failure scenario.
4.14.4.1.7
Exceptions
internalError: Indicates that an internal error or exception has occurred as part of this call.
invalidInput: Indicates that the input given to the operation is invalid.
invalidInput: Indicates that the input given to the operation is invalid.
4.14.4.2
modify
The API allows an OSS/NMS to modify a previous provisioning request. This operation takes the CFS
reference and the corresponding modified service order data and modifies the existing CFS. When this
request is complete, each CFS (associated with the product instance) should be in the targetState
(Provisioned_Active), with all associated RFSs (and subtending resources) configured and allocated to the
appropriate CFS.
Pre-condition(s): The CFSs supporting the product instance must exist.
In case of success, the CFS(s) associated with the product instance will be in the targetState
(Provisioned_Active). Subscribers, users, and SAPs will be added or deleted as indicated in the modify
request.
In case of failure: In the case of an atomic request, all CFS(s) will be returned to their original state before the
service request. Also, no subscriber, users or SAPs will be added or deleted. The best effort is that the CFSs
associated with the product instance remain in their current state; no rollback is attempted in this case.
reference and the corresponding modified service order data and modifies the existing CFS. When this
request is complete, each CFS (associated with the product instance) should be in the targetState
(Provisioned_Active), with all associated RFSs (and subtending resources) configured and allocated to the
appropriate CFS.
Pre-condition(s): The CFSs supporting the product instance must exist.
In case of success, the CFS(s) associated with the product instance will be in the targetState
(Provisioned_Active). Subscribers, users, and SAPs will be added or deleted as indicated in the modify
request.
In case of failure: In the case of an atomic request, all CFS(s) will be returned to their original state before the
service request. Also, no subscriber, users or SAPs will be added or deleted. The best effort is that the CFSs
associated with the product instance remain in their current state; no rollback is attempted in this case.
4.14.4.2.1
Input
Request parameter
Data Type
Description
modifyRequest
modifyRequest
-
basicInput
RequestInfoBasicType
-
productInfo
ProductInfoType
Product information associated with the request.
The target OS will translate the product information
to service-level information and perform the
requested action.
The target OS will translate the product information
to service-level information and perform the
requested action.
subscriberRefList
NamingAttributeType
List of RDN types as a customer object id.
targetState
String
State to which the target OS wants the CFSs
transitioned when the request is complete (the
value is either Provisioned_Inactive or
Provisioned_Active).
transitioned when the request is complete (the
value is either Provisioned_Inactive or
Provisioned_Active).