(Optional) Configuring an Eth-Trunk Member Interface on a Switch Directly Connected to a Server to Forward Packets
Context
- The server configures an IP address for Interface1 based on the default configuration during startup, and sends a request to the remote file server through Interface1 and downloads the configuration file from the remote file server.
- After the configuration file has been successfully downloaded, the server aggregates two interfaces according to the configuration file. The server uses the two interfaces as Eth-Trunk member interfaces to perform LACP negotiation with the switch.
To address this issue, run the lacp force-forward command on the Eth-Trunk of the switch. The Eth-Trunk member interface in Up state can still forward data packets even though the remote device is not enabled with LACP.
Procedure
- Run:
system-view
The system view is displayed.
- Run:
interface eth-trunk trunk-id
The Eth-Trunk interface view is displayed.
- Run:
lacp force-forward
The Eth-Trunk member interface in Up state is configured to forward data packets when the remote interface does not join the Eth-Trunk.
By default, an Eth-Trunk member interface in Up state cannot forward data packets when the remote interface does not join the Eth-Trunk.
- With this command configured, an Eth-Trunk interface does not support Layer 3 forwarding and cannot be used to forward packets sent to the CPU. Only member interfaces in the ForceFwd state can forward Layer 2 traffic through hardware forwarding. The ForceFwd state is automatically set when LACP negotiation fails, and cannot be changed manually. Use the display eth-trunk command to check the value of the Status field.
- This command only applies to the scenario where an Eth-Trunk joins a VLAN as an access, hybrid, trunk, and dot1q-tunnel interfaces.
- When a spanning tree protocol (for example, STP, RSTP, or MSTP) is used, member interfaces that are in ForceFwd state cannot be blocked. Member interfaces in ForceFwd state can continue to forward data packets. When other loop prevention protocols such as ERPS and RRPP are used, member interfaces that are in ForceFwd state can be blocked. The blocked member interfaces in ForceFwd state cannot forward data packets.
- This command cannot be used with E-Trunk. That is, this command cannot be used on the Eth-Trunk that joins an E-Trunk.
- This command cannot be used with max active-linknumber or least active-linknumber.