(Optional) Configuring an Eth-Trunk Member Interface on a Switch Directly Connected to a Server to Forward Packets
Context
A switch uses an Eth-Trunk in LACP mode to directly connect to a server. Before the server obtains a configuration file, negotiation fails at the two ends because the directly connected interface in LACP. To address this issue, configure an Eth-Trunk member interface in Up state to forward data packets if the remote interface does not join the Eth-Trunk.
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 if the remote interface does not join the Eth-Trunk.
By default, an Eth-Trunk member interface in Up state does not forward data packets if the remote interface does not join the Eth-Trunk.
- When this command is used, Layer 3 forwarding is not supported but the member interface in ForceFwd state can forward Layer 2 traffic. The ForceFwd state is automatically set when LACP negotiation fails, and cannot be changed manually. You can use the display eth-trunk command to check the value of the Status field.
- This command applies to only 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, the member interface in ForceFwd state cannot be blocked. That is, the member interface in ForceFwd state can continue to forward data packets. When other loop prevention protocols such as ERPS and RRPP are used, the member interface in ForceFwd state can be blocked. The blocked member interface 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.