04-Layer 2 - LAN Switching Configuration Guide-Book

H3C VSR Series Virtual Services Routers
Layer 2 - LAN Switching

Configuration Guide
Hangzhou H3C Technologies Co., Ltd.

http://www.h3c.com
Software version: VSR1000_H3C-CMW710-E0321-X64

VSR2000_H3C-CMW710-E0321-X64
Document version: 5W100-20151208
Copyright © 2015, Hangzhou H3C Technologies Co., Ltd. and its licensors
All rights reserved
No part of this manual may be reproduced or transmitted in any form or by any means without prior
written consent of Hangzhou H3C Technologies Co., Ltd.
Trademarks
H3C, , H3CS, H3CIE, H3CNE, Aolynk, , H3Care, , IRF, NetPilot, Netflow,

SecEngine, SecPath, SecCenter, SecBlade, Comware, ITCMM and HUASAN are trademarks of
Hangzhou H3C Technologies Co., Ltd.
All other trademarks that may be mentioned in this manual are the property of their respective owners
Notice
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.
Preface
The Layer 2 – LAN Switching Configuration Guide describes the fundamentals and configuration of
Ethernet link aggregation, VLAN, LLDP, and so on.
This preface includes the following topics about the documentation:
• Audience.
• Conventions.
• Obtaining documentation.
• Technical support.
• Documentation feedback.
Audience
This documentation is intended for:
• Network planners.
• Field technical support and servicing engineers.
• Network administrators working with the VSR Routers series.
Conventions
This section describes the conventions used in the documentation.
Port numbering in examples

The port numbers in the documentation are for illustration only and might be unavailable on your device.
Command conventions
Convention Description
Boldface Bold text represents commands and keywords that you enter literally as shown.
Italic Italic text represents arguments that you replace with actual values.
[] Square brackets enclose syntax choices (keywords or arguments) that are optional.
Braces enclose a set of required syntax choices separated by vertical bars, from which
{ x | y | ... }
you select one.
Square brackets enclose a set of optional syntax choices separated by vertical bars, from
[ x | y | ... ]
which you select one or none.
Asterisk marked braces enclose a set of required syntax choices separated by vertical
{ x | y | ... } *
bars, from which you select at least one.
Asterisk marked square brackets enclose optional syntax choices separated by vertical
[ x | y | ... ] *
bars, from which you select one choice, multiple choices, or none.
The argument or keyword and argument combination before the ampersand (&) sign can
&<1-n>
be entered 1 to n times.
# A line that starts with a pound (#) sign is comments.
GUI conventions
Window names, button names, field names, and menu items are in Boldface. For
Boldface
example, the New User window appears; click OK.
> Multi-level menus are separated by angle brackets. For example, File > Create > Folder.
Symbols
An alert that calls attention to important information that if not understood or followed
WARNING! can result in personal injury.
An alert that calls attention to important information that if not understood or followed
CAUTION: can result in data loss, data corruption, or damage to hardware or software.
IMPORTANT: An alert that calls attention to essential information.
NOTE: An alert that contains additional or supplementary information.
TIP: An alert that provides helpful information.
Network topology icons
Represents a generic network device, such as a router, switch, or firewall.
Represents a routing-capable device, such as a router or Layer 3 switch.
Represents a generic switch, such as a Layer 2 or Layer 3 switch, or a router that

supports Layer 2 forwarding and other Layer 2 features.
Represents an access controller, a unified wired-WLAN module, or the access controller

engine on a unified wired-WLAN switch.
Represents an access point.
T Wireless terminator unit.
T Wireless terminator.

Represents a mesh access point.

Represents omnidirectional signals.
Represents directional signals.
Represents a security product, such as a firewall, UTM, multiservice security gateway, or

load balancing device.
Represents a security card, such as a firewall, load balancing, NetStream, SSL VPN, IPS,
or ACG card.
Obtaining documentation
Access the most up-to-date H3C product documentation on the World Wide Web
at http://www.h3c.com.
Click the following links to obtain different categories of product documentation:
[Technical Documents]—Provides hardware installation, software upgrading, and software feature
configuration and maintenance documentation.
[Products & Solutions]—Provides information about products and technologies, as well as solutions.
[Software Download]—Provides the documentation released with the software version.
Technical support
service@h3c.com
http://www.h3c.com
Documentation feedback
You can e-mail your comments about product documentation to info@h3c.com.
We appreciate your comments.
Contents
Configuring Ethernet link aggregation ······················································································································· 1

Basic concepts ··································································································································································· 1
Aggregation group, member port, and aggregate interface ·············································································· 1
Aggregation states of member ports in an aggregation group ·········································································· 2
Operational key ······················································································································································· 2
Configuration types ·················································································································································· 2
Link aggregation modes ·········································································································································· 3
Aggregating links in static mode ····································································································································· 3
Choosing a reference port ······································································································································ 3
Setting the aggregation state of each member port ····························································································· 4
Aggregating links in dynamic mode ······························································································································· 5
LACP ·········································································································································································· 5
How dynamic link aggregation works ··················································································································· 6
Edge aggregate interface ················································································································································ 8
Load sharing modes for link aggregation groups ········································································································· 8
Ethernet link aggregation configuration task list ············································································································9
Configuring an aggregation group ································································································································ 9
Configuration restrictions and guidelines ·············································································································· 9
Configuring a Layer 3 static aggregation group ······························································································· 10
Configuring a Layer 3 dynamic aggregation group ························································································· 10
Configuring an aggregate interface ···························································································································· 11
Setting the description for an aggregate interface ···························································································· 11
Setting the MAC address for an aggregate interface ······················································································· 12
Setting the MTU for a Layer 3 aggregate interface ··························································································· 12
Setting the minimum and maximum numbers of Selected ports for an aggregation group ·························· 13
Setting the expected bandwidth for an aggregate interface ············································································ 14
Configuring an edge aggregate interface·········································································································· 14
Shutting down an aggregate interface ··············································································································· 14
Restoring the default settings for an aggregate interface ················································································· 15
Setting load sharing modes for link aggregation groups ·························································································· 15
Setting the global link-aggregation load sharing mode ···················································································· 15
Setting the group-specific load sharing mode ···································································································· 16
Enabling link-aggregation traffic redirection ··············································································································· 16
Configuration restrictions and guidelines ··········································································································· 16
Configuration procedure ······································································································································ 17
Displaying and maintaining Ethernet link aggregation ····························································································· 17
Ethernet link aggregation configuration examples ····································································································· 17
Layer 3 static aggregation configuration example ···························································································· 17
Layer 3 dynamic aggregation configuration example ······················································································ 19
Layer 3 aggregation load sharing configuration example ··············································································· 20
Layer 3 edge aggregate interface configuration example ··············································································· 22
Configuring VLANs ···················································································································································· 24

Overview········································································································································································· 24
VLAN frame encapsulation ·································································································································· 24
Protocols and standards ······································································································································· 25
Configuring basic VLAN settings·································································································································· 25
Configuring port-based VLANs ····································································································································· 26
Introduction ···························································································································································· 26
i
Assigning an access port to a VLAN ·················································································································· 27
Assigning a trunk port to a VLAN························································································································ 28
Assigning a hybrid port to a VLAN ····················································································································· 28
Configuring a VLAN group ··········································································································································· 29
Displaying and maintaining VLANs ····························································································································· 29
VLAN configuration example········································································································································ 30
Network requirements ··········································································································································· 30
Verifying the configuration ··································································································································· 31
Configuring VLAN termination ·································································································································· 32

Overview········································································································································································· 32
VLAN termination types ········································································································································ 32
VLAN termination application scenarios ············································································································ 33
VLAN termination configuration task list ····················································································································· 34
Configuring Dot1q termination ····································································································································· 35
Configuring ambiguous Dot1q termination ········································································································ 35
Configuring unambiguous Dot1q termination ···································································································· 35
Configuring QinQ termination ····································································································································· 36
Configuring ambiguous QinQ termination········································································································· 36
Configuring unambiguous QinQ termination ···································································································· 37
Configuring untagged termination ······························································································································· 38
Configuring default termination ···································································································································· 38
Enabling a VLAN termination-enabled subinterface to transmit broadcasts and multicasts ·································· 38
Configuring the TPID for VLAN-tagged packets·········································································································· 39
VLAN termination configuration examples ·················································································································· 40
Unambiguous Dot1q termination configuration example ················································································· 40
Ambiguous Dot1q termination configuration example ····················································································· 42
Configuration example for Dot1q termination supporting PPPoE server ························································· 43
Unambiguous QinQ termination configuration example ·················································································· 44
Ambiguous QinQ termination configuration example ······················································································ 46
Configuration example for QinQ termination supporting PPPoE server·························································· 48
Configuration example for QinQ termination supporting DHCP relay ··························································· 49
Configuring LLDP ························································································································································ 53

