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 carried on the failed link is switched to the other two links.

Figure 1 Ethernet link aggregation diagram

Aggregation group, member port, and aggregate interface

Link bundling is implemented through interface bundling. An aggregation group is a group of Ethernet interfaces bundled together, which are called member ports of the aggregation group. For each aggregation group, a logical interface (called an aggregate interface), is created.

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 aggregate interface 1, aggregation group 1 is created.

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 the states of member ports in an aggregation group, 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:

¡ The corresponding aggregate interface is configured as an edge aggregate interface.

¡ The port has not received 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 are assigned the same operational key.

Configuration types

Every configuration setting on a port might affect its aggregation state. Port configurations include the following types:

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

Any attribute configuration change might affect the aggregation state of link aggregation member ports and running services. To make sure that you are aware of the risk, the system displays a warning message every time you attempt to change an attribute configuration setting on a member port.

Table 1 Attribute configurations

Feature	Considerations
Port isolation	Indicates whether the port has joined an isolation group and which isolation group the port belongs to.
VLAN	VLAN attribute configurations include: · Permitted VLAN IDs. · PVID. · Link type (trunk, hybrid, or access). · Operating mode (promiscuous, trunk promiscuous, or host). · VLAN tagging mode. For information about VLAN, see "Configuring VLANs."

Feature

Considerations

Port isolation

Indicates whether the port has joined an isolation group and which isolation group the port belongs to.

VLAN

VLAN attribute configurations include:

· Permitted VLAN IDs.

· PVID.

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

· Operating mode (promiscuous, trunk promiscuous, or host).

· VLAN tagging mode.

For information about VLAN, 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 a member port take effect only when the member port leaves 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, which reduces the administrators' workload.

How static link aggregation works

Reference port selection process

When setting the aggregation state of the ports in an aggregation group, the system automatically picks 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 that are 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 a static aggregation group has reached the limit on Selected ports, any port that joins the group is placed in Unselected state to avoid traffic interruption on the existing Selected ports.

Figure 2 Setting the aggregation state of a member port in a static aggregation group

To configure the maximum number of Selected ports in a static aggregation group, see "Setting the minimum and maximum numbers of Selected ports for an aggregation group."

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

LACP

Dynamic aggregation mode 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 an LACP-enabled aggregation group exchanges 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. This is how the LACP MAD mechanism of the IRF feature is implemented. it can participate in LACP MAD as either an IRF member device or an intermediate device. For more information about IRF and the LACP MAD mechanism, see Virtual Technologies Configuration Guide.

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, after which the system that has lower priority sets port state accordingly.
Port priority	Determines the likelihood of a member port to be selected on a system. The higher port priority, the higher the likelihood of selection.

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, after which the system that has lower priority sets port state accordingly.

Port priority

Determines the likelihood of a member port to be selected on a system. The higher port priority, the higher the likelihood of selection.

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 fails to receive 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 configure the short timeout interval, the peer sends one LACPDU per second.

· Long timeout interval—90 seconds. If you configure 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 that are in up state and have the same attribute configurations as the aggregate interface. A Selected port must have the same operational key and attribute configurations as the reference port.

The local system (the actor) and the remote system (the partner) negotiate a reference port by using the following workflow:

1. The systems compare their system IDs. (A system ID contains the system LACP priority and the system MAC address.) The lower the LACP priority, the smaller the system ID. If LACP priority values are the same, 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 port with the lower priority value is chosen. If two ports have the same aggregation priority, the system compares their port numbers. The port with the smaller port number and the same attribute configurations as the aggregate interface becomes the reference port.

Setting the aggregation state of each member port

After the reference port is chosen, the system with the lower system ID sets the state of each member port in the dynamic aggregation group on its side as shown in Figure 3.

Figure 3 Setting the state of a member port in a dynamic aggregation group

Meanwhile, the system with the higher system ID, being aware of the aggregation state changes on the remote system, sets the aggregation state of local member ports the same as their peer ports.

When you aggregate interfaces in dynamic mode, follow these guidelines:

· To configure the maximum number of Selected ports in a dynamic aggregation group, see "Setting the minimum and maximum numbers of Selected ports for an aggregation group."

