Chapter 36 Configuring QoS

Configuring Standard QoS

 

 

Command

Purpose

 

 

 

 

 

Step 4

policy-mappolicy-map-name

Create a policy map by entering the policy map name, and enter

 

 

 

 

policy-map configuration mode.

 

 

 

 

For more information, see the “Classifying, Policing, and Marking

 

 

 

 

Traffic on Physical Ports by Using Policy Maps” section on

 

 

 

 

page 36-51.

 

 

 

 

 

Step 5

class class-map-name

Define a traffic classification, and enter policy-map class

 

 

 

 

configuration mode.

 

 

 

 

For more information, see the “Classifying, Policing, and Marking

 

 

 

 

Traffic on Physical Ports by Using Policy Maps” section on

 

 

 

 

page 36-51.

 

 

 

 

 

Step 6

police aggregate aggregate-policer-name

Apply an aggregate policer to multiple classes in the same policy

 

 

 

 

map.

 

 

 

 

For aggregate-policer-name, enter the name specified in Step 2.

 

 

 

 

 

Step 7

exit

Return to global configuration mode.

 

 

 

 

 

Step 8

interface interface-id

Specify the port to attach to the policy map, and enter interface

 

 

 

 

configuration mode.

 

 

 

 

Valid interfaces include physical ports.

 

 

 

 

 

Step 9

service-policy input policy-map-name

Specify the policy-map name, and apply it to an ingress port.

 

 

 

 

Only one policy map per ingress port is supported.

 

 

 

 

 

Step 10

end

Return to privileged EXEC mode.

 

 

 

 

 

Step 11

show mls qos aggregate-policer

Verify your entries.

 

 

[aggregate-policer-name]

 

 

 

 

 

 

 

Step 12

copy running-config startup-config

(Optional) Save your entries in the configuration file.

 

 

 

 

 

 

 

 

To remove the specified aggregate policer from a policy map, use the no police aggregate

 

 

 

aggregate-policer-namepolicy map configuration mode. To delete an aggregate policer and its

 

 

 

parameters, use the no mls qos aggregate-policeraggregate-policer-nameglobal configuration

 

 

 

command.

 

 

 

 

 

This example shows how to create an aggregate policer and attach it to multiple classes within a policy

 

 

 

map. In the configuration, the IP ACLs permit traffic from network 10.1.0.0 and from host 11.3.1.1. For

 

 

 

traffic coming from network 10.1.0.0, the DSCP in the incoming packets is trusted. For traffic coming

 

 

 

from host 11.3.1.1, the DSCP in the packet is changed to 56. The traffic rate from the 10.1.0.0 network

 

 

 

and from host 11.3.1.1 is policed. If the traffic exceeds an average rate of 48000 b/s and a normal burst

 

 

 

size of 8000 bytes, its DSCP is marked down (based on the policed-DSCP map) and sent. The policy

 

 

 

map is attached to an ingress port.

 

 

 

 

 

Switch(config)# access-list 1 permit 10.1.0.0 0.0.255.255

 

 

 

Switch(config)# access-list 2 permit 11.3.1.1

 

 

 

Switch(config)# mls qos aggregate-police transmit1 48000 8000 exceed-action

 

 

 

policed-dscp-transmit

 

 

 

 

 

Switch(config)# class-map ipclass1

 

 

 

Switch(config-cmap)# match access-group 1

 

 

 

Switch(config-cmap)# exit

 

 

 

 

 

Switch(config)# class-map ipclass2

 

 

 

Switch(config-cmap)# match access-group 2

 

 

 

Switch(config-cmap)# exit

 

 

 

 

 

Switch(config)# policy-map aggflow1

 

 

 

Switch(config-pmap)# class ipclass1

 

 

 

Catalyst 3750-E and 3560-E Switch Software Configuration Guide

 

 

 

 

36-62

 

 

OL-9775-02

 

 

 

 

 

Page 812
Image 812
Cisco Systems 3750E manual Only one policy map per ingress port is supported, Show mls qos aggregate-policer