Cisco Cisco Evolved Programmable Network Manager 1.2 Developer's Guide
MTOSI Interface Details
Cisco EPN Manager OSS Integration Guide for MTOSI
76
76
getOpticalLinkInterfacesIterato
rResponse
rResponse
MultipleOpticalLinkInterfaceObj
ectsResponseType
ectsResponseType
Holder for containing the list of
Optical Endpoint Id. Each Optical Link
Interface Name details is same as in
the getAllOpticalLinkInterfaces
operation response.
Optical Endpoint Id. Each Optical Link
Interface Name details is same as in
the getAllOpticalLinkInterfaces
operation response.
4.12.2.1.3
Exceptions
internalError: Indicates that an internal error or exception is occurring 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.13 ServiceActivationInterface
Cisco EPN Manager supports Optical and Carrier Ethernet service provisioning using set of operations defined
in the ServiceActivationInterface. When OSS client uses this interface to do service provisioning, a set of CFS
(Customer Facing Service) and RFS (Resource Facing Service) objects will be created/modified to handle the
service management in the Cisco EPN Manager.
This section details the service provision operations that can be performed by the OSS client.
in the ServiceActivationInterface. When OSS client uses this interface to do service provisioning, a set of CFS
(Customer Facing Service) and RFS (Resource Facing Service) objects will be created/modified to handle the
service management in the Cisco EPN Manager.
This section details the service provision operations that can be performed by the OSS client.
4.13.1 Supported Services for Provisioning
The API provides support for provisioning the following services.
Technology
Service
Service Type
Optical
OTN
ODU_TUNNEL
ODU_UNI
TRAIL_UNI
ODU_UNI
TRAIL_UNI
OCH
OCHCC
OCHNC
OCH-Trail
OCHNC
OCH-Trail
Carrier Ethernet
Note: Supplementary provisioning functions
that can be created independent of
Circuits/VC are not supported in the API.
Note: Supplementary provisioning functions
that can be created independent of
Circuits/VC are not supported in the API.
ELINE
EPL
EVPL
EVPL
ELAN
EP-LAN
EVP-LAN
EVP-LAN
E-Tree
EP-Tree
EVP-Tree
EVP-Tree
E-Access
Access EPL
Access EVPL
Access EVPL
4.13.2 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.