Cisco WS-SUP32-GE-3B - Supervisor Engine 32 Software Configuration Manual page 598

Configuring PFC QoS
Using a Named Aggregate Policer
To use a named aggregate policer, perform this task:
Command
Router(config-pmap-c)# police aggregate
aggregate_name
Router(config-pmap-c)# no police aggregate
aggregate_name
Configuring a Per-Interface Policer
To configure a per-interface policer, perform this task:
Command
Router(config-pmap-c)# police [flow [mask {src-only |
dest-only | full-flow}]] bits_per_second
normal_burst_bytes [maximum_burst_bytes] [pir
peak_rate_bps] [[[conform-action {drop |
set-dscp-transmit dscp_value | set-prec-transmit
ip_precedence_value | transmit}] exceed-action {drop
| policed-dscp | transmit}] violate-action {drop |
policed-dscp | transmit}]
Router(config-pmap-c)# no police [flow [mask
{src-only | dest-only | full-flow}]] bits_per_second
normal_burst_bytes [maximum_burst_bytes] [pir
peak_rate_bps] [[[conform-action {drop |
set-dscp-transmit dscp_value | set-prec-transmit
ip_precedence_value | transmit}] exceed-action {drop
| policed-dscp | transmit}] violate-action {drop |
policed-dscp | transmit}]
When configuring a per-interface policer, note the following information:
•
•
•
•
•
Catalyst Supervisor Engine 32 PISA Cisco IOS Software Configuration Guide, Release 12.2ZY
38-64
With a PFC3B, when you apply both ingress policing and egress policing to the same traffic, both
the input policy and the output policy must either mark down traffic or drop traffic. PFC QoS does
not support ingress markdown with egress drop or ingress drop with egress markdown.
You can apply aggregate and microflow policers to IPv6 traffic.
With a PFC3B, policing uses the Layer 2 frame size.
See the "PFC QoS Configuration Guidelines and Restrictions" section on page 38-39
information about rate and burst size granularity.
You can enter the flow keyword to define a microflow policer (you cannot apply microflow policing
to ARP traffic). When configuring a microflow policer, note the following information:
With a PFC3B, you can enter the mask src-only keywords to base flow identification only on
–
source addresses, which applies the microflow policer to all traffic from each source address.
PFC QoS supports the mask src-only keywords for both IP traffic and MAC traffic.
– With a PFC3B, you can enter the mask dest-only keywords to base flow identification only on
destination addresses, which applies the microflow policer to all traffic to each source address.
PFC QoS supports the mask dest-only keywords for both IP traffic and MAC traffic.
By default and with the mask full-flow keywords, PFC QoS bases IP flow identification on
–
source IP address, destination IP address, the Layer 3 protocol, and Layer 4 port numbers.
Purpose
Configures the policy map class to use a previously defined
named aggregate policer.
Clears use of the named aggregate policer.
Purpose
Creates a per-interface policer and configures the policy-map
class to use it.
Deletes the per-interface policer from the policy-map class.
Chapter 38 Configuring PFC QoS
for
OL-11439-03