Ethernet link aggregation bundles multiple physical Ethernet links into one logical link (called an aggregate link). Link aggregation provides 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.

Ethernet link aggregation application scenario

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

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).

When an aggregate interface is created, the device automatically creates an aggregation group of the same type and number as the aggregate interface.

An aggregate interface can be one of the following types:

· Layer 2—A Layer 2 aggregate interface is created manually. The member ports of the corresponding Layer 2 aggregation group can only be Layer 2 Ethernet interfaces.

· Layer 3—A Layer 3 aggregate interface is created manually. The member ports of the corresponding Layer 3 aggregation group can only be Layer 3 Ethernet interfaces.

On a Layer 3 aggregate interface, you can create subinterfaces.

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."

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 affect the aggregation state of the port but the protocol configurations do not.

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.

Table 1 Attribute configurations

Feature	Attribute configurations
VLAN	VLAN attribute configurations: · Permitted VLAN IDs. · PVID. · Link type (trunk, hybrid, or access). · VLAN tagging mode. For information about VLANs, see "Configuring VLANs."

Feature

Attribute configurations

VLAN

VLAN attribute configurations:

· Permitted VLAN IDs.

· PVID.

· Link type (trunk, hybrid, or access).

· VLAN tagging mode.

For information about VLANs, see "Configuring VLANs."

Attribute configuration changes on an aggregate interface are automatically synchronized to all member ports. If the device fails to synchronize the changes to a Selected port, the port might become Unselected. For the port to become Selected again, you can modify the attribute configurations on the aggregate interface or the port. The synchronization failure does not affect the attribute configuration changes made on the aggregate interface. The configurations that have been synchronized from the aggregate interface 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.

Protocol configurations

Settings that do not affect the aggregation state of a member port even if they are different from those on the aggregate interface. MAC address learning settings are examples of protocol configurations.

For an aggregation, only the protocol configurations on the aggregate interface take effect. The protocol configurations on the member ports will not take effect until after the ports leave the 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.

Layer 2 aggregation groups and Layer 3 aggregation groups support both the static and dynamic modes.

How static link aggregation works

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.

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

After the limit on Selected ports is reached, the aggregation state of a new member port is set as follows:

· The port is placed in Unselected state if the port has the same priority as all existing Selected ports. 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.

· The port is placed in Selected state if the following conditions are met:

¡ The existing Selected ports have different port priorities, and the port has a higher port priority than a minimum of one Selected port.

¡ The port has the same attribute configurations as the aggregate interface.

Any operational key or attribute configuration change might affect the aggregation states of link aggregation member ports.

LACP

