Reference Guide

494 Quality of Service
– Exceed Action — Select the action to be performed on incoming
packets that exceed the CIR. The possible options are:
•
None — No action is performed on packets exceeding the defined
CIR value.
•
Drop — Packets exceeding the defined CIR value are dropped.
•
Remark DSCP — The DSCP values of packets exceeding the
defined CIR value are rewritten to a value entered in the
DSCP
Mapping
pages.
Defining Aggregate Policers Using CLI Commands
The following table summarizes the CLI commands for setting the fields in
the Aggregate Policer pages.
The following is an example of the CLI commands:
Policy Table
To create a single policer:
1
Create a policy in the Police Table pages
2 Configure the policy in the Policy Class Maps pages. Here the policy class
can be designated as containing a single policer, or it can be designated as
containing Aggregate policers.
A policy can consist of one of the following:
• One or more class maps of ACLs that define the traffic flows in the policy.
Table 22-13. Aggregate Policer CLI Commands
CLI Command Description
qos aggregate-policer
aggregate-policer-name
committed-rate-kbps excess-
burst-byte[exceed-action
{drop|policed-dscp-transmit}]
no qos aggregate-policer
aggregate-policer-name
Defines the policer parameters that can
be applied to multiple traffic classes
within the same policy map.
Use the no form of this command to
remove an existing aggregate policer.
console(config)# qos aggregate-policer policer1
124000 9600 exceed-action drop