HP 6125XLG Command Reference Manual page 177

is specified in the format of { vlan-id }&<1- 1 0>, where &<1- 1 0> indicates that you can specify up to ten
VLAN IDs. The vlan-id argument is in the range of 1 to 4094. Any of the original VLANs cannot be the
same as the translated VLAN.
nni: Configures network-side many-to-one VLAN mapping to guide Layer 3 forwarding of packets from
the network side to the customer side and replace the VLAN tags of packets with the original VLAN tags
of many-to-one VLAN mapping.
nest range vlan-range-list nested-vlan vlan-id: Configures the original VLAN ranges and nested outer
VLAN ID for one-to-two VLAN mapping. The vlan-range-list argument is specified in the format of
{ vlan-id1 to vlan-id2 }&<1- 1 0>, where vlan-id2 must be greater than vlan-id1 and &<1- 1 0> indicates that
you can specify up to ten { vlan-id1 [ to vlan-id2 ] } parameters. The vlan-id argument is in the range of
1 to 4094. Make sure that different VLAN ranges do not overlap. Any of the original VLANs cannot be
the same as the translated VLAN.
nest single vlan-id-list nested-vlan vlan-id: Configures the original VLANs and nested outer VLAN ID for
one-to-two VLAN mapping. The vlan-id-list argument is specified in the format of { vlan-id }&<1- 1 0>,
where &<1- 1 0> indicates that you can specify up to ten VLAN IDs. The vlan-id argument is in the range
of 1 to 4094. Any of the original VLAN cannot be the same as the translated VLAN.
tunnel outer-vlan-id inner-vlan-id translated-vlan outer-vlan-id inner-vlan-id: Configures the original outer
VLAN ID and inner VLAN ID and the translated outer VLAN ID and inner VLAN ID for two-to-two VLAN
mapping. Either outer-vlan-id or inner-vlan-id is in the range of 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 carrying two layers of VLAN tags, the transparent VLANs and original VLANs
refer to only the outer VLANs). For more information about transparent VLANs, see Layer 2—LAN
Switching Configuration Guide.
To make many-to-one VLAN mapping take effect, configure many-to-one VLAN mapping in pairs
•
on both the customer side and the network side. Do not configure an interface as the customer-side
interface and network-side interface of many-to-one VLAN mapping. 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.
• Before enabling or disabling QinQ, first clear the existing VLAN mapping entries.
QinQ is mutually exclusive with two-to-two VLAN mapping. After QinQ is enabled on an interface,
•
the interface can recognize only the outermost VLAN tag of packets. As a result, the interface
cannot implement two-to-two VLAN mapping.
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 four bytes. When you configure one-to-two VLAN mapping, HP recommends
increasing the MTU (to at least 1504 bytes) on interfaces in the service provider network.
VLAN mapping takes effect on only VLAN-tagged packets received on an interface.
•
VLAN mapping is mutually exclusive with EVB. Do not configure VLAN mapping and EVB on a
•
port.
170