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 links. In an aggregate link, traffic is distributed across the member ports.

· Improved link reliability. The member ports dynamically back up one another. When a member port fails, its traffic is automatically switched to other member ports.

As shown in Figure 1, Device A and Device B are connected by three physical Ethernet links. These physical Ethernet links are combined into an aggregate link called link aggregation 1. The bandwidth of this aggregate link can reach up to the total bandwidth of the three physical Ethernet links. At the same time, the three Ethernet links back up one another. When a physical Ethernet link fails, the traffic previously carried on the failed link is switched to the other two links.

Figure 1 Ethernet link aggregation diagram

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. These Ethernet interfaces are called member ports of the aggregation group. Each aggregation group has a corresponding logical interface (called an aggregate interface).

Aggregate interfaces include Layer 2 aggregate interfaces and Layer 3 aggregate interfaces.

When you create an aggregate interface, the device automatically creates an aggregation group of the same type and number as the aggregate interface. For example, when you create aggregate interface 1, aggregation group 1 is created.

You can assign Layer 2 Ethernet interfaces only to a Layer 2 aggregation group, and Layer 3 Ethernet interfaces only to a Layer 3 aggregation group.

Layer 2 aggregation groups include the following types:

· Generic Layer 2 aggregation group—Corresponds to a generic Layer 2 aggregate interface. You can create up to 240 generic Layer 2 aggregation groups on a device in standalone mode or on an IRF fabric. For a device in standalone mode, the maximum number of Selected ports in a generic Layer 2 aggregation group is 12. For an IRF fabric, the maximum number of Selected ports in a generic Layer 2 aggregation group is identical to 12 multiplied by the number of member devices.

· Lite Layer 2 aggregation group—Corresponds to a lite Layer 2 aggregate interface, and it is configurable only in IRF mode. An IRF fabric supports up to 1024 lite Layer 2 aggregation groups. Each IRF member device can have a maximum of one Selected port in a lite Layer 2 aggregation group. The maximum number of Selected ports in a lite Layer 2 aggregation group is identical to the number of member devices.

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

You can create up to 240 Layer 3 aggregation groups on a device in standalone mode or on an IRF fabric. For a device in standalone mode, the maximum number of Selected ports in a Layer 3 aggregation group is 12. For an IRF fabric, the maximum number of Selected ports in a Layer 3 aggregation group is identical to 12 multiplied by the number of member devices.

You cannot create Layer 3 Ethernet interfaces or subinterfaces, or Layer 3 aggregate interfaces or subinterfaces in the following cases:

· The system is operating in standard mode. For more information about switch's operating modes, see Fundamentals Configuration Guide.

· The switch is operating in IRF mode and the enhanced IRF mode is enabled. For more information about IRF and the enhanced IRF mode, see Virtual Technologies Configuration Guide.

The port rate of an aggregate interface equals the total rate of its Selected member ports. Its duplex mode is the same as that of the Selected member ports. For more information about the states of member ports in an aggregation group, see "Aggregation states of member ports in an aggregation group."

Aggregation states of member ports in an aggregation group

A member port in an aggregation group can be in any of the following aggregation states:

· Selected—A Selected port can forward traffic.

· Unselected—An Unselected port cannot forward traffic.

· Individual—An Individual port can forward traffic as a normal physical port. A port is placed in the Individual state when the following conditions exist:

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

¡ The port has not received LACPDUs from its peer port.

Operational key

When aggregating ports, the system automatically assigns each port an operational key based on port information, such as port rate and duplex mode. Any changes to this information trigger a recalculation of the operational key.

In an aggregation group, all Selected ports are assigned the same operational key.

Configuration types

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

· Attribute configurations—To become a Selected port, a member port must have the same attribute configurations as the aggregate interface. Table 1 describes the attribute configurations.

Attribute configurations made on an aggregate interface are automatically synchronized to all member ports. These configurations are retained on the member ports even after the aggregate interface is removed.

Any attribute configuration changes might affect the aggregation state of link aggregation member ports and running services. The system displays a warning message every time you try to change an attribute configuration setting on a member port.

Table 1 Attribute configurations

Feature	Considerations
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, and VLAN transparent transmission. For information about QinQ, see "Configuring QinQ."
VLAN	VLAN attribute configurations include: · 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—Protocol configurations do not affect the aggregation state of the member ports. 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

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 state of the member ports in a static aggregation group are not affected by the peer ports.

