Content

| 8.2 |  | Quality of Service Mechanisms |
| 8.2.8 |  | Defining the QoS policy – the policy-map |

The policy-map command is used to create a traffic policy. The purpose of a traffic policy is to configure the QoS features that should be associated with the traffic that has been classified in a user-specified traffic class. A traffic policy contains three elements:

- Policy Name
- Traffic class specified with the class command
- QoS policies to be applied to each class

The policy-map shown below creates a traffic policy named policy1. The policy applies to all traffic classified by the previously defined traffic-class “cisco” and specifies that traffic in this example should be allocated bandwidth of 3000 kbps. Any traffic which does not belong to the class “cisco” forms part of the catch-all class-default class and will be given a default bandwidth of 2000 kbps.

> Switch(config)#policy-map policy1
> Switch(config-pmap)#class cisco
> Switch(config-pmap-c)#bandwidth 3000
> Switch(config-pmap-c)#exit
> Switch(config-pmap)#class class-default
> Switch(config-pmap-c)#bandwidth 2000
> Switch(config-pmap)#exit

> Note: The actual policies that can be implemented are platform dependent. The example given above is relevant for a Catalyst 3550 or Catalyst 6500 but the bandwidth command is not supported by the Catalyst 2950.

The Modular QoS CLI does not necessarily require that users associate only one traffic class to one traffic policy. When packets match to more than one match criterion, multiple traffic classes can be associated with a single service policy.