Cisco Cisco Evolved Programmable Network Manager 2.0 Developer's Guide
Cisco Evolved Programmable Network Manager 2.0.1 RESTCONF API Guide
26
Response Content Type
application/xml, application/yang.data+xml, application/json,
application/yang.data+json
application/yang.data+json
Response Data
0 or more QoS Profiles of type qos-profile – see yang model for the data details.
HTTP Status Code
200 OK - Success with response message-body
401, 403 – Authentication and Authorization errors.
400 Bad Request - Invalid request message
500 Internal Server Error - operation-failed
Please refer to RESTCONF standard status codes and standard error response
data for further detail.
data for further detail.
4.16 Service Activation
CEM and MPLS-TE service provisioning is supported through the set of operations defined as RESTCONF
Operations. When the OSS client uses this interface for service provisioning, a set of CFS (Customer Facing
Service) and RFS (Resource Facing Service) objects will be created or modified to handle the service
management in Cisco EPN Manager.
The API provides support for provisioning the following services:
Operations. When the OSS client uses this interface for service provisioning, a set of CFS (Customer Facing
Service) and RFS (Resource Facing Service) objects will be created or modified to handle the service
management in Cisco EPN Manager.
The API provides support for provisioning the following services:
Technology
Service
Service Type
CE
CE
EPL, EVPL, ACESS EPL, ACESS EVPL, EP-
LAN, EVP-LAN, EP-Tree, EVP-Tree
LAN, EVP-LAN, EP-Tree, EVP-Tree
CEM
CEM
T1, T3, E1,E3,VT1.5,VT2,OC1,OC3,
OC12,OC48
OC12,OC48
MPLS-TE
MPLS-TE
Bidirectional TE Tunnel, Layer 3 Link
L3VPN
L3VPN
UNICAST
4.16.1 Service Order Data
The following sub-sections provide the details of each service provisioning order data which is required in the
provision and modify operations of the service activation interface as a POST data in a request object.
provision and modify operations of the service activation interface as a POST data in a request object.
4.16.1.1
Service Order Data – Carrier Ethernet (CE)
The table below lists the Order Data elements and the supported values for Carrier Ethernet Services. Note
that the table below describes all the elements in service order data combined for service and endpoint
configuration for all the CE Services (ELINE, ELAN, ETREE, and EACCESS).
that the table below describes all the elements in service order data combined for service and endpoint
configuration for all the CE Services (ELINE, ELAN, ETREE, and EACCESS).
Carrier Ethernet
Service Order
Data
Service Order
Data
Data Type
Applicable
to Service
Type
to Service
Type
Description
service-name
String
All
Unique name to identify the circuit/VC.
service-
description
description
String
All
Description of the VC that will help to identify the VC.