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
80
<
soap:Envelope
xmlns:soap
=
"http://schemas.xmlsoap.org/soap/envelope/"
>
<
soap:Header
>
<
header
/>
</
soap:Header
>
<
soap:Body
>
<
ns3:provisionResponse
>
<
ns3:cfsCreation
>
<
ns5:vendorExtensions
>
<
ns27:deployResult
actionResult
=
"running"
action
=
"deploy"
>
<
ns25:info
>
<
ns25:code
>
MTOSI_9000
</
ns25:code
>
<
ns25:message
>
Service deployment is in progress
</
ns25:message
>
</
ns25:info
>
</
ns27:deployResult
>
</
ns5:vendorExtensions
>
<
ns5:cfsCreationEvents
>
<!-- -->
</
ns5:cfsCreationEvents
>
</
ns3:cfsCreation
>
</
ns3:provisionResponse
>
</
soap:Body
>
</
soap:Envelope
>
4.14.2.2
List of error or info codes
Error code
Description
MTOSI_0000
Default error code for all the errors/exceptions - any error occurred in the operation
execution will be returned with this code unless the specific error has a different code.
execution will be returned with this code unless the specific error has a different code.
MTOSI_0001
Default error code for all the method not implemented exceptions - returned when user
invokes a operation that is not implemented by EPNM.
invokes a operation that is not implemented by EPNM.
MTOSI_4001
Default error code for provisioning configuration (CLI) deployment failure errors - these
errors/exceptions are returned as part of the deployResults in a provisioning response
(not as a SOAP fault, but in the response of the operation).
errors/exceptions are returned as part of the deployResults in a provisioning response
(not as a SOAP fault, but in the response of the operation).
MTOSI_9000
Default info message code used for service provisioning deployment info messages. When
request timeout happens while deployment is in progress, the deployment results return
the info message with this code.
request timeout happens while deployment is in progress, the deployment results return
the info message with this code.
4.14.3 Service Order Data
The main input for service provisioning is Service Order Data which consists of service level and endpoint
level configuration. Since this configuration is Cisco specific, ensure that you provide it using MTOSI vendor
extensions of the MTOSI request.
level configuration. Since this configuration is Cisco specific, ensure that you provide it using MTOSI vendor
extensions of the MTOSI request.
The schema for the Service Order Data for Optical services versus that for Carrier Ethernet services is
different. The following table provides the details of the service order data input required for each
technology and service type.
different. The following table provides the details of the service order data input required for each
technology and service type.
4.14.3.1
Optical Service Order Data
4.14.3.1.1
OTN Service Order Data
The following table lists Order Data and supported values for OTN services.
OTN Service Order Data
Data Type
Mandatory /
Optional
Optional
Description
ciscoOptServiceOrderData
ciscoOptServiceO
rderData
rderData
Container for Optical service
provisioning order data details.
provisioning order data details.