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).
Overview of MQC

Overview of MQC

Modular QoS Command-Line Interface (MQC) allows you to classify packets based on packet characteristics and specify the same service for packets of the same type. This allows different types of packets to be provided with differentiated services.

As more services are deployed on a network, service deployment becomes increasingly complex because traffic of different services or users requires different services. Using MQC configuration, you can classify network traffic in a fine-grained way and specify the services provided to different types of traffic according to your needs. MQC enhances serviceability of your network.

MQC Entities

MQC involves three entities: traffic classifier, traffic behavior, and traffic policy.

  • Traffic classifier

    A traffic classifier defines a group of matching rules to classify packets.

    The relationship between rules in a traffic classifier can be AND or OR. The default relationship is OR.
    • AND: If a traffic classifier contains ACL rules, a packet matches the traffic classifier only if it matches one ACL rule and all the non-ACL rules. If a traffic classifier does not contain ACL rules, a packet matches the traffic classifier only if it matches all the rules in the classifier.

    • OR: A packet matches a traffic classifier if it matches one of the rules.

  • Traffic behavior

    A traffic behavior defines an action for packets of a specified type.

  • Traffic policy

    A traffic policy binds traffic classifiers and traffic behaviors, and then actions defined in traffic behaviors are taken for classified packets. In Figure 2-1, multiple traffic classifiers and traffic behaviors can be bound to one traffic policy.
    Figure 2-1 Multiple traffic classifiers and traffic behaviors bound to a traffic policy

MQC Configuration Process

Figure 2-2 outlines the MQC configuration process in the following steps:
  1. Configure a traffic classifier. The traffic classifier defines a group of matching rules to classify traffic and is the basis for differentiated services.

  2. Configure a traffic behavior. The traffic behavior defines a flow control action for packets matching the rules.

  3. Create a traffic policy and bind the traffic classifier to the traffic behavior in the traffic policy.

  4. Apply the traffic policy in the corresponding view.

Figure 2-2 MQC configuration process
Translation
Download
Updated: 2019-03-21

Document ID: EDOC1000166640

Views: 47121

Downloads: 219

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