Chapter 36 Configuring QoS

Configuring Standard QoS

To return a port to its non-trusted state, use the no mls qos trust interface configuration command. To return to the default DSCP-to-DSCP-mutation map values, use the no mls qos map dscp-mutationdscp-mutation-nameglobal configuration command.

This example shows how to configure a port to the DSCP-trusted state and to modify the DSCP-to-DSCP-mutation map (named gi1/0/2-mutation) so that incoming DSCP values 10 to 13 are mapped to DSCP 30:

Switch(config)# mls qos map dscp-mutation gi1/0/2-mutation 10 11 12 13 to 30

Switch(config)# interface gigabitethernet1/0/2

Switch(config-if)# mls qos trust dscp

Switch(config-if)#mls qos dscp-mutation gi1/0/2-mutation

Switch(config-if)# end

Configuring a QoS Policy

Configuring a QoS policy typically requires classifying traffic into classes, configuring policies applied to those traffic classes, and attaching policies to ports.

For background information, see the “Classification” section on page 36-5and the “Policing and Marking” section on page 36-8. For configuration guidelines, see the “Standard QoS Configuration Guidelines” section on page 36-35.

These sections describe how to classify, police, and mark traffic. Depending on your network configuration, you must perform one or more of these tasks:

Classifying Traffic by Using ACLs, page 36-46

Classifying Traffic by Using Class Maps, page 36-49

Classifying, Policing, and Marking Traffic on Physical Ports by Using Policy Maps, page 36-51

Classifying, Policing, and Marking Traffic on SVIs by Using Hierarchical Policy Maps, page 36-55

Classifying, Policing, and Marking Traffic by Using Aggregate Policers, page 36-61

 

 

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

 

 

 

 

 

 

OL-9775-02

 

 

36-45

 

 

 

 

 

Page 795
Image 795
Cisco Systems 3750E manual Configuring a QoS Policy, 36-45, Switchconfig-if#mls qos dscp-mutation gi1/0/2-mutation