Configuring Traffic Policing - 3Com S7906E Configuration Manual

Figure 4-4 Line rate implementation
In the token bucket approach to traffic control, bursty traffic can be transmitted so long as enough
tokens are available in the token bucket; if tokens are inadequate, packets cannot be transmitted until
the required number of tokens are generated in the token bucket. Thus, traffic rate is restricted to the
rate for generating tokens, thus limiting traffic rate and allowing bursty traffic.
Line rate can only limit the total traffic rate on a physical port, while traffic policing can limit the rate of a
flow on a port. To limit the rate of all the packets on a port, using line rate is easier.

Configuring Traffic Policing

Configuration Procedure
Follow these steps to configure traffic policing:
To do...
Enter system view
Create a class and enter
class view
Configure the match
criteria
Exit class view
Create a behavior and
enter behavior view
Configure a traffic policing
action
Exit behavior view
Use the command...
system-view
traffic classifier tcl-name [ operator
{ and | or } ]
if-match match-criteria
quit
traffic behavior behavior-name
car cir committed-information-rate
[ cbs committed-burst-size [ ebs
excess-burst-size ] ] [ pir
peak-information-rate ] [ green action ]
[ yellow action ] [ red action ]
quit
4-5
Remarks
—
—
—
—
—
Required
On SC, SA, and EA
LPUs, the granularity of
traffic policing is 64 kbps.
On SD and EB LPUs, the
granularity of traffic
policing is 8 kbps.
—