Using Modular QoS CLI (MQC) for Implementing QoS

Using Modular QoS CLI (MQC) for Implementing QoS

Note

Cisco introduced MQC to help overcome the shortcomings of using the legacy CLI, and to utilize newer QoS tools and features available in Cisco IOS. MQC provides a building-block approach to applying QoS in that a single module can be used repeatedly to apply a policy to multiple interfaces.

The guidelines for using the MQC method are as follows:

STEP 1.	Define traffic classes using the class-map command.
STEP 2.	Define policies for the defined traffic classes using the policy-map command.
STEP 3.	Apply the defined policies in the inbound or outbound direction to each interface, subinterface, or circuit using the service-policy command.

Step 1: Defining Traffic Classes Using the class-map Command

Router(config)# class-map match-any business-traffic	Creates a class map named "business-traffic." Of the following listed match statements, any of them must be matched in order to classify the traffic.
Router(config-cmap)# match protocol ftp	Any traffic using the FTP protocol will be classified as "business-traffic."
Router(config-cmap)# match protocol citrix	Any Citrix traffic will be classified as "business-traffic."
Router(config-cmap)# exit	Returns to global configuration mode.
Router(config)# class-map VOIP	Creates a class map named "VOIP."
Router(config-cmap)# match access-group 100	Any traffic matching access list 100 is classified as "VOIP."
Router(config-cmap)# exit	Returns to global configuration mode.

Note

Names used in the class-map command are case sensitive.

Note

If you use the match-any argument in the class-map command, only one of the listed match statements must be met for classification to occur. If you use the match-all argument, all the listed match statements must be met for classification to occur. If you do not use either argument, then the match-all argument is applied by default.

Tip

The opposite of the match condition is the match not condition.