Configuring PFC QoS
Configuring Policy Map Class Actions
When configuring policy map class actions, note the following information:
•
•
•
•
•
•
•
•
These sections describe policy map class action configuration:
•
•
•
Catalyst Supervisor Engine 32 PISA Cisco IOS Software Configuration Guide, Release 12.2ZY
38-62
Policy maps can contain one or more policy map classes.
Put all trust-state and policing commands for each type of traffic in the same policy map class.
PFC QoS only applies commands from one policy map class to traffic. After traffic has matched the
filtering in one policy map class, QoS does apply the filtering configured in other policy map
classes.
For hardware-switched traffic, PFC QoS does not support the bandwidth, priority, queue-limit, or
random-detect policy map class commands. You can configure these commands because they can
be used for software-switched traffic.
PFC QoS does not support the set qos-group policy map class commands.
PFC QoS supports the set ip dscp and set ip precedence policy map class commands for IPv4
traffic.
You can use the set ip dscp and set ip precedence commands on non-IP traffic to mark the
–
internal DSCP value, which is the basis of the egress Layer 2 CoS value.
The set ip dscp and set ip precedence commands are saved in the configuration file as set dscp
–
and set precedence commands.
PFC QoS supports the set dscp and set precedence policy map class commands for IPv4 and IPv6
traffic.
You cannot do all three of the following in a policy map class:
–
Mark traffic with the set commands
–
Configure the trust state
Configure policing
–
In a policy map class, you can either mark traffic with the set commands or do one or both of the
following:
–
Configure the trust state
Configure policing
–
When configure policing, you can mark traffic with policing keywords.
Note
Configuring Policy Map Class Marking, page 38-63
Configuring the Policy Map Class Trust State, page 38-63
Configuring Policy Map Class Policing, page 38-63
Chapter 38
Configuring PFC QoS
OL-11439-03