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

Figure 1 Ethernet link aggregation diagram

‌

Aggregate interface, aggregation group, and member port

Each link aggregation is represented by a logical aggregate interface. Each aggregate interface has an automatically created aggregation group, which contains member ports to be used for aggregation. The type and number of an aggregation group are the same as its aggregate interface.

Aggregate interface types

An aggregate interface can be one of the following types:

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

The device supports Layer 3 aggregate interfaces. A Layer 3 aggregate interface is created manually. The member ports in its Layer 3 aggregation group can only be Layer 3 Ethernet interfaces. On a Layer 3 aggregate interface, you can create subinterfaces. A Layer 3 aggregate subinterface processes traffic only for the VLAN numbered with the same ID as the subinterface number.

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.

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 configuration includes the attribute configuration and protocol configuration. Attribute configuration affects the aggregation state of the port but the protocol configuration does not.

Attribute configuration

To become a Selected port, a member port must have the same attribute configuration as the aggregate interface. Table 1 describes the attribute configuration.

Table 1 Attribute configuration

Feature	Attribute configuration
VLAN	VLAN attribute settings: · Permitted VLAN IDs. · PVID. · Link type (trunk, hybrid, or access). · PVLAN port type (promiscuous, trunk promiscuous, host, or trunk secondary). · IP subnet-based VLAN configuration. · Protocol-based VLAN configuration. · VLAN tagging mode. For information about VLANs, see "Configuring VLANs."

Feature

Attribute configuration

VLAN

VLAN attribute settings:

· Permitted VLAN IDs.

· PVID.

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

· PVLAN port type (promiscuous, trunk promiscuous, host, or trunk secondary).

· IP subnet-based VLAN configuration.

· Protocol-based VLAN configuration.

· VLAN tagging mode.

For information about VLANs, see "Configuring VLANs."

Protocol configuration

Protocol configuration of a member port does not affect the aggregation state of the member port. MAC address learning and spanning tree settings are examples of the protocol configuration.

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. Dynamic aggregation is implemented through IEEE 802.3ad Link Aggregation Control Protocol (LACP). The local system and the peer system automatically maintain the aggregation states of the member ports. Dynamic link aggregation reduces the administrators' workload.

How static link aggregation works

Reference port selection process

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 varies by following conditions:

· The port is placed in Unselected state if the port and the Selected ports have the same port priority. 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 when the following conditions are met:

¡ The port and the 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

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

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 in 3 seconds after the LACP timeout interval expires, 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.

Load sharing modes for link aggregation groups

In a link aggregation group, traffic can be load shared across the Selected ports based on any of the following modes:

· Per-flow load sharing—Load shares traffic on a per-flow basis. The load sharing mode classifies packets into flows and forwards packets of the same flow on the same link. This mode can be one or any combination of the following traffic classification criteria:

¡ Ingress port.

¡ Source or destination IP address.

¡ Source or destination MAC address.

¡ Source or destination port number.

¡ MPLS label.

¡ Protocol number.

¡ VLAN tag.

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

· Automatic load sharing—Automatically selects a load sharing mode depending on the packet type. For example, the load sharing mode differs between IPv4 packets and Layer 2 packets. This mode is also called flexible load sharing mode.

Ethernet link aggregation tasks at a glance

To configure Ethernet link aggregation, perform the following tasks:

1. Configuring link aggregations

¡ Configuring a manual link aggregation

2. (Optional.) Configuring an aggregate interface

¡ Configuring the description of an aggregate interface

¡ Configuring jumbo frame support

¡ Setting the MTU for a Layer 3 aggregate interface

¡ Setting the expected bandwidth for an aggregate interface

¡ Configuring physical state change suppression on an aggregate interface

¡ Shutting down an aggregate interface

¡ Enabling packet statistics for a Layer 3 aggregate subinterface

¡ Enabling rate statistics for subinterfaces of a Layer 3 aggregate interface

¡ Restoring the default settings for an aggregate interface

3. (Optional.) Adjusting aggregation states of link aggregation member ports

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

¡ Setting the minimum percentage of Selected ports in an aggregation group

¡ Ignoring port speed in setting the aggregation states of member ports

¡ Specifying ignored VLANs for a Layer 2 aggregate interface

