Configuring A Qos Policy - Cisco Catalyst 3120 Software Manual

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-mutation
dscp-mutation-name global 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 gigabitethernet1/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 gigabitethernet1/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
Marking" section on page
Guidelines" section on page
These sections describe how to classify, police, and mark traffic. Depending on your network
configuration, you must perform one or more of these tasks:
•
•
•
•
•
Cisco Catalyst Blade Switch 3120 for HP Software Configuration Guide
36-42
36-8. For configuration guidelines, see the
36-32.
Classifying Traffic by Using ACLs, page 36-43
Classifying Traffic by Using Class Maps, page 36-46
Classifying, Policing, and Marking Traffic on Physical Ports by Using Policy Maps, page 36-48
Classifying, Policing, and Marking Traffic on SVIs by Using Hierarchical Policy Maps, page 36-52
Classifying, Policing, and Marking Traffic by Using Aggregate Policers, page 36-58
"Classification" section on page 36-5
Chapter 36 Configuring QoS
and the "Policing and
"Standard QoS Configuration
OL-12247-01