Cisco Cisco Evolved Programmable Network Manager 1.2 Developer's Guide
MTOSI Interface Details
Cisco EPN Manager OSS Integration Guide for MTOSI
97
Pre-condition(s): The CFSs supporting the product instance must not yet exist.
Post-condition(s): In case of success, the CFS(s) associated with the product instance will be in the
Provisioned_Aactive state. If an atomic request fails, all CFS(s) will be returned to their original state (before
the service request). The best effort is that the CFSs associated with the product instance remain in their
current state; no rollback is attempted in this case.
Note: This API will provision and activate the specified service.
Post-condition(s): In case of success, the CFS(s) associated with the product instance will be in the
Provisioned_Aactive state. If an atomic request fails, all CFS(s) will be returned to their original state (before
the service request). The best effort is that the CFSs associated with the product instance remain in their
current state; no rollback is attempted in this case.
Note: This API will provision and activate the specified service.
4.14.3.1.1
Optical Services
The Optical customer facing services (CFS) can be provisioned for Optical Transport Network (OTN) and
Dense Wavelength Division Multiplexing (DWDM) services.
Dense Wavelength Division Multiplexing (DWDM) services.
4.14.3.1.2
Carrier Ethernet Services
The Carrier Ethernet customer facing services (CFS) can be provisioned for ELINE, ELAN, ETREE, and EACCESS
Services.
Services.
4.14.3.1.3
Service Input Data
The Input data for provisioning services are set in the productInfoType and the Cisco-specific vendor
extensions in basicInput. The following table describes the standard data types. The Service Order Data
Tables above in this section provides details of the data required to provision services and corresponding
example request and responses are provided in the Appendix of this guide.
extensions in basicInput. The following table describes the standard data types. The Service Order Data
Tables above in this section provides details of the data required to provision services and corresponding
example request and responses are provided in the Appendix of this guide.
4.14.3.1.4
Input
Request parameter
Data Type
Description
provisionRequest
provisionRequest
Details of the provision request.
basicInput
RequestInfoBasicType
vendorExtensions which will hold the order
data required for provisioning. (Details of the
XML data is provided in Appendix.)
data required for provisioning. (Details of the
XML data is provided in Appendix.)
orderData
OrderDataType
Cisco-specific vendor extension that holds the
order data for provisioning. Refer the Service
Order Data tables for the detailed data
description.
order data for provisioning. Refer the Service
Order Data tables for the detailed data
description.
productInfo
ProductInfoType
ServiceType of the service requested.
subscriberRefList
NamingAttributeType
List of RDN types as a customer object id.
soaInput
RequestInfoSOAwareType
Service Order Aware Type.
Although this is a mandatory field in the data
model,
Although this is a mandatory field in the data
model,
Cisco
EPN Manager does not process
this data.
requestedCompletionDate
dateTime
Not used. Should be set to current date.
Priority
Integer
Not used. Should be set to 0.
purchaseOrder
String
Not used. Can be set to NONE.
validFor
dateTime
Not used. Should be set to current date.