Configuring Traffic Policing; Syntax - Avaya 1000 Series Configuration Manual

QOS Configuration
complexity (in configuration and implementation as well) without adding much usefulness.
Specifying just the "Rate" and "Burst" makes the policing feature simple and effective. The
"extended burst" parameter is needed to permit a large packet, by loaning tokens, when there
are not enough tokens available at a given time for the entire packet. The Avaya policing
algorithm allows for such "loaning of tokens" by default.

Configuring Traffic Policing

As with CBQ, the first step is traffic classification. Flows should be defined by creating traffic
classes. To classify based on multiple fields, for e.g. source IP address and port, a hierarchy
of classes should be created. Traffic policing for a class can be configured using the "police"
command at the class level as shown below. Policing for non-leaf classes (which define more
aggregate flows) is currently not be supported. Multi-level policing will be supported in a later
release.
The policing rate and burst limit can be configured using the police command. Only the
"rate" parameter is mandatory. Burst limit can be specified in Kbits or milliseconds using the
"burst" parameter or the "burst-time" parameter respectively. If not specified, a default value
of 1000 ms is used for the burst limit. "no" form of the command can be used to unconfigure
policing for a class.

Syntax

police rate <rate in kbps or percent> [burst <burst kbits> |
burst-time <burst msec>]
no police
The example below shows the different variations of the police command. Class c1 is
configured for policing with a rate of 512 Kbps and a burst of 768 Kbits. This translates to a
permissible burst of 1.5 sec at the rate of 512 Kbps.
R1/configure/interface/bundle wan1/qos/class c1>
police rate 512 burst 768
R1/configure/interface/bundle wan1/qos/class c1>
exit
R1/configure/interface/bundle wan1/qos> class c2
R1/configure/interface/bundle wan1/qos/class c2>
police rate 1024 burst-time 800
R1/configure/interface/bundle wan1/qos/class c2>
exit
R1/configure/interface/bundle wan1/qos> class c3
R1/configure/interface/bundle wan1/qos/class c3>
police rate 256
After configuring policing parameters for the individual classes, policing needs to be enabled
at the "/interface/qos" level on that interface for a specific traffic direction. It is not mandatory
for policing to be configured for all classes on the interface for a given traffic direction. If policing
222 Avaya Secure Router 1000 Series Configuration Guide December 2010