Can an AR router limit a rate based on the prefix of a MAC address

1

An AR router does not support rate limit based on the prefix of a MAC address.

Other related questions:
How to configure an AR to limit the rate of traffic based on MAC addresses
You can configure a traffic policy to limit the rate of traffic based on MAC addresses as follows: # traffic classifier mac1 operator and if-match source-mac 0015-c50d-0001 //Configure a matching rule based on the source MAC address 0015-c50d-0001 in the traffic classifier mac1. traffic classifier mac2 operator and if-match source-mac 0015-c50d-0002 //Configure a matching rule based on the source MAC address 0015-c50d-0002 in the traffic classifier mac2. traffic classifier mac3 operator and if-match source-mac 0015-c50d-0003 //Configure a matching rule based on the source MAC address 0015-c50d-0003 in the traffic classifier mac3. # traffic behavior d1 car cir 3000 cbs 564000 pbs 939000 mode color-blind green pass yellow pass red discard //Create the traffic behavior d1 and configure the rate limit to 3000 kbit/s. # traffic policy myqos //Configure the traffic policy myqos. classifier mac1 behavior d1 //Bind the traffic classifier mac1 to the traffic behavior d1. classifier mac2 behavior d1 //Bind the traffic classifier mac2 to the traffic behavior d1. classifier mac3 behavior d1 //Bind the traffic classifier mac3 to the traffic behavior d1. # interface GigabitEthernet 0/0/0 ip address 10.1.1.1 255.255.255.0 traffic-policy myqos inbound //Apply the traffic policy myqos to the inbound interface. #

How to configure rate limiting in a traffic policy on an AR

1. Create a traffic classifier.
2. Creates a traffic behavior.
3. Creates a traffic policy.
4. Apply the traffic policy.
For example, you can configure rate limiting for the network segment 192.168.1.0 as follows:
#
acl number 3000 //Create ACL 3000 to match the network segment to which the rate of packets needs to be limited.
rule 5 permit ip source 192.168.1.0 0.0.0.255
#
traffic classifier c1 operator or //Configure the matching condition of the traffic classifier to ACL 3000.
if-match acl 3000
#
traffic behavior b1 //Configure the action of the traffic behavior to rate limiting: Set the CIR to 384 kbit/s and the PIR to 768 kbit/s, permit green packets to be sent, forward yellow packets after marking the DSCP priority of yellow packets as 0, and discard red packets.
car cir 384 pir 768 cbs 48000 pbs 96000 mode color-blind green pass yellow pass remark-dscp default red discard
#
traffic policy test //Create a traffic policy and bind it to the traffic classifier and traffic behavior.
classifier c1 behavior b1
#
interface GigabitEthernet0/0/0
ip address 192.168.1.254 255.255.255.0
traffic-policy test inbound //Apply the traffic policy test to the inbound direction of an intranet interface.
#
return

Configure rate limiting based on IP addresses
You can run the qos car command in the interface view to configure rate limiting based on IP addresses.

Rate limiting based on IP addresses does not take effect on an AR
Verify that the interface to which rate limiting is applied is the router's interface connecting to intranet users or the interface does not have NAT configured. If the interface has NAT configured, ensure that it can match source and destination IP addresses correctly. For the intranet, inbound and outbound in the command indicate the source and destination IP addresses respectively.

Does an AR support rate limiting based on an individual IP address
In V200R002C00 and later versions, you can run the qos car command to configure rate limiting based on an individual IP address.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top