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

S12700 V200R010C00 Configuration Guide - QoS

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, ACL-based simplified traffic policy, and HQoS.

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).
Introduction to MQC

Introduction to 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 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. Table 2-1 lists traffic classification rules.
    Table 2-1  Traffic classification rules
    Layer Traffic Classification Rule
    Layer 2
    • Destination MAC address
    • Source MAC address
    • VLAN ID in the tag of VLAN-tagged packets
    • 802.1p priority in the tag of VLAN-tagged packets
    • VLAN ID in the inner tag of QinQ packets
    • 802.1p priority in the inner tag of QinQ packets
    • Protocol field in the Layer 2 header
    • EXP precedence in MPLS packets
    • Matching fields in ACL 4000 to ACL 4999
    Layer 3
    • DSCP priority in IP packets
    • IP precedence in IP packets
    • Type of the next IPv6 header
    • IP protocol type (IPv4 or IPv6)
    • TCP-flag in TCP packets
    • Matching fields in ACL 2000 to ACL 3999
    • Matching fields in ACL6 2000 to ACL6 3999
    Others
    • All packets
    • Inbound interface
    • Outbound interface
    • Matching fields in ACL 5000 to ACL 5999 (user-defined ACLs)
    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 when 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 when it matches all the rules in the classifier.

    • OR: A packet matches a traffic classifier as long as it matches one of 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, a traffic policy can be bound to multiple traffic classifiers and traffic behaviors.
    Figure 2-1  Multiple pairs of traffic classifiers and traffic behaviors in 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 or resource allocation 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 to system, LPU, interface, or VLAN.

Figure 2-2  MQC configuration process

Relevant Information

Technology Forum

QoS Issues - Issue 2 QoS Implementation - MQC

Translation
Download
Updated: 2019-12-28

Document ID: EDOC1000142089

Views: 49606

Downloads: 88

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Share
Previous Next