Brocade Multi-Service IronWare QoS and Traffic Management Configuration Guide (Supporting R05.6.00) User Manual
Page 30
16
Multi-Service IronWare QoS and Traffic Management Configuration Guide
53-1003037-02
Traffic policing on the Brocade device
2
on source and destination TCP or UDP addresses. and protocol information. These policies can
be applied to inbound and outbound traffic. Up to 990 Port-and-ACL-based policies can be
configured for a port under normal conditions or 3960 policies if priority-based traffic policing
is disabled as described in
“Configuring for no priority-based traffic policing”
•
Rate Limiting for Copied-CPU-bound Traffic – You can limit the rate of Copied-CPU-bound
packets from applications such as sFlow, ACL logging, RPF logging, and source MAC address
learning (with known destination address). Copied-CPU-bound packets are handled and
queued separately from packets destined to the CPU such as protocol packets and using this
feature they can be assigned to one of eight priority queues which has a rate limit assigned to
it. The queue and rate are assigned by port and apply to all of the ports that are supported by
the same packet processor.
describes the ports that are associated a packet
processor.
Multi-Service IronWare supports applying traffic policing parameters directly to a port or creating a
policy map to define a set of traffic policing parameters and then applying that policy map to one or
more ports. In addition, the traffic policing parameters available from each of these options are
different. The parameters used when applying traffic policing parameters directly to a port reflect
the Multi-Service IronWare features that were available before this release. These parameters and
the information required to use them are described in
“Applying traffic policing parameters directly
The parameters used when applying traffic policing through use of a policy map reflect the traffic
policing features that have been added with this release. These parameters and the information
required to use them are described in
“Applying traffic policing parameters using a policy map”
Applying traffic policing parameters directly to a port
When applying a traffic policing policy directly to a port, there are specific parameters that are
applied to implement the policy that are different than those used when using a policy map. The
Brocade NetIron XMR supports this mode in addition to policy maps. Using this method, a traffic
policing policy specifies two parameters: average rate and maximum burst. These parameters are
used to configure credits and credit totals.
Average rate
The average rate is the maximum number of bits a port is allowed to receive during a one-second
interval. The rate of the traffic that matches the traffic policing policy will not exceed the average
rate.
The average rate represents a percentage of an interface's line rate (bandwidth), expressed in bits
per second (bps). It cannot be smaller than 8,144 bits per second (bps) and it cannot be larger
than the port’s line rate.
For Brocade MLX series and Brocade NetIron XMR devices, the average rate must be entered in
multiples of 8,144 bps. If you enter a number that is not a multiple of 8,144, the software adjusts
the rate down to the lowest multiple of the number so that the calculation of credits does not result
in a remainder of a partial Credit. For example, if you enter 10,000 bps, the value will be adjusted
to 8,144 bps. The adjusted rate is sometimes called the adjusted average rate.
For Brocade NetIron CER and Brocade NetIron CES devices, the average rate can be entered in as
any value from 0 up to the line rate of the port. Multiples of 8,144 do not need to be used.