· A dynamic link aggregation group preferably chooses full-duplex ports as the Selected ports. The group will choose only one half-duplex port as a Selected port when either of the following conditions exist:

¡ None of the full-duplex ports can be chosen as Selected ports.

¡ Only half-duplex ports exist in the group.

· To ensure stable aggregation and service continuity, do not change the operational key or attribute configurations on any member port.

· In a dynamic aggregation group, when the aggregation state of a local port changes, the aggregation state of the peer port also changes.

· After the Selected port limit has been reached, a port joining the aggregation group is placed in the Selected state 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—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 criteria that classify traffic:

¡ Source or destination MAC address.

¡ Source or destination port number.

¡ Ingress port.

¡ Source or destination IP address.

¡ Protocol number.

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

Ethernet link aggregation configuration task list

Tasks at a glance
(Required.) Configuring an aggregation group: · Configuring a static aggregation group · Configuring a dynamic 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 or subinterface · 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 group: · Setting load sharing modes for link aggregation groups · Enabling local-first load sharing for link aggregation
(Optional.) Enabling link-aggregation traffic redirection
(Optional.) Configuring the link aggregation capability for the device

Prerequisites for Layer 3 aggregate interface or subinterface creation

Before creating a Layer 3 aggregate interface or subinterface, you must use the reserve-vlan-interface command to reserve VLAN interface resources. If the number of reserved VLAN interfaces is inadequate, the system will fail to create the Layer 3 aggregate interface or subinterface.

· Before creating a Layer 3 aggregate interface, reserve one VLAN interface for each of the following interfaces:

¡ Layer 3 aggregate interface.

¡ Each member port in the Layer 3 aggregation group.

· Before creating Layer 3 aggregate subinterfaces on a Layer 3 aggregate interface, reserve a VLAN interface resource for each of the following interface:

¡ Layer 3 aggregate interface.

¡ Each member port in the Layer 3 aggregation group.

¡ Each Layer 3 aggregate subinterface.

Table 4 gives examples of VLAN interface resource reservation.

Table 4 Examples of VLAN interface resource reservation

Layer 3 aggregation settings

Number of reserved VLAN interfaces

1 × Layer 3 aggregation interface

3 × Member ports

1 x Layer 3 aggregate interface

2 x member ports

4 x Layer 3 aggregate subinterfaces

IMPORTANT:

A Layer 3 aggregate subinterface must process traffic for the VLAN that has the same VLAN ID as its subinterface number. When you reserve VLAN interfaces and plan the Layer 3 aggregate subinterface numbering scheme, make sure the reserved VLAN interface numbers are different from Layer 3 aggregation subinterface numbers.

To reserve global-type VLAN interface resources, specify the global keyword in the reserve-vlan-interface command. To reserve local-type VLAN interface resources, do not specify the global keyword. Reserved VLAN interface resources are local type in this chapter.

For more information about reserving VLAN interface resources, see "Configuring VLANs."

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:

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

Configuring a static aggregation group

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

Avoid assigning ports to a static aggregation group where the limit on Selected ports has been reached. New member ports in the static aggregation group will be placed in the Unselected state to avoid traffic interruption on the current Selected ports. However, a device reboot can cause the aggregation state of member ports to change.

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 numbered the same.
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 number	Repeat these two sub-steps to assign more Layer 2 Ethernet interfaces to the 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 numbered the same.
3. Exit to system view.	quit	N/A
4. Assign an interface to the specified Layer 3 aggregation group.	a Enter Layer 3 Ethernet interface view: interface interface-type interface-number b Assign the interface to the specified Layer 3 aggregation group: port link-aggregation group number	Repeat these two substeps to assign more Layer 3 Ethernet interfaces to the aggregation group.