Dynamic aggregation is implemented through IEEE 802.3ad Link Aggregation Control Protocol (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 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
Basic LACP functions	Implemented through the basic LACPDU fields, including the system LACP priority, system MAC address, port priority, port number, and operational key.
Extended LACP functions	Implemented by extending the LACPDU with new TLV fields. Extended LACP can implement LACP MAD for the IRF feature. · If a device supports both extended LACP and IRF, it can participate in LACP 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. For more information about IRF and the LACP MAD mechanism, see IRF Configuration Guide.

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.

Table 3 LACP priorities

Type	Description
System LACP priority	Used by two peer devices (or systems) to determine which one is superior in link aggregation. 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.
Port priority	Determines the likelihood of a member port to be a Selected port on a system. A port with a higher port priority is more likely to become Selected.

Type

Description

System LACP priority

Used by two peer devices (or systems) to determine which one is superior in link aggregation.

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.

Port priority

Determines the likelihood of a member port to be a Selected port on a system. A port 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.

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:

· A dynamic link aggregation group chooses only full-duplex ports as the Selected ports.

· 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.

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—Distributes 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. The load sharing mode can use the following criteria individually or in combination:

¡ MPLS label.

¡ Source or destination IP address.

¡ Source or destination MAC address.

¡ Source or destination port number.

¡ Protocol number.

· Bandwidth usage-based load sharing—Distributes a data flow to the Selected port that has the lowest bandwidth usage when the first packet of that data flow arrives. In this mode, each flow is identified by an IP five-tuple (source and destination IP addresses, source and destination ports, and protocol). For packets that do not contain the IP five-tuple, the default load sharing mode applies.

· Per-packet load sharing—Distributes traffic on a per-packet basis.

Ethernet link aggregation configuration task list

Tasks at a glance
(Required.) Configuring an aggregation group: · Configuring a Layer 2 aggregation group · Configuring a Layer 3 aggregation group
(Optional.) Configuring an aggregate interface: · Configuring the description of an aggregate interface · Specifying ignored VLANs for a Layer 2 aggregate interface · Setting the MTU for a Layer 3 aggregate interface · Specifying a traffic processing slot 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 · Enabling BFD for an aggregation group · Shutting down an aggregate interface · Restoring the default settings for an aggregate interface
(Optional.) Configuring load sharing for link aggregation groups
Enabling link-aggregation traffic redirection

Configuring an aggregation group

This section explains how to configure an aggregation group.

Configuration restrictions and guidelines

The following information describes restrictions and guidelines that you must follow when you configure link aggregations.

Aggregation member interface restrictions

· You cannot assign an interface to a Layer 2 aggregation group if any features in Table 4 are configured on the interface.

Table 4 Features incompatible with Layer 2 aggregation member interfaces

Feature on the interface	Reference
Port security	Port security in Security Configuration Guide
Service instance bound to a cross connect	MPLS L2VPN in MPLS Configuration Guide
Service instance bound to a VSI	VPLS in MPLS Configuration Guide

· You cannot assign an interface to a Layer 3 aggregation group if any features in Table 5 are configured on the interface.

Table 5 Features incompatible with Layer 3 aggregation member interfaces

Interface type	Reference
Interface bound to a cross connect	MPLS L2VPN in MPLS Configuration Guide
Interface bound to a VSI	VPLS in MPLS Configuration Guide

· Do not assign a reflector port for port mirroring to an aggregation group. For more information about reflector ports, see Network Management and Monitoring Configuration Guide.

Layer 3 Ethernet subinterface restrictions

For a Layer 3 aggregate interface, the member interfaces in the aggregation group must be Layer 3 Ethernet interfaces or subinterfaces, but not both.

If you are assigning a Layer 3 Ethernet interface to an aggregation group, make sure it does not have subinterfaces. You cannot create subinterfaces on a Layer 3 Ethernet interface after it is assigned to an aggregation group.

If you are assigning a Layer 3 Ethernet subinterface to an aggregation group, follow these restrictions and guidelines:

· Configure VLAN termination before you assign the subinterface to the aggregation group. You cannot modify the VLAN termination configuration after the subinterface is assigned to an aggregation group. The following are VLAN termination commands you might use:

¡ vlan-type dot1q default

¡ vlan-type dot1q untagged

¡ vlan-type dot1q vid

¡ vlan-type dot1q vid second-dot1q

For information about the VLAN termination commands, see "VLAN termination commands."

· All Layer 3 Ethernet subinterfaces in an aggregation group must have the same VLAN termination configuration.

· If you are assigning a subinterface to a dynamic aggregation group, specify only the outer VLAN ID when you use the vlan-type dot1q vid vlan-id-list [ loose ] command on that subinterface.

For a Layer 3 aggregate interface, aggregate subinterfaces and Layer 3 subinterfaces cannot coexist.

· You cannot create aggregate subinterfaces on a Layer 3 aggregate interface if its aggregation group contains Layer 3 Ethernet subinterfaces.

· You cannot assign Layer 3 Ethernet subinterfaces to an aggregation group if its aggregate interface has aggregate subinterfaces.

Configuration consistency requirements

· You must configure the same aggregation mode at the two ends of an aggregate link.

· For a successful static aggregation, make sure the ports at both ends of each link are in the same aggregation state.

· 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.

Miscellaneous

Deleting an aggregate interface also deletes its aggregation group and causes all member ports to leave the aggregation group.

Configuring a Layer 2 aggregation group

Configuring a Layer 2 static aggregation group

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Create a Layer 2 aggregate interface and enter Layer 2 aggregate interface view.	interface bridge-aggregation interface-number	When you create a Layer 2 aggregate interface, the system automatically creates a Layer 2 static aggregation group with the same number as that aggregate interface.
3. Exit to system view.	quit	N/A
4. Assign an interface to the specified Layer 2 aggregation group.	a Enter Layer 2 Ethernet interface view: interface interface-type interface-number b Assign the interface to the specified Layer 2 aggregation group: port link-aggregation group group-id	You can assign multiple Layer 2 Ethernet interfaces to an aggregation group.

Configuring a Layer 2 dynamic aggregation group

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Set the system LACP priority.	lacp system-priority priority	By default, the system LACP priority is 32768. Changing the system LACP priority might affect the aggregation states of the ports in a dynamic aggregation group.
3. Create a Layer 2 aggregate interface and enter Layer 2 aggregate interface view.	interface bridge-aggregation interface-number	When you create a Layer 2 aggregate interface, the system automatically creates a Layer 2 static aggregation group with the same number as that aggregate interface.
4. Configure the aggregation group to operate in dynamic mode.	link-aggregation mode dynamic	By default, an aggregation group operates in static mode.
5. Exit to system view.	quit	N/A
6. Assign an interface to the specified Layer 2 aggregation group.	a Enter Layer 2 Ethernet interface view: interface interface-type interface-number b Assign the interface to the specified Layer 2 aggregation group: port link-aggregation group group-id	You can assign multiple Layer 2 Ethernet interfaces to an aggregation group.
7. Set the port priority for the interface.	link-aggregation port-priority priority	The default setting is 32768.

Configuring a Layer 3 aggregation group

Configuring a Layer 3 static aggregation group

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Create a Layer 3 aggregate interface and enter Layer 3 aggregate interface view.	interface route-aggregation interface-number	When you create a Layer 3 aggregate interface, the system automatically creates a Layer 3 static aggregation group with the same number as that aggregate interface.
3. Exit to system view.	quit	N/A
4. Assign an interface or subinterface to the specified Layer 3 aggregation group.	a Enter Layer 3 Ethernet interface or subinterface view: interface { interface-number \| interface-number.subnumber } b Assign the interface or subinterface to the specified Layer 3 aggregation group: port link-aggregation group group-id	You can assign multiple Layer 3 Ethernet interfaces or subinterfaces to an aggregation group.

Configuring a Layer 3 dynamic aggregation group

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Set the system LACP priority.	lacp system-priority priority	By default, the system LACP priority is 32768. Changing the system LACP priority might affect the aggregation states of the ports in the dynamic aggregation group.
3. Create a Layer 3 aggregate interface and enter Layer 3 aggregate interface view.	interface route-aggregation interface-number	When you create a Layer 3 aggregate interface, the system automatically creates a Layer 3 static aggregation group with the same number as that aggregate interface.
4. Configure the aggregation group to operate in dynamic mode.	link-aggregation mode dynamic	By default, an aggregation group operates in static mode.
5. Exit to system view.	quit	N/A
6. Assign an interface or subinterface to the specified Layer 3 aggregation group.	a Enter Layer 3 Ethernet interface or subinterface view: interface { interface-number \| interface-number.subnumber } b Assign the interface or subinterface to the specified Layer 3 aggregation group: port link-aggregation group group-id	You can assign multiple Layer 3 Ethernet interfaces or subinterfaces to an aggregation group.
7. Set the LACP operating mode on the interface.	· Set the LACP operating mode to passive: lacp mode passive · Set the LACP operating mode to active: undo lacp mode	By default, LACP is operating in active mode.
8. Set the port priority of the interface.	link-aggregation port-priority priority	The default setting is 32768.
9. (Optional.) Enable the short LACP timeout interval (3 seconds) on the interface.	lacp period short	By default, the long LACP timeout interval (90 seconds) is used on the interface. To avoid traffic interruption during an ISSU, do not enable the short LACP 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 2 or Layer 3 Ethernet interfaces can also be made on Layer 2 or Layer 3 aggregate interfaces.

Configuring the description of an aggregate interface

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

To configure the description of an aggregate interface:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter aggregate interface or subinterface view.	· Enter Layer 2 aggregate interface view: interface bridge-aggregation interface-number · Enter Layer 3 aggregate interface or subinterface view: interface route-aggregation { interface-number \| interface-number.subnumber }	N/A
3. Configure the description of the aggregate interface or subinterface.	description text	By default, the description of an interface is interface-name Interface.

Specifying ignored VLANs for a Layer 2 aggregate interface

To become Selected, a member port by default must have the same VLAN permit state and tagging mode as the Layer 2 aggregate interface. To ignore the VLAN permit state and tagging mode of a VLAN when choosing Selected ports, specify the VLAN as an ignored VLAN.

To specify ignored VLANs for a Layer 2 aggregate interface:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter Layer 2 aggregate interface view.	interface bridge-aggregation interface-number	N/A
3. Specify ignored VLANs.	link-aggregation ignore vlan vlan-id-list	By default, a Layer 2 aggregate interface does not ignore any VLANs.

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:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter Layer 3 aggregate interface or subinterface view.	interface route-aggregation { interface-number \| interface-number.subnumber }	N/A
3. Set the MTU for the Layer 3 aggregate interface or subinterface.	mtu size	The default setting is 1500 bytes.

Specifying a traffic processing slot for a Layer 3 aggregate interface

This feature is supported only in IRF mode.

By default, traffic on a Layer 3 aggregate interface is processed on the slot at which the traffic arrives. You can specify a traffic processing slot for all traffic on a Layer 3 aggregate interface to be processed on the same slot. If the aggregate interface contains subinterfaces, traffic on the subinterfaces is not processed on the specified slot.

When NAT is configured on a Layer 3 aggregate interface, you must specify a traffic processing slot for the aggregate interface. For information about NAT, see Layer 3—IP Services Configuration Guide.

To specify a traffic processing slot for a Layer 3 aggregate interface:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter Layer 3 aggregate interface view.	interface route-aggregation interface-number	N/A
3. Specify a primary traffic processing slot for the interface.	In IRF mode: service chassis chassis-number slot slot-number	By default, no primary traffic processing slot is specified for an interface.
4. Specify a backup traffic processing slot for the interface.	In IRF mode: service standby chassis chassis-number slot slot-number	By default, no backup traffic processing slot is specified for an interface.

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 aggregate interface.

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.

The maximum number of Selected ports allowed in an aggregation group is limited by either manual configuration or hardware limitation, whichever value is smaller.

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:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter aggregate interface view.	· Enter Layer 2 aggregate interface view: interface bridge-aggregation interface-number · Enter Layer 3 aggregate interface view: interface route-aggregation interface-number	N/A
3. Set the minimum number of Selected ports for the aggregation group.	link-aggregation selected-port minimum min-number	By default, the minimum number of Selected ports is not specified for an aggregation group.
4. Set the maximum number of Selected ports for the aggregation group.	link-aggregation selected-port maximum max-number	By default, the maximum number of Selected ports for an aggregation group depends on hardware limitation.

Setting the expected bandwidth for an aggregate interface

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter aggregate interface view.	· Enter Layer 2 aggregate interface view: interface bridge-aggregation interface-number · Enter Layer 3 aggregate interface or subinterface view: interface route-aggregation { interface-number \| interface-number.subnumber }	N/A
3. Set the expected bandwidth for the interface.	bandwidth bandwidth-value	By default, the expected bandwidth (in kbps) is 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:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter aggregate interface view.	· Enter Layer 2 aggregate interface view: interface bridge-aggregation interface-number · Enter Layer 3 aggregate interface view: interface route-aggregation interface-number	N/A
3. Configure the aggregate interface as an edge aggregate interface.	lacp edge-port	By default, an aggregate interface does not operate as an edge aggregate interface.

Enabling BFD for an aggregation group

BFD provides link state monitoring and quick failure recovery for link aggregation groups. After you enable BFD on an aggregate interface, each Selected port in the aggregation group establishes a BFD session with its peer port. The failure recovery mechanism differs depending on the aggregation mode.

· BFD for static aggregation—When detecting link failure, BFD notifies the link aggregation feature that a peer port is unreachable, and the link aggregation feature places the local port in Unselected state. The BFD session on the failed link is retained, and the local port keeps sending BFD packets. When the local port receives BFD packets from the peer port again, BFD notifies the link aggregation feature that the peer port becomes reachable. The link aggregation feature then places the local port in Selected state.

· BFD for dynamic aggregation—When detecting link failure, BFD notifies the link aggregation feature that a peer port is unreachable. The BFD session on the failed link is removed, and the local port stops sending BFD packets. When the link is recovered and the local port becomes Selected again, the local port establishes a new BFD session with the peer port. BFD then notifies the link aggregation feature that the peer port becomes reachable.

For more information about BFD, see High Availability Configuration Guide.

Configuration restrictions and guidelines

When you enable BFD on an aggregate interface, follow these restrictions and guidelines:

· If you both specify a traffic processing slot and enable BFD on the aggregate interface, BFD sessions might flap when network congestion occurs.

· Make sure the source and destination IP addresses are consistent between the two ends of an aggregate link. For example, if you execute link-aggregation bfd ipv4 source 1.1.1.1 destination 2.2.2.2 at the local end, execute link-aggregation bfd ipv4 source 2.2.2.2 destination 1.1.1.1 at the peer end.

· The BFD parameters configured on the aggregate interface take effect on all its member interfaces' BFD sessions. BFD sessions for link aggregation do not support the echo packet mode or the Demand mode. For more information about BFD, see High Availability Configuration Guide.

· As a best practice, do not configure other features to collaborate with BFD on a BFD-enabled aggregate interface.

· Make sure the number of member ports in a BFD-enabled aggregation group is less than or identical to the number of BFD sessions supported by the device. If the aggregation group contains more member ports than the supported sessions, some Selected ports might change to the Unselected state.

Configuration procedure

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter Layer 3 aggregate interface view.	interface route-aggregation interface-number	N/A
3. Enable BFD for the aggregation group.	link-aggregation bfd ipv4 source ip-address destination ip-address	By default, BFD is disabled for an aggregation group. The source and destination IP addresses of BFD sessions must be unicast addresses.

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.

To shut down an aggregate interface:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter aggregate interface view.	· Enter Layer 2 aggregate interface view: interface bridge-aggregation interface-number · Enter Layer 3 aggregate interface or subinterface view: interface route-aggregation { interface-number \| interface-number.subnumber }	N/A
3. Shut down the aggregate interface or subinterface.	shutdown	By default, an aggregate 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 aggregate interface view.	· Enter Layer 2 aggregate interface view: interface bridge-aggregation interface-number · Enter Layer 3 aggregate interface or subinterface view: interface route-aggregation { interface-number \| interface-number.subnumber }
3. Restore the default settings for the aggregate interface.	default

Configuring load sharing for link aggregation groups

The following information describes how to configure the load sharing modes for link aggregation groups and how to enable local-first load sharing for link aggregation.

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

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Set the global link-aggregation load sharing mode.	link-aggregation global load-sharing mode { { destination-ip \| destination-mac \| destination-port \| source-ip \| source-mac \| source-port } * \| per-packet }	By default, the device load shares traffic based on source and destination IP addresses.

Setting the group-specific load sharing mode

When you configure the group-specific load sharing mode, following these restrictions and guidelines:

· MAC address-based load sharing is supported only by Layer 2 aggregate interfaces.

· Multicast traffic cannot be load shared based on bandwidth usage.

· If you configure an aggregation group to load shard traffic based on bandwidth usage, any of the following operations might affect the traffic load sharing in the aggregation group:

¡ Setting the global load sharing mode.

¡ Setting the load sharing modes for other aggregation groups.

Make sure you are fully aware of the impacts when you perform these operations.

To set the group-specific load sharing mode:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter aggregate interface view.	· Enter Layer 2 aggregate interface view: interface bridge-aggregation interface-number · Enter Layer 3 aggregate interface view: interface route-aggregation interface-number	N/A
3. Set the load sharing mode for the aggregation group.	link-aggregation load-sharing mode { { destination-ip \| destination-mac \| destination-port \| ip-protocol \| mpls-label1 \| mpls-label2 \| mpls-label3 \| source-ip \| source-mac \| source-port } * \| bandwidth-usage \| per-packet }	By default, the group-specific load sharing mode is the same as the global load sharing mode.
4. (Optional.) Enable the aggregate interface to use IP five-tuple information for MPLS packet distribution.	link-aggregation load-sharing mpls enhanced	By default, link-aggregation load sharing enhancement is disabled for MPLS packets. The IP five-tuple is the source IP address, source port number, destination IP address, destination port number, and protocol number. Use this command only on the provider (P) device. For information about the P device, see MPLS L3VPN configuration in MPLS Configuration Guide.

Enabling local-first load sharing for link aggregation

Use local-first load sharing in a multidevice link aggregation scenario to distribute traffic preferentially across member ports on the ingress card or device.

When you aggregate ports on different member devices in an IRF fabric, you can use local-first load sharing to reduce traffic on IRF links, as shown in Figure 4. For more information about IRF, see IRF Configuration Guide.

Figure 4 Load sharing for multidevice link aggregation in an IRF fabric

To enable local-first load sharing for link aggregation:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enable local-first load sharing for link aggregation.	link-aggregation load-sharing mode local-first	By default, local-first load sharing for link aggregation is enabled.

Enabling link-aggregation traffic redirection

Link-aggregation traffic redirection prevents traffic interruption.

When you restart an IRF member device that contains Selected ports in a multichassis dynamic aggregation, this feature redirects the traffic on the ports to the remaining active IRF member devices. Zero packet loss is guaranteed for known unicast traffic, but not for unknown unicast traffic. (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.

· To prevent packet loss that might occur when the device reboots, do not enable spanning tree together with link-aggregation traffic redirection.

· Link-aggregation traffic redirection cannot operate correctly on an edge aggregate interface.

Configuration procedure

To enable link-aggregation traffic redirection:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enable link-aggregation traffic redirection.	link-aggregation lacp traffic-redirect-notification enable	By default, link-aggregation traffic 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 or multiple aggregate interfaces.	display interface [ { bridge-aggregation \| route-aggregation } [ interface-number ] ] [ brief [ description \| down ] ]
Display the local system ID.	display lacp system-id
Display the global or group-specific link-aggregation load sharing modes.	display link-aggregation load-sharing mode [ interface [ { bridge-aggregation \| route-aggregation } interface-number ] ]
Display detailed link aggregation information for link aggregation member ports.	display link-aggregation member-port [ interface-list ]
Display summary information about all aggregation groups.	display link-aggregation summary
Display detailed information about the specified aggregation groups.	display link-aggregation verbose [ { bridge-aggregation \| route-aggregation } [ interface-number ] ]
Clear LACP statistics for the specified link aggregation member ports.	reset lacp statistics [ interface interface-list ]
Clear statistics for the specified aggregate interfaces.	reset counters interface [ { bridge-aggregation \| route-aggregation } [ interface-number ] ]

Ethernet link aggregation configuration examples

Layer 2 static aggregation configuration example

Network requirements

On the network shown in Figure 5, perform the following tasks:

· Configure a Layer 2 static aggregation group on both Device A and Device B.

· Enable VLAN 10 at one end of the aggregate link to communicate with VLAN 10 at the other end.

· Enable VLAN 20 at one end of the aggregate link to communicate with VLAN 20 at the other end.

Figure 5 Network diagram

Configuration procedure

1. Configure Device A:

# Create VLAN 10, and assign port GigabitEthernet 1/1/4 to VLAN 10.

<DeviceA> system-view

[DeviceA] vlan 10

[DeviceA-vlan10] port gigabitethernet 1/1/4

[DeviceA-vlan10] quit

# Create VLAN 20, and assign port GigabitEthernet 1/1/5 to VLAN 20.

[DeviceA] vlan 20

[DeviceA-vlan20] port gigabitethernet 1/1/5

[DeviceA-vlan20] quit

# Create Layer 2 aggregate interface Bridge-Aggregation 1.

[DeviceA] interface bridge-aggregation 1

[DeviceA-Bridge-Aggregation1] quit

# Assign ports GigabitEthernet 1/1/1 through GigabitEthernet 1/1/3 to link aggregation group 1.

[DeviceA] interface gigabitethernet 1/1/1

[DeviceA-GigabitEthernet1/1/1] port link-aggregation group 1

[DeviceA-GigabitEthernet1/1/1] quit

[DeviceA] interface gigabitethernet 1/1/2

[DeviceA-GigabitEthernet1/1/2] port link-aggregation group 1

[DeviceA-GigabitEthernet1/1/2] quit

[DeviceA] interface gigabitethernet 1/1/3

[DeviceA-GigabitEthernet1/1/3] port link-aggregation group 1

[DeviceA-GigabitEthernet1/1/3] quit

# Configure Layer 2 aggregate interface Bridge-Aggregation 1 as a trunk port and assign it to VLANs 10 and 20.

[DeviceA] interface bridge-aggregation 1

[DeviceA-Bridge-Aggregation1] port link-type trunk

[DeviceA-Bridge-Aggregation1] port trunk permit vlan 10 20

[DeviceA-Bridge-Aggregation1] 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: Bridge-Aggregation1

Aggregation Mode: Static

Loadsharing Type: NonS

Port Status Priority Oper-Key

--------------------------------------------------------------------------------

GE1/1/1 S 32768 1

GE1/1/2 S 32768 1

GE1/1/3 S 32768 1

The output shows that link aggregation group 1 is a Layer 2 static aggregation group that contains three Selected ports.

Layer 2 dynamic aggregation configuration example

Network requirements

On the network shown in Figure 6, perform the following tasks:

· Configure a Layer 2 dynamic aggregation group on both Device A and Device B.

· Enable VLAN 10 at one end of the aggregate link to communicate with VLAN 10 at the other end.

· Enable VLAN 20 at one end of the aggregate link to communicate with VLAN 20 at the other end.

Figure 6 Network diagram

Configuration procedure

1. Configure Device A:

# Create VLAN 10, and assign the port GigabitEthernet 1/1/4 to VLAN 10.

<DeviceA> system-view

[DeviceA] vlan 10

[DeviceA-vlan10] port gigabitethernet 1/1/4

[DeviceA-vlan10] quit

# Create VLAN 20, and assign the port GigabitEthernet 1/1/5 to VLAN 20.

[DeviceA] vlan 20

[DeviceA-vlan20] port gigabitethernet 1/1/5

[DeviceA-vlan20] quit

# Create Layer 2 aggregate interface Bridge-Aggregation 1, and set the link aggregation mode to dynamic.

[DeviceA] interface bridge-aggregation 1

[DeviceA-Bridge-Aggregation1] link-aggregation mode dynamic

[DeviceA-Bridge-Aggregation1] quit

# Assign ports GigabitEthernet 1/1/1 through GigabitEthernet 1/1/3 to link aggregation group 1.

[DeviceA] interface gigabitethernet 1/1/1

[DeviceA-GigabitEthernet1/1/1] port link-aggregation group 1

[DeviceA-GigabitEthernet1/1/1] quit

[DeviceA] interface gigabitethernet 1/1/2

[DeviceA-GigabitEthernet1/1/2] port link-aggregation group 1

[DeviceA-GigabitEthernet1/1/2] quit

[DeviceA] interface gigabitethernet 1/1/3

[DeviceA-GigabitEthernet1/1/3] port link-aggregation group 1

[DeviceA-GigabitEthernet1/1/3] quit

# Configure Layer 2 aggregate interface Bridge-Aggregation 1 as a trunk port and assign it to VLANs 10 and 20.

[DeviceA] interface bridge-aggregation 1

[DeviceA-Bridge-Aggregation1] port link-type trunk

[DeviceA-Bridge-Aggregation1] port trunk permit vlan 10 20

[DeviceA-Bridge-Aggregation1] 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: Bridge-Aggregation1

Aggregation Mode: Dynamic

Loadsharing Type: NonS

System ID: 0x8000, 000f-e267-6c6a

Local:

Port Status Priority Oper-Key Flag

--------------------------------------------------------------------------------

GE1/1/1 S 32768 1 {ACDEF}

GE1/1/2 S 32768 1 {ACDEF}

GE1/1/3 S 32768 1 {ACDEF}

Remote:

Actor Partner Priority Oper-Key SystemID Flag

--------------------------------------------------------------------------------

GE1/1/1 1 32768 1 0x8000, 000f-e267-57ad {ACDEF}

GE1/1/2 2 32768 1 0x8000, 000f-e267-57ad {ACDEF}

GE1/1/3 3 32768 1 0x8000, 000f-e267-57ad {ACDEF}

The output shows that link aggregation group 1 is a Layer 2 dynamic aggregation group that contains three Selected ports.

Layer 2 aggregation load sharing configuration example

Network requirements

On the network shown in Figure 7, perform the following tasks:

· Configure Layer 2 static aggregation groups 1 and 2 on Device A and Device B, respectively.

· Enable VLAN 10 at one end of the aggregate link to communicate with VLAN 10 at the other end.

· Enable VLAN 20 at one end of the aggregate link to communicate with VLAN 20 at the other end.

· Configure link aggregation groups 1 and 2 to load share traffic across aggregation group member ports.

¡ Configure link aggregation group 1 to load share packets based on source MAC addresses.

¡ Configure link aggregation group 2 to load share packets based on destination MAC addresses.

Figure 7 Network diagram

Configuration procedure

1. Configure Device A:

# Create VLAN 10, and assign the port GigabitEthernet 1/1/5 to VLAN 10.

<DeviceA> system-view

[DeviceA] vlan 10

[DeviceA-vlan10] port gigabitethernet 1/1/5

[DeviceA-vlan10] quit

# Create VLAN 20, and assign the port GigabitEthernet 1/1/6 to VLAN 20.

[DeviceA] vlan 20

[DeviceA-vlan20] port gigabitethernet 1/1/6

[DeviceA-vlan20] quit

# Create Layer 2 aggregate interface Bridge-Aggregation 1.

[DeviceA] interface bridge-aggregation 1

# Configure Layer 2 aggregation group 1 to load share packets based on source MAC addresses.

[DeviceA-Bridge-Aggregation1] link-aggregation load-sharing mode source-mac

[DeviceA-Bridge-Aggregation1] quit

# Assign ports GigabitEthernet 1/1/1 and GigabitEthernet 1/1/2 to link aggregation group 1.

[DeviceA] interface gigabitethernet 1/1/1

[DeviceA-GigabitEthernet1/1/1] port link-aggregation group 1

[DeviceA-GigabitEthernet1/1/1] quit

[DeviceA] interface gigabitethernet 1/1/2

[DeviceA-GigabitEthernet1/1/2] port link-aggregation group 1

[DeviceA-GigabitEthernet1/1/2] quit

# Configure Layer 2 aggregate interface Bridge-Aggregation 1 as a trunk port and assign it to VLAN 10.

[DeviceA] interface bridge-aggregation 1

[DeviceA-Bridge-Aggregation1] port link-type trunk

[DeviceA-Bridge-Aggregation1] port trunk permit vlan 10

[DeviceA-Bridge-Aggregation1] quit

# Create Layer 2 aggregate interface Bridge-Aggregation 2.

[DeviceA] interface bridge-aggregation 2

# Configure Layer 2 aggregation group 2 to load share packets based on destination MAC addresses.

[DeviceA-Bridge-Aggregation2] link-aggregation load-sharing mode destination-mac

[DeviceA-Bridge-Aggregation2] quit

# Assign ports GigabitEthernet 1/1/3 and GigabitEthernet 1/1/4 to link aggregation group 2.

[DeviceA] interface gigabitethernet 1/1/3

[DeviceA-GigabitEthernet1/1/3] port link-aggregation group 2

[DeviceA-GigabitEthernet1/1/3] quit

[DeviceA] interface gigabitethernet 1/1/4

[DeviceA-GigabitEthernet1/1/4] port link-aggregation group 2

[DeviceA-GigabitEthernet1/1/4] quit

# Configure Layer 2 aggregate interface Bridge-Aggregation 2 as a trunk port and assign it to VLAN 20.

[DeviceA] interface bridge-aggregation 2

[DeviceA-Bridge-Aggregation2] port link-type trunk

[DeviceA-Bridge-Aggregation2] port trunk permit vlan 20

[DeviceA-Bridge-Aggregation2] 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: Bridge-Aggregation1

Aggregation Mode: Static

Loadsharing Type: Shar

Port Status Priority Oper-Key

--------------------------------------------------------------------------------

GE1/1/1 S 32768 1

GE1/1/2 S 32768 1

Aggregate Interface: Bridge-Aggregation2

Aggregation Mode: Static

Loadsharing Type: Shar

Port Status Priority Oper-Key

--------------------------------------------------------------------------------

GE1/1/3 S 32768 2

GE1/1/4 S 32768 2

The output shows that:

· Link aggregation groups 1 and 2 are both load-shared Layer 2 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

Bridge-Aggregation1 Load-Sharing Mode:

source-mac address

Bridge-Aggregation2 Load-Sharing Mode:

destination-mac address

The output shows that:

· Link aggregation group 1 load shares packets based on source MAC addresses.

· Link aggregation group 2 load shares packets based on destination MAC addresses.

Layer 2 edge aggregate interface configuration example

Network requirements

As shown in Figure 8, a Layer 2 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/1/1 and GigabitEthernet 1/1/2 can forward traffic to improve link reliability.

Figure 8 Network diagram

Configuration procedure

# Create Layer 2 aggregate interface Bridge-Aggregation 1, and set the link aggregation mode to dynamic.

<Device> system-view

[Device] interface bridge-aggregation 1

[Device-Bridge-Aggregation1] link-aggregation mode dynamic

# Configure Layer 2 aggregate interface Bridge-Aggregation 1 as an edge aggregate interface.

[Device-Bridge-Aggregation1] lacp edge-port

[Device-Bridge-Aggregation1] quit

# Assign ports GigabitEthernet 1/1/1 and GigabitEthernet 1/1/2 to link aggregation group 1.

[Device] interface gigabitethernet 1/1/1

[Device-GigabitEthernet1/1/1] port link-aggregation group 1

[Device-GigabitEthernet1/1/1] quit

[Device] interface gigabitethernet 1/1/2

[Device-GigabitEthernet1/1/2] port link-aggregation group 1

[Device-GigabitEthernet1/1/2] quit

Verifying the configuration

# 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

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: Bridge-Aggregation1

Aggregation Mode: Dynamic

Loadsharing Type: NonS

System ID: 0x8000, 000f-e267-6c6a

Local:

Port Status Priority Oper-Key Flag

--------------------------------------------------------------------------------

GE1/1/1 I 32768 1 {AG}

GE1/1/2 I 32768 1 {AG}

Remote:

Actor Partner Priority Oper-Key SystemID Flag

--------------------------------------------------------------------------------

GE1/1/1 0 32768 0 0x8000, 0000-0000-0000 {DEF}

GE1/1/2 0 32768 0 0x8000, 0000-0000-0000 {DEF}

The output shows that GigabitEthernet 1/1/1 and GigabitEthernet 1/1/2 are in Individual state when they do not receive LACPDUs from the server. Both GigabitEthernet 1/1/1 and GigabitEthernet 1/1/2 can forward traffic. When one port fails, its traffic is automatically switched to the other port.

Layer 3 static aggregation configuration example

Network requirements

On the network shown in Figure 9, 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.

Figure 9 Network diagram

Configuration procedure

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/1/1 through GigabitEthernet 1/1/3 to aggregation group 1.

[DeviceA] interface gigabitethernet 1/1/1

[DeviceA-GigabitEthernet1/1/1] port link-aggregation group 1

[DeviceA-GigabitEthernet1/1/1] quit

[DeviceA] interface gigabitethernet 1/1/2

[DeviceA-GigabitEthernet1/1/2] port link-aggregation group 1

[DeviceA-GigabitEthernet1/1/2] quit

[DeviceA] interface gigabitethernet 1/1/3

[DeviceA-GigabitEthernet1/1/3] port link-aggregation group 1

[DeviceA-GigabitEthernet1/1/3] 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/1/1 S 32768 1

GE1/1/2 S 32768 1

GE1/1/3 S 32768 1

The output shows that link aggregation group 1 is a Layer 3 static aggregation group that contains three Selected ports.

Layer 3 dynamic aggregation configuration example

Network requirements

On the network shown in Figure 10, perform the following tasks:

· Configure a Layer 3 dynamic aggregation group on both Device A and Device B.

· Configure IP addresses and subnet masks for the corresponding Layer 3 aggregate interfaces.

Figure 10 Network diagram

Configuration procedure

1. Configure Device A:

# Create Layer 3 aggregate interface Route-Aggregation 1.

<DeviceA> system-view

[DeviceA] interface route-aggregation 1

# Set the link aggregation mode to dynamic.

[DeviceA-Route-Aggregation1] link-aggregation mode dynamic

# Configure an IP address and subnet mask for Route-Aggregation 1.

[DeviceA-Route-Aggregation1] ip address 192.168.1.1 24

[DeviceA-Route-Aggregation1] quit

# Assign Layer 3 Ethernet interfaces GigabitEthernet 1/1/1 through GigabitEthernet 1/1/3 to aggregation group 1.

[DeviceA] interface gigabitethernet 1/1/1

[DeviceA-GigabitEthernet1/1/1] port link-aggregation group 1

[DeviceA-GigabitEthernet1/1/1] quit

[DeviceA] interface gigabitethernet 1/1/2

[DeviceA-GigabitEthernet1/1/2] port link-aggregation group 1

[DeviceA-GigabitEthernet1/1/2] quit

[DeviceA] interface gigabitethernet 1/1/3

[DeviceA-GigabitEthernet1/1/3] port link-aggregation group 1

[DeviceA-GigabitEthernet1/1/3] 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: Dynamic

Loadsharing Type: NonS

System ID: 0x8000, 000f-e267-6c6a

Local:

Port Status Priority Oper-Key Flag

--------------------------------------------------------------------------------

GE1/1/1 S 32768 1 {ACDEF}

GE1/1/2 S 32768 1 {ACDEF}

GE1/1/3 S 32768 1 {ACDEF}

Remote:

Actor Partner Priority Oper-Key SystemID Flag

--------------------------------------------------------------------------------

GE1/1/1 1 32768 1 0x8000, 000f-e267-57ad {ACDEF}

GE1/1/2 2 32768 1 0x8000, 000f-e267-57ad {ACDEF}

GE1/1/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

Network requirements

On the network shown in Figure 11, perform the following tasks:

· Configure Layer 3 static aggregation groups 1 and 2 on Device A and Device B, respectively.

· Configure IP addresses and subnet masks for the corresponding Layer 3 aggregate interfaces.

· 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.

Figure 11 Network diagram

Configuration procedure

1. Configure Device A:

# Create Layer 3 aggregate interface Route-Aggregation 1.

<DeviceA> system-view

[DeviceA] interface route-aggregation 1

# 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.

[DeviceA-Route-Aggregation1] ip address 192.168.1.1 24

[DeviceA-Route-Aggregation1] quit

# Assign Layer 3 Ethernet interfaces GigabitEthernet 1/1/1 and GigabitEthernet 1/1/2 to aggregation group 1.

[DeviceA] interface gigabitethernet 1/1/1

[DeviceA-GigabitEthernet1/1/1] port link-aggregation group 1

[DeviceA-GigabitEthernet1/1/1] quit

[DeviceA] interface gigabitethernet 1/1/2

[DeviceA-GigabitEthernet1/1/2] port link-aggregation group 1

[DeviceA-GigabitEthernet1/1/2] quit

# Create Layer 3 aggregate interface Route-Aggregation 2.

[DeviceA] interface route-aggregation 2

# 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

# Configure an IP address and subnet mask for Layer 3 aggregate interface Route-Aggregation 2.

[DeviceA-Route-Aggregation2] ip address 192.168.2.1 24

[DeviceA-Route-Aggregation2] quit

# Assign Layer 3 Ethernet interfaces GigabitEthernet 1/1/3 and GigabitEthernet 1/1/4 to aggregation group 2.

[DeviceA] interface gigabitethernet 1/1/3

[DeviceA-GigabitEthernet1/1/3] port link-aggregation group 2

[DeviceA-GigabitEthernet1/1/3] quit

[DeviceA] interface gigabitethernet 1/1/4

[DeviceA-GigabitEthernet1/1/4] port link-aggregation group 2

[DeviceA-GigabitEthernet1/1/4] 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: Shar

Port Status Priority Oper-Key

--------------------------------------------------------------------------------

GE1/1/1 S 32768 1

GE1/1/2 S 32768 1

Aggregate Interface: Route-Aggregation2

Aggregation Mode: Static

Loadsharing Type: Shar

Port Status Priority Oper-Key

--------------------------------------------------------------------------------

GE1/1/3 S 32768 2

GE1/1/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

Network requirements

As shown in Figure 12, 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/1/1 and GigabitEthernet 1/1/2 can forward traffic to improve link reliability.

Figure 12 Network diagram

Configuration procedure

# 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

# Configure an IP address and subnet mask for Layer 3 aggregate interface Route-Aggregation 1.

[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/1/1 and GigabitEthernet 1/1/2 to aggregation group 1.

[Device] interface gigabitethernet 1/1/1

[Device-GigabitEthernet1/1/1] port link-aggregation group 1

[Device-GigabitEthernet1/1/1] quit

[Device] interface gigabitethernet 1/1/2

[Device-GigabitEthernet1/1/2] port link-aggregation group 1

[Device-GigabitEthernet1/1/2] quit

Verifying the configuration

# 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

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: Dynamic

Loadsharing Type: NonS

System ID: 0x8000, 000f-e267-6c6a

Local:

Port Status Priority Oper-Key Flag

--------------------------------------------------------------------------------

GE1/1/1 I 32768 1 {AG}

GE1/1/2 I 32768 1 {AG}

Remote:

Actor Partner Priority Oper-Key SystemID Flag

--------------------------------------------------------------------------------

GE1/1/1 0 32768 0 0x8000, 0000-0000-0000 {DEF}

GE1/1/2 0 32768 0 0x8000, 0000-0000-0000 {DEF}

04-Layer 2 - LAN Switching Configuration Guide

Configuration types

Attribute configurations

Protocol configurations

LACP functions

LACP operating modes

LACP priorities

LACP timeout interval

Load sharing modes for link aggregation groups

Aggregation member interface restrictions

Layer 3 Ethernet subinterface restrictions

Configuration consistency requirements

Miscellaneous

Configuring a Layer 3 static aggregation group

Setting the expected bandwidth for an aggregate interface

Configuration restrictions and guidelines

Configuration procedure

Setting the global link-aggregation load sharing mode

Setting the group-specific load sharing mode

Network requirements

Configuration procedure

Verifying the configuration

Network requirements

Configuration procedure

Verifying the configuration

Network requirements

Configuration procedure

Verifying the configuration

Network requirements

Configuration procedure

Verifying the configuration

Network requirements

Configuration procedure

Verifying the configuration

Network requirements

Configuration procedure

Verifying the configuration

Network requirements

Configuration procedure

Verifying the configuration

Network requirements

Configuration procedure

Verifying the configuration

Cloud & AI

InterConnect

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Resources

Partner Business Management

Company Information

News & Events

Contact Us