Licensing Requirements and Limitations for MQC

Involved Network Elements

Other network elements are not required.

Licensing Requirements

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

Hardware Requirements

Feature Limitations

• Before defining matching rules based on application protocols, enable the SAC function and load the signature file.

• When the ACL rules in a traffic classifier match source IP addresses of packets, you can use NAT pre-classification to implement differentiated services for packets from different private IP addresses. To configure NAT pre-classification, run the qos pre-nat command on an interface. Then private IP addresses of packets can be used to classify packets on the outbound interface.

• When permit and other actions are configured in a traffic behavior, the actions are performed in sequence. deny cannot be configured with other actions. When deny is configured, other configured actions, except traffic statistics collection and flow mirroring, do not take effect.

• If you specify a packet filtering action for packets matching an ACL rule, the system first checks the action defined in the ACL rule. If the ACL rule defines permit, the action taken for the packets depends on whether deny or permit is specified in the traffic behavior. If the ACL rule defines deny, the packets are discarded regardless of whether deny or permit is configured in the traffic behavior.

• If a traffic behavior has remark 8021p, remark mpls-exp, or remark dscp action but not remark local-precedence, the local priority of packets are marked 0.

• The NQA test instance that is associated with a redirection behavior must an ICMP test instance. For details, see Configuring an ICMP Test Instance in the NetEngine AR Configuration Guide - NQA Configuration.

• Redirection is invalid for hop-by-hop IPv6 packets.

• V300R019C00 version: The device only supports redirection to 3G/LTE and dialer interfaces. In MPoEoA scenarios, the device does not support redirection to a dialer interface.
• V300R019C10 and later versions: The device only supports redirection to 3G/LTE, dialer interfaces, and Virtual-Template interfaces.
• A traffic policy containing the following traffic behaviors can only be applied to the outbound direction on a WAN interface:
  • Traffic shaping
  • Adaptive traffic shaping
  • Congestion management
  • Congestion avoidance
• If a traffic classifier defines non-first-fragment, the device cannot apply CAR to fragments sent to the device or collect statistics on the fragments.
• When an MQC traffic policy is configured on a bridge, Layer 2 ACL rules cannot be used to match packets. That is, packets cannot be matched based on their Layer 2 information such as the source MAC address, destination MAC address, Layer 2 protocol type, and VLAN.
• When an interface is added to a network bridge, the traffic behavior that is configured on the interface in the inbound direction can only define the following actions:
  • Re-marking the 802.1p priority in VLAN packets.
  • Configuring MQC to implement traffic policing.
  • Traffic statistics.