Brocade Multi-Service IronWare QoS and Traffic Management Configuration Guide (Supporting R05.6.00) - Manual (Page 39)

Multi-Service IronWare QoS and Traffic Management Configuration Guide 25
53-1003037-02
Traffic policing on the Brocade device
2
Using ACLs for filtering in addition to rate limiting
When you use the ACL-based mode, the permit and deny conditions in an ACL you use in a rate
limiting policy work as follows:
• Permit – The traffic is rate limited according to the other parameters in the rate limiting policy.
• Deny – The traffic is forwarded instead of dropped, by default.
You can configure the device to drop traffic that is denied by the ACL instead of forwarding the
traffic, on an individual port basis.
NOTE
Once you configure an ACL-based rate limiting policy on a port, you cannot configure a regular (traffic
filtering) ACL on the same port. To filter traffic, you must enable the strict ACL option.
To configure the device to drop traffic that is denied by a rate limiting ACL, enter the following
command at the configuration level for the port.
Brocade(config-if-1/1)# rate-limit strict-acl
Syntax: [no] rate-limit strict-acl
Configuring for no priority-based traffic policing
By default, up to 990 different traffic policing policies can be applied to a single 10 GB Ethernet
port. This combined with the 4 priorities utilizes 3960 rate limiting classes. You can configure a
system-wide policy so that up to 3960 individual traffic policing policies can be applied to a single
10 GB Ethernet port.
To configure a Brocade device to not allow priority-based traffic policing, enter commands such as
the following at the interface level.
Brocade(config)# qos-policy
Brocade(qos-policy)# no rate-limit internal-priority-based
Syntax: [no] rate-limit internal-priority-based
If this command is implemented, the number of different rate limiting policies that can be applied
to a single port is increased from 990 to 3960.