Use the qos aggregate-policer Global Configuration mode command to define the policer parameters that can be applied to multiple traffic classes. Use the
no form of this command to remove an existing aggregate policer.
Syntax
qos aggregate-policer aggregate-policer-name committed-rate-kbps committed-burst-byte [exceed-action action] [peak peak-rate-kbps peak-burst-byte [violate-action action]]
no qos aggregate-policer aggregate-policer-name
Parameters
-
aggregate-policer-name—Specifies the aggregate policer name. (Length: 1–32 characters)
-
committed-rate-kbps—Specifies the average traffic rate (CIR) in kbits per second (bps).(Range: 3–57982058)
-
committed-burst-byte—Specifies the normal burst size (CBS) in bytes. (Range: 3000–19173960)
-
exceed-action—Specifies the action taken when the committed rate is exceeded and the peak rate is not exceeded. If the keyword is not configured
then the following action is applied:
-
drop, if peak the keyword is not configured.
-
policed-dscp-transmit, if peak the keyword is configured.
-
peak—Specifies the Two-rate Three-color policer. If the peak rate is exceeded the packet is dropped.
-
action—Specifies the taken action. The possible values are:
Default Configuration
No aggregate policer is defined.
Command Mode
Global Configuration mode
User Guidelines
This command is only available when QoS is in advanced mode.
Use the qos aggregate-policer command to define a policer that aggregates traffic from multiple class maps.
Aggregate policers cannot aggregate traffic from multiple devices. If the aggregate policer is applied to more than one device,
the traffic on each device is counted separately and is limited per device.
Traffic from two different ports on the same device can be aggregated for policing purposes.
An aggregate policer can be applied to multiple classes in the same policy map.
An aggregate policer cannot be deleted if it is being used in a policy map. The no police aggregate Policy-map Class Configuration mode command must first be used to delete the aggregate policer from all policy maps before
using the no qos aggregate-policer command.
Policing uses a token bucket algorithm. CIR represents the speed with which the token is added to the bucket. CBS represents
the depth of the bucket.
Examples
Example 1. The following example defines the parameters of a policer called policer1 that can be applied to multiple classes in the same
policy map. When the average traffic rate exceeds 124,000 kbps or the normal burst size exceeds 9600 bytes, the packet is
dropped.
switchxxxxxx(config)# qos aggregate-policer policer1 124000 9600 exceed-action drop
Example 2. The following example defines the parameters of a Two-rate Three-color policer called policer2 that can be applied to multiple
classes in the same policy map. When the average traffic rate exceeds 124,000 kbps or the normal burst size exceeds 9600 bytes,
the packet is remarked. When the average traffic rate exceeds 200,000 kbps or the normal burst size exceeds 9600 bytes, the
packet is dropped.
switchxxxxxx(config)# qos aggregate-policer policer2 124000 9600 exceed-action policed-dscp-transmit peak 200000 19200 violate-action policed-dscp-transmit