To have the system ignore the permit state and tagging mode of a VLAN when it decides Selected ports, perform this task.

4. (Optional.) Configuring load sharing for link aggregation groups

5. (Optional.) Optimizing traffic forwarding

¡ Enabling link-aggregation traffic redirection

This feature redirects traffic on an unavailable Selected port to the remaining available Selected ports of an aggregation group to avoid traffic interruption.

6. (Optional.) Enabling BFD for an aggregation group

Configuring a manual link aggregation

Restrictions and guidelines for aggregation group configuration

Layer 2 aggregation group restrictions

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

Table 4 Features incompatible with Layer 2 aggregation member interfaces

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

‌

Layer 3 aggregation group restrictions

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

Table 5 Features incompatible with Layer 3 aggregation member interfaces

Feature on the interface	Reference
Interface bound to a cross connect	MPLS L2VPN in MPLS Configuration Guide
Interface bound to a VSI	VPLS in MPLS Configuration Guide

‌

Aggregation member port restrictions

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

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.

Attribute and protocol configuration restrictions

Attribute configuration changes made on an aggregate interface are automatically synchronized to all member ports. If the changes fail to be synchronized to a Selected port, the port might change to the Unselected state. To make the port become Selected again, you can change the attribute configurations on the aggregate interface or on 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.

The protocol configurations for an aggregate interface take effect only on the current aggregate interface. The protocol configurations for a member port take effect only when the port leaves its aggregation group.

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.

Configuring a Layer 2 aggregation group

Configuring a Layer 2 static aggregation group

1. Enter system view.

system-view

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 as that interface.

3. Set the aggregation mode to static.

link-aggregation mode static

By default, an aggregation group operates in static aggregation mode.

4. Return to system view.

quit

5. Assign an interface to the Layer 2 aggregation group:

a. Enter Layer 2 Ethernet interface view.

interface interface-type interface-number

b. Assign the interface to the Layer 2 aggregation group.

port link-aggregation group group-id

Repeat these two substeps to assign more interfaces to the aggregation group.

6. (Optional.) Set the port priority of the interface.

link-aggregation port-priority priority

The default port priority of an interface is 32768.

Configuring a Layer 2 dynamic aggregation group

1. Enter system view.

system-view

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 numbered the same as that 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. Return to system view.

quit

6. Assign an interface to the Layer 2 aggregation group:

a. Enter Layer 2 Ethernet interface view.

interface interface-type interface-number

b. Assign the interface to the Layer 2 aggregation group.

port link-aggregation group group-id

Repeat these two substeps to assign more Layer 2 Ethernet interfaces to the aggregation group.

7. Set the LACP operating mode for 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. (Optional.) Set the port priority for the interface.

link-aggregation port-priority priority

The default setting is 32768.

9. (Optional.) Set the short LACP timeout interval (3 seconds) for the interface.

lacp period short

By default, the long LACP timeout interval (90 seconds) is used by the interface.

To avoid traffic interruption during an ISSU, do not set the short LACP timeout interval before performing the ISSU. For more information about ISSU, see Fundamentals Configuration Guide.

Configuring a Layer 3 aggregation group

Configuring a Layer 3 static aggregation group

1. Enter system view.

system-view

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 as that interface.

3. Return to system view.

quit

4. Assign an interface to the Layer 3 aggregation group:

a. Enter Layer 3 Ethernet interface view.

interface interface-type interface-number

b. Assign the interface to the Layer 3 aggregation group.

port link-aggregation group group-id

Repeat these two substeps to assign more interfaces to the aggregation group.

Configuring a Layer 3 dynamic aggregation group

1. Enter system view.

system-view

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

4. Configure the aggregation group to operate in dynamic mode.

link-aggregation mode dynamic

By default, an aggregation group operates in static mode.

5. Return to system view.

quit

6. Assign an interface to the Layer 3 aggregation group:

a. Enter Layer 3 Ethernet interface view.

interface interface-type interface-number

b. Assign the interface to the Layer 3 aggregation group.

port link-aggregation group group-id

Repeat these two substeps to assign more Layer 3 Ethernet interfaces to the aggregation group.

