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

Licensing Requirements and Limitations for MQC (CE12800E)

Involved Network Elements

Other network elements are not required.

Licensing Requirements

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

Version Requirements

Table 2-3 Products and minimum version supporting MQC

Product

Minimum Version Required

CE12800E

V200R002C50

Feature Limitations

Limitations for specifications of MQC

Table 2-4 describes the specifications of MQC.
NOTE:

The values in Table 2-4 are used in each VS only when the MQC service is configured on a network. If the service configurations on the actual network and test network are different, the specifications of MQC may be different from the values in Table 2-4.

Table 2-4 Specifications of MQC

Item

Specification

Maximum number of traffic classifiers

  • Versions earlier than V200R003C00: 512
  • V200R003C00 and later versions: 2048

Maximum number of traffic behaviors

  • Versions earlier than V200R003C00: 512
  • V200R003C00 and later versions: 2048

Maximum number of traffic policies

  • Versions earlier than V200R003C00: 512
  • V200R003C00 and later versions: 2048

Maximum binding count of traffic policies

12288

Maximum number of if-match rules in a traffic classifier

2048

Maximum number of traffic classifiers bound to a traffic policy

  • Versions earlier than V200R003C00: 512
  • V200R003C00 and later versions: 2048

Number of traffic policies supported in each view

Inbound: 2

Outbound: 2

Limitations for Traffic Classifiers

  • When a traffic classifier contains an ACL rule that defines a VPN instance, the vpn-instance field is ignored. That is, both private and public network traffic is matched. To match only private network traffic, apply a traffic policy to the corresponding Layer 3 interface.
  • When editing or modifying traffic classification rules in a traffic policy on the switch configured with the traffic-policy atomic-update-mode command, ensure that the number of remaining ACL resources is larger than twice the number of chip resources occupied by traffic classification rules in the traffic policy.