· Dynamic—An aggregation group in dynamic mode is called a dynamic aggregation group. The local system and the peer system automatically maintain the aggregation state of the member ports, which reduces the administrators' workload.

Aggregating links in static mode

Choosing 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 chooses 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 chosen as the reference port. If two ports have the same port priority, duplex mode, and speed, the original Selected port is chosen. If more than one such original Selected port exists, the one with the smaller port number is chosen.

Setting the aggregation state of each member port

After a static aggregation group reaches the limit on Selected ports, ports attempting to join the group are put in Unselected state. This prevents traffic interruption on the existing Selected ports.

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

NOTE:

Any operational key or attribute configuration changes might affect the aggregation state of link aggregation member ports. To ensure stable aggregation state and service continuity, do not change the operational key or attribute configurations on any member ports.

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 the Selected state.

LACP functions

LACP offers basic LACP functions and extended LACP functions, as described in Table 2.

Table 2 Basic and extended LACP functions

Category	Description
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. A device can participate in LACP MAD as either an IRF member device or an intermediate device. For more information about IRF and the LACP MAD mechanism, see Virtual Technologies Configuration Guide.

LACP 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 the port 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 port state accordingly.
Port priority	Determines the likelihood of a member port to be selected 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 port state accordingly.

Port priority

Determines the likelihood of a member port to be selected 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 does not receive LACPDUs from the peer within the LACP timeout interval, the member port considers the peer as failed.

The LACP timeout interval also determines the LACPDU sending rate of the peer. LACP timeout intervals include the following types:

· Short timeout interval—3 seconds. If you configure the short timeout interval, the peer sends one LACPDU per second.

· Long timeout interval—90 seconds. If you configure the long timeout interval, the peer sends one LACPDU every 30 seconds.

How dynamic link aggregation works

Choosing a reference port

The system chooses a reference port from the member ports that are in up state and have the same attribute configurations as the aggregate interface. A Selected port must have the same operational key and attribute configurations as the reference port.

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

1. The two systems compare their system IDs to 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 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 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

Meanwhile, the system with the higher system ID is aware of the aggregation state changes on the peer system. The 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:

· Half-duplex ports cannot become the Selected ports in a dynamic link aggregation group.

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

· When the aggregation state of a local port changes in a dynamic aggregation group, the aggregation state of the peer port also changes.

· After the Selected port limit has been reached, a port joining the aggregation group is placed in the Selected state if it is more eligible than a current member port.

Edge aggregate interface

You can configure an edge aggregate interface to connect a network device to a server when the device and the server are two ends of a dynamic aggregate link. During the server reboot process, the device cannot receive LACPDUs from the server (the peer system). This feature enables the aggregation member ports on the device to forward packets from the server during the server reboot process.

Without this feature, the member ports on the device are placed in the Unselected state, and the ports discard packets from the server during the server reboot process.

An edge aggregate interface takes effect only when it is configured on an aggregate interface corresponding to a dynamic aggregation group.

After the server reboot, the device can receive LACPDUs from the server. Then, link aggregation between the device and the server operates correctly.

Load sharing modes for link aggregation groups

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

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

¡ Source or destination MAC address.

¡ Source or destination port number.

¡ Ingress port.

¡ Source or destination IP address.

¡ MPLS label.

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

Ethernet link aggregation configuration task list

Tasks at a glance
(Required.) Configuring an aggregation group: · Configuring a static aggregation group · Configuring a dynamic aggregation group
(Optional.) Configuring an aggregate interface: · Setting the description for an aggregate interface · Specifying ignored VLANs for a Layer 2 aggregate interface · Setting the MTU for a Layer 3 aggregate interface · Setting the minimum and maximum numbers of Selected ports for an aggregation group · Setting the expected bandwidth for an aggregate interface · Configuring an edge aggregate interface · Shutting down an aggregate interface · Restoring the default settings for an aggregate interface
(Optional.) Configuring link-aggregation load sharing

Configuring an aggregation group

This section explains how to configure an aggregation group.

Configuration restrictions and guidelines

When you configure an aggregation group, follow these restrictions and guidelines:

