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 12800 and 12800E V200R003C00

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

Configuring Traffic Statistics

Context

After the traffic statistics function is enabled, the device collects statistics on packets matching traffic classification rules. The statistics on forwarded and discarded packets matching a traffic policy help you check whether the traffic policy is correctly applied and locate faults.

Procedure

  1. Configure a traffic classifier.
    1. Run system-view

      The system view is displayed.

    2. Run traffic classifier classifier-name [ type { and | or } ]

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

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

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

      The logical operator or means that packets match a traffic classifier if they match one or more rules in the classifier.

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

    3. Run if-match

      Matching rules are defined for the traffic classifier.

      For details about matching rules in a traffic classifier, see "Configuring a Traffic Classifier" in "MQC Configuration" of the CloudEngine 12800 and 12800E Series Switches Configuration Guide - QoS Configuration Guide.

    4. Run commit

      The configuration is committed.

    5. Run quit

      Exit from the traffic classifier view.

  2. Configure a traffic behavior.
    1. (Optional) Run qos statistics ifg enable

      The device is configured to count the inter-frame gap and preamble of packets when the device collects traffic statistics.

    2. Run traffic behavior behavior-name

      A traffic behavior is created and the traffic behavior view is displayed, or the view of an existing traffic behavior is displayed.

    3. Run statistics enable

      The traffic statistics function is enabled.

      By default, the traffic statistics function is disabled.

    4. Run commit

      The configuration is committed.

    5. Run quit

      Exit from the traffic behavior view.

    6. Run quit

      Exit from the system view.

  3. Configure a traffic policy.
    1. Run system-view

      The system view is displayed.

    2. Run traffic policy policy-name

      A traffic policy is created and the traffic policy view is displayed, or the view of an existing traffic policy is displayed.

    3. Run classifier classifier-name behavior behavior-name [ precedence precedence-value ]

      A traffic behavior is bound to a traffic classifier in the traffic policy.

    4. Run commit

      The configuration is committed.

    5. Run quit

      Exit from the traffic policy view.

    6. Run quit

      Exit from the system view.

  4. Apply the traffic policy.
    NOTE:
    • The traffic policy containing statistics enable cannot be applied in the outbound direction of the system, VLAN, and VSI.

    • For details about the configuration guidelines of applying traffic policies in different views on the CE12800, see Licensing Requirements and Limitations for MQC (CE12800).

    • For details about the configuration guidelines of applying traffic policies in different views on the CE12800E, see Licensing Requirements and Limitations for MQC (CE12800E).

    • If a traffic policy needs to be applied to multiple VLANs and interfaces or multiple traffic classifiers for matching packets from different source IP addresses need to be bound to the same traffic policy, you are advised to add these VLANs, source IP addresses, and interfaces to the same QoS group and apply the traffic policy to the QoS group.

    • Applying a traffic policy to an interface
      1. Run system-view

        The system view is displayed.

      2. Run interface interface-type interface-number

        The interface view is displayed.

      3. Run traffic-policy policy-name { inbound | outbound }

        A traffic policy is applied to the interface.

      4. Run commit

        The configuration is committed.

    • Applying a traffic policy to a VLAN
      1. Run system-view

        The system view is displayed.

      2. Run vlan vlan-id

        The VLAN view is displayed.

      3. Run traffic-policy policy-name { inbound | outbound }

        A traffic policy is applied to the VLAN.

        The system applies traffic policing to the packets that belong to the VLAN and match traffic classification rules in the inbound or outbound direction.

      4. Run commit

        The configuration is committed.

    • Applying a traffic policy to the system or an LPU
      1. Run system-view

        The system view is displayed.

      2. Run traffic-policy policy-name global [ slot slot-id ] { inbound | outbound }

        A traffic policy is applied to the system or an LPU.

      3. Run commit

        The configuration is committed.

    • Applying a traffic policy in a VPN instance
      1. Run system-view

        The system view is displayed.

      2. (Optional) Run qos port-group group-id

        A QoS interface group is created and its view is displayed.

        NOTE:

        The CE12800E configured with ED-E, EG-E, and EGA-E series cards does not support the QoS interface group configuration.

      3. (Optional) Run group-member { interface-type interface-number1 [ to interface-type interface-number2 ] }

        The specified interfaces are added to the QoS interface group.

      4. (Optional) Run quit

        Exit from the QoS interface group view.

      5. Run ip vpn-instance vpn-instance-name

        A VPN instance is created and its view is displayed.

      6. Run traffic-policy policy-name inbound [ exclude qos port-group group-id ]

        A traffic policy is applied to the VPN instance.

      7. Run commit

        The configuration is committed.

    • (For CE12800) Applying a traffic policy to a VSI
      1. Run system-view

        The system view is displayed.

      2. Run vsi vsi-name

        The VSI view is displayed.

      3. Run traffic-policy policy-name { inbound | outbound }

        A traffic policy is applied to the VSI.

      4. Run commit

        The configuration is committed.

    • Applying a traffic policy to a QoS group
      1. Run system-view

        The system view is displayed.

      2. Run qos group group-name

        The QoS group view is displayed.

      3. Run the following commands as required:
        • Run the group-member interface { interface-type interface-number1 [ to interface-type interface-number2 ] } &<1-8> command to add interfaces to the QoS group.

        • Run the group-member vlan { vlan-id1 [ to vlan-id2 ] } &<1-8> command to add VLANs to the QoS group.

        • (For CE12800E) Run the group-member ip source ip-address { mask | mask-length } command to add source IP addresses to the QoS group.

      4. Run traffic-policy policy-name inbound

        A traffic policy is applied to the QoS group.

      5. Run commit

        The configuration is committed.

    • Applying a traffic policy to a BD
      1. Run system-view

        The system view is displayed.

      2. Run bridge-domain bd-id

        The BD view is displayed.

      3. Run traffic-policy policy-name { inbound | outbound }

        A traffic policy is applied to the BD.

      4. Run commit

        The configuration is committed.