Limitations for Traffic Policies

  • In V200R005C10 and earlier versions, a maximum of two traffic policies can be applied to the same direction in the same view.
  • When two traffic policies are applied to the same view and the same direction (assuming that traffic policies p1 and p2 are applied in sequence), if traffic policy p1 is unbound and a traffic policy (traffic policy p1 or another one) is applied again, traffic policy p2 becomes invalid for a period of time. In addition, there is a delay for the re-applied traffic policy to take effect after the configuration is committed.
  • When multiple fields of packets of the same type (such as Layer 2, IPv4, or IPv6 packets) need to be matched in a view, apply one traffic policy in the view and specify multiple traffic classifiers and corresponding traffic behaviors in the traffic policy. If both IPv4 and IPv6 packets need to be matched, create one traffic policy for each type of the packets.
  • Applying, modifying, and deleting a traffic policy take effect after a slight delay, which is proportional to the number of rules. In extreme conditions, the delay may reach minutes.
  • You can run the display traffic-policy apply-information command in the diagnostic view to check the priorities of all traffic policies that have been applied. The applied traffic policies are displayed in descending order of priority in the command output.

  • For the CE12800E configured with FD-X series cards, when the system resource mode is set to large-acl, a traffic policy can contain only the deny and redirect interface actions in bound traffic behaviors.
  • Normal ACLs and ARP-based ACLs cannot be matching in a traffic policy simultaneously, but can be applied in two different traffic policies.

  • When a VLAN is used or a Layer 2 sub-interface connects to a VXLAN on the CE12800E configured with ED-E, EG-E, and EGA-E series cards, a traffic policy cannot match the original VLAN ID of packets and cannot be applied to the VLAN. You can configure a traffic classifier to match fields except for the VLAN ID and apply the traffic policy to the BD corresponding to the VLAN.
  • When a traffic policy is applied to a VLANIF interface:
    • A traffic policy applied to a VLANIF interface takes effect only for Layer 3 unicast packets.
    • When a traffic policy is applied to the inbound direction of a VLANIF interface, the bound traffic classifiers can define matching rules based only on the IP address type (IPv4 or IPv6), source IPv4 address, destination IPv4 address, source IPv6 address, destination IPv6 address, protocol type, source port number, destination port number, and IP fragment flag.

      When a traffic policy is applied to the outbound direction of a VLANIF interface, the bound traffic classifiers can define matching rules based only on the IPv4 address type, source IPv4 address, destination IPv4 address, protocol type, source port number, destination port number, and IP fragment flag.

    • When a traffic policy is applied to the inbound direction of a VLANIF interface, the bound traffic behaviors support only packet filtering, redirection, PBR, CAR, and traffic statistics collection.

      When a traffic policy is applied to the outbound direction of a VLANIF interface, the bound traffic behaviors support only packet filtering, priority re-marking, CAR, and traffic statistics collection.

    • On the CE12800E equipped with FD-X series cards, if a traffic policy is applied in the inbound direction of a VLANIF interface, only the leftmost 64 bits of IPv6 addresses can be matched by default. strict-mode can be specified for a matching rule to match the full 128-bit IPv6 addresses.
  • When a traffic policy is applied to a VBDIF interface:
    • A traffic policy can be applied only to the inbound direction of a VBDIF interface on all switch models running a version earlier than V200R005C10.

      Starting from V200R005C10, a traffic policy can also be applied to the outbound direction of a VBDIF interface on the CE12800E equipped with FD-X series cards.

    • The bound traffic behaviors support only packet filtering, traffic statistics collection, PBR, and CAR if a traffic policy is applied in the inbound direction.

    • In versions earlier than V200R005C00, the bound traffic classifiers can define matching rules based only on the source IPv4 address, destination IPv4 address, protocol type, source port number, destination port number, ICMP type, and IPv4 TCP flag.

      In V200R005C00 and later versions, the bound traffic classifiers can define matching rules based only on the source IPv4 address, destination IPv4 address, source IPv6 address, destination IPv6 address, protocol type, source port number, destination port number, ICMP type, and IPv4 TCP flag.

      Starting from V200R005C10, on the CE12800E equipped with FD-X series cards, a traffic classifier can define matching rules based on the IPv6 TCP flag.

    • If the VBDIF interface is used as the VXLAN gateway, the traffic policy matches only inner IPv4 packets in which the VXLAN header is decapsulated.
  • When a traffic policy is applied to a Layer 2 sub-interface:
    • A traffic policy can be applied to the inbound direction of a Layer 2 sub-interface on the CE12800E configured with ED-E, EG-E, and EGA-E series cards, and to both inbound and outbound directions of a Layer 2 sub-interface on the CE12800E configured with FD-X series cards.
    • In version earlier than V200R005C10, the bound traffic classifiers can define matching rules based only on the destination MAC address, source MAC address, Ethernet type, source IPv4 address, destination IPv4 address, protocol type, source port number, and destination port number. In addition, only the following traffic behaviors are supported: traffic policing (CAR) and traffic statistics.

      In V200R005C10 and later versions, traffic policing (CAR) and re-marking can also be performed for IPv6 packets.

  • When a traffic policy is applied to a VPN instance:
    • A traffic policy can be applied to a VPN instance only in the inbound direction. The bound traffic classifiers can define matching rules based only on the source IPv4 address, destination IPv4 address, protocol type, source port number, and destination port number. The bound traffic behaviors support only traffic statistics collection, packet filtering, and PBR.

  • When a traffic policy is applied to a QoS group:
    • In versions earlier than V200R005C10, a traffic policy can be applied to a QoS group only in the inbound direction.

      In V200R005C10 and later versions, a traffic policy can be applied to the outbound direction of a QoS group containing Ethernet or Eth-Trunk member interfaces.

    • For the CE12800E equipped with FD-X series cards, applying a traffic policy to the outbound direction of a QoS group is mutually exclusive with the following functions:
      • Adding Eth-Trunk interfaces to an FCoE interface and enabling the traffic statistics collection function on the FCoE interface
      • Applying a traffic policy to the outbound direction of an Eth-Trunk interface
      • Configuring an ACL-based simplified traffic policy in the outbound direction of an Eth-Trunk interface
      • Configuring the traffic statistics collection function on a Layer 3 sub-interface of an Eth-Trunk
  • When a traffic policy is applied to a BD:

    • When a traffic policy is applied to the inbound direction of a BD:
      • The bound traffic classifiers can define matching rules based only on the source IPv4 address, destination IPv4 address, protocol type, source port number, destination port number, DSCP value, TCP flag, and inbound interface.
      • The bound traffic behaviors do not support VLAN mapping, VLAN stacking, and MAC address disabling.
    • When a traffic policy is applied to the outbound direction of a BD on the CE12800E configured with ED-E, EG-E, and EGA-E series cards:
      • The bound traffic behaviors support only VLAN mapping, traffic statistics collection, traffic policing, packet filtering, and priority re-marking.
      • If segment VXLAN is used to implement Layer 2 communication and a traffic policy containing a matching rule based on inner information in VXLAN packets is applied to the outbound direction of a BD, the traffic policy does not take effect.

    • When a traffic policy is applied to the outbound direction of a BD on the CE12800E configured with FD-X series cards:
      • The bound traffic behaviors support VLAN mapping, traffic statistics collection, traffic policing, packet filtering, and priority re-marking.
      • If a downlink traffic policy is configured and there are downlink Layer 3 packets, configure uplink and downlink traffic policies.
        • If a traffic policy has been configured in the inbound direction, run the remark qos-local-id qos-local-id command to configure the switch to re-mark packets matching the bound traffic classifier with the QoS local ID and bind this traffic behavior to the traffic policy. Then configure a traffic policy in the outbound direction and define a matching rule based on the QoS local ID in the traffic classifier.
        • If no traffic policy is configured in the inbound direction, run the if-match any command to match all packets and run the remark qos-local-id qos-local-id command to configure the switch to re-mark packets matching the bound traffic classifier with the QoS local ID, and configure and apply a traffic policy to the inbound direction. Then configure a traffic policy in the outbound direction and define a matching rule based on the QoS local ID in the traffic classifier.
  • When a traffic policy is applied to the outbound direction:
    • A traffic policy containing ARP-based ACLs and user-defined ACLs cannot be applied to the outbound direction.
    • On the CE12800E equipped with FD-X series cards:
      • A traffic policy applied in the VLAN view takes effect only for traffic forwarded at Layer 2.
      • If a traffic policy containing rules for matching VLANs is applied to the outbound direction of access and hybrid interfaces, VLAN IDs of packets cannot be matched because they are stripped off the packets.
    • A traffic policy cannot be applied to the outbound direction if the bound traffic behaviors define the following actions:
      • mirroring cpu and mirroring observe-port
      • ip urpf disable
      • remark local-precedence
      • mac-address learning disable
      • redirect cpu and redirect interface
      • redirect nexthop, redirect load-balance, redirect ipv6 nexthop, redirect ipv6 load-balance, and redirect remote
      • car share
Translation
Download
Updated: 2019-05-05

Document ID: EDOC1100004202

Views: 24206

Downloads: 25

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