Dell PowerConnect B-RX Configuration Manual page 577

Configuration considerations for VLAN-group-based rate limiting policies
When configuring VLAN group based rate limiting policies, consider the following rules:
•
•
•
•
•
Configuring a port-and-ACL-based traffic policing policy
You can use standard or extended ACLs for port-and-ACL-based rate limiting policies.
•
•
•
•
Refer to the
To configure a port-and-ACL-based rate limiting policy, enter commands such as the following.
BigIron RX(config)#access-list 50 permit host 1.1.1.2
BigIron RX(config)#access-list 50 deny host 1.1.1.3
BigIron RX(config)#access-list 60 permit host 2.2.2.3
BigIron RX(config)#int e 1/5
BigIron RX(config-if-e1000-1/5)# rate-limit in access-group 50 500000000
750000000
Average rate is adjusted to 499321856 bits per second
BigIron RX(config-if-e1000-1/5)# rate-limit in access-group 60 100000000
200000000
Average rate is adjusted to 97523712 bits per second
BigIron RX Series Configuration Guide
53-1001986-01
The priority <num> parameter specifies the 802.1p priority levels 0 - 7, equivalent to one of
the four QoS queues. For information on the priority levels and the corresponding queue, refer
to "Assigning QoS priorities to traffic"
For information on the requested rate and maximum burst, refer to
rate limiting policy" on page 502.
A rate limit VLAN group must have at least one VLAN member before it can be used in a rate
limit policy. The list cannot be empty if it is being used in a rate limiting policy.
A rate limit VLAN group cannot be deleted if it is being used in a rate limiting policy.
If a rate limit policy for a VLAN group is applied to a port, the group cannot be used in any other
rate limiting policies applied to other ports that are controlled by the same packet processor.
A VLAN can be member of multiple rate limit VLAN groups, but two groups with common
members cannot be applied on ports controlled by the same packet processor.
VLAN-based rate limiting and VLAN groups based rate limiting policies can be applied on the
same ports or ports controlled by the same packet processor as long as there are no common
VLANs in the policies.
Standard IP ACLs match traffic based on source IP address information.
Extended ACLs match traffic based on source and destination IP addresses and IP protocol
information. Extended ACLs for TCP and UDP protocol must also match on source and
destination IP addresses and TCP or UDP protocol information.
You can apply an ACL ID to a port-and-ACL-based rate limiting policy before you define the ACL.
The rate limiting policy does not take effect until the ACL is defined.
It is not necessary to remove an ACL from a port-and-ACL-based rate limiting policy before
deleting the ACL.
Chapter 21, "Access Control List"
Configuring rate limiting policies
on page 472.
for details on how to configure ACLs.
19
"Configuring a port-based
505