H3C Technologies H3C S10500 Series Switches - Manual (Page 48)

40
Traffic policing configuration example
Network requirements
As shown in Figure 13 :
• GigabitEthernet 1/0/3 of Device A is connected to GigabitEthernet1/0/1 of Device B.
• Server, Host A, and Host B can access the Internet through Device A and Device B.
Perform traffic control on GigabitEthernet 1/0/1 of Device A for traffic received from Server and Host A,
respectively, to satisfy the following requirements:
• Limit the rate of traffic from Server to 1024 kbps: transmit the conforming traffic normally, and mark
the excess traffic with DSCP value 0 and then transmit the traffic.
• Limit the rate of traffic from Host A to 256 kbps: transmit the conforming traffic normally, and drop
the excess traffic.
Perform traffic control on GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2 of Device B to satisfy the
following requirements:
• Limit the total incoming traffic rate of GigabitEthernet 1/0/1 to 2048 kbps, and drop the excess
traffic.
• Limit the outgoing HTTP traffic (traffic accessing the Internet) rate of GigabitEthernet 1/0/2 to 1024
kbps, and drop the excess traffic.
Figure 13 Network diagram for traffic policing configuration
Configuration procedures
1. Configure Device A
# Configure ACL 2001 and ACL 2002 to match traffic from Server and Host A, respectively.
<DeviceA> system-view
[DeviceA] acl number 2001
[DeviceA-acl-basic-2001] rule permit source 1.1.1.1 0
[DeviceA-acl-basic-2001] quit
[DeviceA] acl number 2002
[DeviceA-acl-basic-2002] rule permit source 1.1.1.2 0
[DeviceA-acl-basic-2002] quit
# Create a class named server, and use ACL 2001 as the match criterion. Create a class named host,
and use ACL 2002 as the match criterion.
[DeviceA] traffic classifier server
[DeviceA-classifier-server] if-match acl 2001
[DeviceA-classifier-server] quit