Configuring a 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.

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 system-priority	By default, the system LACP priority is 32768. Changing the system LACP priority might affect the aggregation state 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 numbered the same.
4. Configure the aggregation group to operate in dynamic aggregation mode.	link-aggregation mode dynamic	By default, an aggregation group operates in static aggregation 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 number	Repeat these two sub-steps to assign more Layer 2 Ethernet interfaces to the aggregation group.
7. Set the port priority for the interface.	link-aggregation port-priority port-priority	The default setting is 32768.
8. Set the short LACP timeout interval (3 seconds) on the interface.	lacp period short	By default, the long LACP timeout interval (90 seconds) is adopted by the interface. The peer sends LACPDUs slowly.

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 system-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 numbered the same.
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 3 aggregation group.	a Enter Layer 3 Ethernet interface view: interface interface-type interface-number b Assign the interface to the specified Layer 3 aggregation group: port link-aggregation group number	Repeat these two substeps to assign more Layer 3 Ethernet interfaces to the aggregation group.
7. Set the port priority for the interface.	link-aggregation port-priority port-priority	The default setting is 32768.
8. Set the short LACP timeout interval (3 seconds) on the interface.	lacp period short	By default, the long LACP timeout interval (90 seconds) is adopted by the interface.

Configuring an aggregate interface

In addition to the configurations in this section, most of the configurations that can be performed on Layer 2 or Layer 3 Ethernet interfaces can also be performed 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 such as 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 in the format of interface-name Interface.

Specifying ignored VLANs for a Layer 2 aggregate interface

By default, the member ports cannot become Selected ports when the permit state and tagging mode of each VLAN are not same for the member ports and the Layer 2 aggregate interface.

You can set a VLAN as an ignored VLAN if you want to allow member ports to be set in Selected state even if the permit state and tagging mode of the VLAN are different between the member ports and the Layer 2 aggregate interface.

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 or subinterface

The MTU of an interface affects IP packet fragmentation and reassembly on the interface.

To set the MTU for a Layer 3 aggregate interface or subinterface:

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.

Setting the minimum and maximum numbers of Selected ports for an aggregation group

IMPORTANT:

The minimum and maximum number 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 caused by insufficient Selected ports on an aggregate link, you can set the minimum number of Selected ports required for bringing up the specific aggregate interface.

This minimum threshold setting affects the aggregation state of both aggregation member ports and the aggregate interface:

· When the number of member ports eligible to be selected is smaller than the minimum threshold, all member ports change to the Unselected state and the link of the aggregate interface goes down.

· When the minimum threshold is reached, the eligible member ports change to the Selected state, and the link of the aggregate interface goes up.

The maximum number of Selected ports allowed in an aggregation group is limited by either the configured maximum number or hardware capability, whichever value is smaller.

You can configure backup between two ports by assigning two ports to an aggregation group and configuring the maximum number of Selected ports allowed in the aggregation group as 1. In this way, only one Selected port is allowed in the aggregation group at any point in time, while the Unselected port serves 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 number	By default, the minimum number of Selected ports for the aggregation group is not specified.
4. Set the maximum number of Selected ports for the aggregation group.	link-aggregation selected-port maximum number	By default, the maximum number of Selected ports for an aggregation group is 16.

Setting the expected bandwidth for 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 /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

This configuration takes effect on only the aggregate interface corresponding to a dynamic aggregation group.

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 for Ethernet link aggregation can monitor member link status in an aggregation group. After you enable BFD on an aggregate interface, each Selected port in the aggregation group establishes a BFD session with its peer port. All the BFD sessions use UDP port 6784 and destination MAC address 01-00-5E-90-00-01. BFD operates differently depending on the aggregation mode.

· BFD for static aggregation—When BFD detects a link failure, BFD notifies the Ethernet link aggregation module that the peer port is unreachable. The local port is placed in the Unselected state. The BFD session between the local and peer ports remains, and the local port keeps sending BFD packets. When the link is recovered, the local port receives BFD packets from the peer port, and BFD notifies the Ethernet link aggregation module that the peer port is reachable. The local port is placed in the Selected state again. This mechanism ensures that the local and peer ports of a static aggregate link have the same aggregation state.

· BFD for dynamic aggregation—When BFD detects a link failure, BFD notifies the Ethernet link aggregation module that the peer port is unreachable. BFD clears the session and stops sending BFD packets. When the link is recovered and the local port is placed in the Selected state again, the local port establishes a new session with the peer port. BFD notifies the Ethernet link aggregation module that the peer port is reachable. Because BFD provides fast failure detection, the local and peer systems of a dynamic aggregate link can negotiate the aggregation state of their member ports faster.

