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


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


Configuration Guide - Interface Management

S7700 and S9700 V200R010C00

This document describes the principles and configurations of interfaces and provides configuration examples.
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).
Configuring Flow Control

Configuring Flow Control


Flow control prevents packet loss caused by network congestion. If network congestion occurs on the local device after flow control is configured, the local device sends a message to the remote device, requesting the remote device to temporarily stop sending packets. After receiving the message, the remote device temporarily stops sending packets to the local device regardless of the interface working rate.

As shown in Figure 2-6, SwitchA communicates with SwitchC through SwitchB. The flow control function is implemented as follows:
  1. GE1/0/1 of SwitchA and GE1/0/2 of SwitchB are connected, and their negotiation rate is 1000 Mbit/s. The two interfaces send data packets to each other at the rate of 1000 Mbit/s.
  2. The outbound interface Eth2/0/3 of SwitchB provides a maximum transmission rate of only 100 Mbit/s. When congestion occurs during packet forwarding, SwitchB caches the received packets. As the cached packets accumulate, Eth2/0/3 cannot forward all the packets due to forwarding capability limitations, and packet loss will occur.
  3. After flow control is configured on GE1/0/1 of SwitchA and GE1/0/2 of SwitchB, GE1/0/2 sends a Pause frame to GE1/0/1, requesting GE1/0/1 to temporarily stop sending packets. After receiving the Pause frame, GE1/0/1 stops sending packets to GE1/0/2 within the period specified in the Pause frame. If the congestion persists, GE1/0/2 continues to send Pause frames to GE1/0/1.
  4. Eth2/0/3 continues to send cached data packets until the congestion is eliminated.
  5. After the congestion is eliminated, SwitchB stops sending Pause frames to SwitchA. SwitchA then continues to send data packets to SwitchB at the rate of 1000 Mbit/s.
Figure 2-6  Networking diagram of flow control

If the remote device does not support auto-negotiation, you can configure flow control on the local and remote devices. If both the local and remote devices support auto-negotiation, you can configure flow control auto-negotiation on the two devices. The local device then negotiates with the remote device to determine whether to enable flow control based on the network congestion status.


For details about Ethernet interfaces supporting the flow control function, see Licensing Requirements and Limitations for Ethernet Interfaces.

Flow control and flow control auto-negotiation cannot be concurrently configured on Ethernet interfaces.

Flow control auto-negotiation take effect only when configured on interfaces at both ends of a link.

When an interface works in half-duplex mode, flow control does not take effect on the interface.

On X1E series cards, flow control takes effect on inbound interfaces only after you run the undo qos traffic-manage enable command on outbound interfaces. Flow control takes effect only for known unicast packets.

The EH1D2G48TBC0 and EH1D2G48SBC0 cards of the S9700 do not support flow control or flow control auto-negotiation.

On the ES0DG48TFA00 and ES0DF48TFA00 cards of the S7700 and the EH1D2G48TFA0 and EH1D2F48TFA0 cards of the S9700, if interfaces 0 to 23 work as inbound interfaces (or outbound interfaces) and interfaces 24 to 47 work as outbound interfaces (or inbound interfaces), flow control auto-negotiation does not take effect on these interfaces.


  • Configuring flow control
    1. Run:


      The system view is displayed.

    2. Run:

      interface interface-type interface-number

      The interface view is displayed.

    3. Run:


      Flow control is configured.

      By default, flow control is disabled on an Ethernet interface.

  • Configuring flow control auto-negotiation
    1. Run:


      The system view is displayed.

    2. Run:

      interface interface-type interface-number

      The interface view is displayed.

    3. Run:

      negotiation auto

      The interface is configured to work in auto-negotiation mode.

    4. Run:

      flow-control negotiation

      Flow control auto-negotiation is configured on the interface.

      By default, flow control auto-negotiation is disabled on an Ethernet interface.

Checking the Configuration

Run the display interface [ interface-type [ interface-number ] ] command in any view or the display this interface command in the interface view to check the current interface status. Check the Flow-control field in the command output.

Updated: 2019-04-18

Document ID: EDOC1000141901

Views: 18516

Downloads: 79

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