Overview of MQC
Modular QoS Command-Line Interface (MQC) allows you to classify packets based on packet characteristics and specify the same service for packets of the same type. In this way, different types of packets can be provided differentiated services.
As more services are deployed on a network, service deployment becomes increasingly complex because traffic of different services or users requires different services. Using MQC configuration, you can classify network traffic in a fine-grained way and specify the services provided to different types of traffic according to your needs. MQC enhances serviceability of your network.
MQC Entities
MQC involves three entities: traffic classifier, traffic behavior, and traffic policy.
Traffic classifier
A traffic classifier defines a group of matching rules to classify packets. Table 1-1 lists traffic classification rules.Table 1-1 Traffic classification rulesLayer
Traffic Classification Rule
Layer 2
- Destination MAC address
- Source MAC address
- VLAN ID in the tag of VLAN-tagged packets
- 802.1p priority in the tag of VLAN-tagged packets
- VLAN ID in the inner tag of VLAN packets
- 802.1p priority in the inner tag of QinQ packets
- Protocol field in the Layer 2 header
- Discard Eligible (DE) value in Frame Relay (FR) packets
- Data Link Connection Identifier (DLCI) in Frame Relay (FR) packets
- Permanent virtual circuit (PVC) information in ATM packets
- Matching fields in access control list (ACL) 4000 to ACL 4999
Layer 3
- Differentiated Services Code Point (DSCP) priority in IP packets
- IP precedence in IP packets
- IP protocol type (IPv4 or IPv6)
- RTP port number
- TCP-flag in TCP packets
- IPv4 packet length
- QoS group in an IPSec policy
- Matching fields in ACL 2000 to ACL 3999
- Matching fields in ACL6 2000 to ACL6 3999
Others
- All packets
- Inbound interface
- Outbound interface
- SAC
- User group
The relationship between rules in a traffic classifier can be AND or OR. The default relationship is OR.AND: If a traffic classifier contains ACL rules, a packet matches the traffic classifier only when it matches one ACL rule and all the non-ACL rules. If a traffic classifier does not contain ACL rules, a packet matches the traffic classifier only when it matches all the rules in the classifier.
OR: A packet matches a traffic classifier as long as it matches one of rules.
Traffic behavior
A traffic behavior defines an action for packets of a specified type.
Traffic policy
A traffic policy binds traffic classifiers and traffic behaviors, and then actions defined in traffic behaviors are taken for classified packets. As shown in Figure 1-1, a traffic policy can be bound to multiple traffic classifiers and traffic behaviors.
MQC Configuration Process
Configure a traffic classifier. The traffic classifier defines a group of matching rules to classify traffic and is the basis for differentiated services.
Configure a traffic behavior. The traffic behavior defines a flow control or resource allocation action for packets matching the rules.
Create a traffic policy and bind the traffic classifier to the traffic behavior in the traffic policy.
Apply the traffic policy to an interface or sub-interface.