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 - QoS

CloudEngine 8800, 7800, 6800, and 5800 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).
Application Scenarios for Traffic Policing, Traffic Shaping, and Interface-based Rate Limiting

Application Scenarios for Traffic Policing, Traffic Shaping, and Interface-based Rate Limiting

Traffic Policing

As shown in Figure 5-7, voice, video, and data services are transmitted on a data center network. When a large amount of traffic enters the network, congestion may occur due to insufficient bandwidth. Different bandwidth guarantees must be provided for the voice, video, and data services, listed in descending order of priority. In this situation, traffic policing can be configured to provide the highest guaranteed bandwidth for voice packets and the lowest guaranteed bandwidth for data packets. This configuration ensures preferential transmission of voice packets when congestion occurs.

Figure 5-7 Networking of traffic policing

Traffic Shaping

On a data center network shown in Figure 5-8, different interfaces of SwitchA connect to the computing servers and a web server. When a user sends a search request, the computing servers perform distributed computing and send the result to the web server through SwitchA. Then the user obtains the search result from the web server. When the computing servers compute a large amount of data, the heavy traffic sent to the web server causes inbound traffic bursts on SwitchA. As a result, congestion may occur in the outbound direction on the interface of SwitchA connected to the web server. Traffic shaping can be configured in the outbound direction on this interface to transmit burst traffic evenly to the web server.

Figure 5-8 Networking of traffic shaping

Interface-based Rate Limiting

Voice, video, and data services are transmitted on a data center network. When a large amount of traffic enters the network, congestion may occur due to insufficient bandwidth. Different bandwidth guarantees need to be allocated to the three services. As shown in Figure 5-9, different interfaces of SwitchA connect to voice, video, and data servers. Interface-based rate limiting is configured on these interfaces to limit the rates of voice, video, and data service traffic. Excess traffic will be discarded.

Figure 5-9 Networking of interface-based rate limiting

Translation
Download
Updated: 2019-03-21

Document ID: EDOC1000166640

Views: 46846

Downloads: 219

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