36-54
Cisco Catalyst Blade Switch 3130 and 3032 for Dell Software Configuration Guide
OL-12247-04
Chapter 36 Configuring QoS
Configuring Standard QoS
Switch(config-cmap)#
exit
Switch(config)#
Policy-map pm1
Switch(config-pmap)#
class cm-1
Switch(config-pmap-c)#
set dscp 4
Switch(config-pmap-c)#
exit
Switch(config-pmap)#
class cm-2
Switch(config-pmap-c)#
set dscp 6
Switch(config-pmap-c)#
exit
Switch(config-pmap)#
exit
Switch(config)#
interface G1/0/1
Switch(config-if)#
service-policy input pm1
This example shows how to configure a class map that applies to both IPv4 and IPv6 traffic:
Switch(config)#
ip access-list 101 permit ip any any
Switch(config)#
ipv6 access-list ipv6-any permit ip any any
Switch(config)#
Class-map cm-1
Switch(config-cmap)#
match access-group 101
Switch(config-cmap)#
exit
Switch(config)#
Class-map cm-2
Switch(config-cmap)#
match access-group name ipv6-any
Switch(config-cmap)#
exit
Switch(config)#
Policy-map pm1
Switch(config-pmap)#
class cm-1
Switch(config-pmap-c)#
set dscp 4
Switch(config-pmap-c)#
exit
Switch(config-pmap)#
class cm-2
Switch(config-pmap-c)#
set dscp 6
Switch(config-pmap-c)#
exit
Switch(config-pmap)#
exit
Switch(config)#
interface G0/1
Switch(config-if)#
switch mode access
Switch(config-if)#
service-policy input pm1
Classifying, Policing, and Marking Traffic on Physical Ports by Using Policy Maps
You can configure a nonhierarchical policy map on a physical port that specifies which traffic class to
act on. Actions can include trusting the CoS, DSCP, or IP precedence values in the traffic class; setting
a specific DSCP or IP precedence value in the traffic class; and specifying the traffic bandwidth
limitations for each matched traffic class (policer) and the action to take when the traffic is out of profile
(marking).
A policy map also has these characteristics:
•
A policy map can contain multiple class statements, each with different match criteria and policers.
•
A separate policy-map class can exist for each type of traffic received through a port.
Follow these guidelines when configuring policy maps on physical ports:
•
You can attach only one policy map per ingress port.
•
If you configure the IP-precedence-to-DSCP map by using the
mls qos map ip-prec-dscp
dscp1...dscp8
global configuration command, the settings only affect packets on ingress interfaces
that are configured to trust the IP precedence value. In a policy map, if you set the packet IP
precedence value to a new value by using the
set ip precedence
new-precedence
policy-map class
configuration command, the egress DSCP value is not affected by the IP-precedence-to-DSCP map.
If you want the egress DSCP value to be different than the ingress value, use the
set dscp
new-dscp
policy-map class configuration command.
