Cisco 7604 Configuration Manual page 680

Configuring PFC QoS
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:
•
•
•
•
•
•
•
•
Cisco 7600 Series Router Cisco IOS Software Configuration Guide, Release 12.2SX
41-78
Aggregate policing works independently on each DFC-equipped switching module and
independently on the PFC, which supports any non-DFC-equipped switching modules. Aggregate
policing does not combine flow statistics from different DFC-equipped switching modules. You can
display aggregate policing statistics for each DFC-equipped switching module and for the PFC and
any non-DFC-equipped switching modules supported by the PFC.
Each PFC or DFC polices independently, which might affect QoS features being applied to traffic
that is distributed across the PFC and any DFCs. Examples of these QoS feature are:
– Policers applied to a port channel interface.
– Policers applied to a switched virtual interface.
Egress policers applied to either a Layer 3 interface or an SVI. Note that PFC QoS performs
–
egress policing decisions at the ingress interface, on the PFC or ingress DFC.
Policers affected by this restriction deliver an aggregate rate that is the sum of all the independent
policing rates.
With a PFC3, 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.
With Release 12.2(18)SXE and later releases, you can apply aggregate and microflow policers to
IPv6 traffic.
With a PFC3, policing uses the Layer 2 frame size.
With a PFC2, policing uses the Layer 3 packet size.
See the "PFC QoS Configuration Guidelines and Restrictions" section on page 41-50
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:
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 41 Configuring PFC QoS
for
OL-4266-08