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


To have a better experience, please upgrade your IE browser.


CX11x, CX31x, CX710 (Earlier Than V6.03), and CX91x Series Switch Modules V100R001C10 Configuration Guide 12

The documents describe the configuration of various services supported by the CX11x&CX31x&CX91x series switch modules The description covers configuration examples and function configurations.
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).
Configuration Notes

Configuration Notes

This section provides configuration notes for MQC.

  • If a traffic policy in the outbound direction contains car, apply the traffic policy to an interface, a VLAN, and the system in sequence. Otherwise, resources cannot be fully used and the traffic policy fails to be delivered.
  • On the CX110 switch module GE switching plane, you are advised to apply traffic policies with CAR behaviors to the inbound direction.
  • If the packet forwarding mode on the CX31x&CX91x series switch module 10GE switching planes and CX110 switch module GE switching plane is set to cut through, the traffic policy containing car cannot be applied to the outbound direction. If car needs to be used, run the assign forward mode store-and-forward command to change the packet forwarding mode to store-and-forward or apply the traffic policy containing car to the inbound direction.
  • You are advised not to use an ACL defining a VPN instance in a traffic classifier.
  • When packets match multiple traffic policies, either of the following situations occurs:
    • If traffic classification rules in the traffic policies are of the same type, that is, the rules are all user-defined ACL rules, Layer 2 rules, or Layer 3 rules, only one traffic policy takes effect. The traffic policy that takes effect depends on the object that the traffic policy has been applied to. The traffic policies applied to the interface, VLAN, and system take effect in descending order of priority.
    • If traffic classification rules in the traffic policies are of different types and actions do not conflict, all the traffic policies take effect. If actions conflict, the traffic policy that takes effect is relevant to rules. The rule priority is as follows: user-defined ACL rule > Layer 2 rule + Layer 3 rule > Layer 2 rule > Layer 3 rule.

    Configure rules according to priorities; otherwise, it may take a long time for the traffic policy to take effect. For details about traffic classification rules, see Table 13-1 in Traffic classification rules.

  • If an ACL6 defines fragment on the CX111&CX915 switch module GE switching plane, the traffic policy applied to the outbound direction cannot match non-first fragmented packets of IPv6 fragments.

  • Outbound MQC-based traffic statistics or traffic policing cannot be used with outbound interface-based rate limiting, queue-based traffic shaping, and ETS.
  • If a traffic behavior contains the following actions, the traffic policy bound to the traffic behavior cannot be applied to the outbound direction:
    • car share

    • mirroring observe-port

    • ip urpf disable

    • redirect cpu, redirect interface, redirect nexthop, and redirect load-balance

    • mac-address learning disable

    • vlan-stacking
Updated: 2019-08-09

Document ID: EDOC1000041694

Views: 59616

Downloads: 3623

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