Verifying the Configuration

  • Run the display traffic-policy statistics { global [ slot slot-id ] | interface interface-type interface-number | vlan vlan-id | vsi vsi-name | vpn-instance vpn-instance-name | qos group group-id | bridge-domain bd-id } [ policy-name ] [ inbound | outbound ] [ { classifier-base | rule-base } [ class classifier-name ] ] command to display statistics on packets matching a traffic policy.
  • Run the display traffic classifier [ classifier-name ] command to check the traffic classifier configuration.
  • Run the display traffic behavior [ behavior-name ] command to check the traffic behavior configuration on the device.
  • Run the display traffic policy [ policy-name [ classifier classifier-name ] ] command to check the traffic policy configuration.

  • Run the display traffic-policy applied-record [ policy-name ] [ global [ slot slot-id ] | interface interface-type interface-number | vlan vlan-id | vsi vsi-name | vpn-instance vpn-instance-name | qos group group-id | bridge-domain bd-id ] [ inbound | outbound ] command to check the application record of a specified traffic policy.

    NOTE:

    The CE12800E does not support the vsi vsi-name parameter.

  • Run the display system tcam fail-record [ slot slot-id ] command to display TCAM delivery failures.
  • Run the display system tcam service brief [ slot slot-id ] command to display the group index and rule count occupied by different services.
  • Run the display system tcam service { cpcar slot slot-id | service-name slot slot-id [ chip chip-id ] } command to display IDs of entries that deliver services on the specified chip or in the specified slot.
  • Run one of the following commands to display data of a traffic policy that has been applied:
    • display system tcam service traffic-policy { global | vlan vlan-id | interface interface-type interface-number | vsi vsi-name | vpn-instance vpn-instance-name | qos group group-id | bridge-domain bd-id } policy-name { inbound | outbound } [ slot slot-id [ chip chip-id ] ]
      NOTE:

      The CE12800E does not support the vsi vsi-name parameter.

    • display system tcam service traffic-policy slot slot-id policy-name { inbound | outbound } [ chip chip-id ]
  • (For CE12800) Run the display system tcam match-rules slot slot-id [ [ ingress | egress | group group-id ] | [ chip chip-id ] ] * command to display matched entries.
  • (For the CE12800E) Run the display system tcam match-rules slot slot-id chip chip-id index index-id command to display matched entries.
Translation
Download
Updated: 2019-05-05

Document ID: EDOC1100004202

Views: 25248

Downloads: 25

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