Configuring Eth-Trunk Load Balancing

Configuring Load Balancing in Eth-Trunk Interface

1. Run the system-view command to enter the system view.
2. Run the interface eth-trunk number command to enter the Eth-Trunk interface view.

3. Run the mode { lacp-static | manual load-balance } to set the working mode of the Eth-Trunk interface.

   • lacp-static: indicates the static LACP mode. In this mode, both load balancing and redundancy backup can be implemented.
   • manual load-balance: indicates the manual load balancing mode. By default, an Eth-Trunk interface works in manual load balancing mode.
4. (Optional) Run the interface interface-type interface-number command to enter the Eth-Trunk member interface view.

5. (Optional) Run the distribute-weight weight-value command to set the distribute-weight of the member interface.

   By default, the weight of an Eth-Trunk member interface is 1.

   The higher the weight of a member interface, the heavier the load over the member link.

   A maximum of 64 member interfaces in an Eth-Trunk interface can carry out load balancing. The total weights of all member interfaces in an Eth-Trunk interface cannot be greater than 64.

   When multicast traffic is transmitted over an Eth-Trunk interface, if the distribute-weight command is used to change the weight of a member interface, you need to run the shutdown and then undo shutdown commands to restart the member interface for the configuration to take effect.

6. Run the commit.

Configuring Layer 2 Multicast Trunk Load Balancing

1. Run the system-view command to enter the system view.
2. Run the vlan vlan-id command to enter the VLAN view, or run the vsi vis-name command to enter the VSI view.

3. Run the trunk multicast load-balance enable command to enable trunk multicast load-balance.

   By default, trunk load balancing is not enabled for Layer 2 multicast.

   In the same VLAN or VSI, the trunk load balancing function for Layer 2 multicast and IGMP snooping are mutual exclusive. They cannot be configured concurrently.

4. Run the commit.

Follow-up Procedure

Run the save command to save the current configuration to the configuration file when a set of configuration is finished and the expected functions have been achieved.