- Table of Contents
-
- 04-Layer 2 - LAN Switching Configuration Guide
- 00-Preface
- 01-MAC address table configuration
- 02-Ethernet link aggregation configuration
- 03-Port isolation configuration
- 04-Spanning tree configuration
- 05-Loop detection configuration
- 06-VLAN configuration
- 07-QinQ configuration
- 08-VLAN mapping configuration
- 09-LLDP configuration
Title | Size | Download |
---|---|---|
02-Ethernet link aggregation configuration | 299.43 KB |
Contents
Configuring Ethernet link aggregation
Aggregation group, member port, and aggregate interface
Aggregation states of member ports in an aggregation group
Aggregating links in static mode
Setting the aggregation state of each member port
Aggregating links in dynamic mode
How dynamic link aggregation works
Load sharing criteria for link aggregation groups
Ethernet link aggregation configuration task list
Configuring an aggregation group
Configuring a static aggregation group
Configuring a dynamic aggregation group
Configuring an aggregate interface
Configuring the description of an aggregate interface
Configuring the MTU of a Layer 3 aggregate interface
Setting the minimum and maximum numbers of Selected ports for an aggregation group
Shutting down an aggregate interface
Restoring the default settings for an aggregate interface
Configuring the global link-aggregation load sharing criteria
Enhancing the Selected port capacity for link aggregation in IRF mode
Displaying and maintaining Ethernet link aggregation
Ethernet link aggregation configuration examples
Layer 2 static aggregation configuration example
Layer 2 dynamic aggregation configuration example
Layer 3 static aggregation configuration example
Layer 3 dynamic aggregation configuration example
The switch does not support Layer 3 Ethernet interfaces/subinterfaces or Layer 3 aggregate interfaces/subinterfaces when the system is operating in standard mode. For more information about system operating modes, see Fundamentals Configuration Guide.
When the switch operating in IRF mode is enabled with enhanced IRF mode, it does not support creating Layer 3 Ethernet interfaces/subinterfaces or Layer 3 aggregate interfaces/subinterfaces. For more information about enhanced IRF mode, see Fundamentals Configuration Guide.
The switch supports a maximum of 240 aggregation groups. An aggregation group supports a maximum number of 12 Selected ports on a single switch. In IRF mode, the maximum number of Selected ports supported by an aggregation group is 12 multiplied by the number of IRF member devices.
Overview
This chapter gives an overview of Ethernet link aggregation and explains how to configure it.
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 be as high as 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
Basic concepts
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. To an upper layer entity that uses the link aggregation service, a link aggregation group appears the same as a single logical link and data traffic is transmitted through the aggregate interface.
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.
Aggregate interfaces have the following types: Layer 2 aggregate interfaces and Layer 3 aggregate interfaces.
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.
On a Layer 3 aggregate interface, you can create subinterfaces.
The port rate of an aggregate interface equals the total rate of its member ports in Selected state, and its duplex mode is the same as 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 either 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 member ports are assigned the same operational key.
Configuration types
Every configuration setting on a port might affect its aggregation state. Port configurations fall into 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 the isolation group to which the port belongs. |
QinQ |
QinQ enable state (enabled/disabled), TPID for VLAN tags. For information about QinQ, see "Configuring QinQ." |
VLAN mapping |
Different types of VLAN mapping configured on the port. For more information about VLAN mapping, see "Configuring VLAN mapping." |
VLAN |
Permitted VLAN IDs, PVID, link type (trunk, hybrid, or access), IP subnet-based VLAN configuration, protocol-based VLAN configuration, VLAN tagging mode. For information about VLAN, see "Configuring VLANs." |
· Protocol configurations—As opposed to attribute configurations, protocol configurations do not affect the aggregation state of the member ports, even if they are different from those on the aggregate interface. MAC address learning and spanning tree settings are examples of protocol configurations.
|
NOTE: The protocol configuration for a member port is effective only when the member port leaves the aggregation group. |
Link aggregation modes
Link aggregation has dynamic and static modes:
· Static aggregation mode—Aggregation is stable. The aggregation state of the member ports are not affected by the peer ports.
· Dynamic aggregation mode—The peering system automatically maintains the aggregation state of the member ports, thus reducing the workload of administrators.
An aggregation group in static mode is called a "static aggregation group" and an aggregation group in dynamic mode is called a "dynamic aggregation group."
Aggregating links in static mode
The static link aggregation process comprises:
· Setting the aggregation state of each member port
Selecting a reference port
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 selects a reference port from the member ports that are in up state with the same attribute configurations as the aggregate interface.
The candidate ports are sorted in the following order:
1. Highest port priority
2. Full duplex/high speed
3. Full duplex/low speed
4. Half duplex/high speed
5. Half duplex/low speed
The candidate port at the top is selected as the reference port. If two ports have the same port priority, duplex mode, and speed, the original Selected port is selected. If more than one such original Selected port exists, the one with the lower port number is selected.
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
|
NOTE: To ensure stable aggregation state and service continuity, do not change port attributes or class-two configurations on any member port. If you need to make this change, make sure you understand its impact on the live network. Any port attribute or class-two configuration change might affect the aggregation state of link aggregation member ports and ongoing traffic. |
Aggregating links in dynamic mode
Dynamic aggregation mode is implemented through IEEE 802.3ad Link Aggregation Control Protocol (LACP).
LACP
LACP uses LACPDUs to exchange aggregation information between LACP-enabled devices.
Each member port in 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. If a device supports LACP extensions, 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 IRF 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.
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 assumes that the peer port has failed.
The LACP timeout interval also determines the LACPDU sending rate of the peer. You can configure the LACP timeout interval as the short timeout interval (3 seconds) or the long timeout interval (90 seconds). If you configure the short timeout interval, the peer sends LACPDUs fast (one LACPDU per second); if you configure the long timeout interval, the peer sends LACPDUs slowly (one LACPDU every 30 seconds).
How dynamic link aggregation works
The dynamic link aggregation process comprises:
· Setting the aggregation state of each member port
Selecting a reference port
The system selects 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. Compare the system IDs. (A system ID comprises the system LACP priority and the system MAC address.) The system with the lower LACP priority value is selected. If LACP priority values are the same, the two systems compare their MAC addresses. The system with the lower MAC address is selected.
2. The system with the smaller system ID selects the port with the smallest port ID as the reference port. (A port ID comprises a port priority and a port number.) The port with the lower priority value is selected. 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 selected, 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:
· A half-duplex member port cannot become a Selected port.
· 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.
· A port that joins a dynamic aggregation group after the Selected port limit has been reached is placed in Selected state if it is more eligible to be selected than a current member port.
Load sharing criteria for link aggregation groups
In a link aggregation group, traffic may be load-shared across the selected member ports based on a set of criteria, depending on your configuration.
The switch supports per-flow load sharing, which classifies traffic flows by one of the following criteria or any combination of them:
· Source MAC address
· Destination MAC address
· Source port number
· Destination port number
· Ingress port
· Source IP address
· Destination IP address
· MPLS label
The packets of the same flow are forwarded on the same link.
Ethernet link aggregation configuration task list
Tasks at a glance |
(Required.) Configuring an aggregation group: |
(Optional.) Configuring an aggregate interface: · Configuring the description of an aggregate interface · Configuring the MTU of a Layer 3 aggregate interface · Setting the minimum and maximum numbers of Selected ports for an aggregation group |
(Optional.) Configuring the global link-aggregation load sharing criteria |
Enhancing the Selected port capacity for link aggregation in IRF mode |
Configuring an aggregation group
This section explains how to configure an aggregation group.
Configuration guidelines
· You cannot assign a port configured with association between AC and cross connection (see MPLS Configuration Guide) to a Layer 2 aggregation group:
· If a port is used as a reflector port for port mirroring, do not assign it to an aggregation group. For more information about reflector ports, see Network Management and Monitoring Configuration Guide.
· Removing an aggregate interface also removes 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
Avoid assigning ports to a static aggregation group that has reached the limit on Selected ports. These ports will be placed in 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: b.
Assign the interface to the specified
Layer 2 aggregation group: |
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: b.
Assign the interface to the specified
Layer 3 aggregation group: |
Repeat these two sub-steps to assign more Layer 3 Ethernet interfaces to the aggregation group. |
Configuring a dynamic aggregation group
To guarantee a successful dynamic aggregation, make sure that 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 may 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: b.
Assign the interface to the specified
Layer 2 aggregation group: |
Repeat these two sub-steps to assign more Layer 2 Ethernet interfaces to the aggregation group. |
7. Configure the port priority for the interface. |
link-aggregation port-priority port-priority |
The default setting is 32768. |
8. Configure 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. Before performing an ISSU, restore the LACP timeout interval for each member port to the default value. For information about ISSU, see Fundamentals Configuration Guide. |
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 may affect the aggregation state 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 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 3 aggregation group. |
a. Enter Layer 3 Ethernet interface view: b.
Assign the interface to the specified
Layer 3 aggregation group: |
Repeat these two sub-steps to assign more Layer 3 Ethernet interfaces to the aggregation group. |
7. Configure the port priority for the interface. |
link-aggregation port-priority port-priority |
The default setting is 32768. |
8. Configure 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. Before performing an ISSU, restore the LACP timeout interval for each member port to the default value. For information about ISSU, see Fundamentals Configuration Guide. |
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 view. |
·
Enter Layer 2
aggregate interface view: ·
Enter Layer 3 aggregate interface or subinterface view: |
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. |
Configuring the MTU of a Layer 3 aggregate interface
Maximum transmission unit (MTU) of an interface affects IP packets fragmentation and reassembly on the interface.
To change the MTU of a Layer 3 aggregate interface:
Step |
Command |
Remarks |
1. Enter system view. |
system-view |
N/A |
2. Enter Layer 3 aggregate interface or subinterface view. |
interface route-aggregation { interface-number | interface-number.subnumber } |
N/A |
3. Configure the MTU of 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.
After you manually configure the maximum number of Selected ports in an aggregation group, the maximum number of Selected ports allowed in the aggregation group is limited by both the configured number and hardware capabilities, that is, the lower value of the two upper limits.
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: ·
Enter Layer 3 aggregate interface view: |
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 depends on the hardware capabilities of the member ports. |
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 view. |
·
Enter Layer 2
aggregate interface view: ·
Enter Layer 3 aggregate interface or subinterface view: |
N/A |
3. Shut down the aggregate interface or subinterface. |
shutdown |
By default, an aggregate interface is down, and a Layer 3 aggregate subinterface is 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 view. |
·
Enter Layer 2
aggregate interface view: ·
Enter Layer 3 aggregate interface or subinterface view: |
3. Restore the default settings for the aggregate interface. |
default |
Configuring the global link-aggregation load sharing criteria
Step |
Command |
Remarks |
1. Enter system view. |
system-view |
N/A |
2. Configure the global link-aggregation load sharing criteria. |
link-aggregation global load-sharing mode { destination-ip | destination-mac | destination-port | ingress-port | mpls-label1 | mpls-label2 | mpls-label3 | source-ip | source-mac | source-port } * |
By default, all global link-aggregation load sharing criteria except ingress-port are enabled. Global link-aggregation load sharing criteria configuration applies to all aggregation groups. |
Enhancing the Selected port capacity for link aggregation in IRF mode
The Selected port capacity for link aggregation refers to the maximum number of Selected ports allowed in an aggregation group. Generally, this capacity is the same in both IRF mode and non-IRF mode. After you enhance the Selected port capacity for link aggregation, each member device in an IRF fabric has the same Selected port capacity as in non-IRF mode, but the Selected port capacity of the IRF fabric increases dramatically following this formula:
Selected port capacity in each aggregation group in the IRF fabric equals Selected port capacity in the aggregation group in non-IRF mode x Number of member devices in the IRF fabric.
Configuration restrictions
· This feature can be configured only on devices in IRF mode.
· If one end is configured with this feature, make sure the other end is also configured with this feature. Otherwise, link aggregation might not work.
· On a device with this feature enabled, do not set the maximum number of Selected ports allowed in an aggregation group to 1.
Configuration procedure
To enhance the Selected port capacity for link aggregation in IRF mode:
Step |
Command |
Remarks |
1. Enter system view. |
system-view |
N/A |
2. Enhance the Selected port capacity for link aggregation in IRF mode. |
link-aggregation irf-enhanced |
By default, the Selected port capacity is not enhanced in IRF mode. |
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 [ description ] ] display interface { bridge-aggregation | route-aggregation } interface-number [ brief [ description ] ] |
Display the local system ID. |
display lacp system-id |
Display the global link-aggregation load sharing criteria. |
display link-aggregation load-sharing mode |
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 specific or all aggregation groups. |
display link-aggregation verbose [ { bridge-aggregation | route-aggregation } [ interface-number ] ] |
Clear LACP statistics for specific or all link aggregation member ports. |
reset lacp statistics [ interface interface-list ] |
Clear statistics for specific or all aggregate interfaces. |
reset counters interface [ { bridge-aggregation | route-aggregation } [ interface-number ] ] |
Ethernet link aggregation configuration examples
By default, Ethernet, VLAN, and aggregate interfaces are down. To configure such an interface, bring the interface up by executing the undo shutdown command.
Layer 2 static aggregation configuration example
Network requirements
As shown in Figure 4, 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.
Configuration procedure
1. Configure Device A:
# Create VLAN 10, and assign port GigabitEthernet 4/0/4 to VLAN 10.
<DeviceA> system-view
[DeviceA] vlan 10
[DeviceA-vlan10] port GigabitEthernet 4/0/4
[DeviceA-vlan10] quit
# Create VLAN 20, and assign port GigabitEthernet 4/0/5 to VLAN 20.
[DeviceA] vlan 20
[DeviceA-vlan20] port GigabitEthernet 4/0/5
[DeviceA-vlan20] quit
# Create and enable Layer 2 aggregate interface Bridge-Aggregation 1.
[DeviceA] interface bridge-aggregation 1
[DeviceA-Bridge-Aggregation1] undo shutdown
[DeviceA-Bridge-Aggregation1] quit
# Assign ports GigabitEthernet 4/0/1 through GigabitEthernet 4/0/3 to link aggregation group 1.
[DeviceA] interface GigabitEthernet 4/0/1
[DeviceA-GigabitEthernet4/0/1] port link-aggregation group 1
[DeviceA-GigabitEthernet4/0/1] quit
[DeviceA] interface GigabitEthernet 4/0/2
[DeviceA-GigabitEthernet4/0/2] port link-aggregation group 1
[DeviceA-GigabitEthernet4/0/2] quit
[DeviceA] interface GigabitEthernet 4/0/3
[DeviceA-GigabitEthernet4/0/3] port link-aggregation group 1
[DeviceA-GigabitEthernet4/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 as you configure Device A. (Details not shown.)
3. Verify the configurations by displaying 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
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
--------------------------------------------------------------------------------
GE4/0/1 S 32768 1
GE4/0/2 S 32768 1
GE4/0/3 S 32768 1
The output shows that link aggregation group 1 is a load-shared Layer 2 static aggregation group and it contains three Selected ports.
Layer 2 dynamic aggregation configuration example
Network requirements
As shown in Figure 5, 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.
Configuration procedure
1. Configure Device A:
# Create VLAN 10, and assign the port GigabitEthernet 4/0/4 to VLAN 10.
<DeviceA> system-view
[DeviceA] vlan 10
[DeviceA-vlan10] port GigabitEthernet 4/0/4
[DeviceA-vlan10] quit
# Create VLAN 20, and assign the port GigabitEthernet 4/0/5 to VLAN 20.
[DeviceA] vlan 20
[DeviceA-vlan20] port GigabitEthernet 4/0/5
[DeviceA-vlan20] quit
# Create and enable Layer 2 aggregate interface Bridge-Aggregation 1, and configure the link aggregation mode as dynamic.
[DeviceA] interface bridge-aggregation 1
[DeviceA-Bridge-Aggregation1] undo shutdown
[DeviceA-Bridge-Aggregation1] link-aggregation mode dynamic
[DeviceA-Bridge-Aggregation1] quit
# Assign ports GigabitEthernet 4/0/1 through GigabitEthernet 4/0/3 to link aggregation group 1.
[DeviceA] interface GigabitEthernet 4/0/1
[DeviceA-GigabitEthernet4/0/1] port link-aggregation group 1
[DeviceA-GigabitEthernet4/0/1] quit
[DeviceA] interface GigabitEthernet 4/0/2
[DeviceA-GigabitEthernet4/0/2] port link-aggregation group 1
[DeviceA-GigabitEthernet4/0/2] quit
[DeviceA] interface GigabitEthernet 4/0/3
[DeviceA-GigabitEthernet4/0/3] port link-aggregation group 1
[DeviceA-GigabitEthernet4/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 as you configure Device A. (Details not shown.)
3. Verify the configurations by displaying 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
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
--------------------------------------------------------------------------------
GE4/0/1 S 32768 1 {ACDEF}
GE4/0/2 S 32768 1 {ACDEF}
GE4/0/3 S 32768 1 {ACDEF}
Remote:
Actor Partner Priority Oper-Key SystemID Flag
--------------------------------------------------------------------------------
GE4/0/1 1 32768 1 0x8000, 000f-e267-57ad {ACDEF}
GE4/0/2 2 32768 1 0x8000, 000f-e267-57ad {ACDEF}
GE4/0/3 3 32768 1 0x8000, 000f-e267-57ad {ACDEF}
The output shows that link aggregation group 1 is a load-shared Layer 2 dynamic aggregation group and it contains three Selected ports.
Layer 3 static aggregation configuration example
Network requirements
As shown in Figure 6, configure a Layer 3 static aggregation group on both Device A and Device B and configure IP addresses and subnet masks for the corresponding Layer 3 aggregate interfaces.
Configuration procedure
1. Configure Device A:
# Create and enable 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] undo shutdown
[DeviceA-Route-Aggregation1] ip address 192.168.1.1 24
[DeviceA-Route-Aggregation1] quit
# Assign Layer 3 Ethernet interfaces GigabitEthernet 3/0/1 through GigabitEthernet 3/0/3 to aggregation group 1.
[DeviceA] interface GigabitEthernet 3/0/1
[DeviceA-GigabitEthernet3/0/1] port link-mode route
[DeviceA-GigabitEthernet3/0/1] port link-aggregation group 1
[DeviceA-GigabitEthernet3/0/1] quit
[DeviceA] interface GigabitEthernet 3/0/2
[DeviceA-GigabitEthernet3/0/2] port link-mode route
[DeviceA-GigabitEthernet3/0/2] port link-aggregation group 1
[DeviceA-GigabitEthernet3/0/2] quit
[DeviceA] interface GigabitEthernet 3/0/3
[DeviceA-GigabitEthernet3/0/3] port link-mode route
[DeviceA-GigabitEthernet3/0/3] port link-aggregation group 1
[DeviceA-GigabitEthernet3/0/3] quit
2. Configure Device B in the same way as you configure Device A. (Details not shown.)
3. Verify the configurations by displaying 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
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
--------------------------------------------------------------------------------
GE3/0/1 S 32768 1
GE3/0/2 S 32768 1
GE3/0/3 S 32768 1
The output shows that link aggregation group 1 is a load-shared Layer 3 static aggregation group that contains three Selected ports.
Layer 3 dynamic aggregation configuration example
Network requirements
As shown in Figure 7, configure a Layer 3 dynamic aggregation group on both Device A and Device B and configure IP addresses and subnet masks for the corresponding Layer 3 aggregate interfaces.
Configuration procedure
1. Configure Device A:
# Create and enable Layer 3 aggregate interface Route-Aggregation 1, configure the link aggregation mode as dynamic, and configure an IP address and subnet mask for the aggregate interface.
<DeviceA> system-view
[DeviceA] interface route-aggregation 1
[DeviceA-Route-Aggregation1] undo shutdown
[DeviceA-Route-Aggregation1] link-aggregation mode dynamic
[DeviceA-Route-Aggregation1] ip address 192.168.1.1 24
[DeviceA-Route-Aggregation1] quit
# Assign Layer 3 Ethernet interfaces GigabitEthernet 3/0/1 through GigabitEthernet 3/0/3 to aggregation group 1.
[DeviceA] interface GigabitEthernet 3/0/1
[DeviceA-GigabitEthernet3/0/1] port link-mode route
[DeviceA-GigabitEthernet3/0/1] port link-aggregation group 1
[DeviceA-GigabitEthernet3/0/1] quit
[DeviceA] interface GigabitEthernet 3/0/2
[DeviceA-GigabitEthernet3/0/2] port link-mode route
[DeviceA-GigabitEthernet3/0/2] port link-aggregation group 1
[DeviceA-GigabitEthernet3/0/2] quit
[DeviceA] interface GigabitEthernet 3/0/3
[DeviceA-GigabitEthernet3/0/3] port link-mode route
[DeviceA-GigabitEthernet3/0/3] port link-aggregation group 1
[DeviceA-GigabitEthernet3/0/3] quit
2. Configure Device B in the same way as you configure Device A. (Details not shown.)
3. Verify the configurations by displaying 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
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
--------------------------------------------------------------------------------
GE3/0/1 S 32768 1 {ACDEF}
GE3/0/2 S 32768 1 {ACDEF}
GE3/0/3 S 32768 1 {ACDEF}
Remote:
Actor Partner Priority Oper-Key SystemID Flag
--------------------------------------------------------------------------------
GE3/0/1 1 32768 1 0x8000, 000f-e267-57ad {ACDEF}
GE3/0/2 2 32768 1 0x8000, 000f-e267-57ad {ACDEF}
GE3/0/3 3 32768 1 0x8000, 000f-e267-57ad {ACDEF}
The output shows that link aggregation group 1 is a load-shared Layer 3 dynamic aggregation group and it contains three Selected ports.