Cisco OL-21636-01 - Manual (Page 357)

C-1
Cisco IP Solution Center L2VPN and Carrier Ethernet User Guide, 6.0
OL-21636-01
A P P E N D I X
C
Setting Up VLAN Translation
This appendix describes how to set up VLAN translation for L2VPN ERS (EVPL) services. It contains
the following sections:
• VLAN Translation Overview, page C-1
• Setting Up VLAN Translation, page C-1
• Platform-Specific Usage Notes, page C-6
Note For helpful information to be aware of before you create policies and services using VLAN translation,
review
Platform-Specific Usage Notes, page C-6 .
VLAN Translation Overview
VLAN translation provides flexibility in managing VLANs and Metro Ethernet-related services. There
are two types of VLAN translation—one is 1-to-1 translation (1:1), and the other one is 2-to-1 translation
(2:1). This feature is available for L2VPN ERS (EVPL) (with and without a CE). The behavior of
L2VPN ERS (EVPL) service remains the same, even though it is true that it is possible now for one
Q-in-Q port to be shared by both EWS (EPL) and ERS (EVPL) service. VLAN translation is only for an
Ethernet interface, not for other types of interfaces, such as ATM and Frame Relay.
With 1:1 VLAN translation, the VLAN of the incoming traffic (CE VLAN) is replaced by another VLAN
(PE VLAN). It means the service provider is now able to handle the situation where incoming traffic
from two different customers share the same CE VLAN. The SP can map these two CE VLANs to two
different PE VLANs, and customer traffic will not be mixed.
With 2:1 VLAN translation, the double tagged (Q-in-Q) traffic at the U-PE UNI port can be mapped to
different flows to achieve service multiplexing. The translation is based on the combination of the CE
VLAN (inner tag) and the PE VLAN (outer tag). Without this translation, all the traffic from a Q-in-Q
port can only go to one place because it is switched only by the outer tag.
Setting Up VLAN Translation
The following sections described how to create and manage policies and service requests to support
VLAN translation:
• Creating a Policy, page C-2
• Creating a Service Request, page C-3