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 - QoS
CloudEngine 12800 and 12800E V200R002C50

This document describes the configurations of QoS functions, including MQC, priority mapping, traffic policing, traffic shaping, interface-based rate limiting, congestion avoidance, congestion management, packet filtering, redirection, traffic statistics, and ACL-based simplified traffic policy.

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).
Interface-based Rate Limiting

Interface-based Rate Limiting

Interface-based rate limiting controls the total rate of all packets sent or received on an interface.

Interface-based rate limiting uses the token bucket mechanism to control traffic rates. If rate limiting is configured on an interface, all packets passing through this interface must be processed by the token bucket. If there are sufficient tokens in the token bucket for packet forwarding, packets are sent out from the interface. Otherwise, packets are discarded or buffered.

Interface-based rate limiting can be configured in the inbound or outbound direction. The following example illustrates the process of interface-based rate limiting in the outbound direction using the single-rate-single-bucket mechanism.

Figure 5-6 Interface-based rate limiting

The interface-based rate limiting process is as follows:

  1. If there are sufficient tokens in the bucket, the system sends the packets and decreases the number of tokens accordingly.
  2. If tokens in the bucket are insufficient for packet forwarding, the system places the packets into the buffer queue. If the buffer queue is full, the system discards the packets.
  3. When there are packets in the buffer queue, the system compares the number of packets with the number of tokens in the token bucket. If there are sufficient tokens, the system forwards packets until all the packets in the buffer queue are sent.
Updated: 2019-03-21

Document ID: EDOC1000166605

Views: 65918

Downloads: 84

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next