Overview········································································································································································· 53
Basic concepts ······················································································································································· 53
Working mechanism ············································································································································· 58
Protocols and standards ······································································································································· 59
LLDP configuration task list ············································································································································ 60
Performing basic LLDP configurations ·························································································································· 60
Enabling LLDP ························································································································································ 60
Setting the LLDP bridge mode ······························································································································ 61
Setting the LLDP operating mode ························································································································· 61
Setting the LLDP reinitialization delay ················································································································· 62
Enabling LLDP polling············································································································································ 62
Configuring the advertisable TLVs ······················································································································· 62
Configuring the management address and its encoding format ······································································ 63
Setting other LLDP parameters ······························································································································ 64
Setting an encapsulation format for LLDP frames ······························································································· 65
Configuring LLDP trapping and LLDP-MED trapping ·································································································· 65
Setting the source MAC address of LLDP frames to the MAC address of the subinterface associated with the
specified VLAN······························································································································································· 66
Enabling the system to issue the generated ARP entry to a Layer 3 Ethernet subinterface after a port receives an LLDP
frame ··············································································································································································· 67
ii
Displaying and maintaining LLDP ································································································································· 67
Basic LLDP configuration example ································································································································ 68
Network requirements ··········································································································································· 68
Verifying the configuration ··································································································································· 69
Index ··········································································································································································· 73
iii
Configuring Ethernet link aggregation
Ethernet link aggregation bundles multiple physical Ethernet links into one logical link, called an
aggregate link. Link aggregation has the following benefits:
• Increased bandwidth beyond the limits of any single link. In an aggregate link, traffic is distributed
across the member ports.
• Improved link reliability. The member ports dynamically back up one another. When a member
port fails, its traffic is automatically switched to other member ports.
As shown in Figure 1, Device A and Device B are connected by three physical Ethernet links. These
physical Ethernet links are combined into an aggregate link called link aggregation 1. The bandwidth of
this aggregate link can reach up to the total bandwidth of the three physical Ethernet links. At the same
time, the three Ethernet links back up one another. When a physical Ethernet link fails, the traffic
previously transmitted on the failed link is switched to the other two links.
Figure 1 Ethernet link aggregation diagram
Basic concepts
Aggregation group, member port, and aggregate interface
An aggregation group is a group of Ethernet interfaces bundled together. These Ethernet interfaces are
called member ports of the aggregation group. Each aggregation group has a corresponding logical
interface (called an aggregate interface).
Aggregate interfaces include Layer 2 aggregate interfaces and Layer 3 aggregate interfaces. On a
Layer 3 aggregate interface, you can create subinterfaces.
When you create an aggregate interface, the device automatically creates an aggregation group of the
same type and number as the aggregate interface. For example, when you create Layer 2 aggregate
interface 1, the device automatically creates Layer 2 aggregation group 1.
You can assign Layer 2 Ethernet interfaces only to a Layer 2 aggregation group, and Layer 3 Ethernet
interfaces only to a Layer 3 aggregation group.
The port rate of an aggregate interface equals the total rate of its Selected member ports. Its duplex
mode is the same as that of the Selected member ports. For more information about Selected member
ports, see "Aggregation states of member ports in an aggregation group."
NOTE:
The device supports only Layer 3 aggregation groups and aggregate interfaces.
1
Aggregation states of member ports in an aggregation group
A member port in an aggregation group can be in any of the following aggregation states:
• Selected—A Selected port can forward traffic.
• Unselected—An Unselected port cannot forward traffic.
• Individual—An Individual port can forward traffic as a normal physical port. A port is placed in the
Individual state when the following conditions exist:
{ Its aggregate interface is configured as an edge aggregate interface.
{ The port has not received Link Aggregation Control Protocol Data Units (LACPDUs) from its peer
port.
Operational key
When aggregating ports, the system automatically assigns each port an operational key based on port
information, such as port rate and duplex mode. Any change to this information triggers a recalculation
of the operational key.
In an aggregation group, all Selected ports have the same operational key.
Configuration types
Port configurations include attribute configurations and protocol configurations. Attribute configurations
of a link aggregation member port affect its aggregation state.
• Attribute configurations—To become a Selected port, a member port must have the same attribute
configurations as the aggregate interface. Table 1 describes the attribute configurations.
Attribute configurations made on an aggregate interface are automatically synchronized to all
member ports. These configurations are retained on the member ports even after the aggregate
interface is deleted.
Any attribute configuration change on a member port might affect the aggregation states and
running services of the member ports. The system displays a warning message every time you try
to change an attribute configuration setting on a member port.
Table 1 Attribute configurations
Feature Considerations
Indicates whether the port has joined an isolation group and which isolation
Port isolation
group the port belongs to.
QinQ status (enabled/disabled), TPID for VLAN tags, and VLAN transparent
QinQ
transmission. For information about QinQ, see "Configuring QinQ."
VLAN mapping configured on the port. For more information about VLAN
VLAN mapping
mapping, see "Configuring VLAN mapping."
2
Feature Considerations
VLAN attribute configurations include the following:
• Permitted VLAN IDs.
• PVID.
• Link type (trunk, hybrid, or access).
• PVLAN port type (promiscuous, trunk promiscuous, host, or trunk
VLAN
secondary).
• IP subnet-based VLAN configuration.
• Protocol-based VLAN configuration.
• VLAN tagging mode.
For information about VLANs, see "Configuring VLANs."
• Protocol configurations—Protocol configurations of a member port do not affect the aggregation

state of the member port. MAC address learning and spanning tree settings are examples of
protocol configurations.
NOTE:
• The protocol configurations for an aggregate interface take effect only on the current aggregate
interface.
• The protocol configurations for a member port take effect only when the port leaves its aggregation
group.
Link aggregation modes

An aggregation group operates in one of the following modes:
• Static—Static aggregation is stable. An aggregation group in static mode is called a static
aggregation group. The aggregation states of the member ports in a static aggregation group are
not affected by the peer ports.
• Dynamic—An aggregation group in dynamic mode is called a dynamic aggregation group. The
local system and the peer system automatically maintain the aggregation states of the member ports.
Dynamic link aggregation reduces the administrators' workload.
Aggregating links in static mode

Choosing a reference port
When setting the aggregation states of the ports in an aggregation group, the system automatically
chooses a member port as the reference port. A Selected port must have the same operational key and
attribute configurations as the reference port.
The system chooses a reference port from the member ports in up state.
The candidate reference ports are organized into different priority levels following these rules:
1. In descending order of port priority.
2. Full duplex.
3. In descending order of speed.
3
4. Half duplex.
5. In descending order of speed.
From the candidate ports with the same attribute configurations as the aggregate interface, the one with
the highest priority level is chosen as the reference port.
• If multiple ports have the same priority level, the port that has been Selected (if any) is chosen. If
multiple ports with the same priority level have been Selected, the one with the smallest port number
is chosen.
• If multiple ports have the same priority level and none of them has been Selected, the port with the
smallest port number is chosen.
Setting the aggregation state of each member port

After the reference port is chosen, the system sets the aggregation state of each member port in the static
aggregation group.
Figure 2 Setting the aggregation state of a member port in a static aggregation group
Set the aggregation state of a member port
Yes
Is there any hardware restriction?
No
No
Is the port up?
Yes
No
Operational key/attribute configurations
same as the reference port?
Yes
Yes No
More candidate ports than max. number of Port number as low as to set the port
Selected ports? to the Selected state?
No Yes
Set the port to the

Set the port to the Selected state
Unselected state
The maximum number of Selected ports in a static aggregation group is 8.

After the limit on Selected ports is reached in a static aggregation group, new member ports in the group
are placed in the Unselected state. This mechanism prevents traffic interruption on the existing Selected
ports. A device reboot can cause the device to recalculate the aggregation states of member ports.
4
Any operational key or attribute configuration change might affect the aggregation states of link
aggregation member ports.
The device does not have any hardware attributes.
Aggregating links in dynamic mode

Dynamic aggregation is implemented through IEEE 802.3ad Link Aggregation Control Protocol (LACP).
LACP
LACP uses LACPDUs to exchange aggregation information between LACP-enabled devices. Each
member port in a dynamic aggregation group can exchange information with its peer. When a member
port receives an LACPDU, it compares the received information with information received on the other
member ports. In this way, the two systems reach an agreement on which ports are placed in the Selected
state.
LACP functions
LACP offers basic LACP functions and extended LACP functions, as described in Table 2.
Table 2 Basic and extended LACP functions
Category Description
Implemented through the basic LACPDU fields, including the system LACP priority,
Basic LACP functions
system MAC address, port priority, port number, and operational key.
Implemented by extending the LACPDU with new TLV fields. Extended LACP can
implement LACP MAD for the IRF feature.
Extended LACP • If a device supports both extended LACP and IRF, it can participate in LACP
functions MAD as either an IRF member device or an intermediate device.
• If a device supports extended LACP but not IRF, it can participate in LACP MAD
only as an intermediate device.
LACP operating modes

LACP can operate in active or passive mode.
When LACP is operating in passive mode on a local member port and its peer port, both ports cannot
send LACPDUs. When LACP is operating in active mode on either end of a link, both ports can send
LACPDUs.
LACP priorities
LACP priorities include system LACP priority and port priority, as described in Table 3. The smaller the
priority value, the higher the priority.
5
Table 3 LACP priorities
Type Description
Used by two peer devices (or systems) to determine which one is superior in link
aggregation.
System LACP priority In dynamic link aggregation, the system that has higher system LACP priority sets the
Selected state of member ports on its side. The system that has lower priority sets the
aggregation state of local member ports the same as their respective peer ports.
Determines the likelihood of a member port to be a Selected port on a system. A port

Port priority
with a higher port priority is more likely to become Selected.
LACP timeout interval

The LACP timeout interval specifies how long a member port waits to receive LACPDUs from the peer port.
If a local member port has not received LACPDUs from the peer within the LACP timeout interval, the
member port considers the peer as failed.
The LACP timeout interval also determines the LACPDU sending rate of the peer. LACP timeout intervals
include the following types:
• Short timeout interval—3 seconds. If you use the short timeout interval, the peer sends one LACPDU
per second.
• Long timeout interval—90 seconds. If you use the long timeout interval, the peer sends one
LACPDU every 30 seconds.
How dynamic link aggregation works

Choosing a reference port
The system chooses a reference port from the member ports in up state. A Selected port must have the
same operational key and attribute configurations as the reference port.
The local system (the actor) and the peer system (the partner) negotiate a reference port by using the
following workflow:
1. The two systems determine the system with the smaller system ID.
A system ID contains the system LACP priority and the system MAC address.
a. The two systems compare their LACP priority values.
The lower the LACP priority, the smaller the system ID. If the LACP priority values are the same,
the two systems proceed to step b.
b. The two systems compare their MAC addresses.
The lower the MAC address, the smaller the system ID.
2. The system with the smaller system ID chooses the port with the smallest port ID as the reference
port.
A port ID contains a port priority and a port number. The lower the port priority, the smaller the port
ID.
a. The system chooses the port with the lowest priority value as the reference port.
If the ports have the same priority, the system proceeds to step b.
b. The system compares their port numbers.
The smaller the port number, the smaller the port ID.
6
The port with the smallest port number and the same attribute configurations as the aggregate
interface is chosen as the reference port.
Setting the aggregation state of each member port

After the reference port is chosen, the system with the smaller system ID sets the state of each member port
on its side.
Figure 3 Setting the state of a member port in a dynamic aggregation group
The system with the greater system ID can detect the aggregation state changes on the peer system. The
system with the greater system ID sets the aggregation state of local member ports the same as their peer
ports.
When you aggregate interfaces in dynamic mode, follow these guidelines:
• The maximum number of Selected ports in a dynamic aggregation group is 8.
7
• A dynamic link aggregation group preferably chooses full-duplex ports as the Selected ports. The
group chooses only one half-duplex port as a Selected port when either of the following conditions
exist:
{ None of the full-duplex ports can become Selected ports.
{ Only half-duplex ports exist in the group.
• For stable aggregation and service continuity, do not change the operational key or attribute
configurations on any member port.
• After the Selected port limit is reached, a newly joining port becomes a Selected port if it is more
eligible than a current Selected port.
• The device does not have any hardware attributes.
Edge aggregate interface

Dynamic link aggregation fails on a server-facing aggregate interface if dynamic link aggregation is
configured only on the device. The device forwards traffic by using only one of the physical ports that are
connected to the server.
To improve link reliability, configure the aggregate interface as an edge aggregate interface. This
feature enables all member ports of the aggregation group to forward traffic. When a member port fails,
its traffic is automatically switched to other member ports.
After dynamic link aggregation is configured on the server, the device can receive LACPDUs from the
server. Then, link aggregation between the device and the server operates correctly.
An edge aggregate interface takes effect only when it is configured on an aggregate interface
corresponding to a dynamic aggregation group.
Load sharing modes for link aggregation groups

In a link aggregation group, traffic can be load shared across the Selected ports based on any of the
following modes:
• Per-flow load sharing—Load shares traffic on a per-flow basis. The load sharing mode classifies
packets into flows and forwards packets of the same flow on the same link. This mode can be one
or any combination of the following traffic classification criteria:
{ Ingress port.
{ Source or destination IP address.
{ Source or destination MAC address.
{ Source or destination port number.
{ MPLS label.
{ Protocol number.
{ VLAN tag.
• Packet type-based load sharing—Load shares traffic automatically based on packet types.
{ Layer 2 protocol—Layer 2 protocol packets are not load shared.
{ IPv4 and IPv6—IPv4 and IPv6 packets are load shared based on source and destination IP
addresses.
{ MPLS—MPLS packets are load shared based on Layer 1 labels.
8
Ethernet link aggregation configuration task list
Tasks at a glance
(Required.) Configuring an aggregation group:
• Configuring a Layer 3 static aggregation group
• Configuring a Layer 3 dynamic aggregation group
(Optional.) Configuring an aggregate interface:

• Setting the description for an aggregate interface
• Setting the MAC address for an aggregate interface
• Setting the MTU for a Layer 3 aggregate interface
• Setting the minimum and maximum numbers of Selected ports for an aggregation group
• Setting the expected bandwidth for an aggregate interface
• Configuring an edge aggregate interface
• Shutting down an aggregate interface
• Restoring the default settings for an aggregate interface
(Optional.) Setting load sharing modes for link aggregation groups
(Optional.) Enabling link-aggregation traffic redirection
Configuring an aggregation group

This section explains how to configure an aggregation group.
Configuration restrictions and guidelines

When you configure an aggregation group, follow these restrictions and guidelines:
• Table 4 shows the interfaces that cannot be assigned to a Layer 3 aggregation group.
Table 4 Interfaces that cannot be assigned to a Layer 3 aggregation group
Interface type Reference

Interface assigned to a Reth interface Reth interfaces in High Availability Configuration Guide
Interface assigned to a redundancy group Redundancy groups in High Availability Configuration

node Guide
Interface bound to a cross connect MPLS L2VPN in MPLS Configuration Guide
Interface bound to a VSI VPLS in MPLS Configuration Guide
• Deleting an aggregate interface also deletes its aggregation group and causes all member ports to
leave the aggregation group.
• You must configure the same aggregation mode on the two ends of an aggregate link.
9
Configuring a Layer 3 static aggregation group
For a successful static aggregation, make sure the ports at both ends of each link are in the same
aggregation state.
To configure a Layer 3 static aggregation group:
Step Command Remarks

1. Enter system view. system-view N/A
When you create a Layer 3

2. Create a Layer 3 aggregate aggregate interface, the system
interface route-aggregation
interface and enter Layer 3 automatically creates a Layer 3
interface-number
aggregate interface view. static aggregation group
numbered the same.
3. Exit to system view. quit N/A
a. Enter Layer 3 Ethernet

interface view:
interface interface-type
interface-number Repeat these two substeps to
4. Assign an interface to the
assign more Layer 3 Ethernet
specified Layer 3 aggregation b. Assign the interface to the
interfaces to the aggregation
group. specified Layer 3
group.
aggregation group:
port link-aggregation
group number
Configuring a Layer 3 dynamic aggregation group

For a successful dynamic aggregation, make sure the peer ports of the ports aggregated at one end are
also aggregated. The two ends can automatically negotiate the aggregation state of each member port.
To configure a Layer 3 dynamic aggregation group:

By default, the system LACP priority

is 32768.
2. Set the system LACP priority. lacp system-priority system-priority Changing the system LACP priority
might affect the aggregation states
of the ports in the dynamic
aggregation group.
When you create a Layer 3

3. Create a Layer 3 aggregate aggregate interface, the system
interface and enter Layer 3 automatically creates a Layer 3
interface-number
aggregate interface view. static aggregation group
numbered the same.
4. Configure the aggregation
By default, an aggregation group
group to operate in dynamic link-aggregation mode dynamic
operates in static mode.
mode.
10
5. Exit to system view. quit N/A
a. Enter Layer 3 Ethernet
interface view:
interface-number Repeat these two substeps to
6. Assign an interface to the
assign more Layer 3 Ethernet
specified Layer 3 aggregation b. Assign the interface to the
interfaces to the aggregation
group. specified Layer 3
group.
aggregation group:
port link-aggregation
group number
• Set the LACP operating mode
to passive:
7. Set the LACP operating mode lacp mode passive By default, LACP is operating in
for the interface. • Set the LACP operating mode active mode.
to active:
undo lacp mode
8. Set the port priority for the link-aggregation port-priority

The default setting is 32768.
interface. port-priority
By default, the long LACP timeout

interval (90 seconds) is used by the
interface.
9. Set the short LACP timeout To avoid traffic interruption during
interval (3 seconds) for the lacp period short an ISSU, do not set the short LACP
interface. timeout interval before performing
the ISSU. For more information
about ISSU, see Fundamentals
Configuration Guide.
Configuring an aggregate interface

Most configurations that can be made on Layer 3 Ethernet interfaces can also be made on Layer 3
aggregate interfaces.
Setting the description for an aggregate interface

You can set the description for an aggregate interface for administration purposes, for example,
describing the purpose of the interface.
To set the description of an aggregate interface:

11
2. Enter Layer 3 aggregate interface route-aggregation

interface or subinterface { interface-number | N/A
view. interface-number.subnumber }
3. Set the description of the

By default, the description of an
aggregate interface or description text
interface is interface-name Interface.
subinterface.
Setting the MAC address for an aggregate interface

Typically, all aggregate interfaces on a device use the same MAC address, and aggregate interfaces on
different devices use different MAC addresses. However, you must set different MAC addresses for
aggregate interfaces on a device in some situations.
To set the MAC address for an aggregate interface:

2. Enter Layer 3 aggregate
{ interface-number | N/A
interface or subinterface view.
interface-number.subnumber }
The default MAC address of an

3. Set the MAC address for the
mac-address mac-address aggregate interface is the bridge
aggregate interface.
MAC address of the device.
Setting the MTU for a Layer 3 aggregate interface

The MTU of an interface affects IP packets fragmentation and reassembly on the interface.
To set the MTU for a Layer 3 aggregate interface:

3. Set the MTU for the Layer 3
aggregate interface or mtu size The default setting is 1500 bytes.
subinterface.
12
Setting the minimum and maximum numbers of Selected ports
for an aggregation group
IMPORTANT:
The minimum and maximum numbers of Selected ports must be the same for the local and peer
aggregation groups.
The bandwidth of an aggregate link increases as the number of Selected member ports increases. To
avoid congestion, you can set the minimum number of Selected ports required for bringing up an
This minimum threshold setting affects the aggregation states of aggregation member ports and the state
of the aggregate interface.
• When the number of member ports eligible to be Selected ports is smaller than the minimum
threshold, the following events occur:
{ The eligible member ports are placed in Unselected state.
{ The link layer state of the aggregate interface becomes down.
• When the number of member ports eligible to be Selected ports reaches or exceeds the minimum
threshold, the following events occur:
{ The eligible member ports are placed in Selected state.
{ The link layer state of the aggregate interface becomes up.
You can implement backup between two ports by performing the following tasks:
• Assigning two ports to an aggregation group.
• Setting the maximum number of Selected ports to 1 for the aggregation group.
Then, only one Selected port is allowed in the aggregation group, and the Unselected port acts as a
backup port.
To set the minimum and maximum numbers of Selected ports for an aggregation group:


N/A
interface view. interface-number
3. Set the minimum number of By default, the minimum number of

link-aggregation selected-port
Selected ports for the Selected ports is not specified for
minimum number
aggregation group. an aggregation group.
4. Set the maximum number of By default, the maximum number of
link-aggregation selected-port
Selected ports for the Selected ports is not specified for
maximum number
aggregation group. an aggregation group.
13
Setting the expected bandwidth for an aggregate interface
To set the expected bandwidth for an aggregate interface:

By default, the expected

3. Set the expected bandwidth
bandwidth bandwidth-value bandwidth (in kbps) is the interface
for the interface.
baud rate divided by 1000.
Configuring an edge aggregate interface

When you configure an edge aggregate interface, follow these restrictions and guidelines:
• This configuration takes effect only on the aggregate interface corresponding to a dynamic
aggregation group.
• Link-aggregation traffic redirection does not operate correctly on an edge aggregate interface. For
more information about link-aggregation traffic redirection, see "Enabling link-aggregation traffic
redirection."
To configure an edge aggregate interface:


N/A
3. Configure the aggregate By default, an aggregate interface

interface as an edge lacp edge-port does not operate as an edge
aggregate interface. aggregate interface.
Shutting down an aggregate interface

Shutting down or bringing up an aggregate interface affects the aggregation states and link states of
member ports in the corresponding aggregation group as follows:
• When an aggregate interface is shut down, all Selected ports in the corresponding aggregation
group become Unselected ports and all member ports go down.
• When an aggregate interface is brought up, the aggregation states of member ports in the
corresponding aggregation group are recalculated.
The loopback command cannot be configured on the member port of a shut down aggregate interface.
A port configured with the loopback command cannot be assigned to a shut down aggregate interface.
For more information about the loopback command, see Interface Command Reference.
14
To shut down an aggregate interface:

3. Shut down the aggregate By default, a Layer 3 aggregate

shutdown
interface or subinterface. interface or subinterface is up.
Restoring the default settings for an aggregate interface

You can restore all configurations on an aggregate interface to the default settings.
To restore the default settings for an aggregate interface:
Step Command
1. Enter system view. system-view
2. Enter Layer 3 aggregate interface or interface route-aggregation { interface-number |

subinterface view. interface-number.subnumber }
3. Restore the default settings for the

default
Setting load sharing modes for link aggregation

groups
You can set the global or group-specific load sharing mode. A link aggregation group preferentially uses
the group-specific load sharing mode. If the group-specific load sharing mode is not available, the group
uses the global load sharing mode.
Setting the global link-aggregation load sharing mode

15
link-aggregation global load-sharing
mode { { destination-ip |
By default, the global load sharing
2. Set the global destination-mac | destination-port |
mode load shares packets
link-aggregation load ingress-port | ip-protocol | mpls-label1
automatically based on packet
sharing mode. | mpls-label2 | mpls-label3 | source-ip
types.
| source-mac | source-port | vlan-id } *
| flexible }
Setting the group-specific load sharing mode


N/A
link-aggregation load-sharing mode

{ { destination-ip | destination-mac |
By default, an aggregation group
destination-port | ingress-port |
3. Set the load sharing mode load shares packets
ip-protocol | mpls-label1 |
for the aggregation group. automatically based on packet
mpls-label2 | mpls-label3 | source-ip
types.
| source-mac | source-port | vlan-id }
* | flexible }
Enabling link-aggregation traffic redirection

Link-aggregation traffic redirection prevents traffic interruption.
When you shut down a Selected port in an aggregation group, this feature redirects traffic of the
Selected port to other Selected ports. (In standalone mode.)
When you restart an IRF member device that contains Selected ports, this feature redirects traffic of the
IRF member device to other IRF member devices. (In IRF mode.)
Configuration restrictions and guidelines

When you enable link-aggregation traffic redirection, follow these restrictions and guidelines:
• Link-aggregation traffic redirection applies only to dynamic link aggregation groups.
• To prevent traffic interruption, enable link-aggregation traffic redirection on devices at both ends of
the aggregate link.
• Link-aggregation traffic redirection does not operate correctly on an edge aggregate interface.
16
Configuration procedure
To enable link-aggregation traffic redirection:

2. Enable link-aggregation traffic link-aggregation lacp By default, link-aggregation traffic
redirection. traffic-redirect-notification enable redirection is disabled.
Displaying and maintaining Ethernet link

aggregation
Execute display commands in any view and reset commands in user view.
Task Command
Display information for an aggregate interface display interface [ route-aggregation [ interface-number ] ]
or multiple aggregate interfaces. [ brief [ description | down ] ]
Display the local system ID. display lacp system-id
Display the global or group-specific display link-aggregation load-sharing mode [ interface

link-aggregation load sharing modes. [ route-aggregation interface-number ] ]
Display detailed link aggregation information

display link-aggregation member-port [ interface-list ]
for link aggregation member ports.
Display summary information about all

display link-aggregation summary
aggregation groups.
Display detailed information about the specified display link-aggregation verbose [ route-aggregation
aggregation groups. [ interface-number ] ]
Clear LACP statistics for the specified link

reset lacp statistics [ interface interface-list ]
aggregation member ports.
Clear statistics for the specified aggregate reset counters interface [ route-aggregation
interfaces. [ interface-number ] ]
Ethernet link aggregation configuration examples

Layer 3 static aggregation configuration example
Network requirements
On the network shown in Figure 4, perform the following tasks:
• Configure a Layer 3 static aggregation group on both Device A and Device B.
• Configure IP addresses and subnet masks for the corresponding Layer 3 aggregate interfaces.
17
Figure 4 Network diagram
GE1/0/1 GE1/0/1
GE1/0/2 GE1/0/2
Link aggregation 1
GE1/0/3 GE1/0/3
Device A RAGG1 RAGG1 Device B

192.168.1.1/24 192.168.1.2/24
1. Configure Device A:
# Create Layer 3 aggregate interface Route-Aggregation 1, and configure an IP address and
subnet mask for the aggregate interface.
<DeviceA> system-view
[DeviceA] interface route-aggregation 1
[DeviceA-Route-Aggregation1] ip address 192.168.1.1 24
[DeviceA-Route-Aggregation1] quit
# Assign Layer 3 Ethernet interfaces GigabitEthernet 1/0/1 through GigabitEthernet 1/0/3 to
aggregation group 1.
[DeviceA] interface gigabitethernet 1/0/1
[DeviceA-GigabitEthernet1/0/1] port link-aggregation group 1
[DeviceA-GigabitEthernet1/0/1] quit
2. Configure Device B in the same way Device A is configured. (Details not shown.)
Verifying the configuration

# Display detailed information about all aggregation groups on Device A.
[DeviceA] display link-aggregation verbose
Loadsharing Type: Shar -- Loadsharing, NonS -- Non-Loadsharing
Port Status: S -- Selected, U -- Unselected, I -- Individual
Flags: A -- LACP_Activity, B -- LACP_Timeout, C -- Aggregation,
D -- Synchronization, E -- Collecting, F -- Distributing,
G -- Defaulted, H -- Expired
Aggregate Interface: Route-Aggregation1

Aggregation Mode: Static
Loadsharing Type: NonS
Port Status Priority Oper-Key
--------------------------------------------------------------------------------
GE1/0/1 S 32768 1
GE1/0/2 S 32768 1
GE1/0/3 S 32768 1
The output shows that link aggregation group 1 is a Layer 3 static aggregation group that contains three
Selected ports.
18
Layer 3 dynamic aggregation configuration example
• Configure a Layer 3 dynamic aggregation group on both Device A and Device B.
GE1/0/1 GE1/0/1
GE1/0/2 GE1/0/2
Link aggregation 1
GE1/0/3 GE1/0/3
Device A RAGG1 RAGG1 Device B

192.168.1.1/24 192.168.1.2/24
# Create Layer 3 aggregate interface Route-Aggregation 1.
# Configure the link aggregation mode as dynamic.
[DeviceA-Route-Aggregation1] link-aggregation mode dynamic
# Configure an IP address and subnet mask for Route-Aggregation 1.
# Assign Layer 3 Ethernet interfaces GigabitEthernet 1/0/1 through GigabitEthernet 1/0/3 to

19
Aggregation Mode: Dynamic
System ID: 0x8000, 000f-e267-6c6a
Local:
Port Status Priority Oper-Key Flag
--------------------------------------------------------------------------------
GE1/0/1 S 32768 1 {ACDEF}
GE1/0/2 S 32768 1 {ACDEF}
GE1/0/3 S 32768 1 {ACDEF}
Remote:
Actor Partner Priority Oper-Key SystemID Flag
--------------------------------------------------------------------------------
GE1/0/1 1 32768 1 0x8000, 000f-e267-57ad {ACDEF}
GE1/0/2 2 32768 1 0x8000, 000f-e267-57ad {ACDEF}
GE1/0/3 3 32768 1 0x8000, 000f-e267-57ad {ACDEF}
The output shows that link aggregation group 1 is a Layer 3 dynamic aggregation group that contains
three Selected ports.
Layer 3 aggregation load sharing configuration example

• Configure Layer 3 static aggregation groups 1 and 2 on Device A and Device B, respectively.
• Configure link aggregation group 1 to load share packets based on source IP addresses.
• Configure link aggregation group 2 to load share packets based on destination IP addresses.
# Configure Layer 3 aggregation group 1 to load share packets based on source IP addresses.
[DeviceA-Route-Aggregation1] link-aggregation load-sharing mode source-ip
# Configure an IP address and subnet mask for Layer 3 aggregate interface Route-Aggregation 1.
20
# Assign Layer 3 Ethernet interfaces GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2 to
# Configure Layer 3 aggregation group 2 to load share packets based on destination IP
addresses.
[DeviceA-Route-Aggregation2] link-aggregation load-sharing mode destination-ip
# Assign Layer 3 Ethernet interfaces GigabitEthernet 1/0/3 and GigabitEthernet 1/0/4 to


Loadsharing Type: Shar
--------------------------------------------------------------------------------
GE1/0/1 S 32768 1
GE1/0/2 S 32768 1

Loadsharing Type: Shar
--------------------------------------------------------------------------------
21
GE1/0/3 S 32768 2
GE1/0/4 S 32768 2
The output shows that:

• Link aggregation groups 1 and 2 are both load-shared Layer 3 static aggregation groups.
• Each aggregation group contains two Selected ports.
# Display all the group-specific load sharing modes on Device A.
[DeviceA] display link-aggregation load-sharing mode interface
Route-Aggregation1 Load-Sharing Mode:

source-ip address
Route-Aggregation2 Load-Sharing Mode:

destination-ip address
The output shows that:

• Link aggregation group 1 load shares packets based on source IP addresses.
• Link aggregation group 2 load shares packets based on destination IP addresses.
Layer 3 edge aggregate interface configuration example

As shown in Figure 7, a Layer 3 dynamic aggregation group is configured on the device. The server is not
configured with dynamic link aggregation.
Configure an edge aggregate interface so that both GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2
can forward traffic to improve link reliability.
# Create Layer 3 aggregate interface Route-Aggregation 1, and set the link aggregation mode to
dynamic.
<Device> system-view
[Device] interface route-aggregation 1
[Device-Route-Aggregation1] link-aggregation mode dynamic
[Device-Route-Aggregation1] ip address 192.168.1.1 24
# Configure Layer 3 aggregate interface Route-Aggregation 1 as an edge aggregate interface.

[Device-Route-Aggregation1] lacp edge-port
[Device-Route-Aggregation1] quit
# Assign Layer 3 Ethernet interfaces GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2 to aggregation
group 1.
22
[Device] interface gigabitethernet 1/0/1
[Device-GigabitEthernet1/0/1] port link-aggregation group 1
[Device-GigabitEthernet1/0/1] quit
[Device-GigabitEthernet1/0/2] port link-aggregation group 1
[Device-GigabitEthernet1/0/2] quit

# Display detailed information about all aggregation groups on the device when the server is not
configured with dynamic link aggregation.
[Device] display link-aggregation verbose

Aggregation Mode: Dynamic
System ID: 0x8000, 000f-e267-6c6a
Local:
Port Status Priority Oper-Key Flag
--------------------------------------------------------------------------------
GE1/0/1 I 32768 1 {AG}
GE1/0/2 I 32768 1 {AG}
Remote:
Actor Partner Priority Oper-Key SystemID Flag
--------------------------------------------------------------------------------
GE1/0/1 0 32768 0 0x8000, 0000-0000-0000 {DEF}
GE1/0/2 0 32768 0 0x8000, 0000-0000-0000 {DEF}
The output shows that GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2 are in Individual state when
they do not receive LACPDUs from the server. Both GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2
can forward traffic. When one port fails, its traffic is automatically switched to the other port.
23
Configuring VLANs
Overview
Ethernet is a family of shared-media LAN technologies based on the CSMA/CD mechanism. An Ethernet
LAN is both a collision domain and a broadcast domain. Because the medium is shared, collisions and
broadcasts are common in an Ethernet LAN. Typically, bridges and Layer 2 switches can reduce
collisions in an Ethernet LAN. To confine broadcasts, a Layer 2 switch must use the Virtual Local Area
Network (VLAN) technology.
VLANs enable a Layer 2 switch to break a LAN down into smaller broadcast domains, as shown
in Figure 8.
Figure 8 A VLAN diagram
VLAN 2
Switch A Switch B
Router
VLAN 5
A VLAN is logically divided on an organizational basis rather than on a physical basis. For example, you
can assign all workstations and servers used by a particular workgroup to the same VLAN, regardless of
their physical locations. Hosts in the same VLAN can directly communicate with one another. You need
a router or a Layer 3 switch for hosts in different VLANs to communicate with one another.
All these VLAN features reduce bandwidth waste, improve LAN security, and enable flexible virtual
group creation.
VLAN frame encapsulation

To identify Ethernet frames from different VLANs, IEEE 802.1Q inserts a four-byte VLAN tag between the
destination and source MAC address (DA&SA) field and the Type field.
Figure 9 VLAN tag placement and format
24
A VLAN tag includes the following fields:
• TPID—16-bit tag protocol identifier that indicates whether a frame is VLAN-tagged. By default, the
TPID value 0x8100 identifies a VLAN-tagged frame. A device vendor can set the TPID to a different
value. For compatibility with a neighbor device, set the TPID value on the device to be the same as
the neighbor device.
• Priority—3-bit long, identifies the 802.1p priority of the frame. For more information, see ACL and
QoS Configuration Guide.
• CFI—1-bit long canonical format indicator that indicates whether the MAC addresses are
encapsulated in the standard format when packets are transmitted across different media.
Available values include:
{ 0 (default)—The MAC addresses are encapsulated in the standard format.
{ 1—The MAC addresses are encapsulated in a non-standard format.
This field is always set to 0 for Ethernet.
• VLAN ID—12-bit long, identifies the VLAN to which the frame belongs. The VLAN ID range is 0 to
4095. VLAN IDs 0 and 4095 are reserved, and VLAN IDs 1 to 4094 are user configurable.
The way a network device handles an incoming frame depends on whether the frame has a VLAN tag
and the value of the VLAN tag (if any). For more information, see "Introduction."
Ethernet supports encapsulation formats Ethernet II, 802.3/802.2 LLC, 802.3/802.2 SNAP, and 802.3
raw. The Ethernet II encapsulation format is used here. For information about the VLAN tag fields in other
frame encapsulation formats, see related protocols and standards.
For a frame that has multiple VLAN tags, the device handles it according to its outermost VLAN tag and
transmits its inner VLAN tags as the payload.
Protocols and standards

IEEE 802.1Q, IEEE Standard for Local and Metropolitan Area Networks: Virtual Bridged Local Area
Networks
Configuring basic VLAN settings

2. (Optional.) Create a
By default, only the system default VLAN
VLAN and enter its view, vlan vlan-id1 [ to vlan-id2 ]
(VLAN 1) exists.
or create a list of VLANs.
To configure a VLAN after you create a list

3. Enter VLAN view. vlan vlan-id
of VLANs, you must perform this step.
By default, the name of a VLAN is VLAN

vlan-id. The vlan-id argument specifies the
4. Configure a name for VLAN ID in a four-digit format. If the VLAN
name text
the VLAN. ID has fewer than four digits, leading zeros
are added. For example, the name of
VLAN 100 is VLAN 0100.
25
By default, the description of a VLAN is
VLAN vlan-id. The vlan-id argument
specifies the VLAN ID in a four-digit format.
5. Configure the
description text If the VLAN ID has fewer than four digits,
description of the VLAN.
leading zeros are added. For example, the
default description of VLAN 100 is VLAN
0100.
NOTE:
• As the system default VLAN, VLAN 1 cannot be created or deleted.
• Before you delete a dynamic VLAN or a VLAN locked by an application, you must first remove the
configuration from the VLAN.
Configuring port-based VLANs

Introduction
Port-based VLANs group VLAN members by port. A port forwards packets from a VLAN only after it is
assigned to the VLAN.
Port link type

You can set the link type of a port to access, trunk, or hybrid. The link types use the following VLAN tag
handling methods:
• Access—An access port can forward packets only from one VLAN and send these packets
untagged. An access port is typically used in the following conditions:
{ Connecting to a terminal device that does not support VLAN packets.
{ In scenarios that do not distinguish VLANs.
• Trunk—A trunk port can forward packets from multiple VLANs. Except packets from the port VLAN
ID (PVID), packets sent out of a trunk port are VLAN-tagged. Ports connecting network devices are
typically configured as trunk ports.
• Hybrid—A hybrid port can forward packets from multiple VLANs. The tagging status of the packets
forwarded by a hybrid port depends on the port configuration.
PVID
The PVID identifies the port VLAN of a port.
When you configure the PVID on a port, follow these restrictions and guidelines:
• An access port can join only one VLAN. The VLAN to which the access port belongs is the PVID of
the port.
• A trunk or hybrid port supports multiple VLANs and the PVID configuration.
• When you use the undo vlan command to delete the PVID of a port, either of the following events
occurs depending on the port link type:
{ For an access port, the PVID of the port changes to VLAN 1.
{ For a hybrid or trunk port, the PVID setting of the port does not change.
26
You can use a nonexistent VLAN as the PVID for a hybrid or trunk port, but not for an access port.
• H3C recommends that you set the same PVID for a local port and its peer.
• To prevent a port from dropping untagged packets or PVID-tagged packets, assign the port to its
PVID.
How ports of different link types handle frames
Actions Access Trunk Hybrid

In the
inbound • If the PVID is permitted on the port, tags the frame with the
Tags the frame with the PVID tag.
direction for
PVID tag.
an untagged • If not, drops the frame.
frame
• Receives the frame
In the if its VLAN ID is the
inbound same as the PVID.
• Receives the frame if its VLAN is permitted on the port.
direction for • Drops the frame if
• Drops the frame if its VLAN is not permitted on the port.
a tagged its VLAN ID is
frame different from the
PVID.
• Removes the tag and sends
the frame if the frame
carries the PVID tag and
the port belongs to the Sends the frame if its VLAN is
In the PVID. permitted on the port. The
Removes the VLAN tag
outbound tagging status of the frame
and sends the frame. • Sends the frame without
direction depends on the port hybrid vlan
removing the tag if its
command configuration.
VLAN is carried on the
port but is different from
the PVID.
Assigning an access port to a VLAN

You can assign an access port to a VLAN in VLAN view or interface view.
Make sure the VLAN has been created.
Assign one or multiple access ports to a VLAN in VLAN view

2. Enter VLAN view. vlan vlan-id N/A
3. Assign one or multiple access By default, all ports belong to
port interface-list
ports to the VLAN. VLAN 1.
Assign an access port to a VLAN in interface view

27
2. Enter Layer 2 Ethernet
interface interface-type interface-number N/A
interface view.
3. Set the port link type to By default, all ports are access
port link-type access
access. ports.
4. (Optional.) Assign the By default, all access ports
port access vlan vlan-id
access port to a VLAN. belong to VLAN 1.
Assigning a trunk port to a VLAN

A trunk port supports multiple VLANs. You can assign it to a VLAN in interface view.
When you assign a trunk port to a VLAN, follow these restrictions and guidelines:
• To change the link type of a port from trunk to hybrid or vice versa, set the link type to access first.
• To enable a trunk port to transmit packets from its PVID, you must assign the trunk port to the PVID
by using the port trunk permit vlan command.
To assign a trunk port to one or multiple VLANs:

interface view.
3. Set the port link type to By default, all ports are
port link-type trunk
trunk. access ports.
4. Assign the trunk port to By default, a trunk port
port trunk permit vlan { vlan-id-list | all }
the specified VLANs. permits only VLAN 1.
5. (Optional.) Configure
the PVID of the trunk port trunk pvid vlan vlan-id The default setting is VLAN 1.
port.
Assigning a hybrid port to a VLAN

A hybrid port supports multiple VLANs. You can assign it to the specified VLANs in interface view. Make
sure the VLANs have been created.
When you assign a hybrid port to a VLAN, follow these restrictions and guidelines:
• To change the link type of a port from trunk to hybrid or vice versa, set the link type to access first.
• To enable a hybrid port to transmit packets from its PVID, you must assign the hybrid port to the PVID
by using the port hybrid vlan command.
To assign a hybrid port to one or multiple VLANs:

interface view.
28
3. Set the port link type to By default, all ports are
port link-type hybrid
hybrid. access ports.
By default, the hybrid port is

an untagged member of the
4. Assign the hybrid port to port hybrid vlan vlan-id-list { tagged |
VLAN to which the port
the specified VLANs. untagged }
belongs when its link type is
access.
By default, the PVID of a

5. (Optional.) Configure hybrid port is the ID of the
the PVID of the hybrid port hybrid pvid vlan vlan-id VLAN to which the port
port. belongs when its link type is
access.
Configuring a VLAN group

A VLAN group includes a set of VLANs.
A VLAN group name can represent a group of authorization VLANs to be assigned to users that pass
802.1X authentication.
When you configure a VLAN group on an AC, the AC assigns VLANs one by one in the VLAN group to
wireless clients. This VLAN assignment method prevents wireless clients from crowding into a single
VLAN.
To configure a VLAN group:

2. Create a VLAN group and
vlan-group group-name By default, no VLAN group exists.
enter VLAN group view.
By default, no VLAN exists in a

3. Add VLANs to the VLAN VLAN group.
vlan-list vlan-id-list
group. You can add multiple VLAN lists to
a VLAN group.
Displaying and maintaining VLANs

Execute display commands in any view and reset commands in user view.
Task Command
display vlan [ vlan-id1 [ to vlan-id2 ] | all | dynamic | reserved
Display VLAN information.
| static ]
Display brief VLAN information. display vlan brief
Display VLAN group information. display vlan-group [ group-name ]
29
Task Command
Display hybrid ports or trunk ports on the
display port { hybrid | trunk }
device.
VLAN configuration example

As shown in Figure 10:
• Host A and Host C belong to Department A. VLAN 100 is assigned to Department A.
• Host B and Host D belong to Department B. VLAN 200 is assigned to Department B.
Configure port-based VLANs so that only hosts in the same department can communicate with each
other.
# Create VLAN 100, and assign GigabitEthernet 1/0/1 to VLAN 100.
[DeviceA] vlan 100
[DeviceA-vlan100] port gigabitethernet 1/0/1
[DeviceA-vlan100] quit
# Create VLAN 200, and assign GigabitEthernet 1/0/2 to VLAN 200.
[DeviceA] vlan 200
[DeviceA-vlan200] port gigabitethernet 1/0/2
[DeviceA-vlan200] quit
# Configure GigabitEthernet 1/0/3 as a trunk port, and assign the port to VLANs 100 and 200.
[DeviceA-GigabitEthernet1/0/3] port link-type trunk
[DeviceA-GigabitEthernet1/0/3] port trunk permit vlan 100 200
Please wait... Done.
3. Configure hosts:
30
a. Configure Host A and Host C to be on the same IP subnet. For example, 192.168.100.0/24.
b. Configure Host B and Host D to be on the same IP subnet. For example, 192.168.200.0/24.

# Verify that Host A and Host C can ping each other, but they both fail to ping Host B and Host D. (Details
not shown.)
# Verify that Host B and Host D can ping each other, but they both fail to ping Host A and Host C. (Details
not shown.)
# Verify that VLANs 100 and 200 are correctly configured on Device A.
[DeviceA-GigabitEthernet1/0/3] display vlan 100
VLAN ID: 100
VLAN type: Static
Route interface: Not configured
Description: VLAN 0100
Name: VLAN 0100
Tagged ports:
GigabitEthernet1/0/3
Untagged ports:
[DeviceA-GigabitEthernet1/0/3] display vlan 200
VLAN ID: 200
VLAN type: Static
Route interface: Not configured
Description: VLAN 0200
Name: VLAN 0200
Tagged ports:
Untagged ports:
31
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 packet that has two or more 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

Types of packets to be terminated on Tagging status of outgoing
VLAN termination types
the interface packets on the interface
The packets must meet both of the following
requirements:
• The packets include one or more
Dot1q termination Single-tagged
layers of VLAN tags.
• The outermost VLAN tag matches the
configured value.
The packets must meet both of the following

requirements:
• The packets include two or more
QinQ termination Double-tagged
layers of VLAN tags.
• The outermost two layers of tags match
the configured values.
Untagged termination Untagged packets Untagged
Packets that cannot be processed on any

Default termination other subinterfaces of the same main Untagged
interface
32
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 communicate. To restrict communication to the specified VLANs, configure VLAN
termination on Layer 3 Ethernet subinterfaces or Layer 3 aggregate subinterfaces.
As shown in Figure 11, Host A and Host B are in different VLANs. The two hosts 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 11 VLAN termination for inter-VLAN communication
LAN-WAN communication
Typically, WAN protocols such as ATM, Frame Relay, and PPP do not recognize 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 Layer
3 Ethernet subinterfaces or Layer 3 aggregate subinterfaces.
As shown in Figure 12, 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 GigabitEthernet 1/0/1.
33
Figure 12 VLAN termination enables LAN-WAN communication
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 subinterface to transmit broadcasts and multicasts
(Optional.) Configuring the TPID for VLAN-tagged packets
When you configure VLAN termination, follow these restrictions and guidelines:
• A main interface cannot terminate VLAN-tagged packets. To terminate VLAN-tagged packets, you
can create subinterfaces for the main interface.
• Layer 3 Ethernet subinterfaces and Layer 3 aggregate subinterfaces can terminate the following
packets:
{ Packets whose outermost VLAN IDs match the configured values.
{ Packets whose outermost two layers of VLAN IDs match the configured values.
• 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 removed.
After you configure VLAN termination, the system finds an interface for a received 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.
34
• Subinterface configured with untagged termination.
• Subinterface configured with default termination.
• Main interface.
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

• Enter Layer 3 Ethernet
subinterface view:
interface-number.subnumber
• Enter Layer 3 aggregate
2. Enter interface view. subinterface view: N/A
• Enter L3VE subinterface view:
interface ve-l3vpn
3. Configure ambiguous Dot1q By default, Dot1q termination
vlan-type dot1q vid vlan-id-list [ loose ]
termination. is disabled on a subinterface.
Configuring unambiguous Dot1q termination

35
• Enter Layer 3 Ethernet subinterface
view:
interface ve-l3vpn
3. Configure unambiguous By default, Dot1q termination
vlan-type dot1q vid vlan-id [ loose ]
Dot1q termination. is disabled on a subinterface.
Configuring QinQ termination

QinQ termination allows only packets that include specific VLAN tags to pass through the subinterface.
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 receives a packet, it removes the outermost two layers of VLAN tags of the
packet.
When the subinterface 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 receives a packet, it removes the two layers of VLAN tags of the packet.
When the subinterface 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 by using this method, 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.
36
• Subinterfaces under different main interfaces can terminate VLAN-tagged packets with the same
Layer 1 and Layer 2 VLAN IDs.
• 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:

• Enter Layer 3 Ethernet subinterface view:
• Enter Layer 3 aggregate subinterface
view:
2. Enter interface view. N/A
interface ve-l3vpn
3. Configure ambiguous
By default, QinQ
QinQ termination by vlan-type dot1q vid vlan-id-list second-dot1q
termination is disabled on
specifying the outermost { vlan-id-list | any } [ loose ]
a subinterface.
two layers of VLAN IDs.
Configuring unambiguous QinQ termination

view:
interface ve-l3vpn
3. Configure unambiguous
QinQ termination by vlan-type dot1q vid vlan-id By default, QinQ termination
specifying the outermost two second-dot1q vlan-id [ loose ] is disabled on a subinterface.
layers of VLAN IDs.
37
Configuring untagged termination
view:
interface ve-l3vpn
By default, untagged
3. Configure untagged
vlan-type dot1q untagged termination is disabled on
termination.
a subinterface.
Configuring default termination

• Enter Layer 3 aggregate subinterface view:
interface ve-l3vpn interface-number.subnumber
By default, default
3. Configure default
vlan-type dot1q default termination is disabled on
termination.
a subinterface.
Enabling a VLAN termination-enabled subinterface

to transmit broadcasts and multicasts
This function enables ambiguous Dot1q or QinQ termination-enabled subinterfaces to transmit
broadcasts and multicasts.
To enable a VLAN termination-enabled subinterface to transmit broadcasts and multicasts:

38
view:
2. Enter interface view. view: N/A
interface ve-l3vpn
3. Enable the By default, an ambiguous Dot1q or
subinterface to transmit QinQ termination-enabled
vlan-termination broadcast enable
broadcasts and subinterface does not transmit
multicasts. broadcasts and multicasts.
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 following interfaces:
• Main interface of the Layer 3 Ethernet subinterface.
• Main interface of the Layer 3 aggregate subinterface.
• Main interface of the L3VPN access 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 TPID value in the outermost 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:

• Enter Layer 3 Ethernet interface view:
interface-number
• Enter Layer 3 aggregate interface
Configurations made in the
view:
2. Enter interface view. views take effect on all
subinterfaces.
interface-number
• Enter L3VE interface view:
interface ve-l3vpn
39
3. Set the TPID value in the
outermost VLAN tag of
dot1q ethernet-type hex-value The default setting is 0x8100.
packets received and sent
by the interface.
VLAN termination configuration examples

Unambiguous Dot1q termination configuration example
As shown in Figure 13, configure unambiguous Dot1q termination on subinterfaces of the device to
implement intra-VLAN and inter-VLAN communications between hosts.
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,
# On Host C, specify 3.3.3.3/8 and 3.0.0.1/8 as its IP address and gateway IP address,
# On Host D, specify 4.4.4.4/8 and 4.0.0.1/8 as its IP address and gateway IP address,
2. Configure Layer 2 Switch A:
# Create VLAN 10.
<L2_SwitchA> system-view
40
[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.
# 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] 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.
# Configure GigabitEthernet 2/0/1.10, and assign an IP address to this interface.
# Configure GigabitEthernet 2/0/1.20, and assign an IP address to this interface.

# Verify that Host A, Host B, Host C, and Host D can ping each other. (Details not shown.)
41
Ambiguous Dot1q termination configuration example
As shown in Figure 14, configure ambiguous Dot1q termination, so that hosts in different VLANs can
communicate with the server group.
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.)
# Create VLAN 11.
# Create VLAN 12.
# Create VLAN 13.
42
# Configure GigabitEthernet 1/0/7 as a trunk port, and assign the port to VLANs 11 through 13.
[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.
# 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
# Configure an IP address for 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.
# Specify 1.1.2.11/24 as the gateway IP address for the server group. (Details not shown.)

# 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
As shown in Figure 15, the router acts as a PPPoE server. Hosts in different VLANs access the Internet
through the PPPoE server.
Configure Dot1q termination so that hosts in different VLANs can access the Internet.
43
# 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 PPPoE configuration, see Layer 2—WAN Configuration Guide.
Unambiguous QinQ termination configuration example

• 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.
44
Router
L2 Switch B GE1/0/1 Service provider network
VLAN 100
GE1/0/2 GE1/0/1.10 GE1/0/2
QinQ enabled 1.1.1.11/24 1.1.2.11/24
L2 Switch A GE1/0/1
L2 Switch C
GE1/0/2
VLAN 11
Host A Host B
1.1.1.1/24 1.1.2.1/24
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,
# On Host B, specify 1.1.2.1/24 and 1.1.2.11/24 as its IP address and gateway IP address,
# Create VLAN 11.
# Configure GigabitEthernet 1/0/1 as a trunk port, and assign the port to VLAN 11.
[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
45
[L2_SwitchB-GigabitEthernet1/0/2] quit
[L2_SwitchB-GigabitEthernet1/0/1] port trunk permit vlan 100
4. Configure the router:
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

# Verify that Host A and Host B can ping each other. (Details not shown.)
Ambiguous QinQ termination configuration example

As shown in Figure 17, 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.
GE1/0/1 Service provider network

L2 Switch B Router
VLAN 100
GE1/0/2 GE1/0/1.10 GE1/0/2
QinQ enabled 1.1.1.11/24 1.1.2.11/24
GE1/0/7
L2 Switch A L2 Switch C
GE1/0/1 GE1/0/3
GE1/0/2
VLAN 11 VLAN 12 VLAN 13

Server group
Host A Host B Host C

1.1.1.1/24 1.1.1.2/24 1.1.1.3/24
46
In this example, Layer 2 Switch C uses the factory configuration.
1. Configure Host A, Host B, and Host C:
# Assign the 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.)
# Create VLAN 11.
# Create VLAN 12.
# Create VLAN 13.
# Configure GigabitEthernet 1/0/7 as a trunk port, and assign the port to VLANs 11 through 13.
[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-GigabitEthernet1/0/2] port trunk permit vlan 11 to 13 100
[L2_SwitchB-GigabitEthernet1/0/2] port trunk pvid vlan 100
[L2_SwitchB-GigabitEthernet1/0/2] qinq enable
[L2_SwitchB-GigabitEthernet1/0/2] quit
[L2_SwitchB-GigabitEthernet1/0/1] port trunk permit vlan 100
4. Configure the router:
47
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
# Configure GigabitEthernet 1/0/1.10 to terminate VLAN-tagged packets whose Layer 1 VLAN
ID is 100 and Layer 2 VLAN ID is 11, 12, or 13.
[Router-GigabitEthernet1/0/1.10] vlan-type dot1q vid 100 second-dot1q 11 to 13
[Router-GigabitEthernet1/0/1.10] quit
[Router] interface gigabitethernet 1/0/2
[Router-GigabitEthernet1/0/2] ip address 1.1.2.11 255.255.255.0
5. Configure the server group:
# Assign each device in the server group an IP address on the network segment 1.1.2.0/24.
# Specify 1.1.2.11/24 as the gateway IP address for the server group. (Details not shown.)

# Verify that Host A, Host B, and Host C can ping the server group. (Details not shown.)
Configuration example for QinQ termination supporting PPPoE

server
• QinQ is enabled on GigabitEthernet 1/0/2 of Layer 2 Switch B.
• The router acts as a PPPoE server. Hosts in different VLANs access the Internet through the PPPoE
server.
Configure QinQ termination, so that the hosts can access the Internet.
48
L2 Switch B Router
GE1/0/1 Ser2/1/0
Service provider network WAN
VLAN 100
GE1/0/2 GE1/0/1.10
QinQ enabled 1.1.1.11/24
PPPoE server enabled
L2 Switch A GE1/0/7
GE1/0/1 GE1/0/3
GE1/0/2
VLAN 11 VLAN 12 VLAN 13
Host A Host B Host C

1.1.1.1/24 1.1.1.2/24 1.1.1.3/24
# Configure VLANs and QinQ termination. For the configuration procedure, see "Ambiguous QinQ
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 PPPoE configuration, see Layer 2—WAN Configuration Guide.
Configuration example for QinQ termination supporting DHCP

relay
• Provider A and Provider B are edge devices on the service provider network.
• DHCP client A and DHCP client B are devices on the customer networks.
• Provider A is the DHCP relay agent. Provider B is the DHCP server.
• Provider A and Provider B communicate with each other through Layer 3 interfaces.
Configure QinQ termination on Provider A so that DHCP client A and DHCP client B can obtain IP
settings from Provider B.
49
1. Configure the DHCP relay agent Provider A:
# Enable DHCP service.
<ProviderA> system-view
[ProviderA] dhcp enable
# Create a Layer 3 Ethernet subinterface GigabitEthernet 1/0/1.100.
[ProviderA] interface gigabitethernet 1/0/1.100
# Configure GigabitEthernet 1/0/1.100 to terminate packets whose Layer 1 VLAN ID is 100 and
Layer 2 VLAN ID is 10 or 20.
[ProviderA-GigabitEthernet1/0/1.100] vlan-type dot1q vid 100 second-dot1q 10 20
# Enable GigabitEthernet 1/0/1.100 to transmit broadcast and multicast packets.
[ProviderA-GigabitEthernet1/0/1.100] vlan-termination broadcast enable
# Enable DHCP relay on GigabitEthernet 1/0/1.100 and specify 10.2.1.1 as the DHCP server
address.
[ProviderA-GigabitEthernet1/0/1.100] dhcp select relay
[ProviderA-GigabitEthernet1/0/1.100] dhcp relay server-address 10.2.1.1
# Assign an IP address to GigabitEthernet 1/0/1.100.
[ProviderA-GigabitEthernet1/0/1.100] ip address 192.168.1.1 24
[ProviderA-GigabitEthernet1/0/1.100] quit
# Enable recording of relay entries on the relay agent.
[ProviderA] dhcp relay client-information record
50
[ProviderA] interface gigabitethernet 1/0/2
[ProviderA-GigabitEthernet1/0/2] ip address 10.1.1.1 24
[ProviderA-GigabitEthernet1/0/2] quit
# Configure a static route to the DHCP server.
[ProviderA] ip route-static 10.2.1.1 24 10.1.1.1
2. Configure the DHCP server Provider B:
# Assign an IP address to the DHCP server.
<ProviderB> system-view
[ProviderB] interface gigabitethernet 1/0/2
[ProviderB-GigabitEthernet1/0/2] ip address 10.2.1.1 24
[ProviderB-GigabitEthernet1/0/2] quit
# Enable DHCP.
[ProviderB] dhcp enable
# Configure an IP address pool on the DHCP server.
[ProviderB] dhcp server ip-pool 1
[ProviderB-dhcp-pool-1] network 192.168.1.0 24
[ProviderB-dhcp-pool-1] gateway-list 192.168.1.1
[ProviderB-dhcp-pool-1] quit
# Configure a static route to GigabitEthernet 1/0/1.100.
[ProviderB] ip route-static 192.168.1.1 24 10.1.1.1
3. Configure Switch A:
# Configure the uplink port GigabitEthernet 1/0/1 as a trunk port, and assign the port to VLAN
100.
<SwitchA> system-view
[SwitchA] interface gigabitethernet 1/0/1
[SwitchA-GigabitEthernet1/0/1] port link-type trunk
[SwitchA-GigabitEthernet1/0/1] port trunk permit vlan 100
[SwitchA-GigabitEthernet1/0/1] quit
# Configure the downlink port GigabitEthernet 1/0/2 as a trunk port, and assign the port to
VLANs 10 and 100.
[SwitchA-GigabitEthernet1/0/2] port trunk permit vlan 10 100
[SwitchA-GigabitEthernet1/0/2] port trunk pvid vlan 100
# Enable QinQ on GigabitEthernet1/0/2.
[SwitchA-GigabitEthernet1/0/2] qinq enable
# Configure the downlink port GigabitEthernet 1/0/3 as a trunk port, and assign the port to
VLANs 20 and 100.
[SwitchA-GigabitEthernet1/0/3] port trunk permit vlan 20 100
[SwitchA-GigabitEthernet1/0/3] port trunk pvid vlan 100
51
[SwitchA-GigabitEthernet1/0/3] qinq enable
# Assign GigabitEthernet 1/0/2 and GigabitEthernet 1/0/3 to VLAN 100.
[SwitchA] vlan 100
[SwitchA-vlan100] port gigabitethernet 1/0/2
[SwitchA-vlan100] port gigabitethernet 1/0/3
4. Configure Switch B:
# Create VLAN 10.
<SwitchB> system-view
[SwitchB] vlan 10
[SwitchB-vlan10] port gigabitethernet 1/0/2
[SwitchB-vlan10] quit
[SwitchB] interface gigabitethernet 1/0/1
[SwitchB-GigabitEthernet1/0/1] port link-type trunk
[SwitchB-GigabitEthernet1/0/1] port trunk permit vlan 10
5. Configure Switch C:
# Create VLAN 20.
<SwitchC> system-view
[SwitchC] vlan 20
[SwitchC-vlan20] port gigabitethernet 1/0/2
[SwitchC-vlan20] quit
[SwitchC] interface gigabitethernet 1/0/1
[SwitchC-GigabitEthernet1/0/1] port link-type trunk
[SwitchC-GigabitEthernet1/0/1] port trunk permit vlan 20

# Verify that DHCP client A and DHCP client B can obtain IP settings from Provider B. (Details not shown.)
52
Configuring LLDP
Overview
In a heterogeneous network, a standard configuration exchange platform ensures that different types of
network devices from different vendors can discover one another and exchange configuration.
The Link Layer Discovery Protocol (LLDP) is specified in IEEE 802.1AB. The protocol operates on the data
link layer to exchange device information between directly connected devices. With LLDP, a device sends
local device information as TLV (type, length, and value) triplets in LLDP Data Units (LLDPDUs) to the
directly connected devices. Local device information includes its system capabilities, management IP
address, device ID, port ID, and so on. The device stores the device information in LLDPDUs from the LLDP
neighbors in a standard MIB. For more information about MIBs, see Network Management and
Monitoring Configuration Guide. LLDP enables a network management system to quickly detect and
identify Layer 2 network topology changes.
Basic concepts
LLDP agent
An LLDP agent is a mapping of an entity where LLDP runs. Multiple LLDP agents can run on the same
interface.
LLDP agents are divided into the following types:
• Nearest bridge agent.
• Nearest customer bridge agent.
• Nearest non-TPMR bridge agent.
A Two-port MAC Relay (TPMR) is a type of bridge that has only two externally-accessible bridge ports.
It supports a subset of the features of a MAC bridge. A TPMR is transparent to all frame-based
media-independent protocols except for the following protocols:
• Protocols destined to it.
• Protocols destined to reserved MAC addresses that the relay feature of the TPMR is configured not
to forward.
LLDP exchanges packets between neighbor agents and creates and maintains neighbor information for
them. Figure 20 shows the neighbor relationships for these LLDP agents. LLDP has two bridge modes:
customer bridge (CB) and service bridge (SB).
53
Figure 20 LLDP neighbor relationships
LLDP frame formats

LLDP sends device information in LLDP frames. LLDP frames are encapsulated in Ethernet II or Subnetwork
Access Protocol (SNAP) frames.
• LLDP frame encapsulated in Ethernet II
Figure 21 Ethernet II-encapsulated LLDP frame
Table 5 Fields in an Ethernet II-encapsulated LLDP frame
Field Description
MAC address to which the LLDP frame is advertised. LLDP specifies
different multicast MAC addresses as destination MAC addresses for LLDP
frames destined for agents of different types. This helps distinguish
between LLDP frames sent and received by different agent types on the
same interface. The destination MAC address is fixed to one of the
following multicast MAC addresses:
Destination MAC address
• 0x0180-C200-000E for LLDP frames destined for nearest bridge
agents.
• 0x0180-C200-0000 for LLDP frames destined for nearest customer
bridge agents.
• 0x0180-C200-0003 for LLDP frames destined for nearest non-TPMR
bridge agents.
Source MAC address MAC address of the sending port.
Type Ethernet type for the upper-layer protocol. This field is 0x88CC for LLDP.
Data LLDPDU.
54
Field Description
Frame check sequence, a 32-bit CRC value used to determine the validity
FCS
of the received Ethernet frame.
• LLDP frame encapsulated in SNAP

Figure 22 SNAP-encapsulated LLDP frame
Table 6 Fields in a SNAP-encapsulated LLDP frame
Field Description
MAC address to which the LLDP frame is advertised. It is the same as that
Destination MAC address
for Ethernet II-encapsulated LLDP frames.
Source MAC address MAC address of the sending port.
SNAP type for the upper-layer protocol. This field is

Type
0xAAAA-0300-0000-88CC for LLDP.
Data LLDPDU.
Frame check sequence, a 32-bit CRC value used to determine the validity
FCS
of the received Ethernet frame.
LLDPDUs
LLDP uses LLDPDUs to exchange information. An LLDPDU comprises multiple TLVs. Each TLV carries a type
of device information, as shown in Figure 23.
Figure 23 LLDPDU encapsulation format
An LLDPDU can carry up to 32 types of TLVs. Mandatory TLVs include Chassis ID TLV, Port ID TLV, Time
to Live TLV, and End of LLDPDU TLV. Other TLVs are optional.
TLVs
A TLV is an information element that contains the type, length, and value fields.
LLDPDU TLVs include the following categories:
• Basic management TLVs
• Organizationally (IEEE 802.1 and IEEE 802.3) specific TLVs
55
• LLDP-MED (media endpoint discovery) TLVs
Basic management TLVs are essential to device management.
Organizationally specific TLVs and LLDP-MED TLVs are used for enhanced device management. They are
defined by standardization or other organizations and are optional for LLDPDUs.
• Basic management TLVs
Table 7 lists the basic management TLV types. Some of them are mandatory for LLDPDUs.
Table 7 Basic management TLVs
Type Description Remarks

Chassis ID Specifies the bridge MAC address of the sending device.
Specifies the ID of the sending port:

• If the LLDPDU carries LLDP-MED TLVs, the port ID TLV
Port ID
carries the MAC address of the sending port.
Mandatory.
• Otherwise, the port ID TLV carries the port name.
Specifies the life of the transmitted information on the

Time to Live
receiving device.
End of LLDPDU Marks the end of the TLV sequence in the LLDPDU.
Port Description Specifies the description for the sending port.
System Name Specifies the assigned name of the sending device.
System Description Specifies the description for the sending device.
Identifies the primary features of the sending device and the

System Capabilities Optional.
enabled primary features.
Specifies the following elements:

• The management address of the local device.
Management Address
• The interface number and object identifier (OID)
associated with the address.
• IEEE 802.1 organizationally specific TLVs

Table 8 IEEE 802.1 organizationally specific TLVs
Type Description
Port VLAN ID (PVID) Specifies the port VLAN identifier.
Port And Protocol VLAN ID Indicates whether the device supports protocol VLANs and, if so, what
(PPVID) VLAN IDs these protocols will be associated with.
VLAN Name Specifies the textual name of any VLAN to which the port belongs.
Protocol Identity Indicates protocols supported on the port.
DCBX Data center bridging exchange protocol.
EVB module Edge Virtual Bridging module, including EVB TLV and CDCP TLV.
Indicates whether the port supports link aggregation, and if yes, whether
Link Aggregation
link aggregation is enabled.
Management VID Management VLAN ID.
VID Usage Digest VLAN ID usage digest.
56
Type Description
ETS Configuration Enhanced Transmission Selection configuration.
ETS Recommendation ETS recommendation.
PFC Priority-based Flow Control.
APP Application protocol.
QCN Quantized Congestion Notification.
NOTE:
• H3C devices support only receiving protocol identity TLVs and VID usage digest TLVs.
• Layer 3 Ethernet ports support only link aggregation TLVs.
• IEEE 802.3 organizationally specific TLVs

Table 9 IEEE 802.3 organizationally specific TLVs
Type Description
Contains the bit-rate and duplex capabilities of the port, support
MAC/PHY Configuration/Status for autonegotiation, enabling status of autonegotiation, and the
current rate and duplex mode.
Contains the power supply capabilities of the port:

• Port class (PSE or PD).
• Power supply mode.
• Whether PSE power supply is supported.
• Whether PSE power supply is enabled.
Power Via MDI • Whether pair selection can be controlled.
• Power supply type.
• Power source.
• Power priority.
• PD requested power.
• PSE allocated power.
Indicates the supported maximum frame size. It is now the MTU of

Maximum Frame Size
the port.
Indicates the power state control configured on the sending port,

including the following:
Power Stateful Control • Power supply mode of the PSE/PD.
• PSE/PD priority.
• PSE/PD power.
Energy-Efficient Ethernet Indicates Energy Efficient Ethernet (EEE).
NOTE:
The Power Stateful Control TLV is defined in IEEE P802.3at D1.0 and is not supported in later
versions. H3C devices send this type of TLVs only after receiving them.
• LLDP-MED TLVs
LLDP-MED TLVs provide multiple advanced applications for voice over IP (VoIP), such as basic
configuration, network policy configuration, and address and directory management. LLDP-MED
57
TLVs provide a cost-effective and easy-to-use solution for deploying voice devices in Ethernet.
LLDP-MED TLVs are shown in Table 10.
Table 10 LLDP-MED TLVs
Type Description
Allows a network device to advertise the LLDP-MED TLVs that it
LLDP-MED Capabilities
supports.
Allows a network device or terminal device to advertise the VLAN

Network Policy ID of a port, the VLAN type, and the Layer 2 and Layer 3 priorities
for specific applications.
Allows a network device or terminal device to advertise power

Extended Power-via-MDI supply capability. This TLV is an extension of the Power Via MDI
TLV.
Hardware Revision Allows a terminal device to advertise its hardware version.
Firmware Revision Allows a terminal device to advertise its firmware version.
Software Revision Allows a terminal device to advertise its software version.
Serial Number Allows a terminal device to advertise its serial number.
Manufacturer Name Allows a terminal device to advertise its vendor name.
Model Name Allows a terminal device to advertise its model name.
Allows a terminal device to advertise its asset ID. The typical case
Asset ID is that the user specifies the asset ID for the endpoint to facilitate
directory management and asset tracking.
Allows a network device to advertise the appropriate location

Location Identification identifier information for a terminal device to use in the context of
location-based applications.
NOTE:
• If the MAC/PHY configuration/status TLV is not advertisable, none of the LLDP-MED TLVs will be
advertised even if they are advertisable.
• If the LLDP-MED capabilities TLV is not advertisable, the other LLDP-MED TLVs will not be advertised
even if they are advertisable.
Management address
The network management system uses the management address of a device to identify and manage the
device for topology maintenance and network management. The management address is encapsulated
in the management address TLV.
Working mechanism
LLDP operating modes
An LLDP agent can operate in one of the following modes:
• TxRx mode—An LLDP agent in this mode can send and receive LLDP frames.
• Tx mode—An LLDP agent in this mode can only send LLDP frames.
• Rx mode—An LLDP agent in this mode can only receive LLDP frames.
58
• Disable mode—An LLDP agent in this mode cannot send or receive LLDP frames.
Each time the LLDP operating mode of an LLDP agent changes, its LLDP protocol state machine
reinitializes. A configurable reinitialization delay prevents frequent initializations caused by frequent
changes to the operating mode. If you configure the reinitialization delay, an LLDP agent must wait the
specified amount of time to initialize LLDP after the LLDP operating mode changes.
Transmitting LLDP frames

An LLDP agent operating in TxRx mode or Tx mode sends LLDP frames to its directly connected devices
both periodically and when the local configuration changes. To prevent LLDP frames from overwhelming
the network during times of frequent changes to local device information, LLDP uses the token bucket
mechanism to rate limit LLDP frames. For more information about the token bucket mechanism, see ACL
and QoS Configuration Guide.
LLDP automatically enables the fast LLDP frame transmission mechanism in either of the following cases:
• A new LLDP frame is received and carries device information new to the local device.
• The LLDP operating mode of the LLDP agent changes from Disable or Rx to TxRx or Tx.
The fast LLDP frame transmission mechanism successively sends the specified number of LLDP frames at
a configurable fast LLDP frame transmission interval. The mechanism helps LLDP neighbors discover the
local device as soon as possible. Then, the normal LLDP frame transmission interval resumes.
Receiving LLDP frames

An LLDP agent operating in TxRx mode or Rx mode confirms the validity of TLVs carried in every received
LLDP frame. If the TLVs are valid, the LLDP agent saves the information and starts an aging timer. When
the TTL value in the Time To Live TLV carried in the LLDP frame becomes zero, the information ages out
immediately.
Protocols and standards

• IEEE 802.1AB-2005, Station and Media Access Control Connectivity Discovery
• IEEE 802.1AB-2009, Station and Media Access Control Connectivity Discovery
• ANSI/TIA-1057, Link Layer Discovery Protocol for Media Endpoint Devices
• DCB Capability Exchange Protocol Specification Rev 1.00
• DCB Capability Exchange Protocol Base Specification Rev 1.01
• IEEE Std 802.1Qaz-2011, Media Access Control (MAC) Bridges and Virtual Bridged Local Area
Networks-Amendment 18: Enhanced Transmission Selection for Bandwidth Sharing Between Traffic
Classes
59
LLDP configuration task list
Tasks at a glance
Performing basic LLDP configurations:

• (Required.) Enabling LLDP
• (Optional.) Setting the LLDP bridge mode
• (Optional.) Setting the LLDP operating mode
• (Optional.) Setting the LLDP reinitialization delay
• (Optional.) Enabling LLDP polling
• (Optional.) Configuring the advertisable TLVs
• (Optional.) Configuring the management address and its encoding format
• (Optional.) Setting other LLDP parameters
• (Optional.) Setting an encapsulation format for LLDP frames
(Optional.) Configuring LLDP trapping and LLDP-MED trapping
(Optional.) Setting the source MAC address of LLDP frames to the MAC address of the subinterface associated
with the specified VLAN
(Optional.) Enabling the system to issue the generated ARP entry to a Layer 3 Ethernet subinterface after a port
receives an LLDP frame
Performing basic LLDP configurations

Enabling LLDP
To make LLDP take effect on specific ports, you must enable LLDP both globally and on these ports.
To use LLDP together with OpenFlow, you must enable LLDP globally on OpenFlow switches. To prevent
LLDP from affecting topology discovery of OpenFlow controllers, H3C recommends that you disable LLDP
on ports of OpenFlow instances. For more information about OpenFlow, see OpenFlow Configuration
Guide.
To enable LLDP:

By default, LLDP is disabled

2. Enable LLDP globally. lldp global enable
globally.

interface view or Layer 3 interface interface-type interface-number N/A
aggregate interface view.
By default, LLDP is enabled

4. Enable LLDP. lldp enable
on a port.
60
Setting the LLDP bridge mode
The following LLDP bridge modes are available:
• Customer bridge mode—LLDP supports nearest bridge agents, nearest non-TPMR bridge agents,
and nearest customer bridge agents. LLDP processes the LLDP frames with destination MAC
addresses for these agents and transparently transmits the LLDP frames with other destination MAC
addresses in the VLAN.
• Service bridge mode—LLDP supports nearest bridge agents and nearest non-TPMR bridge agents.
LLDP processes the LLDP frames with destination MAC addresses for these agents and transparently
transmits the LLDP frames with other destination MAC addresses in the VLAN.
To set the LLDP bridge mode:

2. Set the LLDP bridge mode to By default, LLDP operates in
lldp mode service-bridge
service bridge. customer bridge mode.
Setting the LLDP operating mode

By default:
• The nearest bridge
agent operates in txrx
mode.
• The nearest customer
bridge agent and
• In Layer 3 Ethernet interface view: nearest non-TPMR
lldp [ agent { nearest-customer | bridge agent operate
nearest-nontpmr } ] admin-status in disable mode.
3. Set the LLDP operating { disable | rx | tx | txrx }
In Ethernet interface view, if
mode. • In Layer 3 aggregate interface view: you do not specify an agent
lldp agent { nearest-customer | type, the command sets the
nearest-nontpmr } admin-status operating mode for nearest
{ disable | rx | tx | txrx } bridge agents.
In aggregate interface
view, you can set the
operating mode only for
nearest customer bridge
agents and nearest
non-TPMR bridge agents.
61
Setting the LLDP reinitialization delay
When the LLDP operating mode changes on a port, the port initializes the protocol state machines after
an LLDP reinitialization delay. By adjusting the delay, you can avoid frequent initializations caused by
frequent changes to the LLDP operating mode on a port.
To set the LLDP reinitialization delay for ports:

2. Set the LLDP reinitialization
lldp timer reinit-delay delay The default setting is 2 seconds.
delay.
Enabling LLDP polling

With LLDP polling enabled, a device periodically searches for local configuration changes. When the
device detects a configuration change, it sends LLDP frames to inform neighboring devices of the change.
To enable LLDP polling:


• In Layer 3 Ethernet interface view:

lldp [ agent { nearest-customer |
nearest-nontpmr } ]
3. Enable LLDP polling and set check-change-interval interval By default, LLDP polling is
the polling interval. • In Layer 3 aggregate interface view: disabled.
lldp agent { nearest-customer |
nearest-nontpmr }
check-change-interval interval
Configuring the advertisable TLVs


62
By default:
• lldp tlv-enable { basic-tlv { all |
• Nearest bridge
port-description | system-capability |
agents can advertise
system-description | system-name |
all types of LLDP TLVs
management-address-tlv [ ip-address |
(only link
interface loopback interface-number ] }
aggregation TLV is
| dot1-tlv { all | link-aggregation } |
supported in 802.1
dot3-tlv { all | mac-physic |
organizationally
max-frame-size | power } | med-tlv { all
specific TLVs) except
| capability | inventory |
3. Configure the advertisable network policy TLVs.
power-over-ethernet | location-id
TLVs (in Layer 3 Ethernet • Nearest non-TPMR
{ civic-address device-type country-code
interface view). bridge agents
{ ca-type ca-value }&<1-10> |
elin-address tel-number } } } advertise no TLVs.
• lldp agent { nearest-nontpmr | • Nearest customer
nearest-customer } tlv-enable { basic-tlv bridge agents can
{ all | port-description | advertise basic TLVs
system-capability | system-description and IEEE 802.1
| system-name | organizationally
management-address-tlv [ ip-address ] } specific TLVs (only
| dot1-tlv { all | link-aggregation } } link aggregation TLV
is supported).
By default:
• Nearest non-TPMR
bridge agents
advertise no TLVs.
lldp agent { nearest-nontpmr |
4. Configure the advertisable • Nearest customer
nearest-customer } tlv-enable basic-tlv { all |
TLVs (in Layer 3 aggregate bridge agents can
management-address-tlv [ ip-address ] |
interface view). advertise only basic
port-description | system-capability |
TLVs.
system-description | system-name }
Nearest bridge agents
are not supported on
Layer 3 aggregate
interfaces.
Configuring the management address and its encoding format

LLDP encodes management addresses in numeric or string format in management address TLVs.
If a neighbor encodes its management address in string format, set the encoding format of the
management address to string on the connecting port. This guarantees normal communication with the
neighbor.
To configure a management address to be advertised and its encoding format on a port:

interface view or Layer 3 N/A
interface-number
63
• In Layer 3 Ethernet interface
view:
lldp [ agent
By default:
{ nearest-customer |
nearest-nontpmr } ] • Nearest bridge agents and
tlv-enable basic-tlv nearest customer bridge
3. Allow LLDP to advertise the
management-address-tlv agents can advertise the
management address in LLDP
[ ip-address ] management address in LLDP
frames and configure the
frames.
advertised management • In Layer 3 aggregate
address. interface view: • Nearest non-TPMR bridge
lldp agent { nearest-customer agents cannot advertise the
| nearest-nontpmr } management address in LLDP
tlv-enable basic-tlv frames.
management-address-tlv
[ ip-address ]
• In Layer 3 Ethernet interface
view:
lldp [ agent
{ nearest-customer |
nearest-nontpmr } ]
4. Set the encoding format of the management-address-forma By default, the encoding format of
management address to t string the management address is
string. • In Layer 3 aggregate numeric.
interface view:
lldp agent { nearest-customer
| nearest-nontpmr }
management-address-forma
t string
Setting other LLDP parameters

The Time to Live TLV carried in an LLDPDU determines how long the device information carried in the
LLDPDU can be saved on a recipient device.
By setting the TTL multiplier, you can configure the TTL of locally sent LLDPDUs. The TTL is expressed by
using the following formula:
TTL = Min (65535, (TTL multiplier × LLDP frame transmission interval + 1))
As the expression shows, the TTL can be up to 65535 seconds. TTLs greater than 65535 will be rounded
down to 65535 seconds.
To set LLDP parameters:

2. Set the TTL multiplier. lldp hold-multiplier value The default setting is 4.
3. Set the LLDP frame The default setting is 30
lldp timer tx-interval interval
transmission interval. seconds.
4. Set the token bucket size for
lldp max-credit credit-value The default setting is 5.
sending LLDP frames.
64
5. Set the number of LLDP frames
sent each time fast LLDP frame lldp fast-count count The default setting is 4.
transmission is triggered.
6. Set the fast LLDP frame
lldp timer fast-interval interval The default setting is 1 second.
transmission interval.
Setting an encapsulation format for LLDP frames

LLDP frames can be encapsulated in the following formats:
• Ethernet II—With Ethernet II encapsulation configured, an LLDP port sends LLDP frames in Ethernet
II frames.
• SNAP—With SNAP encapsulation configured, an LLDP port sends LLDP frames in SNAP frames.
Earlier versions of LLDP require the same encapsulation format on both ends to process LLDP frames. To
successfully communicate with a neighboring device running an earlier version of LLDP, the local device
must be set with the same encapsulation format.
To set the encapsulation format for LLDP frames to SNAP:

3. Set the encapsulation By default, Ethernet II
nearest-nontpmr } ] encapsulation snap
format for LLDP frames to encapsulation format
SNAP. • In Layer 3 aggregate interface view:
applies.
nearest-nontpmr } encapsulation snap
Configuring LLDP trapping and LLDP-MED trapping

LLDP trapping or LLDP-MED trapping notifies the network management system of events such as newly
detected neighboring devices and link failures.
To prevent excessive LLDP traps from being sent when the topology is unstable, set a trap transmission
interval for LLDP.
To configure LLDP trapping and LLDP-MED trapping:

65
nearest-nontpmr } ] notification
remote-change enable By default, LLDP trapping is
3. Enable LLDP trapping.
• In Layer 3 aggregate interface view: disabled.
nearest-nontpmr } notification
remote-change enable
4. Enable LLDP-MED trapping
lldp notification med-topology-change By default, LLDP-MED
(in Layer 3 Ethernet
enable trapping is disabled.
interface view).
5. Return to system view. quit N/A
6. (Optional.) Set the LLDP The default setting is 30
lldp timer notification-interval interval
trap transmission interval. seconds.
Setting the source MAC address of LLDP frames to

the MAC address of the subinterface associated
with the specified VLAN
This feature allows you to configure the source MAC address of LLDP frames as the MAC address of the
Layer 3 Ethernet subinterface associated with the specified VLAN in Dot1q termination. For more
information about Dot1q termination, see "Configuring VLAN termination."
To set the source MAC address of LLDP frames to the MAC address of the Layer 3 Ethernet subinterface
associated with the specified VLAN:

interface view.
By default, the source MAC

3. Set the source MAC
address of LLDP frames is the
address of LLDP frames
MAC address of the port.
to the MAC address of
lldp source-mac vlan vlan-id vlan-id specifies the VLAN ID
the Layer 3 Ethernet
subinterface associated associated with a Layer 3
with the specified VLAN. Ethernet subinterface in Dot1q
termination.
66
Enabling the system to issue the generated ARP
entry to a Layer 3 Ethernet subinterface after a port
receives an LLDP frame
With this feature enabled, when an interface receives an LLDP frame carrying a management address
TLV in IPv4 format, the system performs the following operations:
• Generates an ARP entry that contains the management address and the source MAC address of the
frame.
• Issues the ARP entry to the Layer 3 subinterface associated with the specified VLAN ID in Dot1q
termination.
To enable the system to issue the generated ARP entry to a Layer 3 Ethernet subinterface after a port
receives an LLDP frame:

interface view.
By default, the system does not

3. Enable the system to issue an ARP entry to interfaces
issue the generated ARP after a port receives an LLDP
entry to a Layer 3 lldp management-address arp-learning frame.
Ethernet subinterface vlan vlan-id vlan-id specifies the VLAN ID
after a port receives an associated with a Layer 3
LLDP frame. Ethernet subinterface in Dot1q
termination.
Displaying and maintaining LLDP

Execute display commands in any view.
Task Command
Display local LLDP display lldp local-information [ global | interface interface-type
information. interface-number ]
Display the information

display lldp neighbor-information [ [ [ interface interface-type interface-number ]
contained in the LLDP TLVs
[ agent { nearest-bridge | nearest-customer | nearest-nontpmr } ] [ verbose ] ] |
sent from neighboring
list [ system-name system-name ] ]
devices.
display lldp statistics [ global | [ interface interface-type interface-number ]

Display LLDP statistics.
[ agent { nearest-bridge | nearest-customer | nearest-nontpmr } ] ]
Display LLDP status of a display lldp status [ interface interface-type interface-number ] [ agent
port. { nearest-bridge | nearest-customer | nearest-nontpmr } ]
67
Task Command
Display types of
display lldp tlv-config [ interface interface-type interface-number ] [ agent
advertisable optional LLDP
{ nearest-bridge | nearest-customer | nearest-nontpmr } ]
TLVs.
Basic LLDP configuration example

As shown in Figure 24, enable LLDP globally on Switch A and Switch B to perform the following tasks:
• Monitor the link between Switch A and Switch B on the NMS.
• Monitor the link between Switch A and the MED device on the NMS.
MED
GE1/0/1
NMS
GE1/0/2 GE1/0/1
Switch A Switch B
1. Configure Switch A:
# Enable LLDP globally.
<SwitchA> system-view
[SwitchA] lldp global enable
# Enable LLDP on GigabitEthernet 1/0/1. By default, LLDP is enabled on ports.
[SwitchA-GigabitEthernet1/0/1] lldp enable
# Set the LLDP operating mode to Rx on GigabitEthernet 1/0/1.
[SwitchA-GigabitEthernet1/0/1] lldp admin-status rx
[SwitchA] interface gigabitethernet1/2
[SwitchA-GigabitEthernet1/0/2] lldp enable
# Set the LLDP operating mode to Rx on GigabitEthernet 1/0/2.
[SwitchA-GigabitEthernet1/0/2] lldp admin-status rx
2. Configure Switch B:
# Enable LLDP globally.
68
<SwitchB> system-view
[SwitchB] lldp global enable
[SwitchB] interface gigabitethernet 1/0/1
[SwitchB-GigabitEthernet1/0/1] lldp enable
# Set the LLDP operating mode to Tx on GigabitEthernet 1/0/1.
[SwitchB-GigabitEthernet1/0/1] lldp admin-status tx
[SwitchB-GigabitEthernet1/0/1] quit

# Verify the following items:
• GigabitEthernet 1/0/1 of Switch A connects to a MED device.
• GigabitEthernet 1/0/2 of Switch A connects to a non-MED device.
• Both ports operate in Rx mode, and they can receive LLDP frames but cannot send LLDP frames.
[SwitchA] display lldp status
Global status of LLDP: Enable
Bridge mode of LLDP: customer-bridge
The current number of LLDP neighbors: 2
The current number of CDP neighbors: 0
LLDP neighbor information last changed time: 0 days, 0 hours, 4 minutes, 40 seconds
Transmit interval : 30s
Fast transmit interval : 1s
Transmit credit max : 5
Hold multiplier : 4
Reinit delay : 2s
Trap interval : 30s
Fast start times : 4
LLDP status information of port 1 [GigabitEthernet1/0/1]:

LLDP agent nearest-bridge:
Port status of LLDP : Enable
Admin status : RX_Only
Trap flag : No
MED trap flag : No
Polling interval : 0s
Number of LLDP neighbors : 1
Number of MED neighbors : 1
Number of CDP neighbors : 0
Number of sent optional TLV : 21
Number of received unknown TLV : 0
LLDP agent nearest-customer:

Admin status : Disable
Trap flag : No
MED trap flag : No
69

Trap flag : No
MED trap flag : No
LLDP agent nearest-nontpmr:

Trap flag : No
MED trap flag : No

Trap flag : No
MED trap flag : No
# Remove the link between Switch A and Switch B.

# Verify that GigabitEthernet 1/0/2 of Switch A does not connect to any neighboring devices.
[SwitchA] display lldp status
Global status of LLDP: Enable
The current number of LLDP neighbors: 1
70
The current number of CDP neighbors: 0
LLDP neighbor information last changed time: 0 days, 0 hours, 5 minutes, 20 seconds
Transmit interval : 30s
Fast transmit interval : 1s
Transmit credit max : 5
Hold multiplier : 4
Reinit delay : 2s
Trap interval : 30s
Fast start times : 4

Trap flag : No
MED trap flag : No

Trap flag : No
MED trap flag : No

Trap flag : No
MED trap flag : No
71
Trap flag : No
MED trap flag : No

Trap flag : No
MED trap flag : No
72
Index
Numerics port-based VLAN hybrid port, 28

802 port-based VLAN trunk port, 28
802.1 LLDPDU TLV types, 55 attribute
802.3 LLDPDU TLV types, 55 Ethernet link aggregation attribute configuration, 2
VLAN group configuration, 29 B
VLAN termination default, 38 bandwidth
VLAN termination Dot1q Ethernet link aggregate interface (expected
ambiguous, 35, 35, 42 bandwidth), 14
VLAN termination Dot1q PPPoE server basic management LLDPDU TLV types, 55
support, 43
bridge
VLAN termination Dot1q
LLDP agent customer bridge, 53
unambiguous, 35, 35, 40
LLDP agent nearest bridge, 53
VLAN termination QinQ
LLDP agent non-TPMR bridge, 53
ambiguous, 36, 36, 46
broadcast
VLAN termination QinQ DHCP relay
support, 49 VLAN termination transmission, 38
VLAN termination QinQ PPPoE server C
support, 48
choosing
VLAN termination QinQ
Ethernet link aggregation reference port, 3, 6
unambiguous, 36, 37, 44
configuring
VLAN termination untagged, 38
Ethernet aggregate interface, 11
A Ethernet link aggregation, 1, 9, 17
accessing Ethernet link aggregation edge aggregate
port-based VLAN assignment (access port), 27 interface, 14
advertising Ethernet link aggregation group, 9
LLDP advertisable TLV, 62 Ethernet link aggregation group (dynamic), 10
aggregating Ethernet link aggregation group (static), 10
link. See Ethernet link aggregation Layer 3 Ethernet link aggregation (dynamic), 19
application scenario Layer 3 Ethernet link aggregation (static), 17
VLAN termination inter-VLAN Layer 3 Ethernet link aggregation edge aggregate
communication, 33 interface, 22
VLAN termination LAN-WAN Layer 3 Ethernet link aggregation load sharing, 20
communication, 33 LLDP, 53, 60
ARP LLDP advertisable TLVs, 62
LLDP ARP entry generation, 67 LLDP basics, 60, 68
assigning LLDP management address, 63
Layer 2 LAN switching port-based VLAN access LLDP management address encoding format, 63
port, 27 LLDP trapping, 65
port-based VLAN access port (interface LLDP-MED trapping, 65
view), 27 port-based VLAN, 26
port-based VLAN access port (VLAN view), 27
73
VLAN, 24, 30 Ethernet link aggregation, 17
VLAN basic settings, 25 LLDP, 67
VLAN group, 29 VLAN, 29
VLAN termination, 32, 34, 40 Dot1q
VLAN termination (default), 38 VLAN termination default, 38
VLAN termination (Dot1q VLAN termination Dot1q ambiguous, 35, 35, 42
ambiguous), 35, 35, 42 VLAN termination Dot1q PPPoE server support, 43
VLAN termination (Dot1q PPPoE server VLAN termination Dot1q unambiguous, 35, 35, 40
support), 43 VLAN termination QinQ ambiguous, 36, 36, 46
VLAN termination (Dot1q VLAN termination QinQ DHCP relay support, 49
unambiguous), 35, 35, 40
VLAN termination QinQ PPPoE server support, 48
VLAN termination (QinQ
VLAN termination QinQ unambiguous, 36, 37, 44
ambiguous), 36, 36, 46
VLAN termination type, 32
VLAN termination (QinQ DHCP relay
support), 49
dynamic
VLAN termination (QinQ PPPoE server
support), 48 Ethernet link aggregation dynamic mode, 5
VLAN termination (QinQ Ethernet link aggregation edge aggregate
unambiguous), 36, 37, 44 interface, 8
VLAN termination (untagged), 38 Ethernet link aggregation group, 10
VLAN termination packet TPID, 39 Ethernet link aggregation mode, 3
customer Layer 3 Ethernet link aggregation, 19
LLDP customer bridge mode, 61 Layer 3 Ethernet link aggregation edge aggregate
interface, 22
CVLAN
VLAN termination application scenario, 33 E
VLAN termination configuration, 32, 34, 40 enabling
D Ethernet link aggregation traffic redirection, 16
LLDP, 60
default
LLDP ARP entry generation, 67
Ethernet link aggregate interface default
settings, 15 LLDP polling, 62
VLAN default termination, 32, 38 VLAN termination subinterface broadcast
transmission, 38
device
VLAN termination subinterface multicast
LLDP basic configuration, 60, 68
transmission, 38
LLDP configuration, 53, 60
encapsulating
LLDP parameters, 64
LLDP frame encapsulation (Ethernet II), 54
VLAN termination Dot1q PPPoE server
LLDP frame encapsulation (SNAP), 54
support, 43
LLDP frame encapsulation format, 65
VLAN termination QinQ DHCP relay
support, 49 VLAN frame encapsulation, 24
VLAN termination QinQ PPPoE server Ethernet
support, 48 ARP entry generation, 67
DHCP link aggregation. See Ethernet link aggregation
VLAN termination QinQ DHCP relay LLDP frame encapsulation, 54
support, 49 LLDP trapping, 65
VLAN termination QinQ unambiguous, 36 LLDP-MED trapping, 65
displaying port-based VLAN assignment (access port), 27
74
port-based VLAN assignment (hybrid port), 28 traffic redirection, 16
port-based VLAN assignment (trunk port), 28 traffic redirection restrictions, 16
port-based VLAN configuration, 26 F
VLAN basic configuration, 25
format
VLAN configuration, 24, 30
LLDP frame encapsulation (Ethernet II), 54
VLAN frame encapsulation, 24
LLDP frame encapsulation (SNAP), 54
Ethernet link aggregation
aggregate group Selected ports min/max, 13
LLDP management address encoding format, 63
aggregate interface, 1
frame
aggregate interface (description), 11
aggregate interface (MAC address), 12
aggregate interface configuration, 11
LLDP MAC address setting, 66
aggregate interface default settings, 15
port-based VLAN frame handling, 27
aggregate interface shutdown, 14
aggregation group, 1
aggregation group restrictions, 9 G
basic concepts, 1 group
configuration, 1, 9, 17 Ethernet link aggregate group Selected ports
configuration types, 2 min/max, 13
display, 17 Ethernet link aggregation, 9
dynamic mode, 5 Ethernet link aggregation group, 1
edge aggregate interface, 8, 14 Ethernet link aggregation group (dynamic), 10
group configuration, 9 Ethernet link aggregation group (static), 10
group configuration (dynamic), 10 Ethernet link aggregation LACP, 5
group configuration (static), 10 Ethernet link aggregation load sharing mode, 8, 15
group load sharing mode, 15 Ethernet link aggregation member port state, 2
how dynamic link aggregation works, 6 VLAN group configuration, 29
interface configuration (expected H
bandwidth), 14
hybrid port
LACP, 5
port-based VLAN assignment (hybrid port), 28
Layer 3 aggregate interface configuration
(MTU), 12 I
Layer 3 aggregation (dynamic), 19 interface
Layer 3 aggregation (static), 17 Ethernet aggregate interface, 11
Layer 3 aggregation load sharing, 20 Ethernet aggregate interface (description), 11
Layer 3 edge aggregate interface, 22 Ethernet aggregate interface (MAC address), 12
load sharing mode, 8 Ethernet link aggregate interface default
maintain, 17 settings, 15
member port, 1 Ethernet link aggregate interface shutdown, 14
member port state, 2, 4, 7 Ethernet link aggregation edge aggregate
modes, 3 interface, 8, 14
operational key, 2 Layer 3 aggregate interface configuration
reference port, 6 (MTU), 12
reference port choice, 3 interval
static mode, 3 Ethernet link aggregation LACP long timeout, 6
75
Ethernet link aggregation LACP short timeout, 6 port-based VLAN assignment (trunk port), 28
IPv4 port-based VLAN configuration, 26
VLAN termination QinQ unambiguous, 36 VLAN basic configuration, 25
K VLAN configuration, 24, 30
VLAN display, 29
key
VLAN group configuration, 29
Ethernet link aggregation operational key, 2
VLAN maintain, 29
L VLAN protocols and standards, 25
LACP VLAN termination configuration, 32, 34, 40
Ethernet link aggregation, 5 VLAN termination default, 38
LAN VLAN termination Dot1q, 35
Virtual Local Area Network. Use VLAN VLAN termination Dot1q ambiguous, 42
LAN switching VLAN termination Dot1q PPPoE server support, 43
Ethernet aggregate interface (description), 11 VLAN termination Dot1q unambiguous, 40
Ethernet link aggregate group Selected ports VLAN termination packet TPID, 39
min/max, 13 VLAN termination QinQ, 36
Ethernet link aggregate interface (expected VLAN termination QinQ ambiguous, 46
bandwidth), 14 VLAN termination QinQ DHCP relay support, 49
Ethernet link aggregate interface default VLAN termination QinQ PPPoE server support, 48
settings, 15
VLAN termination QinQ unambiguous, 44
Ethernet link aggregate interface shutdown, 14
Ethernet link aggregation basic concepts, 1
Layer 2
Ethernet link aggregation configuration, 1, 9
LLDP basic configuration, 68
Ethernet link aggregation display, 17
LLDP trapping, 65
Ethernet link aggregation dynamic mode, 5
LLDP-MED trapping, 65
Ethernet link aggregation edge aggregate
VLAN basic configuration, 25
interface, 8, 14
Ethernet link aggregation group, 9
Layer 3
Ethernet link aggregation group load sharing
aggregate interface configuration (MTU), 12
mode, 15
Ethernet link aggregation group restrictions, 9
Ethernet aggregate interface (description), 11
Ethernet link aggregation LACP, 5
Ethernet aggregate interface (MAC address), 12
Ethernet link aggregation load sharing mode, 8
Ethernet link aggregate group Selected ports
Ethernet link aggregation maintain, 17
min/max, 13
Ethernet link aggregation static mode, 3
Ethernet link aggregate interface (expected
Ethernet link aggregation traffic redirection, 16
bandwidth), 14
Ethernet link aggregation traffic redirection
Ethernet link aggregate interface default
restrictions, 16
settings, 15
LLDP basic concepts, 53
Ethernet link aggregate interface shutdown, 14
Ethernet link aggregation (dynamic), 19
Ethernet link aggregation (static), 17
LLDP display, 67
Ethernet link aggregation configuration, 1, 9, 17
LLDP protocols and standards, 59
Ethernet link aggregation edge aggregate
port-based VLAN assignment (access port), 27 interface, 8, 14, 22
port-based VLAN assignment (hybrid port), 28 Ethernet link aggregation group, 9
76
Ethernet link aggregation group (dynamic), 10 operating mode set, 61
Ethernet link aggregation group (static), 10 parameter set, 64
Ethernet link aggregation group load sharing polling enable, 62
mode, 15 protocols and standards, 59
Ethernet link aggregation load sharing, 20 reinitialization delay, 62
Ethernet link aggregation traffic redirection, 16 trapping configuration, 65
LLDP ARP entry generation, 67 LLDPDU
LLDP basic configuration, 68 LLDP basic configuration, 60, 68
LLDP trapping, 65 LLDP configuration, 53, 60
LLDP-MED trapping, 65 LLDP parameters, 64
port-based VLAN assignment (access port), 27 management address configuration, 63
port-based VLAN assignment (hybrid port), 28 management address encoding format, 63
port-based VLAN assignment (trunk port), 28 management address TLV, 58
port-based VLAN configuration, 26 TLV basic management types, 55
link TLV LLDP-MED types, 55
aggregation. See Ethernet link aggregation TLV organization-specific types, 55
link layer discovery protocol. Use LLDP load sharing
LLDP Ethernet link aggregation group load sharing, 8
advertisable TLV configuration, 62 Ethernet link aggregation load sharing mode, 15
agent, 53 Ethernet link aggregation packet type-based load
ARP entry generation, 67 sharing, 8
basic concepts, 53 Ethernet link aggregation per-flow load sharing, 8
basic configuration, 60, 68 Ethernet link aggregation per-packet load
bridge mode setting, 61 sharing, 8
configuration, 53, 60 Layer 3 Ethernet link aggregation configuration, 20
display, 67 M
enable, 60
MAC addressing
frame encapsulation (Ethernet II), 54
frame encapsulation (SNAP), 54
frame encapsulation format, 65
frame format, 54
MAC relay (LLDP agent), 53
frame reception, 59
maintaining
frame transmission, 59
Ethernet link aggregation, 17
how it works, 58
VLAN, 29
LLDPDU management address TLV, 58
management address
LLDPDU TLV types, 55
LLDP encoding format, 63
LLDPDU TLVs, 55
MED (LLDP-MED trapping), 65
LLDP-MED trapping configuration, 65
MIB
MAC address setting, 66
management address configuration, 63
management address encoding format, 63
mode
operating mode (disable), 58
Ethernet link aggregation dynamic, 3, 5
operating mode (Rx), 58
Ethernet link aggregation LACP operation active, 5
operating mode (Tx), 58
Ethernet link aggregation LACP operation
operating mode (TxRx), 58 passive, 5
77
Ethernet link aggregation load sharing, 8 VLAN termination Dot1q, 35
Ethernet link aggregation static, 3, 3 VLAN termination Dot1q ambiguous, 35, 42
LLDP customer bridge mode, 61 VLAN termination Dot1q PPPoE server support, 43
LLDP disable, 58, 61 VLAN termination Dot1q unambiguous, 35, 40
LLDP Rx, 58, 61 VLAN termination packet TPID, 39
LLDP service bridge mode, 61 VLAN termination QinQ, 36
LLDP Tx, 58, 61 VLAN termination QinQ ambiguous, 36, 46
LLDP TxRx, 58, 61 VLAN termination QinQ DHCP relay support, 49
MPLS VLAN termination QinQ PPPoE server support, 48
VLAN termination QinQ unambiguous, 36 VLAN termination QinQ unambiguous, 37, 44
MTU VLAN termination subinterface broadcast
Layer 3 Ethernet aggregate interface, 12 transmission, 38
multicast VLAN termination subinterface multicast
VLAN termination transmission, 38 transmission, 38
VLAN termination types, 32
N
network network management
Ethernet link aggregation configuration types, 2 Ethernet link aggregation configuration, 1, 9, 17
Ethernet link aggregation dynamic mode, 5 LLDP basic concepts, 53
Ethernet link aggregation edge aggregate LLDP configuration, 53, 60
interface, 8
VLAN termination configuration, 32, 34, 40
Ethernet link aggregation member port
state, 4, 7 O
Ethernet link aggregation modes, 3 operational key (Ethernet link aggregation), 2
Ethernet link aggregation operational key, 2 organization-specific LLDPDU TLV types, 55
Ethernet link aggregation reference port, 6 P
Ethernet link aggregation reference port
packet
choice, 3
Ethernet link aggregation packet type-based load
sharing, 8
Layer 3 Ethernet link aggregation (dynamic), 19
Layer 3 Ethernet link aggregation (static), 17
VLAN termination Dot1q, 35
Layer 3 Ethernet link aggregation edge
VLAN termination QinQ, 36
per-flow load sharing, 8
Layer 3 Ethernet link aggregation load
sharing, 20 per-packet load sharing, 8
LLDP basic configuration, 60, 68 polling
LLDP MAC address setting, 66 LLDP enable, 62
port-based VLAN assignment (access port), 27 port
port-based VLAN assignment (hybrid port), 28 aggregate interface (MAC address), 12
port-based VLAN assignment (trunk port), 28 Ethernet aggregate interface, 11
port-based VLAN configuration, 26 Ethernet aggregate interface (description), 11
VLAN basic configuration, 25 Ethernet link aggregate group Selected ports
min/max, 13
VLAN group configuration, 29
Ethernet link aggregate interface (expected
VLAN termination application scenario, 33
bandwidth), 14
VLAN termination default, 38
78
Ethernet link aggregate interface default LLDP TxRx operating mode, 58
settings, 15 VLAN port link type, 26
Ethernet link aggregate interface shutdown, 14 port-based VLAN
Ethernet link aggregation access port assignment (interface view), 27
configuration, 1, 9, 17 access port assignment (VLAN view), 27
Ethernet link aggregation configuration types, 2 assignment (access port), 27
Ethernet link aggregation dynamic mode, 5 assignment (hybrid port), 28
Ethernet link aggregation edge aggregate assignment (trunk port), 28
interface, 8, 14
configuration, 26
port frame handling, 27
Ethernet link aggregation group (dynamic), 10
port link type, 26
Ethernet link aggregation group (static), 10
PVID, 26
PPPoE
Ethernet link aggregation LACP port priority, 5
VLAN termination Dot1q PPPoE server support, 43
Ethernet link aggregation load sharing mode, 8
VLAN termination QinQ PPPoE server support, 48
Ethernet link aggregation member port, 1
VLAN termination QinQ unambiguous, 36
Ethernet link aggregation member port
priority
state, 2, 4, 7
Ethernet link aggregation modes, 3
Ethernet link aggregation LACP port priority, 5
Ethernet link aggregation operational key, 2
Ethernet link aggregation LACP system priority, 5
Ethernet link aggregation reference port, 6
procedure
Ethernet link aggregation reference port
assigning port-based VLAN access port, 27
choice, 3
assigning port-based VLAN access port (interface
view), 27
Ethernet link aggregation traffic redirection, 16
assigning port-based VLAN access port (VLAN
Layer 3 aggregate interface configuration
view), 27
(MTU), 12
assigning port-based VLAN hybrid port, 28
Layer 3 Ethernet link aggregation (dynamic), 19
assigning port-based VLAN trunk port, 28
Layer 3 Ethernet link aggregation (static), 17
configuring Ethernet aggregate interface, 11
Layer 3 Ethernet link aggregation edge
configuring Ethernet link aggregation, 9
configuring Ethernet link aggregation edge
Layer 3 Ethernet link aggregation load
sharing, 20
configuring Ethernet link aggregation group, 9
configuring Ethernet link aggregation group
(dynamic), 10
configuring Ethernet link aggregation group
LLDP disable operating mode, 58
(static), 10
LLDP enable, 60
configuring Layer 3 Ethernet link aggregation
LLDP frame encapsulation format, 65 (dynamic), 19
LLDP frame reception, 59 configuring Layer 3 Ethernet link aggregation
LLDP frame transmission, 59 (static), 17
LLDP operating mode, 61 configuring Layer 3 Ethernet link aggregation edge
LLDP polling, 62 aggregate interface, 22
LLDP reinitialization delay, 62 configuring Layer 3 Ethernet link aggregation load
LLDP Rx operating mode, 58 sharing, 20
LLDP Tx operating mode, 58 configuring LLDP, 60
79
configuring LLDP advertisable TLVs, 62 setting Ethernet aggregate interface (MAC
configuring LLDP basics, 60, 68 address), 12
configuring LLDP management address, 63 setting Ethernet link aggregate group Selected ports
configuring LLDP management address min/max, 13
encoding format, 63 setting Ethernet link aggregate interface (expected
configuring LLDP trapping, 65 bandwidth), 14
configuring LLDP-MED trapping, 65 setting Ethernet link aggregation group load
sharing mode, 15
configuring port-based VLAN, 26
setting Ethernet link aggregation load sharing
configuring VLAN basic settings, 25
mode (global), 15
configuring VLAN group, 29
setting Ethernet link aggregation load sharing
configuring VLAN termination, 34
mode (group-specific), 16
configuring VLAN termination (default), 38
setting Layer 3 aggregate interface (MTU), 12
configuring VLAN termination (Dot1q
setting LLDP bridge mode, 61
ambiguous), 35, 35, 42
setting LLDP frame encapsulation format, 65
configuring VLAN termination (Dot1q PPPoE
setting LLDP MAC address, 66
server support), 43
setting LLDP operating mode, 61
configuring VLAN termination (Dot1q
unambiguous), 35, 35, 40 setting LLDP parameters, 64
configuring VLAN termination (QinQ setting LLDP reinitialization delay, 62
ambiguous), 36, 36, 46 shutting down Ethernet link aggregate interface, 14
configuring VLAN termination (QinQ DHCP protocols and standards
relay support), 49 Ethernet link aggregation protocol configuration, 2
configuring VLAN termination (QinQ PPPoE LLDP, 59
server support), 48 VLAN, 25
configuring VLAN termination (QinQ PVID (port-based VLAN), 26
unambiguous), 36, 37, 44
Q
configuring VLAN termination (untagged), 38
configuring VLAN termination packet TPID, 39 QinQ
displaying Ethernet link aggregation, 17 VLAN termination QinQ ambiguous, 36, 36, 46
displaying LLDP, 67 VLAN termination QinQ DHCP relay support, 49
displaying VLAN, 29 VLAN termination QinQ PPPoE server support, 48
enabling Ethernet link aggregation traffic VLAN termination QinQ unambiguous, 36, 37, 44
redirection, 16 VLAN termination type, 32
enabling LLDP, 60 R
enabling LLDP ARP entry generation, 67
receiving
enabling LLDP polling, 62
LLDP frames, 59
enabling VLAN termination subinterface
reference port (Ethernet link aggregation), 3, 6
broadcast transmission, 38
reinitialization delay (LLDP), 62
enabling VLAN termination subinterface
multicast transmission, 38 restoring
maintaining Ethernet link aggregation, 17 Ethernet link aggregate interface default
settings, 15
maintaining VLAN, 29
restrictions
restoring Ethernet link aggregate interface
default settings, 15 Ethernet link aggregation group, 9
setting Ethernet aggregate interface Ethernet link aggregation traffic redirection, 16
(description), 11 S
80
selecting SVLAN
Ethernet link aggregation Selected ports VLAN termination application scenario, 33
min/max, 13 VLAN termination configuration, 32, 34, 40
Ethernet link aggregation selected state, 2
T
Ethernet link aggregation unselected state, 2
tag
service
VLAN termination application scenario, 33
LLDP service bridge mode, 61
setting
Ethernet aggregate interface (description), 11
VLAN termination packet TPID, 39
Ethernet aggregate interface (MAC
address), 12 VLAN termination QinQ, 36
Ethernet link aggregate group Selected ports VLAN termination types, 32
min/max, 13 time
Ethernet link aggregate interface (expected Ethernet link aggregation LACP timeout interval, 5
bandwidth), 14 timeout
Ethernet link aggregation group load sharing Ethernet link aggregation LACP long timeout
mode, 15 interval, 6
Ethernet link aggregation load sharing mode Ethernet link aggregation LACP short timeout
(global), 15 interval, 6
Ethernet link aggregation load sharing mode timer
(group-specific), 16 LLDP reinitialization delay, 62
Ethernet link aggregation member port TLV
state, 4, 7 LLDP advertisable TLV configuration, 62
Layer 3 aggregate interface (MTU), 12 LLDP management address configuration, 63
LLDP bridge mode, 61 LLDP management address encoding format, 63
LLDP frame encapsulation format, 65 LLDP parameters, 64
LLDP MAC address, 66 LLDPDU basic management types, 55
LLDP operating mode, 61 LLDPDU LLDP-MED types, 55
LLDP parameters, 64 LLDPDU management address TLV, 58
LLDP reinitialization delay, 62 LLDPDU organization-specific types, 55
shutting down TPID for VLAN-tagged packets, 39
Ethernet link aggregate interface, 14 traffic
SNAP Ethernet link aggregation traffic redirection, 16
LLDP frame encapsulation, 54 transmitting
LLDP frame encapsulation format, 65 LLDP frames, 59
state VLAN termination broadcast, 38
Ethernet link aggregation member port VLAN termination multicast, 38
state, 2, 4, 7
trapping
static
LLDP configuration, 65
LLDP-MED configuration, 65
Ethernet link aggregation mode, 3
trunk port
port-based VLAN assignment (trunk port), 28
Layer 3 Ethernet link aggregation, 17
type
subinterface
VLAN termination default, 32
81
VLAN termination QinQ, 32 VLAN termination LAN-WAN communication, 33
U
untagged VLAN termination, 32, 38
V
virtual
Local Area Network. Use VLAN
Virtual Local Area Network. Use VLAN
VLAN
basic configuration, 25
configuration, 24, 30
display, 29
frame encapsulation, 24
group configuration, 29
maintain, 29
port link type, 26
port-based configuration, 26
port-based VLAN assignment (access port), 27
port-based VLAN assignment (hybrid port), 28
port-based VLAN assignment (trunk port), 28
port-based VLAN frame handling, 27
protocols and standards, 25
PVID, 26
VLAN termination
application scenario, 33
configuration, 32, 34, 40
default, 38
Dot1q ambiguous, 35, 35, 42
Dot1q PPPoE server support, 43
Dot1q unambiguous, 35, 35, 40
packet TPID, 39
QinQ ambiguous, 36, 36, 46
QinQ DHCP relay support, 49
QinQ PPPoE server support, 48
QinQ unambiguous, 36, 37, 44
subinterface broadcast transmission, 38
subinterface multicast transmission, 38
types, 32
untagged, 38
W
WAN access
82

04-Layer 2 - LAN Switching Configuration Guide-Book

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

04-Layer 2 - LAN Switching Configuration Guide-Book

Uploaded by

Copyright:

Available Formats

H3C VSR Series Virtual Services Routers

Layer 2 - LAN Switching

Hangzhou H3C Technologies Co., Ltd.

Software version: VSR1000_H3C-CMW710-E0321-X64

All rights reserved

H3C, , H3CS, H3CIE, H3CNE, Aolynk, , H3Care, , IRF, NetPilot, Netflow,

Port numbering in examples

IMPORTANT: An alert that calls attention to essential information.

NOTE: An alert that contains additional or supplementary information.

TIP: An alert that provides helpful information.

Network topology icons

Represents a generic network device, such as a router, switch, or firewall.

Represents a routing-capable device, such as a router or Layer 3 switch.

Represents a generic switch, such as a Layer 2 or Layer 3 switch, or a router that

Represents an access controller, a unified wired-WLAN module, or the access controller

Represents an access point.

T Wireless terminator unit.

Represents a security product, such as a firewall, UTM, multiservice security gateway, or

Configuring Ethernet link aggregation ······················································································································· 1

Configuring VLAN termination ·································································································································· 32

• Protocol configurations—Protocol configurations of a member port do not affect the aggregation

Link aggregation modes

Aggregating links in static mode

Setting the aggregation state of each member port

Set the aggregation state of a member port

Set the port to the

The maximum number of Selected ports in a static aggregation group is 8.

Aggregating links in dynamic mode

LACP operating modes

Determines the likelihood of a member port to be a Selected port on a system. A port

LACP timeout interval

How dynamic link aggregation works

Setting the aggregation state of each member port

Edge aggregate interface

Load sharing modes for link aggregation groups

(Optional.) Configuring an aggregate interface:

(Optional.) Setting load sharing modes for link aggregation groups

(Optional.) Enabling link-aggregation traffic redirection

Configuring an aggregation group

Configuration restrictions and guidelines

Interface type Reference

Interface assigned to a redundancy group Redundancy groups in High Availability Configuration

Interface bound to a cross connect MPLS L2VPN in MPLS Configuration Guide

Interface bound to a VSI VPLS in MPLS Configuration Guide

Step Command Remarks

When you create a Layer 3

3. Exit to system view. quit N/A

a. Enter Layer 3 Ethernet

Configuring a Layer 3 dynamic aggregation group

Step Command Remarks

By default, the system LACP priority

When you create a Layer 3

8. Set the port priority for the link-aggregation port-priority

By default, the long LACP timeout

Configuring an aggregate interface

Setting the description for an aggregate interface

Step Command Remarks

2. Enter Layer 3 aggregate interface route-aggregation

3. Set the description of the

Setting the MAC address for an aggregate interface

Step Command Remarks

The default MAC address of an

Setting the MTU for a Layer 3 aggregate interface