· Do not use the link-aggregation mode dynamic or undo link-aggregation mode command to switch the link aggregation mode of an aggregation group containing Selected ports. Otherwise, traffic might be forwarded incorrectly. You can identify the Selected state of member ports by using the display link-aggregation summary command. H3C recommends you use the shutdown command to shut down an aggregate interface before switching the link aggregation mode.

· You cannot assign a port to an aggregation group if an AC is bound to a cross-connect on the port (see MPLS Configuration Guide).

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

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

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

When you configure a lite Layer 2 aggregation group, also follow these restrictions and guidelines:

· Make sure a port has no manually configured MAC address entries before assigning the port to a lite Layer 2 aggregation group.

· Do not manually modify or remove the MAC address entries of a member port in a lite Layer 2 aggregation group. Otherwise, traffic cannot be forwarded correctly.

· In IRF mode, do not configure a lite Layer 2 aggregation group and an isolation group on the same device. Otherwise, traffic cannot be forwarded correctly. For more information about port isolation, see "Configuring port isolation."

· You cannot enable EVI on a member port in a lite Layer 2 aggregation group. Moreover, do not assign a transport-facing physical interface of an EVI tunnel to a lite Layer 2 aggregation group. Otherwise, traffic cannot be forwarded through the EVI tunnel. For more information about EVI, see EVI Configuration Guide.

· A lite Layer 2 aggregate interface cannot operate as an OpenFlow port. For more information about OpenFlow, see OpenFlow Configuration Guide.

Configuring a static aggregation group

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

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

Configuring a Layer 2 static aggregation group

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Create a Layer 2 aggregate interface and enter Layer 2 aggregate interface view.	interface bridge-aggregation interface-number [ lite ]	When you create a Layer 2 aggregate interface, the system automatically creates a Layer 2 static aggregation group numbered the same. If you specify the lite keyword, the system creates a lite Layer 2 aggregate interface. Otherwise, the system creates a generic Layer 2 aggregate interface. To create a lite or a generic Layer 2 aggregation group, remove the generic or the lite Layer 2 aggregation group with the same number first.
3. Exit to system view.	quit	N/A
4. Assign an interface to the specified Layer 2 aggregation group.	a. Enter Layer 2 Ethernet interface view: interface interface-type interface-number b. Assign the interface to the specified Layer 2 aggregation group: port link-aggregation group number	Repeat these two sub-steps to assign more Layer 2 Ethernet interfaces to the aggregation group.

Configuring a Layer 3 static aggregation group

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Create a Layer 3 aggregate interface and enter Layer 3 aggregate interface view.	interface route-aggregation interface-number	When you create a Layer 3 aggregate interface, the system automatically creates a Layer 3 static aggregation group numbered the same.
3. Exit to system view.	quit	N/A
4. Assign an interface to the specified Layer 3 aggregation group.	a. Enter Layer 3 Ethernet interface view: interface interface-type interface-number b. Assign the interface to the specified Layer 3 aggregation group: port link-aggregation group number	Repeat these two 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 might affect the aggregation state of the ports in a dynamic aggregation group.
3. Create a Layer 2 aggregate interface and enter Layer 2 aggregate interface view.	interface bridge-aggregation interface-number [ lite ]	When you create a Layer 2 aggregate interface, the system automatically creates a Layer 2 static aggregation group numbered the same. If you specify the lite keyword, the system creates a lite Layer 2 aggregate interface. Otherwise, the system creates a generic Layer 2 aggregate interface. To create a lite or a generic Layer 2 aggregation group, remove the generic or the lite Layer 2 aggregation group with the same number first.
4. Configure the aggregation group to operate in dynamic aggregation mode.	link-aggregation mode dynamic	By default, an aggregation group operates in static aggregation mode.
5. Exit to system view.	quit	N/A
6. Assign an interface to the specified Layer 2 aggregation group.	a. Enter Layer 2 Ethernet interface view: interface interface-type interface-number b. Assign the interface to the specified Layer 2 aggregation group: port link-aggregation group number	Repeat these two sub-steps to assign more Layer 2 Ethernet interfaces to the aggregation group.
7. Set the LACP operating mode on the interface.	· Set LACP to operate in passive mode: lacp mode passive · Set LACP to operate in active mode: undo lacp mode	By default, LACP is operating in active mode.
8. Set the port priority for the interface.	link-aggregation port-priority port-priority	The default setting is 32768.
9. Set the short LACP timeout interval (3 seconds) on the interface.	lacp period short	By default, the long LACP timeout interval (90 seconds) is adopted by the interface. The peer sends LACPDUs slowly. 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 dynamic aggregation group

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Set the system LACP priority.	lacp system-priority system-priority	By default, the system LACP priority is 32768. Changing the system LACP priority might affect the aggregation state of the ports in 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: interface interface-type interface-number b. Assign the interface to the specified Layer 3 aggregation group: port link-aggregation group number	Repeat these two sub-steps to assign more Layer 3 Ethernet interfaces to the aggregation group.
7. Set the LACP operating mode on the interface.	· Set LACP to operate in passive mode: lacp mode passive · Set LACP to operate in active mode: undo lacp mode	By default, LACP is operating in active mode.
8. Set the port priority for the interface.	link-aggregation port-priority port-priority	The default setting is 32768.
9. Set the short LACP timeout interval (3 seconds) on the interface.	lacp period short	By default, the long LACP timeout interval (90 seconds) is adopted by the interface. The peer sends LACPDUs slowly. 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 an aggregate interface

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.

