Creating Named Aggregate Policers - Cisco 7604 Configuration Manual

Chapter 41 Configuring PFC QoS

Creating Named Aggregate Policers

To create a named aggregate policer, perform this task:
Command
Router(config)# mls qos aggregate-policer
policer_name bits_per_second normal_burst_bytes
[ maximum_burst_bytes ] [pir peak_rate_bps ]
[[[conform-action {drop | set-dscp-transmit
dscp_value | set-prec-transmit
transmit}] exceed-action {drop | policed-dscp |
transmit}] violate-action {drop | policed-dscp |
transmit}]
Router(config)# no mls qos aggregate-policer
policer_name
1. The set-dscp-transmit and set-prec-transmit keywords are only supported for IP traffic.
When creating a named aggregate policer, note the following information:
•
•
•
•
•
•
•
•
•
•
OL-4266-08
1
1
ip_precedence_value |
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.
In Release 12.2(18)SXE and later releases, you can apply aggregate 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.
The valid range of values for the CIR bits_per_second parameter is as follows:
Minimum—32 kilobits per second, entered as 32000
–
Maximum with Release 12.2(18)SXE and later releases:
–
10 gigabits per second, entered as 10000000000
Maximum with releases earlier than Release 12.2(18)SXE:
–
4 gigabits per second, entered as 4000000000
The normal_burst_bytes parameter sets the CIR token bucket size.
The maximum_burst_bytes parameter sets the PIR token bucket size.
When configuring the size of a token bucket, note the following information:
Cisco 7600 Series Router Cisco IOS Software Configuration Guide, Release 12.2SX
Purpose
Creates a named aggregate policer.
Deletes a named aggregate policer.
Configuring PFC QoS
for
41-63