7. Set the LACP operating mode for 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. (Optional.) Set the short LACP timeout interval (3 seconds) for the interface.

lacp period short

By default, the long LACP timeout interval (90 seconds) is used by the interface.

To avoid traffic interruption during an ISSU, do not set the short LACP timeout interval before performing the ISSU. For more information about ISSU, see Fundamentals Configuration Guide.

Configuring a 1+1 backup aggregation group

About 1+1 backup link aggregation

As shown in Figure 4, a 1+1 backup aggregation group is used on a CE that is dualhomed to PEs for high availability of services. A 1+1 backup aggregation group is a static Layer 3 aggregation group that contains one primary member port and one secondary member port. The primary member port is placed in Selected state to forward all traffic, and the secondary member port is placed in Unselected state as a standby.

Figure 4 Application scenarios for 1+1 backup link aggregation

1+1 backup link aggregation tasks at a glance

To configure a 1+1 backup aggregation group, perform the following tasks:

1. Configuring a static 1+1 backup aggregation group

2. (Optional.) Specifying a primary member port

3. (Optional.) Setting the reversion delay

4. (Optional.) Configuring a 1+1 backup aggregation group to place its secondary member port in down state

5. (Optional.) Performing a primary/secondary member port switchover

Configuring a static 1+1 backup aggregation group

Restrictions and guidelines

A 1+1 backup aggregation group can contain a maximum of two member ports.

Procedure

1. Enter system view.

system-view

2. Create a Layer 3 aggregate interface and enter Layer 3 aggregate interface view.

interface route-aggregation interface-number

3. Set the aggregation mode to static 1+1 backup.

link-aggregation mode static backup

4. Return to system view.

quit

5. Assign an interface to the Layer 3 aggregation group:

a. Enter Layer 3 Ethernet interface view.

interface interface-type interface-number

b. Assign the interface to the Layer 3 aggregation group.

port link-aggregation group group-id

Repeat these two substeps to assign more interfaces to the aggregation group.

6. (Optional.) Set the port priority of the interface.

link-aggregation port-priority priority

The default port priority of an interface is 32768.

Specifying a primary member port

About this task

In a 1+1 backup aggregation group, the primary member port is placed in Selected state to forward all traffic, and the secondary member port is placed in Unselected state as a standby. You can specify a primary member port or let the system to select a primary member port. If you specify a primary member port for a 1+1 backup aggregation group, the aggregation group can revert to the primary member port when that port recovers from failure. As a best practice, manually specify a primary member port.

If you do not specify a primary member port for an aggregation group, the system acts as follows:

· Assigns the primary role to the reference port If the member ports join the aggregation group simultaneously.

· Assigns the primary role to the member port that first becomes Selected if the member ports join the aggregation group successively.

Restrictions and guidelines

You cannot perform this task on a port that is not an aggregation group member or is in an aggregation group not operating in 1+1 backup mode.

A 1+1 backup aggregation group can have only one primary member port.

Procedure

1. Enter system view.

system-view

2. Enter Layer 3 Ethernet interface view.

interface interface-type interface-number

3. Assign the primary role to the interface.

link-aggregation primary-port

By default, a member port is not assigned the primary role in a 1+1 backup aggregation group.

Setting the reversion delay

About this task

The reversion delay is the time a 1+1 backup aggregation group must wait before reverting to the primary member port after that port recovers from failure. This timer prevents link flapping from causing frequent primary/secondary member port switchovers.

Restrictions and guidelines

For the reversion delay to take effect on an aggregation group, first configure the aggregation group to operate in 1+1 backup mode and manually specify its primary member port.

Procedure

1. Enter system view.

system-view

2. Enter Layer 3 aggregate interface view.

interface route-aggregation interface-number

3. Set the reversion delay.

link-aggregation reversion delay time-value

By default, a 1+1 backup aggregation group reverts to the primary member port immediately after that port recovers from failure.

Configuring a 1+1 backup aggregation group to place its secondary member port in down state

About this task

If the peer for a 1+1 backup aggregation group is unaware of the member port roles, it might send traffic to the secondary member port, and traffic loss occurs consequently. To prevent traffic loss, configure the aggregation group to place its secondary member port in down state. This allows the peer and local ends to use only up ports to transmit traffic.

