HPE FlexNetwork VSR1000 User manual

HPE VSR1000 Virtual Services Router
Layer 2—LAN Switching Configuration Guide
Part number: 5200-3153
Software version: VSR1000_HPE-CMW710-E0518-X64
Document version: 5W100-20170314

© Copyright 2017 Hewlett Packard Enterprise Development LP
The information contained herein is subject to change without notice. The only warranties for Hewlett Packard
Enterprise products and services are set forth in the express warranty statements accompanying such
products and services. Nothing herein should be construed as constituting an additional warranty. Hewlett
Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein.
Confidential computer software. Valid license from Hewlett Packard Enterprise required for possession, use, or
copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software
Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s
standard commercial license.
Links to third-party websites take you outside the Hewlett Packard Enterprise website. Hewlett Packard
Enterprise has no control over and is not responsible for information outside the Hewlett Packard Enterprise
website.
Acknowledgments
Intel®, Itanium®, Pentium®, Intel Inside®, and the Intel Inside logo are trademarks of Intel Corporation in the
United States and other countries.
Microsoft® and Windows® are either registered trademarks or trademarks of Microsoft Corporation in the
United States and/or other countries.
Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated.
Java and Oracle are registered trademarks of Oracle and/or its affiliates.
UNIX® is a registered trademark of The Open Group.

i
Contents
Configuring VLAN termination ········································································ 1
Overview ···························································································································································· 1
VLAN termination types ····························································································································· 1
VLAN termination application scenarios ···································································································· 1
Configuration restrictions and guidelines ··········································································································· 3
VLAN termination configuration task list ············································································································ 3
Configuring Dot1q termination ··························································································································· 4
Configuring ambiguous Dot1q termination ································································································· 4
Configuring unambiguous Dot1q termination ····························································································· 4
Configuring QinQ termination ···························································································································· 5
Configuring ambiguous QinQ termination ·································································································· 5
Configuring unambiguous QinQ termination ······························································································ 6
Configuring untagged termination ······················································································································ 7
Configuring default termination ·························································································································· 7
Enabling a VLAN termination-enabled interface to transmit broadcasts and multicasts ···································· 7
Configuring the TPID for VLAN-tagged packets ································································································ 8
VLAN termination configuration examples ········································································································· 9
Unambiguous Dot1q termination configuration example ··········································································· 9
Ambiguous Dot1q termination configuration example ·············································································· 11
Configuration example for Dot1q termination supporting PPPoE server ················································· 12
Unambiguous QinQ termination configuration example··········································································· 13
Ambiguous QinQ termination configuration example ··············································································· 15
Configuration example for QinQ termination supporting PPPoE server ·················································· 17
Configuration example for QinQ termination supporting DHCP relay ······················································ 18
Configuring LLDP ·························································································· 21
Overview ·························································································································································· 21
Basic concepts ········································································································································· 21
Working mechanism ································································································································· 26
Protocols and standards ·························································································································· 27
LLDP configuration task list ····························································································································· 27
Performing basic LLDP configurations ············································································································· 28
Enabling LLDP ········································································································································· 28
Setting the LLDP bridge mode ················································································································· 28
Setting the LLDP operating mode ············································································································ 28
Setting the LLDP reinitialization delay ······································································································ 29
Enabling LLDP polling ······························································································································ 29
Configuring the advertisable TLVs ··········································································································· 30
Configuring the management address and its encoding format ······························································· 31
Setting other LLDP parameters ················································································································ 32
Setting an encapsulation format for LLDP frames ··················································································· 32
Disabling LLDP PVID inconsistency check ······························································································ 33
Configuring LLDP trapping and LLDP-MED trapping ······················································································ 33
Setting the source MAC address of LLDP frames to the MAC address of the subinterface associated with the
specified VLAN ················································································································································ 34
Enabling the device to generate ARP or ND entries for received management address LLDP TLVs ············· 34
Displaying and maintaining LLDP ···················································································································· 35
LLDP configuration examples ·························································································································· 35
Basic LLDP configuration example ·········································································································· 35
Document conventions and icons ································································· 41
Conventions ····················································································································································· 41
Network topology icons ···································································································································· 42
Support and other resources ········································································ 43
Accessing Hewlett Packard Enterprise Support ······························································································ 43
Accessing updates ··········································································································································· 43

ii
Websites ·················································································································································· 44
Customer self repair ································································································································· 44
Remote support ········································································································································ 44
Documentation feedback ························································································································· 44
Index ············································································································· 46