To enable BFD 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. 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.

Shutting down an aggregate interface

Make sure no member port in an aggregation group is configured with the loopback command when you shut down the aggregate interface. Similarly, a port configured with the loopback command cannot be assigned to an aggregate interface already shut down. For more information about the loopback command, see Layer 2—LAN Switching Command Reference.

Shutting down or bringing up an aggregate interface affects the aggregation state and link state of ports in the corresponding aggregation group in the following ways:

· When an aggregate interface is shut down, all Selected ports in the corresponding aggregation group become unselected and their link state becomes down.

· When an aggregate interface is brought up, the aggregation state of ports in the corresponding aggregation group is recalculated.

To shut down 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. Shut down the aggregate interface.	shutdown	By default, aggregate interfaces are up.

Restoring the default settings for an aggregate interface

You can return all configurations on an aggregate interface to default settings.

To restore the default settings for an aggregate interface:

Step	Command
1. Enter system view.	system-view
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 }
3. Restore the default settings for the aggregate interface.	default

Configuring load sharing for link aggregation groups

This section explains how to set 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. The global load sharing mode takes effect on all link aggregation groups. 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.

If you configure both link aggregation load sharing and per-flow load sharing over equal-cost routes, the latest configuration takes effect. Per-flow load sharing over equal-cost routes identifies a flow based on five tuples (source IP address, destination IP address, source port number, destination port number, and IP protocol number). For information about configuring per-flow load sharing over equal-cost routes, see Layer 3—IP Services Configuration Guide.

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 \| ingress-port \| ip-protocol \| source-ip \| source-mac \| source-port } *	The default settings are as follows: · Layer 2 traffic is distributed based on the Ethernet type, source and destination MAC address, and source port. · IPv4 or IPv6 traffic is distributed based on the source and destination IP addresses, source and destination ports, and protocol number. · MPLS traffic with three or fewer layers of labels is distributed based on the source and destination IP addresses, source and destination ports, and protocol number. MPLS traffic with more than three layers of labels is distributed based on the source and destination IP addresses. In system view, the switch supports any combinations of these keywords.

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 | ingress-port | ip-protocol | source-ip | source-mac | source-port } *

The default settings are as follows:

· Layer 2 traffic is distributed based on the Ethernet type, source and destination MAC address, and source port.

· IPv4 or IPv6 traffic is distributed based on the source and destination IP addresses, source and destination ports, and protocol number.

· MPLS traffic with three or fewer layers of labels is distributed based on the source and destination IP addresses, source and destination ports, and protocol number. MPLS traffic with more than three layers of labels is distributed based on the source and destination IP addresses.

In system view, the switch supports any combinations of these keywords.

NOTE:

· If you set the global load-sharing mode to source MAC address, the setting takes effect only on Layer 2 aggregation groups. A Layer 3 aggregation group forwards traffic by using one of its Selected ports rather than load shares traffic. When the Selected port fails, traffic is switched to another Selected port in the aggregation group.

· If an unsupported load sharing mode is set, an error prompt appears.

Setting the group-specific load sharing mode

The switch can perform link-aggregation load sharing on a per-packet basis.

To set the group-specific load sharing mode:

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. Configure the aggregation group to load share traffic on a per-packet basis.	link-aggregation load-sharing mode flexible	By default, the load sharing mode of a group is the same as the global load sharing mode.

Enabling local-first load sharing for link aggregation

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

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 Virtual Technologies Configuration Guide.

Figure 4 Load sharing for multi-switch 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.

NOTE:

Local-first load sharing for link aggregation takes effect on only known unicast packets.

Enabling link-aggregation traffic redirection

Link-aggregation traffic redirection prevents traffic interruption.

