Cisco 6500 Series Software Configuration Manual page 436

Hide thumbs Also See for 6500 Series:
Table of Contents

Advertisement

Configuring PFC QoS
Configuring a Per-Interface Policer
To configure a per-interface policer (see the
Command
Router(config-pmap-c)# police [flow] bits_per_second
normal_burst_bytes [maximum_burst_bytes] [pir
peak_rate_bps] [[[conform-action {drop |
2
set-dscp-transmit
dscp_value | set-prec-transmit
ip_precedence_value | transmit}] exceed-action {drop
| policed-dscp | transmit}] violate-action
policed-dscp | transmit}]
Router(config-pmap-c)# no police [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}]
1. Supported only with PFC2. Not supported in microflow policers (the flow keyword configures a microflow policer).
2. With PFC2, the set-dscp-transmit and set-prec-transmit keywords are only supported for IP traffic.
When configuring a per-interface policer, note the following:
Catalyst 6500 Series Switch Cisco IOS Software Configuration Guide—Release 12.1 E
31-46
1
1
{drop |
Policing uses the Layer 3 packet size.
See the
"PFC QoS Configuration Guidelines and Restrictions" section on page 31-31
information about rate and burst size granularity.
You can enter the flow keyword to define a microflow policer. During microflow policing, the
following occurs:
PFC QoS considers IPX traffic with same source network, destination network, and destination
node to be part of the same flow, including traffic with different source nodes or sockets.
PFC QoS considers MAC-Layer traffic with the same protocol and the same source and
destination MAC-Layer addresses to be part of the same flow, including traffic with different
ethertypes.
Microflow policers do not support the maximum_burst_bytes parameter, the
pir bits_per_second keyword and parameter, or the violate-action keyword.
The valid range of values for the CIR bits_per_second parameter is as follows:
Minimum—32 kilobits per second, entered as 32000
Maximum—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 (not supported with the flow
keyword)
When configuring the size of a token bucket, note the following:
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 approximately 32 megabytes, entered as 31250000
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).
"Policers" section on page
Purpose
Creates a per-interface policer and configures the policy map
class to use it.
2
Deletes the per-interface policer from the policy map class.
Chapter 31
Configuring PFC QoS
31-19), perform this task:
for
78-14099-04

Advertisement

Table of Contents
loading

Table of Contents