Configuring Traffic Policing - HP 5830 Series Configuration Manual

Rate limit also uses token buckets for traffic control. With rate limit configured on an interface, all packets
to be sent through the interface are handled by the token bucket for rate limiting. If enough tokens are in
the token bucket, packets can be forwarded. Otherwise, packets are put into QoS queues for congestion
management. In this way, the traffic passing the physical interface is controlled.
Figure 11 Rate limit implementation
The token bucket mechanism limits traffic rate when accommodating bursts. It allows bursty traffic to be
transmitted if enough tokens are available. If tokens are scarce, packets cannot be transmitted until
efficient tokens are generated in the token bucket. It restricts the traffic rate to the rate for generating
tokens.
Rate limit controls the total rate of all packets on a physical interface. It is easier to use than traffic policing
in controlling the total traffic rate on a physical interface.
NOTE:
Both Layer 2 and Layer 3 Ethernet interfaces support the traffic shaping and rate limit functions. The term
"interface" in this chapter collectively refers to these two types of interfaces. You can use the port
link-mode command to configure an Ethernet port as a Layer 2 or Layer 3 interface (see
Switching Configuration Guide

Configuring traffic policing

Do not configure traffic policing with any priority marking action (including local precedence, drop
precedence, 802.1p priority, DSCP value, or IP precedence marking actions) in the same traffic behavior.
Otherwise, you will fail to apply the QoS policy successfully.
To configure traffic policing:
Step
1. Enter system view.
2. Create a class and enter
class view.
3. Configure match criteria.
).
Command
system-view
traffic classifier tcl-name
[ operator { and | or } ]
if-match match-criteria
33
Remarks
N/A
N/A
N/A
Layer 2—LAN