In the first part of the MQC review – we examined class maps. These devices place our traffic into containers that we can assign QoS actions to. In this article, we are going to look at policy maps for assigning those actions.
Here I will create a quick class map, verify the class map, and then enter policy map configuration mode:
R1(config)#class-map match-any CM_ICMP
R1(config-cmap)#match access-group 100
R1(config-cmap)#exit
R1(config)#exit
R1#! The access-list 100 is not shown in this configuration
R1#show class-map
Class Map match-any class-default (id 0)
Match any
Class Map match-any CM_ICMP (id 1)
Match access-group 100
R1#conf t
R1(config)#policy-map PM_ICMP
R1(config-pmap)#?
Policy-map configuration commands:
class policy criteria
description Policy-Map description
exit Exit from policy-map configuration mode
no Negate or set default values of a command
rename Rename this policy-map
R1(config-pmap)#
As you can see from the above configuration, there is not much going on in policy map configuration mode. We can add a description or rename the policy map but that is about it. The magic happens when we enter policy map class configuration for one of the classes that we configured: Continue reading The Modular Quality of Service CLI (MQC) Review – Policy Maps