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

Multi-Service IronWare QoS and Traffic Management Configuration Guide 5
53-1003037-02
Traffic policing on Brocade NetIron CES and Brocade NetIron CER devices
1
For Drop Precedence, the Brocade MLX Series and Brocade NetIron XMR has 4 levels, while
Brocade NetIron CER and Brocade NetIron CES have 3 levels. The Brocade NetIron CER and
Brocade NetIron CES internally converts the 4 levels as follows:
0 -> 0, 1 -> 1, 2 -> 1, 3 -> 2
The excess-dscp parameter specifies that traffic whose bandwidth requirements exceeds what is
available in the CIR bucket and is sent to the EIR bucket. These packets will have their DSCP priority
set to the value set in the dscp-num variable. Acceptable values for the dscp-num are 0 - 63. When
this parameter is used together with the excess-dp parameter, the value set for bits 2:1
(zero-based) in the excess-dscp parameter must be equal to the value set for excess-dp. The
excess-dp parameter is compared with excess-dscp in bit [2:1] first, then it is converted.
The excess-priority parameter specifies that traffic whose bandwidth requirements exceeds what is
available in the CIR bucket and is sent to the EIR bucket. These packets will have their priority
queue or TC set to the value set in the priority num variable. Acceptable values for the priority-num
are 0 - 7.
The excess-pcp parameter specifies that traffic whose bandwidth requirements exceeds what is
available in the CIR bucket and is sent to the EIR bucket. These packets will have their pcp or UP
(user priority) set to the value set in the pcp num variable. Acceptable values for the priority-num
are 0 - 7.
The excess-exp parameter specifies that traffic whose bandwidth requirements exceeds what is
available in the CIR bucket and is sent to the EIR bucket. These packets will their EXP set to the
value set in the exp num variable. Acceptable values for the exp num are 0-7.
Configuring a policy-map to remark profile tables
The Brocade NetIron CER and Brocade NetIron CES each use have four remark profile tables per
packet processor. The profile determines the CoS remapping tables sets to use, and each profile
contains the 5 excess parameters (i.e., excess-dp, excess-dscp, excess-priority, excess-pcp,
excess-exp), which remark the Quality of Service parameters if the rate is over the limits that are
specified in the CIR, CBS, EIR and EBS parameters.
The profile is selected per port configuration. For the Ingress policier, the profile is selected per the
source port; and for the Egress policier, the profile is selected per target port. You can configure as
many policy-maps as you want. However, when you apply or bind the policy-map to an interface,
only four different profiles are available, where each of the four profiles may be applied to multiple
ports.
Note that a policy-map includes both rates and sizes and the 5 excess parameters. A remark profile
table has the 5 excess parameters only, so multiple policy-maps may share a single remark profile
table, if the 5 excess parameters match.
Configuring port-based traffic policing for inbound and outbound ports
Port-based traffic policing limits the rate on an individual inbound or outbound physical port to a
specified rate.
To configure port-based traffic policing policy for outbound ports, enter commands such as the
following at the interface level.
Brocade(config)# interface ethernet 1/1
Brocade(config-if-1/1)# rate-limit out 500000000 750000000