Configuring An Ingress Qos Policy - Cisco Catalyst 3750 Software Configuration Manual

Configuring Standard QoS
Command
Step 5 mls qos dscp-mutation
dscp-mutation-name
Step 6
end
Step 7
show mls qos maps dscp-mutation
Step 8 copy running-config startup-config
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
Policing and Marking" section on page
Configuration Guidelines" section on page
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:
•
•
•
•
For information on configuring egress policies for the ES ports, see the
Hierarchical QoS Policy" section on page
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.
Catalyst 3750 Metro Switch Software Configuration Guide
26-48
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
Purpose
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.
Return to privileged EXEC mode.
Verify your entries.
(Optional) Save your entries in the configuration file.
"Ingress Classification" section on page 26-6
26-9. For configuration guidelines, see the
26-40.
26-77. This section describes how to classify egress traffic by
Chapter 26 Configuring QoS
and the "Ingress
"Standard QoS
"Configuring an Egress
78-15870-01