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).
Licensing Requirements and Limitations for MQC

Licensing Requirements and Limitations for MQC

Involved Network Elements

Other network elements are not required.

Licensing Requirements

MQC is a basic feature of a switch and is not under license control.

Version Requirements

Table 2-2 describes the products and versions supporting MQC.

Table 2-2  Products and versions supporting MQC

Product

Product Model

Software Version

S12700

S12708 and S12712

V200R005C00, V200R006C00, V200R007C00, V200R007C20, V200R008C00, V200R009C00, V200R010C00, V200R011C10

S12710

V200R010C00, V200R011C10

S12704

V200R008C00, V200R009C00, V200R010C00, V200R011C10

NOTE:
To know details about software mappings, see Hardware Query Tool.

Feature Limitations

  • Table 2-3 describes the specifications of MQC.
    Table 2-3  Specifications of MQC

    Item

    Specification

    Maximum number of traffic classifiers

    512

    Maximum number of if-match rules in a traffic classifier

    2048

    Maximum number of traffic behaviors

    256

    Maximum number of traffic policies

    256

    Maximum number of traffic classifiers bound to a traffic policy

    256

  • Applying traffic policies consumes ACL resources. If there are no sufficient ACL resources, some traffic policies will fail to be applied. For example, if an if-match rule in a traffic policy occupies one ACL, M ACL resources will be used to apply the traffic policy to M interfaces. When a traffic policy is applied to L VLANs on a device with N LPUs, L*N ACLs are occupied. When a traffic policy is applied globally on a device with N LPUs, N ACLs are occupied. Table 2-4 describes the ACL resource usage of if-match rules.
    Table 2-4  ACLs occupied by traffic classification rules

    Traffic Classification Rule

    ACL Resource Usage

    if-match vlan-id start-vlan-id [ to end-vlan-id ] [ cvlan-id cvlan-id ]

    if-match cvlan-id start-vlan-id [ to end-vlan-id ] [ vlan-id vlan-id ]

    Rules are delivered according to the VLAN ID range, and multiple ACLs are occupied. You can run the display acl division start-id to end-id command to check how ACL resources are used in a specified VLAN range.

    if-match acl { acl-number | acl-name }

    if-match ipv6 acl { acl-number | acl-name }

    Uplink: When the range resources are exhausted, rules containing range port-start port-end are delivered and multiple ACLs are occupied. Each rule containing tcp-flag established occupies two ACLs. (The ACL resource usage on X series cards is similar to that in the downlink direction.)

    Downlink: Rules containing range port-start port-end are delivered according to the port number range, and multiple ACLs are occupied. In other situations, one rule occupies one ACL. You can run the display acl division start-id to end-id command to check how ACL resources are used in a specified port number range.

    Other if-match rules

    Each rule occupies one ACL resource.

  • A traffic policy can be applied to the system, a VLAN, an SSID profile, or an interface. When a traffic policy needs to be applied in multiple views, apply the traffic policy in the interface view/SSID profile view, VLAN view, and system view in sequence. If the switch supports SSID profile view and different interface views, apply the traffic policy in the VLANIF interface view, WLAN-ESS interface view/SSID profile view, sub-interface view of physical interfaces/Eth-Trunk sub-interface view, and physical interface view/Eth-Trunk interface view/port group view in sequence.

  • When packets match multiple traffic policies, the following rules apply:

    • If traffic classification rules in the traffic policies are of the same type, only one traffic policy takes effect. The precedence of the traffic policies depends on the objects to which they are applied: interface/SSID profile > VLAN > global. That is, the traffic policy applied to an interface has the highest priority, whereas the traffic policy applied to the system has the lowest priority. If the traffic policies are applied to an SSID profile and different interfaces, the precedence of the traffic policies depends on the interface types: VLANIF interface > WLAN-ESS interface/SSID profile> sub-interface of physical interface/Eth-Trunk sub-interface > physical interface/Eth-Trunk interface/port group. When different traffic policies are applied in the same view, the precedence of the policies depends on the configuration sequence.

    • For the X series cards: If traffic classification rules in the traffic policies are of different types, only one traffic policy takes effect. The precedence of the traffic policies depends on the objects to which they are applied: interface > VLAN > global. That is, the traffic policy applied to an interface has the highest priority, whereas the traffic policy applied to the system has the lowest priority. If traffic policies are applied to the same object, the traffic policy that contains the traffic classifier with the highest priority takes effect.

    • For other cards except the X series cards: If traffic classification rules in the traffic policies are of different types and the actions do not conflict, all the traffic policies take effect. If actions conflict, the precedence of the traffic policies depends on precedence of rules in the policies: Layer 2 rule + Layer 3 rule > advanced ACL6 rule > basic ACL6 rule > Layer 3 rule > Layer 2 rule > user-defined ACL rule.

    • On the S5300EI, S5300HI, S5306, S5310EI, S5320EI, S6300EI, and S6320EI: On the S5700EI, S5700HI, S5710EI, S5710HI, S5720EI, S6700EI, S6720EI, and S6720S-EI: If traffic classification rules in the traffic policies are of different types and the actions do not conflict, all the traffic policies take effect. If actions conflict, the precedence of the traffic policies depends on the precedence of rules in the policies. Traffic policies applied in the inbound direction take effect in descending order of priority as follows: Layer 2 rule + Layer 3 rule > advanced ACL6 rule > basic ACL6 rule > Layer 3 rule > Layer 2 rule > user-defined ACL rule. Traffic policies applied in the outbound direction take effect in descending order of priority as follows: Layer 2 rule + Layer 3 rule > advanced ACL6 rule > basic ACL6 rule > Layer 2 rule > Layer 3 rule > user-defined ACL rule.

    It is recommended that you configure traffic policies in descending order of priority; otherwise, traffic policies may not take effect immediately. For details about traffic classification rules, see "Introduction to MQC".

  • If an MQC-based traffic policy and an ACL-based simplified traffic policy matching the same ACL are applied to the same object, the ACL-based simplified traffic policy takes effect.

  • If the ACL rule matches the VPN instance name of packets, the ACL-based traffic policy fails to be delivered.

  • If a traffic policy fails to be applied due to insufficient ACL resources on the switch, it is recommended that you delete the configuration of the traffic policy failing to be applied. Otherwise, if the configuration is saved and the switch is restarted, configuration of other services that runs properly will fail to be restored.

  • The packets destined for the local switch are sent to the CPU. After functions related to some protocols such as BGP, OSPF, and LACP are enabled, packets of these protocols are also sent to the CPU. If packets sent to the CPU match both CPCAR and a traffic classification rule in a traffic policy, but the actions to be taken conflict with each other, CPCAR takes effect.
Translation
Download
Updated: 2019-08-21

Document ID: EDOC1000142089

Views: 45253

Downloads: 87

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