Foundry Configuration Guide for the FESX, FSX, and FWSX
15 2 © Foundry Networks, Inc. December 2005
are configuring. The total number of active TPDs cannot exceed the system maximum. See “Maximum
Number of Traffic Policies Supported on a Device” on page 15-3.
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, see “Configuring ACL-Based Fixed Rate Limiting” on
page 15-4 and “Configuring ACL-Based Adaptive Rate Limiting” on page 15-5.
To configure traffic policies for ACL counting, see “Enabling ACL Counting” on page 15-8.
Configuration Notes and Feature Limitations
Note the following when configuring traffic policies:
• This feature is supported in the Layer 2 and Layer 3 code.
• This feature applies to IP ACLs only. X-Series devices do not support Layer 2 ACLs.
• Traffic policies are not supported on 10-Gigabit Ethernet interfaces.
• 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. See “Maximum
Number of Traffic Policies Supported on a Device” on page 15-3.
• You can reference the same traffic policy in more than one ACL entry within an access list. 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 access list. For example, ACLs 101 and 102 could
both reference a TPD named TPD1.
• 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 Table 15.2.
Table 15.2: CoS Parameters for Packets that use Rate Limiting Traffic Policies
If the packet’s Conformance
Level is...
and the packet’s DSCP Value
is...
the device sets the Traffic
Class and 802.1p Priority to...
0 (Green)
or
1 (Yellow)
0 – 7 0 (lowest priority queue)
8 – 15 1
16 – 23 2
24 – 31 3
32 – 39 4
40 – 47 5
48 – 55 6
56 – 63 7 (highest priority queue)
2 (Red) N/A 0 (lowest priority queue)
To Next Page
Loading...
Need help?
General