1
Configuring VLAN termination
Overview
VLAN termination typically processes packets that include VLAN tags. A VLAN termination-enabled
interface performs the following tasks when receiving a VLAN-tagged packet:
1. Assigns the packet to an interface according to its VLAN tags.
2. Removes the VLAN tags of the packet.
3. Delivers the packet to Layer 3 forwarding or other processing pipelines.
Before sending the packet, the VLAN termination-enabled interface determines whether to add new
VLAN tags to the packet, based on the VLAN termination type.
VLAN termination can also process packets that do not include any VLAN tags.
This document uses the following VLAN tag concepts for a pa cket that has two or m ore layers of
VLAN tags:
•Layer 1 VLAN tag—Specifies the outermost layer of VLAN tags.
•Layer 2 VLAN tag—Specifies the second outermost layer of VLAN tags.
The VLAN IDs of the packets are numbered in the same manner as the VLAN tags.
VLAN termination types
VLAN termination
types Types of packets to be terminated on the interface Tagging status of outgoing packets on the interface
Dot1q termination
The packets must meet both of the
following requirements:
• The packets include one or more
layers of VLAN tags.
• The outermost VLAN tag matches
the configured value.
Single-tagged
QinQ termination
The packets must meet both of the
following requirements:
• The packets include two or more
layers of VLAN tags.
• The outermost two layers of tags
match the configured values.
Double-tagged
Untagged termination Untagged packets Untagged
Default termination
Packets that cannot be processed on any
other subinterfaces of the same main
interface
Untagged
VLAN termination application scenarios
Inter-VLAN communication
Hosts in different VLANs cannot directly communicate with each other. You can use Layer 3 routing
to allow all VLANs to com municate. To restrict communication to the specified VLANs, configure
VLAN termination on subinterfaces.

2
As shown in Figure 1, Host A and Host B are in dif ferent VLANs. The two host s can communicate
with each other after you perform the following tasks:
1. Specify 1.1.1.1/24 and 1.1.2.1/24 as the gateway IP addresses for Host A and Host B,
respectively.
2. On the device, configure VLAN termination on Layer 3 Ethernet subinterfaces GigabitEthernet
1/0/1.1 and GigabitEthernet 1/0/2.1.
Figure 1 VLAN termination for inter-VLAN communication
LAN-WAN communication
Typically, WAN protocols such as ATM, Frame Relay, and PPP do not re cognize VLAN-tagged
packets from LANs. Before packets are sent to a WAN, the sending port must locally record the
VLAN information and remove VLAN tags from the packets. To do that, configure VLAN termination
on subinterfaces.
As shown in Figure 2, a host is located on a customer network and wants to access the WAN network
through a PPPoE connection. CVLAN and SVLAN represent the VLAN on the customer network and
service provider network, respectively.
To access the WAN network, a packet originating from the host is processed as follows:
1. Layer 2 Switch A adds a CVLAN tag to the packet and sends the packet.
2. Layer 2 Switch B adds an SVLAN tag to the packet on the QinQ-enabled port.
3. The packet is forwarded on the service provider network based on the SVLAN tag.
4. The PPPoE gateway removes the two layers of VLAN tags from the packet and adds new
VLAN tags on the QinQ termination-enabled port.
5. The PPPoE gateway sends the packet to the WAN network through
synchronous/asynchronous serial interface Serial 2/1/0.
Figure 2 VLAN termination enables LAN-WAN communication

