Configuring and Monitoring Policy Maps

This topic describes the Cisco IOS MQC commands required to configure and monitor a policy map.

You can configure service policies by using the policy-map command. Use up to 256 classes within one policy map by using the class command with the name of a preconfigured class map.

You can also use a nonexistent class within the policy-map configuration mode if the match condition is specified after the name of the class. The running configuration will reflect such a configuration by using the match-any strategy and inserting a full class map configuration.

The table shows starting and resulting configuration modes for the class-map, policy-map, and class commands:

Configuration Modes

Starting configuration mode


Configuration mode










All traffic that is not classified by any of the class maps that are used within the policy map is part of the default class "class-default." This class has no QoS guarantees, by default. The default class, when used on output, can use one FIFO queue or flow-based weighted fair queuing (WFQ). The default class is part of every policy map, even if not configured.

Configuring Policy Maps (Cont.)


, ... , . .

• You should use descriptions in large and complex configurations.

• The description has no operational meaning.


<PHB mechanism>

• Per-class service policies are configured within the per-class policy-map configuration mode.

• MQC supports the following QoS mechanisms:

- Class-based weighted fair queuing (CBWFQ)

- Low-latency queuing

- Class-based policing

- Class-based shaping

- Class-based marking

— 1

Policy maps, like class maps, should use descriptions in large QoS implementations where a large number of different policy maps are used.

Renaming a policy map would normally require the renaming of all the references to the policy map. Using the rename command simplifies the renaming process by automatically renaming all references.

Was this article helpful?

0 0

Post a comment