Ruckus Wireless Ruckus ICX 7150 Series, Руководство по настройке

Страница: 54 / 65

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.
You can configure ACL-based rate limiting on the following interface types:
• Physical Ethernet interfaces
• Virtual interfaces
• Trunk ports
• Specific VLAN members on a port.
• A subset of ports on a virtual interface.
For more information on ACLs, refer to the
Ruckus FastIron Security Configuration Guide
.
ACL-based fixed rate limiting
Fixed rate limiting enforces a strict bandwidth limit. The device forwards traffic that is within the limit but either drops all traffic that exceeds
the limit, or forwards all traffic that exceeds the limit at the lowest priority level, according to the action specified in the traffic policy.
ACL-based adaptive rate limiting
Adaptive rate limiting enforces a flexible bandwidth limit that allows for bursts above the limit. You can configure adaptive rate limiting to
forward traffic, modify the IP precedence of and forward traffic, or drop traffic based on whether the traffic is within the limit or exceeds the
limit.
Traffic policies for ACL-based rate limit restrictions and limitations
When you apply a traffic policy to an interface, you do so by adding a reference to the traffic policy in an ACL entry, instead of applying the
individual traffic policy to the interface. The traffic policy becomes an active traffic policy or active TPD when you bind its associated ACL to
an interface.
Note the following when configuring traffic policies:
• Traffic policies applies to IP ACLs only.
• The maximum number of supported active TPDs is a system-wide parameter and depends on the device you are configuring. The
total number of active TPDs cannot exceed the system maximum. Refer to the “Maximum number of traffic policies supported on
a device” section.
• You can reference the same traffic policy in more than one ACL entry within an ACL. For example, two or more ACL statements in
ACL 101 can reference a TPD named TPD1.
• You can reference the same traffic policy in more than one ACL. For example, ACLs 101 and 102 could both reference a TPD
named TPD1.
• Rate limits and ACL counting are applied at the traffic policy level, and are cumulative across ACLs and ACL entries on which they
are applied. However, they are not cumulative across port regions.
• To modify or delete an active traffic policy, you must first unbind the ACL that references the traffic policy.
• When you define a TPD (when you enter the traffic-policy command), explicit marking of CoS parameters, such as traffic class and
802.1p priority, are not available on the device. In the case of a TPD defining rate limiting, the device re-marks CoS parameters
based on the DSCP value in the packet header and the determined conformance level of the rate limited traffic, as shown in the
following table.
Rate Limiting and Rate Shaping
Rate Limiting
Ruckus FastIron QoS and Traffic Management Configuration Guide, 08.0.70
54 Part Number: 53-1005294-01