Configuring PFC QoS
The maximum_burst_bytes parameter is supported with PFC2. The maximum_burst_bytes
parameter is not supported with PFC, but can be entered with a value equal to the
The valid range of values for the pir bits_per_second parameter is as follows:
The pir bits_per_second parameter is supported with the PFC2. The pir bits_per_second parameter
is not supported with the PFC1 but can be entered with the PFC1 if the value is equal to the CIR
(Optional) You can specify a conform action for matched in-profile traffic as follows:
(Optional) For traffic that exceeds the CIR, you can specify an exceed action as follows:
(Optional) For traffic that exceeds the PIR, you can specify a violate action as follows:
Catalyst 6500 Series Switch Cisco IOS Software Configuration Guide—Release 12.1 E
Minimum—32 kilobits per second, entered as 32000 (the value cannot be smaller than the
CIR bits_per_second parameters)
Maximum—4 gigabits per second, entered as 4000000000
The default conform action is transmit, which sets the policy map class trust state to trust
DSCP unless the policy map class contains a trust command (see the
"Configuring Policy Map Class Actions" section on page
To set PFC QoS labels in untrusted traffic, enter the set-dscp-transmit keyword to mark
matched untrusted traffic with a new DSCP value or enter the set-prec-transmit keyword to
mark matched untrusted traffic with a new IP precedence value (with the PFC2, the
set-dscp-transmit and set-prec-transmit keywords are only supported for IP traffic). PFC QoS
sets egress ToS and CoS from the configured value.
Enter the drop keyword to drop all matched traffic.
When you configure drop as the conform action, PFC QoS configures drop as the exceed
action and the violate action.
The default exceed action is drop, except with a maximum_burst_bytes parameter (drop is not
supported with a maximum_burst_bytes parameter).
When the exceed action is drop, PFC QoS ignores any configured violate action.
Enter the policed-dscp-transmit keyword to cause all matched out-of-profile traffic to be
marked down as specified in the markdown map (see the
Values" section on page
When you create a policer that does not use the pir keyword and the maximum_burst_bytes
parameter is equal to the normal_burst_bytes parameter (which is the case if you do not enter
the maximum_burst_bytes parameter), the exceed-action policed-dscp-transmit keywords
cause PFC QoS to mark traffic down as defined by the policed-dscp max-burst markdown
To mark traffic without policing, enter the transmit keyword to transmit all matched
The default violate action is equal to the exceed action.
Configuring PFC QoS
"Policy Maps" section on
"Configuring DSCP Markdown