Setting the description for an aggregate interface

You can set the description for an aggregate interface for administration purposes such as describing the purpose of the interface.

To set the description for an aggregate interface:

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

Specifying ignored VLANs for a Layer 2 aggregate interface

By default, to become Selected ports, the member ports must have the same VLAN permit state and VLAN tagging mode as the corresponding Layer 2 aggregate interface.

The system ignores the permit state and tagging mode of an ignored VLAN when choosing Selected ports.

To specify ignored VLANs for a Layer 2 aggregate interface:

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

Setting the MTU for a Layer 3 aggregate interface

Maximum transmission unit (MTU) of an interface affects IP packets fragmentation and reassembly on the interface.

To set the MTU for a Layer 3 aggregate interface:

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

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.

· Do not configure the minimum and maximum number of Selected ports for a lite Layer 2 aggregation group because each IRF member device can have only one Selected port in the aggregation group.

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 state of both aggregation member ports and the aggregate interface.

· When the number of member ports eligible to be Selected ports is smaller than the minimum threshold:

¡ All member ports are placed in the Unselected state.

¡ The link of the aggregate interface goes down.

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

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

You can configure backup between two ports by performing the following tasks:

· Assign two ports to an aggregation group.

· Configure 1 as the maximum number of Selected ports allowed in the aggregation group.

Then, only one Selected port is allowed in the aggregation group at any point in time, and the Unselected port acts as a backup port.

If the configured maximum number of Selected ports in an aggregation group in IRF mode is greater than that permitted by the hardware, enable link aggregation enhancement. For more information, see "Enabling link aggregation enhancement in IRF mode."

To set the minimum and maximum numbers of Selected ports for an aggregation group:

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

Setting the expected bandwidth for an aggregate interface

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter aggregate interface view.	· Enter Layer 2 aggregate interface view: interface bridge-aggregation interface-number [ lite ] · Enter Layer 3 aggregate interface /subinterface view: interface route-aggregation { interface-number \| interface-number.subnumber }	N/A
3. Set the expected bandwidth for the interface.	bandwidth bandwidth-value	By default, the expected bandwidth (in kbps) is the interface baud rate divided by 1000.

Configuring an edge aggregate interface

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

To configure an edge aggregate interface:

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

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: interface bridge-aggregation interface-number [ lite ] · Enter Layer 3 aggregate interface or subinterface view: interface route-aggregation { interface-number \| interface-number.subnumber }	N/A
3. Shut down the aggregate interface or subinterface.	shutdown	By default, Layer 2 and Layer 3 aggregate interfaces are down and Layer 3 subinterfaces are up.

Restoring the default settings for an aggregate interface

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

To restore the default settings for an aggregate interface:

Step	Command
1. Enter system view.	system-view
2. Enter aggregate interface view.	· Enter Layer 2 aggregate interface view: interface bridge-aggregation interface-number [ lite ] · Enter Layer 3 aggregate interface or subinterface view: interface route-aggregation { interface-number \| interface-number.subnumber }
3. Restore the default settings for the aggregate interface.	default

Configuring link-aggregation load sharing

