Licensing Requirements and Limitations for HQoS
Involved Network Elements
Other network elements are not required.
Licensing Requirements
HQoS is a basic feature of a router and is not under license control.
Hardware Requirements
This section is applicable to all models. For details about differences for specific models, see the description in the corresponding section.
Feature Limitations
- MQC can be used to implement hierarchical scheduling on tunnel interfaces only in V300R019C10 and later versions.
- Sub-interfaces can inherit the traffic policy on a VE interface only in V300R019C10 and later versions.
- The sub traffic policy configured in the traffic behavior of a traffic policy cannot be the traffic policy itself.
- On the device, traffic policy nesting can be configured on Layer 2 VE interfaces, physical WAN interfaces, or sub-interfaces.
If traffic policy nesting is configured on a sub-interface, queue-based functions cannot be configured on the main interface, including traffic shaping, congestion management, and congestion avoidance.
If traffic shaping, congestion management, or congestion avoidance is configured in both a traffic policy and its sub traffic policy, traffic policy nesting and traffic shaping cannot be configured on the same sub-interface.
If you configure traffic policy nesting on a sub-interface, only one pair of traffic classifiers and traffic behaviors can be configured in the traffic policy, and only the default traffic classifier default-class can be used.