Selective VLAN Mapping to VPLS
ExtremeXOS currently supports filtering a set of CVIDs received on a VMAN
port by classifying the port as a CEP. Since a VPLS can already be configured to carry VMAN
traffic, ExtremeXOS 15.4 release extends support for mapping a CEP to a VPLS.
VMAN is the
VLAN stacking feature in EXOS. It
has two types of ports: access and network. The access port can be both aware or unaware of VLAN.
The customer edge port is the VLAN aware port of VMAN. The CEP allows several configurable
options:
- An Ethernet port can be associated with multiple VMANs based on the
CVIDs.
- Multiple CVIDs on multiple Ethernet ports can be associated with a
VMAN.
- A range of CVIDs can be specified instead of individually
configured.
- CVID translations and egress filtering.
VMAN with CEP ports can work as a way to achieve some of the requirements.
However, you cannot currently assign it to a VPLS.
When implemented, a VMAN with CNP, or CEP, or both can be assigned as a service to a VPLS. This
feature does not add any other capability beyond associating a VMAN with CEP port to a VPLS.
Existing VMAN features such as CVID translation and egress filtering do not change. The existing
VPLS feature to include or exclude SVLAN also does not change.
Supported Platforms
VLAN mapping to VPLS is supported on the following platforms:
- ExtremeSwitching X460-G2 (supported
from ExtremeXOS
15.6)
- ExtremeSwitching X590 (supported from ExtremeXOS 30.2)
- ExtremeSwitching X670-G2 (supported
from ExtremeXOS
15.6)
- ExtremeSwitching X690 (supported
from ExtremeXOS
22.3)
- ExtremeSwitching X770
- ExtremeSwitching X465 (supported from ExtremeXOS 30.2)
- ExtremeSwitching X870
(supported from ExtremeXOS 22.2)
Limitations
The Selective VLAN Mapping to VPLS feature has the following
limitations:
- You cannot assign multiple VMANs to a VPLS.
- You cannot use SNMP and XML to assign a
VMAN with CEP port to VPLS.