Restrictions and guidelines

For this feature to take effect on an aggregation group, first configure the aggregation group to operate in 1+1 backup mode.

Procedure

1. Enter system view.

system-view

2. Enter Layer 3 aggregate interface view.

interface route-aggregation interface-number

3. Configure the aggregation group to place its secondary member port in down state.

link-aggregation secondary-down

By default, the secondary member port in a 1+1 backup aggregation group is in Unselected state.

Performing a primary/secondary member port switchover

About this task

Perform this task to switch member port roles for a 1+1 backup aggregation group whose primary member port is set by the system when the state of peer ports changes.

Restrictions and guidelines

This task might cause traffic loss. Make sure you are fully aware of the impacts of this task when you perform it on a live network.

If the link-aggregation secondary-down command has been executed for a 1+1 backup aggregation group, this task brings up the down secondary member port for it to take over the primary role.

Before you perform this task for a 1+1 backup aggregation group, verify that the following requirements are met:

· The aggregation group contains one Selected port and one Unselected port.

· The primary member port is set by the system.

· The secondary member port can become Selected.

Procedure

1. Enter system view.

system-view

2. Enter Layer 3 aggregate interface view.

interface route-aggregation interface-number

3. Perform a primary/secondary member port switchover.

link-aggregation switchover

Configuring an aggregate interface

Most settings 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

About this task

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

Procedure

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. Configure the interface description.

description text

By default, the description of an interface is interface-name Interface.

Configuring jumbo frame support

About this task

An aggregate interface might receive frames larger than 9732 bytes during high-throughput data exchanges, such as file transfers. These frames are called jumbo frames.

How an aggregate interface processes jumbo frames depends on whether jumbo frame support is enabled on the interface.

· If configured to deny jumbo frames, the aggregate interface discards jumbo frames.

· If enabled with jumbo frame support, the aggregate interface performs the following operations:

¡ Processes the jumbo frames that are within the allowed length.

¡ Discards the jumbo frames that exceed the allowed length.

Procedure

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

interface route-aggregation interface-number

3. Configure jumbo frame support.

jumboframe enable [ size ]

By default, an aggregate interface allows jumbo frames with a maximum length of 9732 bytes to pass through.

If you execute this command multiple times, the most recent configuration takes effect.

Setting the MTU for a Layer 3 aggregate interface

About this task

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

Restrictions and guidelines

When you set the MTU of a Layer 3 aggregate interface, you can specify the spread keyword to issue the MTU setting to all its subinterfaces. If you do not specify the spread keyword, the MTU setting takes effect only on the Layer 3 aggregate interface.

On an aggregate subinterface, the MTU set in subinterface view takes precedence over the MTU inherited from the aggregate interface.

Procedure

1. Enter system view.

system-view

2. Enter Layer 3 aggregate interface or subinterface view.

interface route-aggregation { interface-number | interface-number.subnumber }

3. Set the MTU.

¡ Set the MTU of the Layer 3 aggregate interface or subinterface.

mtu size

¡ Set the MTU of the Layer 3 aggregate interface and issue the MTU to all its subinterfaces.

mtu size spread

This command is available only in Layer 3 aggregate interface view.

The default setting is 1500 bytes.

Setting the expected bandwidth for an aggregate interface

About this task

Expected bandwidth is an informational parameter used only by higher-layer protocols for calculation. You cannot adjust the actual bandwidth of an interface by performing this task.

Procedure

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. 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 physical state change suppression on an aggregate interface

About this task

The physical link state of an aggregate interface is either up or down. Each time the physical link of an interface comes up or goes down, the system immediately reports the change to the CPU. The CPU then performs the following operations:

· Notifies the upper-layer protocol modules (such as routing and forwarding modules) of the change for guiding packet forwarding.

· Automatically generates traps and logs to inform users to take the correct actions.

To prevent frequent physical link flapping from affecting system performance, configure physical state change suppression. You can configure this feature to suppress only link-down events, only link-up events, or both. If an event of the specified type still exists when the suppression interval expires, the system reports the event to the CPU.

Restrictions and guidelines

When you configure suppression interval settings on an aggregate interface, make sure its peer interface is also an aggregate interface in the same aggregation mode. In addition, the suppression interval settings must be the same between the peer aggregate interfaces.

