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.

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 Huawei AR Series Access Routers Configuration Guide - NQA Configuration.

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

• The device supports only redirection to 3G/LTE cellular and dialer interfaces. When MPoEoA is used, the device does not support redirection to dialer 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 matched. That is, Layer 2 information such as source MAC addresses, destination MAC addresses, Layer 2 protocol types, and VLANs cannot be matched.

• The 4GE-2S, 4ES2G-S, 4ES2GP-S, 9ES2 and 24ES2GP cards do not support MQC.

• The AR150, AR200, AR1200, AR3600 series, AR161F, AR161FG-L, AR161FGW-L, AR161FGW-Lc, AR161FW, AR162F, AR168F, AR169F, AR169FVW, AR169JFVW-4B4S, AR169FGW-L, AR161FW-P-M5, AR161F-DGP, AR161FGW-La, AR161FV-1P, AR168F-4P, AR169BF, AR169FVW-8S, AR169FGVW-L, AR1220C, AR1220E, AR1220EV, AR1220EVW, AR1220-AC, AR1220-DC, AR1220-8GE, AR1220F, AR1220L, AR1220V, AR1220W, AR1220VW, AR2204E-D, AR2220E, AR2240C, AR2204, AR2204E, AR2220L-AC, and AR2220L-DC do not support Layer 2 MQC.