No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Configuration Guide - Ethernet Switching

S7700 and S9700 V200R012C00

This document describes the configuration of Ethernet services, including configuring MAC address table, link aggregation, VLANs, VLAN aggregation, MUX VLAN, VLAN termination, Voice VLAN, VLAN mapping, QinQ, GVRP, VCMP, STP/RSTP/MSTP, VBST, SEP, RRPP, ERPS, LBDT, HVRP, and Layer 2 protocol transparent transmission.
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
(Optional) Configuring an Eth-Trunk Member Interface on a Switch Directly Connected to a Server to Forward Packets

(Optional) Configuring an Eth-Trunk Member Interface on a Switch Directly Connected to a Server to Forward Packets

Context

Figure 3-23  A switch directly connects to a server
In Figure 3-23, two interfaces of two network adapters on a server are directly connected to a switch. The switch is configured with an Eth-Trunk in LACP mode. The process on the server is as follows:
  1. The server configures an IP address for Interface1 based 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.
  2. After the configuration file is downloaded successfully, 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.
Before the server obtains the configuration file, Interface1 is an independent physical interface and is not configured with LACP. As a result, LACP negotiation on the switch interface fails. The switch does not forward traffic on the Eth-Trunk, and the server cannot download the configuration file through Interface1. In this case, the server cannot communicate 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

  1. Run system-view

    The system view is displayed.

  2. Run interface eth-trunk trunk-id

    The Eth-Trunk interface view is displayed.

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

    NOTE:
    • 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.

Translation
Download
Updated: 2019-01-18

Document ID: EDOC1100038843

Views: 107361

Downloads: 71

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next