As a best practice, use the default setting in an S-MLAG environment.

On an interface, you can configure different suppression intervals for link-up and link-down events. If you execute the link-delay command multiple times for link-up or link-down events, the most recent configuration takes effect.

Procedure

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

interface route-aggregation interface-number

3. Configure physical state change suppression.

link-delay { down | up } [ msec ] delay-time

By default, each time the physical link of an aggregate interface goes up or comes down, the system immediately reports the change to the CPU.

Shutting down an aggregate interface

Restrictions and guidelines

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 its Selected ports become Unselected and all member ports go down.

· When an aggregate interface is brought up, the aggregation states of all its member ports are recalculated.

When you shut down or bring up a Layer 3 aggregate interface, all its aggregate subinterfaces are also shut down or brought up. Shutting down or bringing up a Layer 3 aggregate subinterface does not affect the state of the main aggregate interface.

Procedure

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. Shut down the interface.

shutdown

By default, an interface is not manually shut down.

Enabling packet statistics for a Layer 3 aggregate subinterface

Restrictions and guidelines

The packet statistics feature is CPU intensive. When you use this command for Layer 3 aggregate subinterfaces, make sure you fully understand its impact on system performance.

You can use the flow-interval command to adjust the interval at which the statistics are polled. To conserve hardware resources, increase the polling interval. For more information about this command, see Ethernet interface commands in Interface Command Reference.

Procedure

1. Enter system view.

system-view

2. Enter Layer 3 aggregate subinterface view.

interface route-aggregation interface-number.subnumber

3. Enable packet statistics for the Layer 3 aggregate subinterface.

traffic-statistic enable

By default, the packet statistics feature is disabled for a Layer 3 aggregate subinterface.

4. (Optional.) Display the packet statistics for the Layer 3 aggregate subinterface.

display interface route-aggregation interface-number.subnumber

In the command output, the Input and Output fields display packet statistics.

Enabling rate statistics for subinterfaces of a Layer 3 aggregate interface

Restrictions and guidelines

Rate statistics collection for Layer 3 aggregate subinterfaces is resource intensive. When you use this feature on a live network, make sure you fully understand its impact.

This feature enables the device to periodically refresh rate statistics for the subinterfaces of a Layer 3 aggregate interface. The rate statistics are available in two statistics polling intervals after you enable this feature. To set the statistics polling interval, use the flow-interval command.

Procedure

1. Enter system view.

system-view

2. Enter Layer 3 aggregate interface view.

interface route-aggregation interface-number

3. Enable rate statistics collection for the subinterfaces of the Layer 3 aggregate interface.

sub-interface rate-statistic

By default, rate statistics collection is disabled for Layer 3 aggregate subinterfaces.

4. (Optional.) Display rate statistics for a Layer 3 aggregate subinterface.

display interface route-aggregation interface-number.subnumber

Restoring the default settings for an aggregate interface

Restrictions and guidelines

CAUTION:

The default command might interrupt ongoing network services. Make sure you are fully aware of the impacts of this command when you execute it on a live network.

The default command might fail to restore the default settings for some commands for reasons such as command dependencies and system restrictions.

To resolve this issue:

1. Use the display this command in interface view to identify these commands.

2. Use their undo forms or follow the command reference to restore their default settings.

3. If the restoration attempt still fails, follow the error message instructions to resolve the issue.

Procedure

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

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

About this task

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.

Restrictions and guidelines

On a static aggregate link, you must set the maximum number of Selected ports to the same value at its two ends.

On a dynamic aggregate link, the two ends of the aggregate link compare their maximum Selected port number settings and use the smaller value.

For an aggregation group, the maximum number of Selected ports must be equal to or higher than the minimum number of Selected ports.

Procedure

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

interface route-aggregation interface-number

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 is the hardware limitation.

Setting the minimum percentage of Selected ports in an aggregation group

About this task

The minimum number of Selected ports in an aggregation group equals the higher one of the following values:

· The number of member ports in the aggregation group multiplied by the minimum percentage of Selected ports.

· The limit set by using the link-aggregation selected-port minimum command.

Restrictions and guidelines

