Table of Contents
Advertisement
nni: Configures the network-side port to use the original VLAN tags of the many-to-one mapping to
replace the VLAN tags of the packets destined for the user network.
nest range vlan-range-list nested-vlan vlan-id: Specifies the CVLAN ranges and the SVLAN for a
one-to-two VLAN mapping. The vlan-range-list argument specifies a space-separated list of up to 10
CVLAN items. Each item specifies a CVLAN ID or a range of CVLAN IDs in the form of vlan-id1 to
vlan-id2. The value range for CVLAN IDs is 1 to 4094. The value for the vlan-id2 argument must be
equal to or greater than the value for the vlan-id1 argument. Different CVLAN ranges cannot overlap.
The vlan-id argument specifies the SVLAN ID in the range of 1 to 4094.
nest single vlan-id-list nested-vlan vlan-id: Specifies the CVLANs and the SVLAN for a one-to-two
VLAN mapping. The vlan-id-list argument specifies a space-separated list of up to 10 CVLAN IDs,
each of which is in the range of 1 to 4094. The vlan-id argument specifies the SVLAN ID in the range
of 1 to 4094.
tunnel outer-vlan-id inner-vlan-id translated-vlan outer-vlan-id inner-vlan-id: Specifies the original
SVLAN ID and CVLAN ID and the translated SVLAN ID and CVLAN ID for a two-to-two VLAN
mapping. The value ranges for the outer-vlan-id argument and the inner-vlan-id argument are both 1
to 4094.
all: Deletes all VLAN mapping configurations from the interface.
Usage guidelines
For different types of VLAN mapping entries on an interface, both the original VLANs and the
translated VLANs cannot overlap. For one-to-one VLAN mapping entries or two-to-two VLAN
mapping entries, the translated VLANs cannot overlap. When the original VLANs of one-to-one or
two-to-two VLAN mapping entries overlap, the most recent configuration takes effect.
On an interface, a transparent VLAN cannot be configured as an original VLAN or translated VLAN.
For packets that have two layers of VLAN tags, both of the translated VLANs and original VLANs
refer to only the outer VLANs. For more information about transparent VLANs, see Layer 2—LAN
Switching Configuration Guide.
For many-to-one VLAN mapping to take effect, configure many-to-one VLAN mapping in pairs on
both the customer side and the network side. An interface cannot be configured as the
customer-side port and network-side port of many-to-one VLAN mapping at the same time. After you
configure an interface as the network-side interface of many-to-one VLAN mapping, do not configure
the other types of VLAN mapping on the interface.
Customer-side many-to-one VLAN mapping is not supported in Layer 2 aggregate interface view.
Before you enable or disable QinQ on a port, you must remove all VLAN mappings on the port. You
cannot configure two-to-two VLAN mapping on a QinQ-enabled port.
To ensure correct traffic forwarding from the service provider network to the customer network, do
not configure many-to-one VLAN mapping together with uRPF. For more information about uRPF,
see Security Configuration Guide.
The MTU of an interface is 1500 bytes by default. After a VLAN tag is added to a packet, the packet
length is added by 4 bytes. As a best practice, set the MTU to a minimum of 1504 bytes for ports on
the forwarding path of the packet in the service provider network.
VLAN mapping takes effect only on VLAN-tagged packets received on an interface.
Examples
# Configure a one-to-one VLAN mapping on GigabitEthernet 1/0/1 to map VLAN 1 to VLAN 101.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] vlan mapping 1 translated-vlan 101
# Configure many-to-one VLAN mappings on the customer-side port GigabitEthernet 1/0/2 to map
VLANs 1 through 50 and VLAN 80 to VLAN 101. Configure the network-side port GigabitEthernet
1/0/3 to use the original VLAN tags of the many-to-one mappings to replace the VLAN tags of the
packets destined for the user network.
248
Advertisement
Table of Contents