You can determine how traffic is load shared in a link aggregation group by configuring load sharing modes. The system uses hash algorithm to compute load sharing modes based on the MPLS labels, source and destination port numbers, IP addresses, MAC addresses, ingress ports, or any combination. Also, you can specify traffic to be load shared by packet.

Configuration restrictions and guidelines

When you configure link-aggregation load sharing, follow these restrictions and guidelines:

· Ingress-port load sharing cannot cooperate with any other load sharing modes.

· Per-packet load sharing is not configurable in IRF mode. Because per-packet load sharing might disorder the packets, H3C recommends not configuring per-packet load sharing when the internal interface on the OAP card belongs to an aggregation group. For more information about the OAP card, see OAA Configuration Guide.

· All load sharing modes (except mpls-label1, mpls-label2, mpls-label3, and per-packet) take effect on ECMP load sharing of unicast traffic. If per-packet load sharing is configured, ECMP load sharing is performed according to the default load sharing mode supported by the switch. For more information about ECMP, see Layer 3—IP Routing Configuration Guide.

Setting the global link-aggregation load sharing mode

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Configure the global link-aggregation load sharing mode.	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 } * \| per-packet }	By default, the switch performs load sharing according to all load sharing modes except ingress-port and per-packet. After this command is configured, load sharing modes for all link aggregation groups change.

Step

Command

Remarks

1. Enter system view.

system-view

N/A

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

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 } * | per-packet }

By default, the switch performs load sharing according to all load sharing modes except ingress-port and per-packet.

After this command is configured, load sharing modes for all link aggregation groups change.

Enabling link aggregation enhancement in IRF mode

Link aggregation enhancement is configurable in IRF mode. It increases the maximum number of Selected ports that hardware supports in one aggregation group in an IRF fabric.

The maximum number of aggregated links in an aggregation group is subject to one of the following values, whichever is smaller:

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

· The hardware limitation.

The hardware limitation for an aggregation group varies by status of this feature.

· If this feature is disabled, the value is the maximum number supported by one IRF member device.

· If this feature is enabled, the value is the maximum number supported by per member device multiplied by the number of member devices.

For example, a four-chassis IRF fabric is as follows:

· Each IRF member device supports a maximum of 12 links per aggregation in hardware.

· The link-aggregation selected-port maximum number command is set to 48 for a link aggregation group.

If this feature is disabled in the IRF fabric, the actual number of Selected ports in an aggregation group can only reach 12. If this feature is enabled in the IRF fabric, the actual number of Selected ports can reach 48.

Configuration restrictions and guidelines

When you enable link aggregation enhancement in IRF mode, follow these restrictions and guidelines:

· This feature is configurable only 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 operate if the local end has more eligible Selected ports than the maximum number of Selected ports allowed. When both ends are configured with this feature, the smaller maximum number of Selected ports allowed applies.

· If this feature is enabled, the maximum number of Selected ports in an aggregation group must be greater than one.

Configuration procedure

