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).
Configuring a Traffic Classifier

Configuring a Traffic Classifier

Pre-configuration Tasks

Before configuring a traffic classifier, complete the following tasks:
  • Configure link layer attributes of interfaces to ensure that the interfaces work properly.

  • Configure an ACL if an ACL needs to be used to classify traffic.

Configuration Process

Non-conflicting rules can be configured in a traffic classifier.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    traffic classifier classifier-name [ operator { and | or } ] [ precedence precedence-value ]

    A traffic classifier is created and the traffic classifier view is displayed, or the existing traffic classifier view is displayed.

    and is the logical operator between the rules in the traffic classifier, which means that:
    • If the traffic classifier contains ACL rules, packets match the traffic classifier only when they match one ACL rule and all the non-ACL rules.

    • If the traffic classifier does not contain any ACL rules, packets match the traffic classifier only when they match all the rules in the classifier.

    The logical operator or means that packets match the traffic classifier as long as they match one of rules in the classifier.

    By default, the relationship between rules in a traffic classifier is OR.

  3. Configure matching rules according to the following table.
    NOTE:

    The if-match ip-precedence and if-match tcp commands are only valid for IPv4 packets.

    X series cards do not support traffic classifiers with advanced ACLs containing the ttl-expired field or user-defined ACLs.

    When a traffic classifier contains if-match ipv6 acl { acl-number | acl-name }, X series cards do not support add-tag vlan-id vlan-id, remark 8021p [ 8021p-value | inner-8021p ], remark cvlan-id cvlan-id, remark vlan-id vlan-id, or mac-address learning disable.

    Matching Rule

    Command

    Remarks

    Inner and outer VLAN IDs in QinQ packets

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

    -

    802.1p priority in VLAN packets

    if-match 8021p 8021p-value &<1-8>

    If you enter multiple 802.1p priority values in one command, a packet matches the traffic classifier as long as it matches any one of the 802.1p priorities, regardless of whether the relationship between rules in the traffic classifier is AND or OR.

    Inner 802.1p priority in QinQ packets

    if-match cvlan-8021p 8021p-value &<1-8>

    -

    Outer VLAN ID or inner and outer VLAN IDs of QinQ packets

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

    -

    Drop packet

    if-match discard

    A traffic classifier containing this matching rule can only be bound to traffic behaviors containing traffic statistics collection and flow mirroring actions.

    Double tags in QinQ packets

    if-match double-tag

    -

    EXP priority in MPLS packets

    if-match mpls-exp exp-value &<1-8>

    If you enter multiple MPLS EXP priority values in one command, a packet matches the traffic classifier as long as it matches any one of the MPLS EXP priorities, regardless of whether the relationship between rules in the traffic classifier is AND or OR.

    SA cards of the S series and X series cards do not support matching of EXP priorities in MPLS packets.

    Destination MAC address

    if-match destination-mac mac-address [ [ mac-address-mask ] mac-address-mask ]

    -

    Source MAC address

    if-match source-mac mac-address [ [ mac-address-mask ] mac-address-mask ]

    -

    Protocol type field in the Ethernet frame header

    if-match l2-protocol { arp | ip | mpls | rarp | protocol-value }

    -

    All packets

    if-match any

    -

    DSCP priority in IP packets

    if-match [ ipv6 ] dscp dscp-value &<1-8>

    • If you enter multiple DSCP values in one command, a packet matches the traffic classifier as long as it matches any one of the DSCP values, regardless of whether the relationship between rules in the traffic classifier is AND or OR.

    • If the relationship between rules in a traffic classifier is AND, the if-match [ ipv6 ] dscp and if-match ip-precedence commands cannot be used in the traffic classifier simultaneously.

    IP precedence in IP packets

    if-match ip-precedence ip-precedence-value &<1-8>
    • The if-match [ ipv6 ] dscp and if-match ip-precedence commands cannot be configured in a traffic classifier in which the relationship between rules is AND.

    • If you enter multiple IP precedence values in one command, a packet matches the traffic classifier as long as it matches any one of the IP precedence values, regardless of whether the relationship between rules in the traffic classifier is AND or OR.

    Layer 3 protocol type

    if-match protocol { ip | ipv6 }

    -

    First Next Header field in the IPv6 packet header

    if-match ipv6 next-header header-number first-next-header

    The ET1D2X12SSA0 card does not support the routes whose prefix length ranges from 64 to 128.

    SYN Flag in the TCP packet

    if-match tcp syn-flag { syn-flag-value | ack | fin | psh | rst | syn | urg }

    -

    Inbound interface

    if-match inbound-interface interface-type interface-number

    A traffic policy containing this matching rule cannot be applied to the outbound direction or in the interface view.

    Outbound interface

    if-match outbound-interface interface-type interface-number

    A traffic policy containing this matching rule cannot be applied to the inbound direction on X series cards.

    The traffic policy containing this matching rule cannot be applied in the interface view.

    ACL rule

    if-match acl { acl-number | acl-name }
    • When an ACL is used to define a traffic classification rule, it is recommended that the ACL be configured first.
    • If an ACL in a traffic classifier defines multiple rules, a packet matches the ACL as long as it matches one of rules, regardless of whether the relationship between rules in the traffic classifier is AND or OR.

    ACL6 rule

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

    Before specifying an ACL6 in a matching rule, configure the ACL6.

    Flow ID

    if-match flow-id flow-id

    The traffic classifier containing if-match flow-id and the traffic behavior containing remark flow-id must be bound to different traffic policies.

    The traffic policy containing if-match flow-id can be only applied to an interface, a VLAN, a card, or the system in the inbound direction.

    X series cards and SA cards of the S series do not support matching of flow IDs.

  4. Run:

    quit

    Exit from the traffic classifier view.

Translation
Download
Updated: 2019-08-21

Document ID: EDOC1000142089

Views: 43475

Downloads: 87

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