HP 6125G HP 6125G & 6125G/XG Blade Switches ACL and QoS Configuration - Page 41

Configuring traffic policing, Configuration restrictions and guidelines, Configuration procedure

Page 41 highlights

The line rate of a physical interface specifies the maximum rate for forwarding packets (including critical packets). Line rate also uses token buckets for traffic control. With line rate configured on an interface, all packets to be sent through the interface are handled by the token bucket at line rate. 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 12 Line rate 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. Line rate can only limit traffic rate on a physical interface, and traffic policing can limit the rate of a flow on an interface. To limit the rate of all the packets on interfaces, using line rate is easier. Configuring traffic policing Configuration restrictions and guidelines In a traffic behavior, do not configure traffic policing with any priority marking action (including local precedence, drop precedence, 802.1p priority, DSCP value, and IP precedence marking actions) in the same traffic behavior. Otherwise, you will fail to apply the QoS policy successfully. Configuration procedure To configure traffic policing: Step 1. Enter system view. 2. Create a class and enter class view. 3. Configure match criteria. Command Remarks system-view N/A traffic classifier tcl-name [ operator { and | or } ] N/A if-match match-criteria N/A 35

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84

35
The line rate of a physical interface specifies the maximum rate for forwarding packets (including critical
packets).
Line rate also uses token buckets for traffic control. With line rate configured on an interface, all packets
to be sent through the interface are handled by the token bucket at line rate. 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 12
Line rate 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.
Line rate can only limit traffic rate on a physical interface, and traffic policing can limit the rate of a flow
on an interface. To limit the rate of all the packets on interfaces, using line rate is easier.
Configuring traffic policing
Configuration restrictions and guidelines
In a traffic behavior, do not configure traffic policing with any priority marking action (including local
precedence, drop precedence, 802.1p priority, DSCP value, and IP precedence marking actions) in the
same traffic behavior. Otherwise, you will fail to apply the QoS policy successfully.
Configuration procedure
To configure traffic policing:
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Create a class and enter class
view.
traffic classifier
tcl-name
[
operator
{
and
|
or
} ]
N/A
3.
Configure match criteria.
if-match
match-criteria
N/A