To enable link aggregation enhancement in IRF mode:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enable link aggregation enhancement in IRF mode.	link-aggregation irf-enhanced	By default, link aggregation enhancement is disabled 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 } [ 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 for link aggregation member ports.	display link-aggregation member-port [ interface-list ]
Display summary information about all aggregation groups.	display link-aggregation summary
Display detailed information about the specified aggregation groups.	display link-aggregation verbose [ { bridge-aggregation \| route-aggregation } [ interface-number ] ]
Clear LACP statistics for the specified link aggregation member ports.	reset lacp statistics [ interface interface-list ]
Clear statistics for the specified aggregate interfaces.	reset counters interface [ { bridge-aggregation \| route-aggregation } [ interface-number ] ]

Ethernet link aggregation configuration examples

By default, Ethernet, VLAN, and aggregate interfaces are shut down. You must use the undo shutdown command to bring them up. The examples assume that all these interfaces are already up.

The following Layer 2 static and dynamic aggregation configuration examples use generic Layer 2 aggregation groups. You can configure a lite Layer 2 aggregation group in a similar way a generic Layer 2 aggregation group is configured. To configure a lite Layer 2 aggregation group, specify the lite keyword and assign only one member port on each IRF member device to the aggregation group.

Layer 2 static aggregation configuration example

Network requirements

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

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 Layer 2 aggregate interface Bridge-Aggregation 1.

[DeviceA] interface bridge-aggregation 1

[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 Device A is configured. (Details not shown.)

Verifying the configuration

# Display detailed information about all aggregation groups on Device A.

[DeviceA] display link-aggregation verbose

Loadsharing Type: Shar -- Loadsharing, NonS -- Non-Loadsharing

Port Status: S -- Selected, U -- Unselected, I -- Individual

Flags: A -- LACP_Activity, B -- LACP_Timeout, C -- Aggregation,

D -- Synchronization, E -- Collecting, F -- Distributing,

G -- Defaulted, H -- Expired

Aggregate Interface: Bridge-Aggregation1

Aggregation Mode: Static

Loadsharing Type: Shar

Port Status Priority Oper-Key

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

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.

· The aggregation group contains three Selected ports.

Layer 2 dynamic aggregation configuration example

Network requirements

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

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 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 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 Device A is configured. (Details not shown.)

Verifying the configuration

# Display detailed information about all aggregation groups on Device A.

[DeviceA] display link-aggregation verbose

Loadsharing Type: Shar -- Loadsharing, NonS -- Non-Loadsharing

Port Status: S -- Selected, U -- Unselected, I -- Individual

Flags: A -- LACP_Activity, B -- LACP_Timeout, C -- Aggregation,

D -- Synchronization, E -- Collecting, F -- Distributing,

G -- Defaulted, H -- Expired

Aggregate Interface: Bridge-Aggregation1

Aggregation Mode: Dynamic

Loadsharing Type: Shar

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

Local:

Port Status Priority Oper-Key Flag

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

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.

· The aggregation group contains three Selected ports.

Layer 2 edge aggregate interface configuration example

Network requirements

As shown in Figure 6, the device and the server are two ends of a Layer 2 dynamic aggregate link. Configure an edge aggregate interface so that GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2 can forward packets from the server during the server reboot process.

Figure 6 Network diagram

Configuration procedure

1. Configure the device:

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

<Device> system-view

[Device] interface bridge-aggregation 1

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

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

[Device-Bridge-Aggregation1] lacp edge-port

[Device-Bridge-Aggregation1] quit

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

[Device] interface gigabitethernet 1/0/1

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

[Device-GigabitEthernet1/0/1] quit

[Device] interface gigabitethernet 1/0/2

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

[Device-GigabitEthernet1/0/2] quit

2. Configure the server as required. (Details not shown.)

Verifying the configuration

# Display detailed information about all aggregation groups on the device during the server reboot process.

[Device] display link-aggregation verbose

Loadsharing Type: Shar -- Loadsharing, NonS -- Non-Loadsharing

Port Status: S -- Selected, U -- Unselected, I -- Individual

Flags: A -- LACP_Activity, B -- LACP_Timeout, C -- Aggregation,

D -- Synchronization, E -- Collecting, F -- Distributing,

G -- Defaulted, H -- Expired

Aggregate Interface: Bridge-Aggregation1

Aggregation Mode: Dynamic

Loadsharing Type: Shar

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

Local:

Port Status Priority Oper-Key Flag

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

GE1/0/1 I 32768 1 {AG}

GE1/0/2 I 32768 1 {AG}

Remote:

Actor Partner Priority Oper-Key SystemID Flag

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

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

GE1/0/2 0 32768 0 0x8000, 0000-0000-0000 {EF}

The output shows that GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2 are in Individual state when they have not received LACPDUs from the server. Both GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2 can forward packets, which ensures zero packet loss.

Layer 3 static aggregation configuration example

Network requirements

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

Configuration procedure

1. Configure Device A:

# Create Layer 3 aggregate interface Route-Aggregation 1, and configure an IP address and subnet mask for the aggregate interface.

<DeviceA> system-view

[DeviceA] interface route-aggregation 1

[DeviceA-Route-Aggregation1] ip address 192.168.1.1 24

[DeviceA-Route-Aggregation1] quit

# Assign Layer 3 Ethernet interfaces GigabitEthernet 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 Device A is configured. (Details not shown.)

Verifying the configuration

# Display detailed information about all aggregation groups on Device A.

[DeviceA] display link-aggregation verbose

Loadsharing Type: Shar -- Loadsharing, NonS -- Non-Loadsharing

Port Status: S -- Selected, U -- Unselected, I -- Individual

Flags: A -- LACP_Activity, B -- LACP_Timeout, C -- Aggregation,

D -- Synchronization, E -- Collecting, F -- Distributing,

G -- Defaulted, H -- Expired

Aggregate Interface: Route-Aggregation1

Aggregation Mode: Static

Loadsharing Type: Shar

Port Status Priority Oper-Key

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

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

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

Configuration procedure

1. Configure Device A:

# Create Layer 3 aggregate interface Route-Aggregation 1.

<DeviceA> system-view

[DeviceA] interface route-aggregation 1

# Set the link aggregation mode to dynamic.

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

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

[DeviceA-Route-Aggregation1] ip address 192.168.1.1 24

[DeviceA-Route-Aggregation1] quit

# Assign Layer 3 Ethernet interfaces GigabitEthernet 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 Device A is configured. (Details not shown.)

Verifying the configuration

# Display detailed information about all aggregation groups on Device A.

[DeviceA] display link-aggregation verbose

Loadsharing Type: Shar -- Loadsharing, NonS -- Non-Loadsharing

Port Status: S -- Selected, U -- Unselected, I -- Individual

Flags: A -- LACP_Activity, B -- LACP_Timeout, C -- Aggregation,

D -- Synchronization, E -- Collecting, F -- Distributing,

G -- Defaulted, H -- Expired

Aggregate Interface: Route-Aggregation1

Aggregation Mode: Dynamic

Loadsharing Type: Shar

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

Local:

Port Status Priority Oper-Key Flag

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

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.

· The aggregation group contains three Selected ports.

Layer 3 edge aggregate interface configuration example

Network requirements

As shown in Figure 9, the device and the server are the two ends of a Layer 3 dynamic aggregate link. Configure an edge aggregate interface so that GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2 can forward packets from the server during the server reboot process.

Figure 9 Network diagram

Configuration procedure

1. Configure the device:

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

<Device> system-view

[Device] interface route-aggregation 1

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

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

[Device-Route-Aggregation1] ip address 192.168.1.1 24

# Configure Layer 3 aggregate interface Route-Aggregation 1 as an edge aggregate interface.

[Device-Route-Aggregation1] lacp edge-port

[Device-Route-Aggregation1] quit

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

[Device] interface gigabitethernet 1/0/1

[Device-GigabitEthernet1/0/1] port link-mode route

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

[Device-GigabitEthernet1/0/1] quit

[Device] interface gigabitethernet 1/0/2

[Device-GigabitEthernet1/0/2] port link-mode route

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

[Device-GigabitEthernet1/0/2] quit

2. Configure the server as required. (Details not shown.)

Verifying the configuration

# Display detailed information about all aggregation groups on the device during the server reboot process.

[Device] display link-aggregation verbose

Loadsharing Type: Shar -- Loadsharing, NonS -- Non-Loadsharing

Port Status: S -- Selected, U -- Unselected, I -- Individual

Flags: A -- LACP_Activity, B -- LACP_Timeout, C -- Aggregation,

D -- Synchronization, E -- Collecting, F -- Distributing,

G -- Defaulted, H -- Expired

Aggregate Interface: Route-Aggregation1

Aggregation Mode: Dynamic

Loadsharing Type: Shar

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

Local:

Port Status Priority Oper-Key Flag

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

GE1/0/1 I 32768 1 {AG}

GE1/0/2 I 32768 1 {AG}

Remote:

Actor Partner Priority Oper-Key SystemID Flag

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

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

GE1/0/2 0 32768 0 0x8000, 0000-0000-0000 {EF}

04-Layer 2 - LAN Switching Configuration Guide

Configuration types

LACP functions

LACP operating modes

LACP priorities

LACP timeout interval

Load sharing modes for link aggregation groups

Configuring a Layer 2 static aggregation group

Setting the expected bandwidth for an aggregate interface

Network requirements

Configuration procedure

Verifying the configuration

Network requirements

Configuration procedure

Verifying the configuration

Network requirements

Configuration procedure

Verifying the configuration

Network requirements

Configuration procedure

Verifying the configuration

Network requirements

Configuration procedure

Verifying the configuration

Network requirements

Configuration procedure

Verifying the configuration

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Policy & Program

Global Learning

Partner Sales Resources

Service Business

News & Events

Contact Us