The system calculates the minimum percentage of Selected ports based on the total number of member ports in an aggregation group, including the member ports on an absent card. To view the total number of member ports in an aggregation group, execute the display link-aggregation verbose all-configuration command.

For the device to calculate the minimum number of Selected ports correctly, save the running configuration and reboot the device after you execute the link-aggregation selected-port minimum percentage command.

After you perform this task, aggregate interface flapping might occur when ports join or leave an aggregation group. Make sure you are fully aware of the impacts of this command when you execute it on a live network.

You must set the same minimum percentage of Selected ports at the two ends of an aggregate link.

Procedure

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.

interface route-aggregation { interface-number }

3. Set the minimum percentage of Selected ports.

link-aggregation selected-port minimum percentage number

By default, the minimum percentage of Selected ports is not set for an aggregation group.

Ignoring port speed in setting the aggregation states of member ports

About this task

This feature allows ports at a different speed than the reference port to become Selected by ignoring the port speed during operational key calculation.

You must configure the same port speed ignoring setting at the two ends of a static configuration to ensure that the peer ports are placed in the same aggregation state. This requirement does not apply to a dynamic aggregation, on which the two ends negotiate the aggregation state of the peer ports automatically.

Restriction and guidelines

Make sure you are fully aware of the impacts of this feature when you use it on a live network.

· When you execute the link-aggregation ignore speed command or its undo form, the operational key changes and the aggregate interface flaps temporarily.

· The link-aggregation ignore speed command might cause traffic loss on Selected ports operating at a speed lower than the other Selected ports in the aggregation group when traffic is distributed among the ports.

Procedure

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

interface route-aggregation interface-number

3. Configure the aggregation group to ignore port speed in setting the aggregation states of member ports.

link-aggregation ignore speed

By default, an aggregation group does not ignore port speed in setting the aggregation states of member ports.

Specifying ignored VLANs for a Layer 2 aggregate interface

About this task

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

Prerequisites

Make sure the link type of the Layer 2 aggregate interface is hybrid or trunk.

Procedure

1. Enter system view.

system-view

2. Enter Layer 2 aggregate interface view.

interface bridge-aggregation interface-number

3. Specify ignored VLANs.

link-aggregation ignore vlan vlan-id-list

By default, a Layer 2 aggregate interface does not ignore any VLANs.

Configuring load sharing for link aggregation groups

Setting load sharing modes for link aggregation groups

Restrictions and guidelines

This task is available only on the default MDC. Non-default MDCs use the global load sharing mode set on the default MDC.

When load sharing traffic, the device always uses the source and destination MAC addresses, IP addresses, or port numbers as hash keys in pairs. If you specify one of the hash keys in a pair, the device will use both hash keys in that pair for load sharing. For example, if you specify the source MAC address, the device uses both source and destination MAC addresses for load sharing.

Setting the global link-aggregation load sharing mode

1. Enter system view.

system-view

2. Set the global link-aggregation load sharing mode.

link-aggregation global load-sharing mode { { destination-ip | destination-mac | destination-port | mpls-label1 | mpls-label2 | source-ip | source-mac | source-port } * | per-packet }

By default, the device selects a load sharing mode for packets depending on their packet type, as follows:

¡ Non-MPLS packets are load shared based on the source and destination IP addresses and source and destination port numbers.

¡ MPLS packets are load shared based on the source and destination IP addresses, source and destination port numbers, and MPLS labels.

Enabling link-aggregation traffic redirection

About link-aggregation traffic redirection

This feature operates on dynamic link aggregation groups. It redirects traffic on a Selected port to the remaining available Selected ports of an aggregation group if one of the following events occurs:

· The port is shut down by using the shutdown command.

· The slot that hosts the port reboots, but the aggregation group contains Selected ports on other slots.

NOTE:

The device does not redirect traffic to member ports that become Selected during the traffic redirection process.

This feature ensures zero packet loss for known unicast traffic, but does not protect unknown unicast traffic.

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.

Restrictions and guidelines for link-aggregation traffic redirection

Link-aggregation traffic redirection applies only to dynamic link aggregation groups.

To prevent traffic interruption, enable link-aggregation traffic redirection at both ends of the aggregate link.

