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  

 

 

96 

The following table describes the elements for adding and removing the UNI as part of the modify operation 
of ELAN and ETREE services: 
 

uniModifyOpe
ration 

String 

EP-LAN, EVP-
LAN, EP-TREE, 
EVP-TREE 

Operation type on a modify request for a ELAN and ETREE 
service to add or remove or update UNI.  
Valid values: add, remove, update 
In case of ELAN services, this element should present inside 
each endpoint data to add/remove or update that specific 
endpoint. 
For ETREE services, this element should be present along 
with uniRefList below in order data. 

uniRefList 

UniRefLi
stType 

EP-TREE, EVP-
TREE 

Container element to hold the UNI references used in 
add/remove UNIs in modify request of ETREE services. 
Should contain uniRef elements list. For example: 
<uniList> 
<uniRef> 
<rdn><type>MD</type><value>CISCO_EPNM</va
lue></rdn> 
<rdn><type>UNI</type><value>my_endpoint_u
ni</value></rdn> 
</uniRef> 
<uniList> 

 

QinQ Configuration of the endpoints in the order data is supported only for EVPL and Access EVPL, EVP-LAN 
services. 

For E-LAN Services provisioning, adding multiple UNIs as part of the Endpoint configuration is supported. The 
configuration for each UNI should be added as each AEnd Endpoint under the AEndEndpointList container 
element.  
 
Note: EP-Tree, EVP-Tree only supports single UNI configuration in order data. 
 
The following request xml snippet shows how the multiple UNI configurations can be specified for EVP-LAN 
service provisioning. 

 

 

<ciscoCeServiceOrderData> 
   <!-- service configuration --> 
    <serviceName>EvpLanSevice1</serviceName> 
    <coreTechnology>VPLS</coreTechnology> 
    ... 
    ... 
    <!--==== Multi Uni/Endpoints Configuration ==== --> 
    <aEndEpDataList> 
        <endpointData> 
            <uniModifyOperation>add</uniModifyOperation>