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

NE40E V800R010C10SPC500 Configuration Guide - QoS 01

This is NE40E V800R010C10SPC500 Configuration Guide - QoS
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 Class-based QoS

Licensing Requirements and Limitations for Class-based QoS

Licensing Requirements

This feature is a basic feature and is not under license control.

Restrictions and Guidelines

Restrictions

Guidelines

Impact

When the IPv6 address mask is configured and the current algorithm table is in mask mode, if the configured mask prefix length is not an integer multiple of 4, the rule cannot be matched, and the function does not take effect.

Configure the mask prefix length as an integer multiple of 4 based on the matching rule.

Set the mask prefix length to an integer multiple of 4 based on the matching rule.

Run the traffic-policy ipv6-address-rule match mask command in the slot view.

MIBs and NMS do not support level-2 ACL sub-policy statistics query and clearing.

None

Failed to query and clear the statistics about sub-policies that MIB and the NMS do not support.

Only MF classification in ip-layer mode (default mode) is supported on an IPv6 GRE tunnel interface.

When configuring MF classification on an IPv6 GRE tunnel interface, do not specify layer informaiton, or use ip-layer when specifying layer information.

If link-layer or all-layer is specified for MF classification on IPv6 GRE tunnel interfaces, Layer 2 rules cannot be matched.if mpls-layer is specified, MPLS rules cannot be matched.

CAR in color-aware mode is not supported on an IPv6 GRE tunnel interface.

When configuring CAR on an IPv6 GRE tunnel interface, do not specify the color-aware mode.

CAR in color-aware mode is not supported on an IPv6 GRE tunnel interface.

When rate limiting based on Layer 3 packets is configured in a traffic policy, CAR based on the packet rate or CAR based on packet length compensation cannot be configured. Otherwise, rate limiting based on Layer 3 packets does not take effect.

Do not configure CAR based on the packet rate or CAR based on packet length compensation in a traffic policy when rate limiting based on Layer 3 packets is required.

When rate limiting based on Layer 3 packets is configured in a traffic policy, CAR based on the packet rate or CAR based on packet length compensation cannot be configured. Otherwise, rate limiting based on Layer 3 packets does not take effect.

Hierarchical CAR and QPPB Policy CAR are mutually exclusive. If both functions are configured on the same interface, QPPB Policy CAR takes effect, and only second-level ACL in hierarchical CAR takes effect. First-level ACL CAR does not take effect. However, if hierarchical CAR is enabled and MF classification contains only level-1 CAR, both QPPB Policy CAR and hierarchical CAR take effect.
  • When hierarchical CAR and QPPB policy CAR are both configured on an interface and level-2 CAR is configured for hierarchical CAR, QPPB policy CAR takes effect, and only CAR for the second-level ACL takes effect. First-level ACL CAR does not take effect.
  • When hierarchical CAR and QPPB policy CAR are configured on an interface and one CAR (CAR is configured in a parent or child policy) is configured for hierarchical CAR, QPPB policy CAR takes effect, and the one CAR for hierarchical CAR also takes effect.

Configuring only one of hierarchical CAR and CAR in ar QPPB Policy on one interface is recommended.

Hierarchical CAR and QPPB Policy CAR are mutually exclusive. If both functions are configured on the same interface, QPPB Policy CAR takes effect, and only second-level ACL in hierarchical CAR takes effect. First-level ACL CAR does not take effect. However, if hierarchical CAR is enabled and MF classification contains only level-1 CAR, both QPPB Policy CAR and hierarchical CAR take effect.

  • When a traffic policy is applied to a remote AP or Eth-Trunk AP interface, sampling can be configured in the traffic policy using commands but does not take effect.
  • ACL sampling does not support traffic policies in shared mode. Sampling can be configured in the traffic policy using commands but does not take effect.
  • ACL sampling is supported only on common sub-interfaces. It can be configured on sub-interfaces using commands but does not take effect.
  • Do not configure sampling in the traffic behavior in a traffic policy applied to a remote AP or Eth-Trunk AP interface.
  • When ACL sampling is configured, configure the traffic policy to work in unshared mode.
  • When ACL sampling is configured, apply the traffic policy to common sub-interfaces.
  • When a traffic policy is applied to a remote AP or Eth-Trunk AP interface, sampling can be configured in the traffic policy using commands but does not take effect.
  • ACL sampling does not support traffic policies in shared mode. Sampling can be configured in the traffic policy using commands but does not take effect.
  • ACL sampling is supported only on common sub-interfaces. It can be configured on sub-interfaces using commands but does not take effect.
Translation
Download
Updated: 2019-01-03

Document ID: EDOC1100055024

Views: 22440

Downloads: 115

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