This feature functions by adding an extended TLV in LACPDUs, which might not be supported by some third-party devices. As a best practice to ensure the functionality of this feature in a multivendor aggregation environment, enable link-aggregation traffic redirection on a per-aggregate-interface basis instead of globally.

Enabling link-aggregation traffic redirection globally

1. Enter system view.

system-view

2. Enable link-aggregation traffic redirection globally.

link-aggregation lacp traffic-redirect-notification enable

By default, link-aggregation traffic redirection is disabled globally.

Enabling link-aggregation traffic redirection for an aggregation group

1. Enter system view.

system-view

2. Enter aggregate interface view.

¡ Enter Layer 3 aggregate interface view.

interface route-aggregation interface-number

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.

Enabling BFD for an aggregation group

About this task

You can use BFD to 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. BFD operates differently depending on the aggregation mode.

· BFD on a 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 then placed in Unselected state. However, the BFD session between the local and peer ports remains, and the local port keeps sending BFD packets. When BFD on the local port receives packets from the peer port upon link recovery, BFD notifies the Ethernet link aggregation module that the peer port is reachable. Then, the local port is placed in Selected state again. This mechanism ensures that the local and peer ports of a static aggregate link have the same aggregation state.

· BFD on a dynamic aggregation—When BFD detects a link failure, BFD notifies the Ethernet link aggregation module that the peer port is unreachable. At the same time, BFD clears the session and stops sending BFD packets. When the local port is placed in Selected state again upon link recovery, the local port establishes a new session with the peer port and 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.

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

Restrictions and guidelines

When you enable BFD for an aggregation group, follow these restrictions and guidelines:

· Make sure the source and destination IP addresses are reversed 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 source and destination IP addresses cannot be the same.

· The BFD parameters configured on an aggregate interface take effect on all BFD sessions established by the member ports in its aggregation group. BFD on a link aggregation supports only control packet mode for session establishment and maintenance. The two ends of an established BFD session can only operate in Asynchronous mode.

· As a best practice, do not configure BFD for any protocols 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.

· If both IPv4 and IPv6 BFD sessions exist on an aggregate interface, the device places the aggregation member ports in Unselected state when either IPv4 or IPv6 BFD detects a link failure.

Procedure

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

interface route-aggregation interface-number

3. Enable BFD compatible mode.

link-aggregation bfd-compatible enable

By default, BFD compatible mode is disabled on aggregate interfaces. Perform this step if the remote aggregation system is a third-party device that implements BFD differently from the local end.

4. Enable BFD.

link-aggregation bfd { ipv4 | ipv6 } source { ipv4-address | ipv6-address } destination { ipv4-address | ipv6-address }

By default, BFD is disabled for an aggregation group.

Display and maintenance commands for Ethernet link aggregation

Execute display commands in any view and reset commands in user view.

Task	Command
Display information about 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 link-aggregation load sharing modes.	display link-aggregation load-sharing mode
Display detailed link aggregation information about 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 ] ] [ all-configuration ]
Clear statistics for the specified aggregate interfaces.	reset counters interface [ bridge-aggregation \| route-aggregation [ interface-number ] ]
Clear LACP statistics for the specified link aggregation member ports.	reset lacp statistics [ interface interface-list ]

Ethernet link aggregation configuration examples

Example: Configuring a Layer 2 static aggregation group

Network configuration

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

‌

Procedure

1. Configure Device A:

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

<DeviceA> system-view

[DeviceA] vlan 10

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

[DeviceA-vlan10] quit

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

[DeviceA] vlan 20

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

[DeviceA] interface gigabitethernet 1/2/0/1

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

[DeviceA-GigabitEthernet1/2/0/1] quit

[DeviceA] interface gigabitethernet 1/2/0/2

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

[DeviceA-GigabitEthernet1/2/0/2] quit

[DeviceA] interface gigabitethernet 1/2/0/3

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

