Creating Named Aggregate Policers - Cisco WS-SUP32-GE-3B - Supervisor Engine 32 Software Configuration Manual

Configuring PFC QoS
This example shows how to enable egress ACL support for remarked DSCP on Fast Ethernet port 5/36:
Router# configure terminal
Enter configuration commands, one per line.
Router(config)# interface fastethernet 5/36
Router(config-if)# platform ip features sequential
Router(config-if)# end

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:
•
•
•
•
•
•
•
Catalyst Supervisor Engine 32 PISA Cisco IOS Software Configuration Guide, Release 12.2ZY
38-50
1
1
ip_precedence_value |
You can apply aggregate 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.
The valid range of values for the CIR bits_per_second parameter is as follows:
– Minimum—32 kilobits per second, entered as 32000
– Maximum—10 gigabits per second, entered as 10000000000
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:
The minimum token bucket size is 1 kilobyte, entered as 1000 (the maximum_burst_bytes
–
parameter must be set larger than the normal_burst_bytes parameter).
The maximum token bucket size is 32 megabytes, entered as 32000000.
–
To sustain a specific rate, set the token bucket size to be at least the rate value divided by 4000
–
because tokens are removed from the bucket every 1/4000th of a second (0.25 ms).
Because the token bucket must be large enough to hold at least one frame, set the parameter
–
larger than the maximum size of the traffic being policed.
– For TCP traffic, configure the token bucket size as a multiple of the TCP window size, with a
minimum value at least twice as large as the maximum size of the traffic being policed.
End with CNTL/Z.
Purpose
Creates a named aggregate policer.
Deletes a named aggregate policer.
Chapter 38 Configuring PFC QoS
for
OL-11439-03