3
Configuration restrictions and guidelines
When you configure VLAN termination, follow these restrictions and guidelines:
•On a portal-enabled interface, log off all portal users before you change the VLAN termination
type, for example, from Dot1q termination to QinQ termination. Any portal users who remain
online after the change cannot be logged off or reauthenticated. For more information about
portal authentication, see Security Configuration Guide.
•A main interface cannot terminate VLAN-tagged packets. To terminate VLAN-tagged packets,
you can create subinterfaces for the main interface.
•Subinterfaces (Layer 3 Ethernet subinterfaces and Layer 3 aggregate subinterfaces for
example) can terminate the following packets:
{ Packets with matching Layer 1 VLAN IDs.
{ Packets with matching Layer 1 and Layer 2 VLAN IDs.
•After you modify the VLAN termination configuration for a Layer 3 Ethernet subinterface or
Layer 3 aggregate subinterface, the subinterface automatically restarts. All dynamic ARP table
entries for the subinterface are deleted.
•When a main interface bound to a VLAN interface receives a VLAN-tagged packet, the main
interface processes the packet according to the VLAN interface configuration.
After you configure VLAN termination, the system finds an inte rface for a re ceived packet in the
following order:
•Subinterface configured with QinQ termination.
•Subinterface configured with loose QinQ termination.
•Subinterface configured with Dot1q termination, or subinterface that supports Dot1q
termination by default.
•Subinterface configured with loose Dot1q termination.
•Subinterface configured with untagged termination.
•Subinterface configured with default termination.
•Main interface.
VLAN termination configuration task list
Tasks at a glance
(Required.) Perform one of the following tasks:
• Configuring Dot1q termination
{ Configuring ambiguous Dot1q termination
{ Configuring unambiguous Dot1q termination
• Configuring QinQ termination
{ Configuring ambiguous QinQ termination
{ Configuring unambiguous QinQ termination
• Configuring untagged termination
• Configuring default termination
(Optional.) Enabling a VLAN termination-enabled interface to transmit broadcasts and multicasts
(Optional.) Configuring the TPID for VLAN-tagged packets

4
Configuring Dot1q termination
Based on the range of outermost VLAN IDs in the VLAN-tagged packets that can be terminated by a
subinterface, the following types of Dot1q termination are available:
•Ambiguous Dot1q termination—Terminates VLAN-tagged packets whose outermost VLAN
IDs are in the specified range. Any other VLAN-tagged packets are not allowed to pass through
this subinterface.
When the subinterface receives a packet, it removes the outermost layer of tags from the
packet. When the subinterface sends a packet, it tags the packet with a VLAN ID as follows:
{ For a PPPoE packet, the VLAN ID is obtained by searching the PPPoE session entries.
{ For a DHCP relay packet, the VLAN ID is obtained by searching the DHCP session entries.
{ For an IPv4 or MPLS packet, the VLAN ID is obtained by searching the ARP entries.
•Unambiguous Dot1q termination—Terminates only VLAN-tagged packets whose outermost
VLAN ID matches the specified VLAN ID. Any other VLAN-tagged packets are not allowed to
pass through this subinterface.
When the subinterface receives a packet, it removes the outermost VLAN tag of the packet.
When the subinterface sends a packet, it tags the packet with the specified VLAN ID.
Configuring ambiguous Dot1q termination
Step Command Remarks
1. Enter system view. system-view N/A
2. Enter interface view.
• Enter Layer 3 Ethernet
subinterface view:
interface interface-type
interface-number.subnumber
• Enter Layer 3 aggregate
subinterface view:
interface route-aggregation
interface-number.subnumber
• Enter L3VE subinterface view:
interface ve-l3vpn
interface-number.subnumber
• Enter Reth subinterface view:
interface reth
interface-number.subnumber
N/A
3. Configure ambiguous Dot1q
termination. vlan-type dot1q vid vlan-id-list
[loose ]
By default, Dot1q termination
is disabled on a subinterface.
Configuring unambiguous Dot1q termination
Step Command Remarks
1. Enter system view. system-view N/A

5
Step Command Remarks
2. Enter interface view.
• Enter Layer 3 Ethernet
subinterface view:
interface interface-type
interface-number.subnumber
• Enter Layer 3 aggregate
subinterface view:
interface route-aggregation
interface-number.subnumber
• Enter L3VE subinterface view:
interface ve-l3vpn
interface-number.subnumber
• Enter Reth subinterface view:
interface reth
interface-number.subnumber
N/A
3. Configure unambiguous
Dot1q termination. vlan-type dot1q vid vlan-id [ loose ] By default, Dot1q termination
is disabled on a subinterface.
Configuring QinQ termination
QinQ termination allows only packet s that incl ude specific VLAN tags to pass throu gh the
subinterface or VLAN interface. The following types of QinQ termination are available:
•Ambiguous QinQ termination—Terminates QinQ packets whose outermost two layers of
VLAN IDs are in the specified range.
When the subinterface or VLAN interface receives a packet, it removes the outermost two
layers of VLAN tags of the packet.
When the subinterface or VLAN interface sends a packet, it tags the packet with the outermost
two layers of VLAN IDs, which are determined as follows:
{ For a PPPoE packet, the outermost two layers of VLAN IDs are obtained by searching the
PPPoE session entries.
{ For a DHCP relay packet, the outermost two layers of VLAN IDs are obtained by searching
the DHCP relay entries.
{ For an IPv4 or MPLS packet, the outermost two layers of VLAN IDs are obtained by
searching the ARP entries.
•Unambiguous QinQ termination—Terminates QinQ packets whose outermost two layers of
VLAN IDs match the specified values.
When the subinterface or VLAN interface receives a packet, it removes the two layers of VLAN
tags of the packet.
When the subinterface or VLAN interface sends the packet, it tags the packet with two layers of
VLAN tags as specified.
Configuring ambiguous QinQ termination
When you configure ambiguous QinQ termination, follow these restrictions and guidelines:
•If you specify the same Layer 1 VLAN ID for multiple subinterfaces under a main interface, the
Layer 2 VLAN IDs specified for them must be different. However, if you specify different Layer 1
VLAN IDs for the subinterfaces, the Layer 2 VLAN IDs specified for the subinterfaces are not
required to be different.
•Subinterfaces under different main interfaces can terminate VLAN-tagged packets with the
same Layer 1 and Layer 2 VLAN IDs.

6
•When you use the vlan-type dot1q vid second-dot1q command to configure ambiguous
QinQ termination multiple times, one of the following conditions occurs:
{ If the most recently specified Layer 1 ID is the same as the current Layer 1 ID, the specified
Layer 2 IDs in both configurations take effect.
{ If the most recently specified Layer 1 ID is different from the current Layer 1 ID, you must
first delete the old configuration.
To configure ambiguous QinQ termination:
Step Command Remarks
1. Enter system view. system-view N/A
2. Enter interface view.
• Enter Layer 3 Ethernet subinterface
view:
interface interface-type
interface-number.subnumber
• Enter Layer 3 aggregate subinterface
view:
interface route-aggregation
interface-number.subnumber
• Enter L3VE subinterface view:
interface ve-l3vpn
interface-number.subnumber
• Enter Reth subinterface view:
interface reth
interface-number.subnumber
N/A
3. Configure ambiguous
QinQ termination by
specifying the outermost
two layers of VLAN IDs.
vlan-type dot1q vid vlan-id-list
second-dot1q { vlan-id-list | any } [ loose ]
By default, QinQ
termination is disabled on
a subinterface.
Configuring unambiguous QinQ termination
Step Command Remarks
1. Enter system view. system-view N/A
2. Enter interface view.
• Enter Layer 3 Ethernet
subinterface view:
interface interface-type
interface-number.subnumber
• Enter Layer 3 aggregate
subinterface view:
interface route-aggregation
interface-number.subnumber
• Enter L3VE subinterface view:
interface ve-l3vpn
interface-number.subnumber
• Enter Reth subinterface view:
interface reth
interface-number.subnumber
N/A
3. Configure unambiguous
QinQ termination by
specifying the outermost two
layers of VLAN IDs.
vlan-type dot1q vid vlan-id
second-dot1q vlan-id [ loose ]
By default, QinQ termination
is disabled on a subinterface.

7
Configuring untagged termination
Step Command Remarks
1. Enter system view. system-view N/A
2. Enter interface view.
• Enter Layer 3 Ethernet subinterface
view:
interface interface-type
interface-number.subnumber
• Enter Layer 3 aggregate subinterface
view:
interface route-aggregation
interface-number.subnumber
• Enter L3VE subinterface view:
interface ve-l3vpn
interface-number.subnumber
• Enter Reth subinterface view:
interface reth
interface-number.subnumber
N/A
3. Configure untagged
termination. vlan-type dot1q untagged By default, untagged
termination is disabled on
a subinterface.
Configuring default termination
Step Command Remarks
1. Enter system view. system-view N/A
2. Enter interface view.
• Enter Layer 3 Ethernet subinterface view:
interface interface-type
interface-number.subnumber
• Enter Layer 3 aggregate subinterface view:
interface route-aggregation
interface-number.subnumber
• Enter L3VE subinterface view:
interface ve-l3vpn
interface-number.subnumber
• Enter Reth subinterface view:
interface reth interface-number.subnumber
N/A
3. Configure default
termination. vlan-type dot1q default
By default, default
termination is not
configured on a
subinterface.
Enabling a VLAN termination-enabled interface to
transmit broadcasts and multicasts
This function enables ambiguous Dot1q or Qi nQ termination-enabled interfaces to tran smit
broadcasts and multicasts.
As a be st practice, use t he vlan-termination broadcast ra command to en able an am biguous
Dot1q or QinQ termination-enabled interface to transmit RA multicast packets on an IPv6 network.

8
This command prohibits transmission of broadcast packets and other types of multicast packets, and
consumes less CPU resources than the vlan-termination broadcast enable command.
To enable a VLAN termination-enabled interface to transmit broadcasts and multicasts:
Step Command Remarks
1. Enter system view. system-view N/A
2. Enter interface view.
• Enter Layer 3 Ethernet subinterface
view:
interface interface-type
interface-number.subnumber
• Enter Layer 3 aggregate
subinterface view:
interface route-aggregation
interface-number.subnumber
• Enter L3VE subinterface view:
interface ve-l3vpn
interface-number.subnumber
• Enter Reth subinterface view:
interface reth
interface-number.subnumber
N/A
3. Enable the interface
to transmit broadcasts
and multicasts.
• Enable the interface to transmit
broadcasts and multicasts:
vlan-termination broadcast
enable
• Enable the interface to transmit only
RA multicasts on an IPv6 network:
vlan-termination broadcast ra
By default, an ambiguous Dot1q
or QinQ termination-enabled
interface does not transmit
broadcasts and multicasts.
Use one of the commands.
Configuring the TPID for VLAN-tagged packets
TPID identifies whether or not a frame contains VLAN tags. By default, the value of 0x8100 identifies
an IEEE 802.1Q-tagged frame. You can set another TPID value to identify VLAN-tagged packets.
To work with VLAN termination on a subinterface, set the TPID value in the outermost VLAN tag of
packets on the main interface of the subinterface.
The interface processes packets as untagged packets if their outermost VLAN tag is not 0x8100 or
the configured value.
When sending a packet, the interface sets the TP ID value in the outermo st VLAN tag to the
configured value. If the packet includes two or more layers of VLAN tags, the interface sets the TPID
values to 0x8100 in all VLAN tags except the outermost VLAN tag.
To set the TPID value for VLAN-tagged packets:
Step Command Remarks
1. Enter system view. system-view N/A

9
Step Command Remarks
2. Enter interface view.
• Enter Layer 3 Ethernet interface
view:
interface interface-type
interface-number
• Enter Layer 3 aggregate interface
view:
interface route-aggregation
interface-number
• Enter L3VE interface view:
interface ve-l3vpn
interface-number.subnumber
• Enter Reth interface view:
interface reth interface-number
Configurations made in the
following views take effect on
all the subinterfaces:
• Layer 3 Ethernet
interface view.
• Layer 3 aggregate
interface view.
• L3VE interface view.
• Reth interface view.
3. Set the TPID value in the
outermost VLAN tag of
packets received and
sent by the interface.
dot1q ethernet-type hex-value The default setting is 0x8100.
VLAN termination configuration examples
Unambiguous Dot1q termination configuration example
Network requirements
As shown in Figure 3, configure unambiguous Dot1q termination on subinterfaces of the device to
implement intra-VLAN and inter-VLAN communications between hosts.
Figure 3 Network diagram
Configuration procedure
1. Configure Host A, Host B, Host C, and Host D:
# On Host A, specify 1.1.1.1/8 and 1.0.0.1/8 as its IP address and gateway IP address,
respectively. (Details not shown.)
# On Host B, specify 2.2.2.2/8 and 2.0.0.1/8 as its IP address and gateway IP address,
respectively. (Details not shown.)

10
# On Host C, specify 3.3.3.3/8 and 3.0.0.1/8 as its IP address and gateway IP address,
respectively. (Details not shown.)
# On Host D, specify 4.4.4.4/8 and 4.0.0.1/8 as its IP address and gateway IP address,
respectively. (Details not shown.)
2. Configure Layer 2 Switch A:
# Create VLAN 10.
<L2_SwitchA> system-view
[L2_SwitchA] vlan 10
# Assign GigabitEthernet 1/0/2 to VLAN 10.
[L2_SwitchA-vlan10] port gigabitethernet 1/0/2
[L2_SwitchA-vlan10] quit
# Create VLAN 20.
[L2_SwitchA] vlan 20
# Assign GigabitEthernet 1/0/3 to VLAN 20.
[L2_SwitchA-vlan20] port gigabitethernet 1/0/3
[L2_SwitchA-vlan20] quit
# Configure GigabitEthernet 1/0/1 as a trunk port, and assign the port to VLANs 10 and 20.
[L2_SwitchA] interface gigabitethernet 1/0/1
[L2_SwitchA-GigabitEthernet1/0/1] port link-type trunk
[L2_SwitchA-GigabitEthernet1/0/1] port trunk permit vlan 10 20
3. Configure Layer 2 Switch B in the same way you configure Layer 2 Switch A. (Details not
shown.)
4. Configure the device:
# Create GigabitEthernet 1/0/1.10, and assign an IP address to this interface.
<Device> system-view
[Device] interface gigabitethernet 1/0/1.10
[Device-GigabitEthernet1/0/1.10] ip address 1.0.0.1 255.0.0.0
# Configure GigabitEthernet 1/0/1.10 to terminate packets tagged with VLAN 10.
[Device-GigabitEthernet1/0/1.10] vlan-type dot1q vid 10
[Device-GigabitEthernet1/0/1.10] quit
# Create GigabitEthernet 1/0/1.20, and assign an IP address to this interface.
[Device] interface gigabitethernet 1/0/1.20
[Device-GigabitEthernet1/0/1.20] ip address 2.0.0.1 255.0.0.0
# Configure GigabitEthernet 1/0/1.20 to terminate packets tagged with VLAN 20.
[Device-GigabitEthernet1/0/1.20] vlan-type dot1q vid 20
[Device-GigabitEthernet1/0/1.20] quit
# Configure GigabitEthernet 2/0/1.10, and assign an IP address to this interface.
[Device] interface gigabitethernet 2/0/1.10
[Device-GigabitEthernet2/0/1.10] ip address 3.0.0.1 255.0.0.0
# Configure GigabitEthernet 2/0/1.10 to terminate packets tagged with VLAN 10.
[Device-GigabitEthernet2/0/1.10] vlan-type dot1q vid 10
[Device-GigabitEthernet2/0/1.10] quit
# Configure GigabitEthernet 2/0/1.20, and assign an IP address to this interface.
[Device] interface gigabitethernet 2/0/1.20
[Device-GigabitEthernet2/0/1.20] ip address 4.0.0.1 255.0.0.0
# Configure GigabitEthernet 2/0/1.20 to terminate packets tagged with VLAN 20.
[Device-GigabitEthernet2/0/1.20] vlan-type dot1q vid 20

11
[Device-GigabitEthernet2/0/1.20] quit
Verifying the configuration
# Verify that Host A, Host B, Host C, and Host D can ping each other. (Details not shown.)
Ambiguous Dot1q termination configuration example
Network requirements
As shown in Figure 4, configure ambiguous Dot1q termination, so that hosts in different VLANs can
communicate with the server group.
Figure 4 Network diagram
Configuration procedure
In this example, L2 switch B uses the factory configuration.
1. Configure Host A, Host B, and Host C:
# Assign 1.1.1.1/24, 1.1.1.2/24, and 1.1.1.3/24 to Host A, Host B, and Host C, respectively.
(Details not shown.)
# Specify 1.1.1.11/24 as the gateway IP address for the hosts. (Details not shown.)
2. Configure Layer 2 Switch A:
# Create VLAN 11.
<L2_SwitchA> system-view
[L2_SwitchA] vlan 11
# Assign GigabitEthernet 1/0/1 to VLAN 11.
[L2_SwitchA-vlan11] port gigabitethernet 1/0/1
[L2_SwitchA-vlan11] quit
# Create VLAN 12.
[L2_SwitchA] vlan 12
# Assign GigabitEthernet 1/0/2 to VLAN 12.
[L2_SwitchA-vlan12] port gigabitethernet 1/0/2
[L2_SwitchA-vlan12] quit
# Create VLAN 13.

12
[L2_SwitchA] vlan 13
# Assign GigabitEthernet 1/0/3 to VLAN 13.
[L2_SwitchA-vlan13] port gigabitethernet 1/0/3
[L2_SwitchA-vlan13] quit
# Configure GigabitEthernet 1/0/7 as a trunk port, and assign the port to VLANs 11 through 13.
[L2_SwitchA] interface gigabitethernet 1/0/7
[L2_SwitchA-GigabitEthernet1/0/7] port link-type trunk
[L2_SwitchA-GigabitEthernet1/0/7] port trunk permit vlan 11 to 13
3. Configure the device:
# Create Ethernet subinterface GigabitEthernet 1/0/1.10, and assign an IP address to the
subinterface.
<Device> system-view
[Device] interface gigabitethernet 1/0/1.10
[Device-GigabitEthernet1/0/1.10] ip address 1.1.1.11 255.255.255.0
# Enable Dot1q termination on GigabitEthernet 1/0/1.10 to terminate VLAN-tagged packets
whose Layer 1 VLAN IDs are 11, 12, or 13.
[Device-GigabitEthernet1/0/1.10] vlan-type dot1q vid 11 to 13
# Enable GigabitEthernet 1/0/1.10 to transmit broadcasts and multicasts.
[Device-GigabitEthernet1/0/1.10] vlan-termination broadcast enable
[Device-GigabitEthernet1/0/1.10] quit
# Configure an IP address for GigabitEthernet 1/0/2.
[Device] interface gigabitethernet 1/0/2
[Device-GigabitEthernet1/0/2] ip address 1.1.2.11 255.255.255.0
4. Configure the server group:
# Assign each device in the server group an IP address on the network segment 1.1.2.0/24.
(Details not shown.)
# Specify 1.1.2.11/24 as the gateway IP address for the server group. (Details not shown.)
Verifying the configuration
# Verify that Host A, Host B, and Host C can ping the device in the server group. (Details not shown.)
Configuration example for Dot1q termination supporting
PPPoE server
Network requirements
As shown in Figure 5, the router ac ts as a PPPoE s erver. Hosts in dif ferent VLANs access the
Internet through the PPPoE server.
Configure Dot1q termination so that hosts in different VLANs can access the Internet.

13
Figure 5 Network diagram
Configuration procedure
# Configure VLANs and Dot1q termination. For the configuration procedure, see "Ambiguous Dot1q
termination configuration example." (Details not shown.)
# Configure the router as the PPPoE server. Configure PPPoE settings on GigabitEthernet 1/0/1.10
on the router. For more information about the PPPo E configuration, see Layer 2—WAN
Configuration Guide. (Details not shown.)
Unambiguous QinQ termination configuration example
Network requirements
As shown in Figure 6:
•Layer 2 Switch C supports only single VLAN-tagged packets.
•On Layer 2 Switch B, GigabitEthernet 1/0/2 is enabled with QinQ to adds an SVLAN tag 100 to
the packets with CVLAN ID 11.
Configure unambiguous QinQ termination so that Host A can communicate with Host B.

14
Figure 6 Network diagram
Configuration procedure
In this example, Layer 2 Switch C uses the factory configuration.
1. Configure Host A and Host B:
# On Host A, specify 1.1.1.1/24 and 1.1.1.11/24 as its IP address and gateway IP address,
respectively. (Details not shown.)
# On Host B, specify 1.1.2.1/24 and 1.1.2.11/24 as its IP address and gateway IP address,
respectively. (Details not shown.)
2. Configure Layer 2 Switch A:
# Create VLAN 11.
<L2_SwitchA> system-view
[L2_SwitchA] vlan 11
# Assign GigabitEthernet 1/0/2 to VLAN 11.
[L2_SwitchA-vlan11] port gigabitethernet 1/0/2
[L2_SwitchA-vlan11] quit
# Configure GigabitEthernet 1/0/1 as a trunk port, and assign the port to VLAN 11.
[L2_SwitchA] interface gigabitethernet 1/0/1
[L2_SwitchA-GigabitEthernet1/0/1] port link-type trunk
[L2_SwitchA-GigabitEthernet1/0/1] port trunk permit vlan 11
3. Configure Layer 2 Switch B:
# Configure GigabitEthernet 1/0/2 as a trunk port, and assign the port to VLAN 11 and VLAN
100.
<L2_SwitchB> system-view
[L2_SwitchB] interface gigabitethernet 1/0/2
[L2_SwitchB-GigabitEthernet1/0/2] port link-type trunk
[L2_SwitchB-GigabitEthernet1/0/2] port trunk permit vlan 11 100
# Set the PVID of GigabitEthernet 1/0/2 to VLAN 100.
[L2_SwitchB-GigabitEthernet1/0/2] port trunk pvid vlan 100
# Enable QinQ on GigabitEthernet 1/0/2.
[L2_SwitchB-GigabitEthernet1/0/2] qinq enable
[L2_SwitchB-GigabitEthernet1/0/2] quit
# Configure GigabitEthernet 1/0/1 as a trunk port, and assign the port to VLAN 100.
Router
Host A
1.1.1.1/24
Host B
1.1.2.1/24
L2 Switch A
L2 Switch B
L2 Switch C
VLAN 11
GE1/0/1.10
1.1.1.11/24
Service provider network
VLAN 100
GE1/0/1
GE1/0/2
GE1/0/2
QinQ enabled
GE1/0/1
GE1/0/2
1.1.2.11/24

15
[L2_SwitchB] interface gigabitethernet 1/0/1
[L2_SwitchB-GigabitEthernet1/0/1] port link-type trunk
[L2_SwitchB-GigabitEthernet1/0/1] port trunk permit vlan 100
4. Configure the router:
# Create Ethernet subinterface GigabitEthernet 1/0/1.10, and assign an IP address to the
subinterface.
<Router> system-view
[Router] interface gigabitethernet 1/0/1.10
[Router-GigabitEthernet1/0/1.10] ip address 1.1.1.11 255.255.255.0
# Enable QinQ termination on GigabitEthernet 1/0/1.10 to terminate the VLAN-tagged packets
with the Layer 1 VLAN ID 100 and the Layer 2 VLAN ID 11.
[Router-GigabitEthernet1/0/1.10] vlan-type dot1q vid 100 second-dot1q 11
[Router-GigabitEthernet1/0/1.10] quit
# Assign an IP address to GigabitEthernet 1/0/2.
[Router] interface gigabitethernet 1/0/2
[Router-GigabitEthernet1/0/2] ip address 1.1.2.11 255.255.255.0
Verifying the configuration
# Verify that Host A and Host B can ping each other. (Details not shown.)
Ambiguous QinQ termination configuration example
Network requirements
As shown in Figure 7, QinQ is enabled on GigabitEthernet 1/0/2 of Layer 2 Switch B.
Configure ambiguous QinQ termination, so that hosts can communicate with the server group.
Figure 7 Network diagram
Configuration procedure
In this example, Layer 2 Switch C uses the factory configuration.
1. Configure Host A, Host B, and Host C:
Router
L2 Switch B
L2 Switch C
GE1/0/1.10
1.1.1.11/24
Service provider network
VLAN 100
Host A
1.1.1.1/24
Host B
1.1.1.2/24
Host C
1.1.1.3/24
VLAN 11 VLAN 12 VLAN 13
L2 Switch A
Server group
GE1/0/1
GE1/0/2
GE1/0/3
GE1/0/7
GE1/0/2
1.1.2.11/24
GE1/0/2
QinQ enabled
GE1/0/1

16
# Assign IP addresses 1.1.1.1/24, 1.1.1.2/24, and 1.1.1.3/24 to Host A, Host B, and Host C,
respectively. (Details not shown.)
# Specify 1.1.1.11/24 as the gateway address for the hosts. (Details not shown.)
2. Configure Layer 2 Switch A:
# Create VLAN 11.
<L2_SwitchA> system-view
[L2_SwitchA] vlan 11
# Assign GigabitEthernet 1/0/1 to VLAN 11.
[L2_SwitchA-vlan11] port gigabitethernet 1/0/1
[L2_SwitchA-vlan11] quit
# Create VLAN 12.
[L2_SwitchA] vlan 12
# Assign GigabitEthernet 1/0/2 to VLAN 12.
[L2_SwitchA-vlan12] port gigabitethernet 1/0/2
[L2_SwitchA-vlan12] quit
# Create VLAN 13.
[L2_SwitchA] vlan 13
# Assign GigabitEthernet 1/0/3 to VLAN 13.
[L2_SwitchA-vlan13] port gigabitethernet 1/0/3
[L2_SwitchA-vlan13] quit
# Configure GigabitEthernet 1/0/7 as a trunk port, and assign the port to VLANs 11 through 13.
[L2_SwitchA] interface gigabitethernet 1/0/7
[L2_SwitchA-GigabitEthernet1/0/7] port link-type trunk
[L2_SwitchA-GigabitEthernet1/0/7] port trunk permit vlan 11 to 13
3. Configure Layer 2 Switch B:
# Configure GigabitEthernet 1/0/2 as a trunk port, and assign the port to VLANs 11 through 13
and VLAN 100.
<L2_SwitchB> system-view
[L2_SwitchB] interface gigabitethernet 1/0/2
[L2_SwitchB-GigabitEthernet1/0/2] port link-type trunk
[L2_SwitchB-GigabitEthernet1/0/2] port trunk permit vlan 11 to 13 100
# Set the PVID of GigabitEthernet 1/0/2 to VLAN 100.
[L2_SwitchB-GigabitEthernet1/0/2] port trunk pvid vlan 100
# Enable QinQ on GigabitEthernet 1/0/2.
[L2_SwitchB-GigabitEthernet1/0/2] qinq enable
[L2_SwitchB-GigabitEthernet1/0/2] quit
# Configure GigabitEthernet 1/0/1 as a trunk port, and assign the port to VLAN 100.
[L2_SwitchB] interface gigabitethernet 1/0/1
[L2_SwitchB-GigabitEthernet1/0/1] port link-type trunk
[L2_SwitchB-GigabitEthernet1/0/1] port trunk permit vlan 100
4. Configure the router:
# Create Ethernet subinterface GigabitEthernet 1/0/1.10, and assign an IP address to the
subinterface.
<Router> system-view
[Router] interface gigabitethernet 1/0/1.10
[Router-GigabitEthernet1/0/1.10] ip address 1.1.1.11 255.255.255.0