mode (Eth-Trunk interface view)

Function

The mode command sets the working mode of an Eth-Trunk.

The undo mode command restores the default working mode of an Eth-Trunk interface.

Format

mode { lacp-static | manual { load-balance | backup } }

undo mode

Parameters

Parameter	Description	Value
lacp-static	Indicates the static LACP mode. The static LACP mode must be set on both ends simultaneously. If interfaces of various bandwidths are added to an Eth-Trunk, you cannot configure the static LACP mode.	-
manual { load-balance \| backup }	load-balance: indicates the manual load balancing mode. backup: indicates the manual active/standby backup mode.	-

Views

Eth-Trunk interface view, Layer-2 Eth-Trunk interface view

Default Level

2: Configuration level

Usage Guidelines

By default, an Eth-Trunk works in manual load balancing mode.

Usage Scenario

Currently, the FW supports Eth-Trunk interfaces to work in the following modes:

Static LACP mode

When the devices that are directly connected through an Eth-Trunk link support LACP, you can run the mode lacp-static command to configure the Eth-Trunk interface to work in static LACP mode. In this manner, both load balancing and redundancy backup can be implemented.

In static LACP mode, you must manually create an Eth-Trunk interface and add interfaces to the Eth-Trunk interface. Different from link aggregation in manual load balancing mode, active member interfaces are selected by sending LACP data units (LACPDUs) in static LACP mode. That is, when a group of interfaces are added to an Eth-Trunk interface, devices at the two ends determine active interfaces and inactive interfaces by sending LACPDUs to each other.
Manual load balancing mode

When one of the devices at the two ends of an Eth-Trunk link does not support LACP, you can run the mode manual load-balance command to configure the Eth-Trunk interface to work in manual load balancing mode. In addition, you can add multiple member interfaces to increase the bandwidth between the two devices and improve reliability.

The manual load balancing mode is a basic link aggregation mode. In this mode, you must manually create an Eth-Trunk interface, add interfaces to the Eth-Trunk interface, and specify active member interfaces. LACP is not involved.

In manual load balancing mode, all active member interfaces forward data and perform load balancing.

Traffic can be evenly balanced among all member interfaces. Alternatively, you can also set the weight for each member interface to implement uneven load balancing; in this manner, the interface that has a greater weight value transmits a larger volume of traffic.

If an active link of the link aggregation group fails, traffic is balanced among the remaining active links.
Manual 1:1 active/standby mode

When an intermediate device exists between the devices at the two ends of an Eth-Trunk link, you can run the mode manual backup command to configure the Eth-Trunk interface to work in manual 1:1 master/backup mode. The networking provides 1:1 master/backup links for data transmission.

In manual 1:1 master/backup mode, you must manually create an Eth-Trunk interface and add interfaces into it. An Eth-Trunk interface in manual 1:1 master/backup mode contains only two interfaces: one master interface and one backup interface.

When an Eth-Trunk interface on a FW device works in manual 1:1 master/backup mode, it can be in Layer 3 or Layer 2 mode.

Prerequisites

The Eth-Trunk interface is correctly configured.

Configuration Impact

If you run the mode command several times to configure the working mode for an Eth-Trunk interface, the last configuration takes effect.

Precautions

Before changing the working mode of an Eth-Trunk, ensure that the Eth-Trunk does not have any member interfaces.

If an Eth-Trunk has member interfaces, you can switch the working mode of the Eth-Trunk from the manual mode to the LACP mode, but cannot switch the working mode from the LACP mode to the manual mode.

When you switch the working mode of an Eth-Trunk interface from manual mode to static LACP mode, note the following:

If an Eth-Trunk interface contains member interfaces, the default protection time for mode switching is 90s.
During the protection time, if the working mode of the remote interface is not switched, the status of the local interface remains unchanged.
During the protection time, any interface status change which may be caused by external operations or configurations does not take effect. When the protection time expires, the interface status is refreshed.
When the protection time expires and the working mode of the remote interface is not switched, the negotiation between the local and remote interfaces fails.

Example

# Create Eth-Trunk 1 and configure it to work in static LACP mode.

<sysname> system-view
[sysname] interface Eth-Trunk 1
[sysname-Eth-Trunk1] mode lacp-static