When configuring a VPLS E-Tree service, the etree keyword must be specified when the VPLS service is created. This is the first operation required before any SAPs or SDPs are added to the service, because the E-Tree service type affects the operations of the SAPs and SDP bindings.
When configuring AC SAPs, the configuration model is very similar to normal SAPs. Because the VPLS service must be designated as an E-Tree, the default AC SAP is a root-ac SAP. An E-Tree service with all root-ac behaves just as a regular VPLS service. A leaf-ac SAP must be configured for leaf behavior.
For root-leaf-tag SAPs, the SAP is created with both root and leaf VIDs. The 1/1/1:x.* or 1/1/1:x would be the typical format, where x designates the root tag. A leaf-tag is configured at SAP creation and replaces the x with a leaf-tag VID. Combined statistics for root and leaf SAPs are reported under the SAP. There are no individual statistics shown for root and leaf.
The following example illustrates the configuration of a VPLS E-Tree service with root-ac (default configuration for SAPs and SDP binds) and leaf-ac interfaces, as well as a root leaf tag SAP and SDP bind.
In the example, the SAP 1/1/7:2006.200 is configured using the root-leaf-tag parameter, where the outer VID 2006 is used for root traffic and the outer VID 2007 is used for leaf traffic.
*A:ALA-48>config>service# info
----------------------------------------------
...
service vpls 2005 etree customer 1 create
sap 1/1/1:2005 leaf-ac create
exit
sap 1/1/7:2006.200 root-leaf-tag leaf-tag 2007 create
exit
sap 1/1/7:0.* create
exit
spoke-sdp 12:2005 vc-type vlan root-leaf-tag create
no shutdown
exit
spoke-sdp 12:2006 leaf-ac create
no shutdown
exit
no shutdown
exit
....
*A:ALA-48>config>service# info
----------------------------------------------