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 (CE Switches Excluding CE6870EI and CE6875EI)

Licensing Requirements and Limitations for Priority Mapping (CE Switches Excluding 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 3-1 Products and minimum version supporting priority mapping

Product

Minimum Version Required

CE5810EI

V100R002C00

CE5850EI

V100R001C00

CE5850HI

V100R003C00

CE5855EI

V100R005C10

CE5880EI

V200R005C10

CE6810EI

V100R003C00

CE6810-48S4Q-LI, CE6810-48S-LI

V100R003C10

CE6810-32T16S4Q-LI, CE6810-24S2Q-LI

V100R005C10

CE6850EI

V100R001C00

CE6850-48S6Q-HI

V100R005C00

CE6850-48T6Q-HI, CE6850U-HI, CE6851HI

V100R005C10

CE6855HI

V200R001C00

CE6856HI

V200R002C50

CE6857EI

V200R005C10

CE6860EI

V200R002C50

CE6865EI

V200R005C00

CE6880EI

V200R002C50

CE7850EI

V100R003C00

CE7855EI

V200R001C00

CE8850-32CQ-EI

V200R002C50

CE8850-64CQ-EI

V200R005C00

CE8860EI

V100R006C00

CE8861EI

V200R005C10

CE8868EI

V200R005C10

Feature Limitations

Default Trusted Priority

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

Limitations on Priority Mapping

  • The default DiffServ domain is default. In addition to this domain, the device supports a maximum of seven DiffServ domains. You can change the mapping in the DiffServ domain default, but cannot delete the domain.
  • Colors are used to determine whether the packets are discarded during congestion avoidance and are independent of the mapping between internal priorities and queues.
  • On the CE6800 (excluding the CE6865EI, CE6857EI, CE6856HI, CE6850HI, CE6850U-HI, CE6851HI, and CE6855HI), CE5880EI, and CE5850HI, only queues 0, 1, 2, and 6 are available for unknown unicast packets.
  • For CE7850EI, CE6851HI, CE6850U-HI, and CE6850HI series switches, MPLS QoS on the penultimate hop device becomes invalid in MPLS PHP scenarios:
    • When the penultimate hop device receives packets with multiple labels, the EXP priority of outgoing packets remains unchanged.
    • When the penultimate hop device receives packets with a single label and the mapping between PHBs and DSCP priorities is enabled on the outbound interface, the DSCP priority of outgoing packets is mapped based on the configured QoS profile. If the mapping between PHBs and DSCP priorities is not enabled on the outbound interface, the DSCP priority of outgoing packets remains unchanged.
  • In a stack of devices other than the CE5880EI and CE6880EI, when traffic is forwarded from a QinQ Layer 2 sub-interface of QinQ transparent transmission type to another QinQ Layer 2 sub-interface of QinQ transparent transmission type on another device, mapping from PHBs to DSCP priorities and mapping from PHBs to 802.1p priorities in the outbound direction do not take effect. You can apply the traffic policy containing priority re-marking to an interface in the outbound direction to implement priority mapping.
  • 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 of the CE VLAN and the DiffServ domain of physical ports for receiving packets 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 a transit node, the internal priority is mapped based on the 802.1p priority of the carrier VLAN and DiffServ domain of physical ports for receiving packets 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 physical outbound interface in the outbound direction.

Limitations on Interface Priority

  • The priority of a Layer 3 physical interface is 0 and cannot be configured.
  • If no DiffServ domain is applied to an inbound interface and the interface priority is configured, the device adds a VLAN tag to received packets, uses the interface priority as the packet priority, and sends packets to queues based on the interface priority.
  • 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.
  • For the CE6880-48S4Q2CQ-EI and CE6880-48T4Q2CQ-EI, when 10GE interfaces numbered 1 to 12 are used to form a stack, stacking packets enter the interface queue corresponding to priority 7, and non-stacking packets with priority 7 enter the interface queue corresponding to priority 6. In this case, the interface queue corresponding to priority 6 is congested and packets are lost. When the CE6880-48S4Q2CQ-EI or CE6880-48T4Q2CQ-EI is used in a stack, 40GE/100GE interfaces are recommended. If 10GE interfaces are used, 10GE interfaces numbered 13 to 48 are recommended.

Translation
Download
Updated: 2019-03-21

Document ID: EDOC1000166640

Views: 52594

Downloads: 221

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