[DeviceA-GigabitEthernet1/2/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

Port: A -- Auto

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/2/0/1 S 32768 1

GE1/2/0/2 S 32768 1

GE1/2/0/3 S 32768 1

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

Example: Configuring a Layer 2 dynamic aggregation group

Network configuration

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

‌

Procedure

1. Configure Device A:

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

<DeviceA> system-view

[DeviceA] vlan 10

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

[DeviceA-vlan10] quit

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

[DeviceA] vlan 20

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

[DeviceA] interface gigabitethernet 1/2/0/1

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

[DeviceA-GigabitEthernet1/2/0/1] quit

[DeviceA] interface gigabitethernet 1/2/0/2

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

[DeviceA-GigabitEthernet1/2/0/2] quit

[DeviceA] interface gigabitethernet 1/2/0/3

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

[DeviceA-GigabitEthernet1/2/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

Port: A -- Auto

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 Index Oper-Key Flag

GE1/2/0/1 S 32768 11 1 {ACDEF}

GE1/2/0/2 S 32768 12 1 {ACDEF}

GE1/2/0/3 S 32768 13 1 {ACDEF}

Remote:

Actor Priority Index Oper-Key SystemID Flag

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

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

GE1/2/0/3 32768 83 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.

Example: Configuring a Layer 3 static aggregation group

Network configuration

On the network shown in Figure 7, 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 7 Network diagram

‌

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

[DeviceA] interface gigabitethernet 1/2/0/1

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

[DeviceA-GigabitEthernet1/2/0/1] quit

[DeviceA] interface gigabitethernet 1/2/0/2

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

[DeviceA-GigabitEthernet1/2/0/2] quit

[DeviceA] interface gigabitethernet 1/2/0/3

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

[DeviceA-GigabitEthernet1/2/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

Port: A -- Auto

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/2/0/1 S 32768 1

GE1/2/0/2 S 32768 1

GE1/2/0/3 S 32768 1

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

Example: Configuring a Layer 3 dynamic aggregation group

Network configuration

On the network shown in Figure 8, 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 8 Network diagram

‌

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

[DeviceA] interface gigabitethernet 1/2/0/1

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

[DeviceA-GigabitEthernet1/2/0/1] quit

[DeviceA] interface gigabitethernet 1/2/0/2

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

[DeviceA-GigabitEthernet1/2/0/2] quit

[DeviceA] interface gigabitethernet 1/2/0/3

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

[DeviceA-GigabitEthernet1/2/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

Port: A -- Auto

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 Index Oper-Key Flag

GE1/2/0/1 S 32768 11 1 {ACDEF}

GE1/2/0/2 S 32768 12 1 {ACDEF}

GE1/2/0/3 S 32768 13 1 {ACDEF}

Remote:

Actor Priority Index Oper-Key SystemID Flag

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

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

GE1/2/0/3 32768 83 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.

04-Layer 2—LAN Switching Configuration Guide

Aggregate interface types

Configuration types

Attribute configuration

Protocol configuration

Reference port selection process

About LACP

LACP functions

LACP operating modes

LACP priorities

LACP timeout interval

Load sharing modes for link aggregation groups

Layer 2 aggregation group restrictions

Layer 3 aggregation group restrictions

Aggregation member port restrictions

Attribute and protocol configuration restrictions

Configuration consistency requirements

Configuring a Layer 3 static aggregation group

Restrictions and guidelines

Procedure

About this task

Restrictions and guidelines

Procedure

About this task

Restrictions and guidelines

Procedure

About this task

Restrictions and guidelines

Procedure

About this task

Restrictions and guidelines

Procedure

About this task

Procedure

About this task

Procedure

About this task

Restrictions and guidelines

Procedure

Setting the expected bandwidth for an aggregate interface

About this task

Procedure

About this task

Restrictions and guidelines

Procedure

Restrictions and guidelines

Procedure

Restrictions and guidelines

Procedure

Restrictions and guidelines

Procedure

Restrictions and guidelines

Procedure

About this task

Restrictions and guidelines

Procedure

About this task

Restrictions and guidelines

Procedure

About this task

Restriction and guidelines

Procedure

About this task

Prerequisites

Procedure

Restrictions and guidelines

Setting the global link-aggregation load sharing mode

About this task

Restrictions and guidelines

Procedure

Network configuration

Procedure

Verifying the configuration

Network configuration

Procedure

Verifying the configuration

Example: Configuring a Layer 3 static aggregation group

Network configuration

Procedure

Verifying the configuration