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

NE40E V800R010C10SPC500 Configuration Guide - QoS 01

This is NE40E V800R010C10SPC500 Configuration Guide - QoS
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 Profile-based HQoS

Configuring Profile-based HQoS

Profile-based HQoS places traffic from multiple interfaces into an SQ for scheduling. It implements uniform scheduling for traffic on multiple interfaces by defining QoS profiles and applying the profiles to different interfaces.

Usage Scenario

To achieve uniform scheduling of incoming traffic flows on multiple interfaces, you need to implement traffic management by user levels. Interface-based HQoS only supports classifying traffic flows on one interface into an SQ for scheduling. It does not support uniform scheduling of traffic flows on multiple interfaces. Profile-based HQoS, by comparison, supports classifying traffic flows on multiple interfaces into an SQ for scheduling. It implements uniform scheduling of traffic flows on multiple interfaces by defining QoS scheduling profiles and applying the profiles to different interfaces. The profile-based HQoS technique is used mainly on the access devices deployed at the edge of a MAN.

The difference between the complex traffic classification-based traffic policy and the profile-based HQoS is as follows:

The traffic policy based on complex traffic classification identifies the quintuple information of packets and performs traffic policing, traffic shaping, traffic statistics, and information modification for packets in a certain direction. In this manner, the direction of the traffic and the bandwidth consumed by the traffic are controlled. The configuration of queue scheduling is not involved. Traffic policing identifies and matches the quintuple information of packets to restrict the volume of the incoming traffic within a reasonable range and discard the excess traffic. In this manner, the network resources and the interests of carriers can be protected. Traffic policing is unaware of users and service priorities. This method is applicable to the case where traffic in only one direction is to be restricted.

Profile-based HQoS adjusts the scheduling policy and traffic control of various services in different queues and at different scheduling levels by configuring a QoS profile to control the bandwidth and priorities of packets from different users and interfaces. This method is applicable to the case where differentiated services are required by users.
NOTE:

The GQ scheduling does not take effect in virtual access scenario. The command can be configured. But it does not take effect.

The differences between the traffic policy and QoS profile are as follows:

Compared Item

Traffic Policy

QoS Profile

Identification of packets

In-depth identification of the quintuple information of packets, such as the source/destination MAC address, source/destination IP address, user group number, protocol type, and TCP/UDP port number of the application program.

Identification of users and packet types.

Action taken on the packets

Various actions, including packet filtering, traffic policing, re-marking of packet priorities, re-marking of packet types, setting forwarding actions, and load balancing.

Traffic policing, traffic shaping, and queue scheduling.

Traffic control

There is no cache; the excess packets are discarded; traffic scheduling is implemented in a uniform manner.

Packets in different queues are hierarchically scheduled and then cached. Traffic is scheduled and restricted in a more granular manner.

Applied object

Traffic that is in the same direction and shares the same quintuple information.

Traffic that is sent by different users and belongs to different services.

Applied interface

This function is configured on the inbound interface.

This function can be configured on both upstream and downstream interfaces and is mostly configured on the outbound interface.

Association with packet suppression

Traffic policing and packet suppression cannot be configured on an inbound interface at the same time.

Traffic policing and packet suppression can be configured at the same time through the configuration of the QoS profile.

Pre-configuration Tasks

Before configuring profile-based HQoS, complete the following tasks:

  • Configuring the physical parameters and link attributes of interfaces for them to work properly

  • Assigning IP addresses to interfaces

  • Configuring IP routes on the router to make devices on the link reachable

Configuration Procedures

Figure 8-5 Flowchart of configuring profile-based HQoS

Translation
Download
Updated: 2019-01-03

Document ID: EDOC1100055024

Views: 25425

Downloads: 117

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