Brocade TurboIron 24X Series Configuration Guide - Manual (Page 965)

Brocade TurboIron 24X Series Configuration Guide 931
53-1003053-01
Maximum number of traffic policies supported on a device
Maximum number of traffic policies supported on a device
The maximum number of supported active traffic policies is a system-wide parameter and depends
on the device you are configuring, as follows:
• By default, up to 1024 active traffic policies are supported on Layer 2 and on Layer 3 switches.
This value is fixed on Layer 2 switches and cannot be modified.
• The number of active traffic policies supported on Layer 3 switches varies depending on the
configuration and the available system memory. The default value and also the maximum
number of traffic policies supported on Layer 3 switches is 1024.
Setting the maximum number of traffic policies supported
on a Layer 3 device
If desired you can adjust the maximum number of active traffic policies that a Layer 3 device will
support. To do so, enter commands such as the following at the Global CONFIG level of the CLI.
TurboIron(config)#system-max hw-traffic-conditioner 25
TurboIron(config)#write memory
TurboIron(config)#reload
NOTE
You must save the configuration and reload the software to place the change into effect.
Syntax: [no] system-max hw-traffic-conditioner <num>
<num> is a value from 0 to n, where 0 disables hardware resources for traffic policies, and n is a
number up to 1024. The maximum number you can configure depends on the configuration and
available memory on your device. If the configuration you enter causes the device to exceed the
available memory, the device will reject the configuration and display a warning message on the
console.
NOTE
Brocade does not recommend setting the system-max for traffic policies to 0 (zero), since this
renders traffic policies ineffective.
ACL-based rate limiting using traffic policies
ACL-based rate limiting provides the facility to limit the rate for IP traffic that matches the permit
conditions in extended IP ACLs. This feature is available in the Layer 2 and Layer 3 code.
To configure ACL-based rate limiting, you create individual traffic policies, then reference the traffic
policies in one or more ACL entries (also called clauses or statements). The traffic policies become
effective on ports to which the ACLs are bound. Refer to
“About traffic policies” on page 929.
When you configure a traffic policy for rate limiting, the device automatically enables rate limit
counting, similar to the two-rate three-color marker (trTCM) mechanism described in RFC 2698 for
adaptive rate limiting, and the single-rate three-color marker (srTCM) mechanism described in RFC
2697 for fixed rate limiting. This feature counts the number of bytes and trTCM or srTCM
conformance level per packet to which rate limiting traffic policies are applied. Refer to
“ACL and
rate limit counting” on page 936.