26-48
Catalyst 3750 Metro Switch Software Configuration Guide
78-15870-01
Chapter 26 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-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/1/1-mutation) so that inbound DSCP values 10 to 13 are
mapped to DSCP 30:
Switch(config)# mls qos map dscp-mutation gi1/1/1-mutation 10 11 12 13 to 30
Switch(config)# interface gigabitethernet1/1/1
Switch(config-if)# mls qos trust dscp
Switch(config-if)# mls qos dscp-mutation gi1/1/1-mutation
Switch(config-if)# end
Configuring an Ingress QoS Policy
Configuring an ingress QoS policy typically requires classifying traffic into classes, configuring policies
applied to those traffic classes, and attaching the policies to a port.
For background information, see the “Ingress Classification” section on page 26-6 and the “Ingress
Policing and Marking” section on page 26-9. For configuration guidelines, see the “Standard QoS
Configuration Guidelines” section on page 26-40.
These sections describe how to classify, police, and mark inbound traffic. Depending on your network
configuration, you must perform one or more of these tasks:
• Classifying Ingress Traffic by Using ACLs, page 26-49
• Classifying Ingress Traffic by Using Class Maps, page 26-52
• Classifying, Policing, and Marking Ingress Traffic by Using Policy Maps, page 26-54
• Classifying, Policing, and Marking Ingress Traffic by Using Aggregate Policers, page 26-57
For information on configuring egress policies for the ES ports, see the “Configuring an Egress
Hierarchical QoS Policy” section on page 26-77. This section describes how to classify egress traffic by
using class maps, how to configure an egress two-rate traffic policer, how to configure class-based packet
marking in an egress traffic policy, how to configure CBWFQ, tail drop, DSCP-based WRED, and IP
precedence-based WRED, how to enable LLQ, and how to configure shaping.
Step 5
mls qos dscp-mutation
dscp-mutation-name
Apply the map to the specified ingress DSCP-trusted port.
For dscp-mutation-name, specify the mutation map name created in
Step 2.
You can configure multiple DSCP-to-DSCP-mutation maps on an
ingress port.
Step 6
end Return to privileged EXEC mode.
Step 7
show mls qos maps dscp-mutation Verify your entries.
Step 8
copy running-config startup-config (Optional) Save your entries in the configuration file.
Command Purpose
To Next Page
Loading...
Need help?
General