When you restart a card that contains Selected ports, this feature redirects traffic of the card to other cards. (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. When you restart a card that contains Selected ports, this feature redirects traffic of the card to other cards. (In IRF mode.)

You can enable link-aggregation traffic redirection globally or for an aggregation group. Global link-aggregation traffic redirection settings take effect on all aggregation groups. A link aggregation group preferentially uses the group-specific link-aggregation traffic redirection settings. If group-specific link-aggregation traffic redirection is not configured, the group uses the global link-aggregation traffic redirection settings.

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 at a reboot, do not enable spanning tree together with link-aggregation traffic redirection.

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

· As a best practice, enable link-aggregation traffic redirection on aggregate interfaces. If you enable this feature globally, communication with a third-party peer device might be affected if the peer is not compatible with this feature.

Configuration procedure

To enable link-aggregation traffic redirection globally:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enable link-aggregation traffic redirection globally.	link-aggregation lacp traffic-redirect-notification enable	By default, link-aggregation traffic redirection is disabled globally.

To enable link-aggregation traffic redirection 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. Enable link-aggregation traffic redirection for the aggregation group.	link-aggregation lacp traffic-redirect-notification enable	By default, link-aggregation traffic redirection is disabled for an aggregation group.

Configuring the link aggregation capability for the device

By default, the device supports a maximum of 1024 aggregation groups, and an aggregation group can have a maximum of 16 Selected ports. You can perform this task to modify the maximum number of aggregation groups and the maximum number of Selected ports per aggregation group.

After you configure the link aggregation capability for the device, save the configuration and reboot the device for the configuration to take effect. Before rebooting the device, make sure you know the possible impact on the network.

The maximum number of Selected ports allowed in an aggregation group is limited by one of the following values, whichever value is smaller:

· Maximum number set by using the link-aggregation selected-port maximum command.

· Maximum number of Selected ports allowed by the link aggregation capability.

To configure the link aggregation capability for the device:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Configure the link aggregation capability for the device.	link-aggregation capability max-group max-group-number max-selected-port max-selected-port-number	By default, the device supports a maximum of 1024 aggregation groups, and an aggregation group can have a maximum of 16 Selected ports.

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 ] [ brief [ down \| description ] ] display interface { bridge-aggregation \| route-aggregation } interface-number [ brief [ description ] ]
Display the local system ID.	display lacp system-id
Display the link aggregation capability for the device.	display link-aggregation capability
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 forwarding information for the specified traffic flow.	display link-aggregation load-sharing path interface { bridge-aggregation \| route-aggregation } interface-number ingress-port interface-type interface-number [ route ] { { destination-ip ip-address \| destination-ipv6 ipv6-address } \| { source-ip ip-address \| source-ipv6 ipv6-address } \| destination-mac mac-address \| destination-port port-id \| ethernet-type type-number \| ip-protocol protocol-id \| source-mac mac-address \| source-port port-id \| vlan vlan-id }*
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

As shown in Figure 5, configure a Layer 2 static aggregation group on both Device A and Device B, and enable VLAN 10 at one end of the aggregate link to communicate with VLAN 10 at the other end, and VLAN 20 at one end 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 FortyGigE 1/0/4 to VLAN 10.

<DeviceA> system-view

[DeviceA] vlan 10

[DeviceA-vlan10] port fortygige 1/0/4

[DeviceA-vlan10] quit

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

[DeviceA] vlan 20

[DeviceA-vlan20] port fortygige 1/0/5

[DeviceA-vlan20] quit

# Create Layer 2 aggregate interface Bridge-Aggregation 1.

[DeviceA] interface bridge-aggregation 1

[DeviceA-Bridge-Aggregation1] quit

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

[DeviceA] interface fortygige 1/0/1

[DeviceA-FortyGigE1/0/1] port link-aggregation group 1

[DeviceA-FortyGigE1/0/1] quit

[DeviceA] interface fortygige 1/0/2

[DeviceA-FortyGigE1/0/2] port link-aggregation group 1

[DeviceA-FortyGigE1/0/2] quit

[DeviceA] interface fortygige 1/0/3

[DeviceA-FortyGigE1/0/3] port link-aggregation group 1

