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 8800, 7800, 6800, and 5800 V200R002C50

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 Priority Mapping (CE6870EI and CE6875EI)

Licensing Requirements and Limitations for Priority Mapping (CE6870EI and CE6875EI)

Involved Network Elements

Other network elements are not required.

Licensing Requirements

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

Version Requirements

Table 4-1 Products and minimum version supporting MQC

Product

Minimum Version Required

CE6870-24S6CQ-EI, CE6870-48S6CQ-EI

V200R001C00

CE6870-48T6CQ-EI

V200R002C50

CE6875-48S4CQ-EI

V200R003C00

Feature Limitations

Default Trusted Priority

  • Layer 3 physical interfaces trust DSCP priorities. This cannot be modified.
  • On an MPLS network, MPLS EXP priorities are trusted. This cannot be modified.

  • By default, the inbound interface trusts 802.1p priorities of multicast packets that are forwarded based on MAC addresses, and trusts DSCP priorities of multicast packets that are forwarded based on IP addresses.

Limitations on Priority Mapping

  • The default DiffServ domain is default. In addition to this domain, the device supports a maximum of six DiffServ domains. You can change the mapping in the DiffServ domain default, but cannot delete the domain.
  • If the mapping between PHBs and DSCP priorities is configured in the outbound direction of a VLAN, a maximum of three DiffServ domains (including the DiffServ domain default) can be applied to all VLANs on the device. The same DiffServ domain can be applied to different VLANs.
  • Colors are used to determine whether the packets are discarded during congestion avoidance and are independent of the mapping between internal priorities and queues.
  • When a DiffServ domain is applied to a MUX VLAN or super-VLAN, the device can only map inbound Layer 3 traffic based on 802.1p priorities in the DiffServ domain.
  • If the mapping from PHBs to DSCP priorities is enabled on the outbound interface, bits 6 and 7 in the ToS field of IPv6 packets are mapped to 0. The device does not support ECN for IPv6 packets or IPv6 over MPLS packets.
  • The VXLAN decapsulation device maps PHBs of Layer 3 packets to DSCP priorities based on the mapping between inner DSCP fields of VXLAN packets and the mapping template of the VBDIF interface. To modify the outer DSCP field of VXLAN packets, configure a traffic policy containing DSCP priority re-marking on the device in the inbound direction.
  • In V200R003C00 versions, when the CE6875EI functions as a Layer 3 VXLAN gateway and performs VXLAN encapsulation, the DSCP priority in the outer IP header of a VXLAN packet is incorrectly mapped and differs from the DSCP priority in the inner IP header. It is recommended that you do not configure the CE6875EI as a Layer 3 VXLAN gateway.

  • On a TRILL network, priority mapping can be performed based only on 802.1p priorities.
    • On an ingress node, the internal priority is mapped based on the 802.1p priority and DiffServ domain of the CE VLAN in the inbound direction. The 802.1p priority of the outer carrier VLAN is mapped based on the internal priority and DiffServ domain of the CE VLAN in the outbound direction.
    • On a transit node, the internal priority is mapped based on the 802.1p priority and DiffServ domain of the carrier VLAN in the inbound direction. The 802.1p priority of the outer carrier VLAN is mapped based on the internal priority and DiffServ domain of the carrier VLAN in the outbound direction.
    • On an egress node, the internal priority is mapped based on the 802.1p priority and DiffServ domain of the carrier VLAN in the inbound direction. The 802.1p priority of the inner CE VLAN is mapped based on the internal priority and DiffServ domain of the carrier VLAN in the outbound direction.

Limitations on Interface Priority

  • The priority of a Layer 3 physical interface is 0 and cannot be configured.
  • When an interface is added to a VLAN and the trusted priority is configured on the interface and in the VLAN, the trusted priority on the interface takes effect.
  • The priority cannot be configured for Eth-Trunk member interfaces.

Limitations When Priority Mapping Is Used with Other Services

  • When FCF or NPV is configured, the mapping from PHBs to 802.1p priorities in the outbound direction cannot be disabled. Otherwise, the device cannot send backpressure signals.
Translation
Download
Updated: 2019-03-21

Document ID: EDOC1000166640

Views: 47236

Downloads: 219

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