Brocade FastIron Ethernet Switch Traffic Management Guide User Manual
Page 64
Brocade devices use traffic policies for the following reasons:
•
To rate limit inbound traffic
•
To count the packets and bytes per packet to which ACL permit or deny clauses are applied
Traffic policies consist of policy names and policy definitions:
•
Traffic policy name - A string of up to eight alphanumeric characters that identifies individual traffic
policy definitions.
•
Traffic policy definition (TPD) - The command filter associated with a traffic policy name. A TPD
can define any one of the following:
‐
Rate limiting policy
‐
ACL counting policy
‐
Combined rate limiting and ACL counting policy (not applicable on ICX 6650)
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
Maximum number of traffic policies supported on a device
on page 63.
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.
To configure traffic policies for ACL-based rate limiting, refer to
Configuring ACL-based fixed rate
on page 65 and
ACL-based adaptive rate limiting configuration
To configure traffic policies for ACL counting, refer to
on page 70.
Configuration notes and feature limitations for traffic policies
Note the following when configuring traffic policies:
•
Traffic policies applies to IP ACLs only.
•
Traffic policies are supported on FastIron X Series devices, but not on the 10 Gbps Ethernet
interfaces of the SX-FI62XG and SX-FI42XG modules.
•
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
Maximum number of traffic policies supported on a device
on page 63.
•
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.
•
For all types of rate limiting on Brocade ICX 6650 (ACL-based; Port-based; and Broadcast,
unknown Unicast, and Multicast rate limiting) the minimum value is 125 packets and can be
increased in steps of 125 packets.
•
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 CLI command traffic-policy ), 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.
Configuration notes and feature limitations for traffic policies
62
FastIron Ethernet Switch Traffic Management Guide
53-1003093-03