[DeviceA-FortyGigE1/0/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: Shar

Port Status Priority Oper-Key

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

FGE1/0/1 S 32768 1

FGE1/0/2 S 32768 1

FGE1/0/3 S 32768 1

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

Layer 2 dynamic aggregation configuration example

Network requirements

As shown in Figure 6, 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, and VLAN 20 at one end 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 FortyGigE 1/0/4 to VLAN 10.

<DeviceA> system-view

[DeviceA] vlan 10

[DeviceA-vlan10] port fortygige 1/0/4

[DeviceA-vlan10] quit

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

[DeviceA] vlan 20

[DeviceA-vlan20] port fortygige 1/0/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 FortyGigE 1/0/1 through FortyGigE 1/0/3 to link aggregation group 1.

[DeviceA] interface fortygige 1/0/1

[DeviceA-FortyGigE1/0/1] port link-aggregation group 1

[DeviceA-FortyGigE1/0/1] quit

[DeviceA] interface fortygige 1/0/2

[DeviceA-FortyGigE1/0/2] port link-aggregation group 1

[DeviceA-FortyGigE1/0/2] quit

[DeviceA] interface fortygige 1/0/3

[DeviceA-FortyGigE1/0/3] port link-aggregation group 1

[DeviceA-FortyGigE1/0/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: Shar

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

Local:

Port Status Priority Oper-Key Flag

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

FGE1/0/1 S 32768 1 {ACDEF}

FGE1/0/2 S 32768 1 {ACDEF}

FGE1/0/3 S 32768 1 {ACDEF}

Remote:

Actor Partner Priority Oper-Key SystemID Flag

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

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

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

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

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

Layer 2 aggregation load sharing configuration example

Network requirements

As shown in Figure 7:

· Configure two 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 the global load sharing mode to load share traffic across aggregation group member ports based on source MAC addresses.

Figure 7 Network diagram

Configuration procedure

1. Configure Device A:

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

<DeviceA> system-view

[DeviceA] vlan 10

[DeviceA-vlan10] port fortygige 1/0/5

[DeviceA-vlan10] quit

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

[DeviceA] vlan 20

[DeviceA-vlan20] port fortygige 1/0/6

[DeviceA-vlan20] quit

# Create Layer 2 aggregate interface Bridge-Aggregation 1.

[DeviceA] interface bridge-aggregation 1

[DeviceA-Bridge-Aggregation1] quit

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

[DeviceA] interface fortygige 1/0/1

[DeviceA-FortyGigE1/0/1] port link-aggregation group 1

[DeviceA-FortyGigE1/0/1] quit

[DeviceA] interface fortygige 1/0/2

[DeviceA-FortyGigE1/0/2] port link-aggregation group 1

[DeviceA-FortyGigE1/0/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

[DeviceA-Bridge-Aggregation2] quit

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

[DeviceA] interface fortygige 1/0/3

[DeviceA-FortyGigE1/0/3] port link-aggregation group 2

[DeviceA-FortyGigE1/0/3] quit

[DeviceA] interface fortygige 1/0/4

[DeviceA-FortyGigE1/0/4] port link-aggregation group 2

[DeviceA-FortyGigE1/0/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

# Configure the global link-aggregation load sharing mode to load share packets based on source MAC addresses.

[DeviceA] link-aggregation global load-sharing mode source-mac

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

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

FGE1/0/1 S 32768 1

FGE1/0/2 S 32768 1

Aggregate Interface: Bridge-Aggregation2

Aggregation Mode: Static

Loadsharing Type: Shar

Port Status Priority Oper-Key

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

FGE1/0/3 S 32768 2

FGE1/0/4 S 32768 2

The output shows that link aggregation groups 1 and 2 are both load-shared Layer 2 static aggregation groups and each 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:

source-mac address

The output shows that both link aggregation group 1 and link aggregation group 2 load share packets based on source MAC addresses.

Layer 3 static aggregation configuration example

Network requirements

As shown in Figure 8:

· Reserve four VLAN interface resources before creating a Layer 3 aggregate interface.

· 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 8 Network diagram

Configuration procedure

1. Configure Device A:

# Reserve VLAN interfaces 3000 to 3500. For more information about reserving VLAN interface resources, see "Configuring VLANs."

<DeviceA> system-view

[DeviceA] reserve-vlan-interface 3000 to 3500

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

[DeviceA] interface fortygige 1/0/1

[DeviceA-FortyGigE1/0/1] port link-aggregation group 1

[DeviceA-FortyGigE1/0/1] quit

[DeviceA] interface fortygige 1/0/2

[DeviceA-FortyGigE1/0/2] port link-aggregation group 1

[DeviceA-FortyGigE1/0/2] quit

[DeviceA] interface fortygige 1/0/3

[DeviceA-FortyGigE1/0/3] port link-aggregation group 1

[DeviceA-FortyGigE1/0/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: Shar

Port Status Priority Oper-Key

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

FGE1/0/1 S 32768 1

FGE1/0/2 S 32768 1

FGE1/0/3 S 32768 1

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

Layer 3 dynamic aggregation configuration example

Network requirements

As shown in Figure 9:

· Reserve four VLAN interfaces before creating a Layer 3 aggregate interface.

· 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 9 Network diagram

Configuration procedure

1. Configure Device A:

# Reserve VLAN interfaces 3000 to 3500. For more information about reserving VLAN interface resources, see "Configuring VLANs."

<DeviceA> system-view

[DeviceA] reserve-vlan-interface 3000 to 3500

# Create Layer 3 aggregate interface Route-Aggregation 1.

<DeviceA> system-view

[DeviceA] 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.

[DeviceA-Route-Aggregation1] ip address 192.168.1.1 24

[DeviceA-Route-Aggregation1] quit

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

[DeviceA] interface fortygige 1/0/1

[DeviceA-FortyGigE1/0/1] port link-aggregation group 1

[DeviceA-FortyGigE1/0/1] quit

[DeviceA] interface fortygige 1/0/2

[DeviceA-FortyGigE1/0/2] port link-aggregation group 1

[DeviceA-FortyGigE1/0/2] quit

[DeviceA] interface fortygige 1/0/3

[DeviceA-FortyGigE1/0/3] port link-aggregation group 1

[DeviceA-FortyGigE1/0/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: Shar

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

Local:

Port Status Priority Oper-Key Flag

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

FGE1/0/1 S 32768 1 {ACDEF}

FGE1/0/2 S 32768 1 {ACDEF}

FGE1/0/3 S 32768 1 {ACDEF}

Remote:

Actor Partner Priority Oper-Key SystemID Flag

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

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

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

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

The output shows that:

· Link aggregation group 1 is a non-load-shared Layer 3 dynamic aggregation group.

· The aggregation group contains three Selected ports.

Layer 3 edge aggregate interface configuration example

Network requirements

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

Reserve three VLAN interface resources before creating the Layer 3 aggregate interface.

Figure 10 Network diagram

Configuration procedure

# Reserve VLAN interfaces 3000 to 3500. For more information about reserving VLAN interface resources, see "Configuring VLANs."

<DeviceA> system-view

[DeviceA] reserve-vlan-interface 3000 to 3500

# 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 FortyGigE 1/0/1 and FortyGigE 1/0/2 to aggregation group 1.

[Device] interface fortygige 1/0/1

[Device-FortyGigE1/0/1] port link-aggregation group 1

[Device-FortyGigE1/0/1] quit

[Device] interface fortygige 1/0/2

[Device-FortyGigE1/0/2] port link-aggregation group 1

[Device-FortyGigE1/0/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

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

FGE1/0/1 I 32768 1 {AG}

FGE1/0/2 I 32768 1 {AG}

Remote:

Actor Partner Priority Oper-Key SystemID Flag

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

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

FGE1/0/2 0 32768 0 0x8000, 0000-0000-0000 {DEF}

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

03-Layer 2-LAN Switching Configuration Guide

Configuration types

Reference port selection process

LACP functions

LACP priorities

LACP timeout interval

Load sharing modes for link aggregation groups

Configuring a Layer 2 static aggregation group

Configuring a Layer 2 dynamic aggregation group

Setting the MTU for a Layer 3 aggregate interface or subinterface

Setting the expected bandwidth for an aggregate interface

Setting the global link-aggregation 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

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