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

Multi-Service IronWare QoS and Traffic Management Configuration Guide 189
53-1003037-02
Hierarchical QoS (HQoS) for 8x10G modules
5
At the level-1 scheduler policy configuration, there are two customer groups competing in a
weighted fair queue.
• CustomerGrp1 will get preferential treatment with twice the bandwidth of CustomerGrp2
because of the weight values associated with them.
• CustomerGrp1 can receive up to 666 Mbps and CustomerGrp2 receives up to 333 Mbps
from the total 1Gbps shaped at this level.
Brocade(config)# hqos scheduler-policy logical-port-type1 level level-1
Brocade(config-hqos-scheduler-logical-port-type1)# shaper-rate 1000000
Brocade(config-hqos-scheduler-logical-port-type1)# shaper-burst-size 10
Brocade(config-hqos-scheduler-logical-port-type1)# scheduler-type weighted
Brocade(config-hqos-scheduler-logical-port-type1)# scheduler-flow CustomerGrp1
scheduler-input 3 weight 2 scheduler-policy customer-group-type1
Brocade(config-hqos-scheduler-logical-port-type1)# scheduler-flow CustomerGrp2
scheduler-input 2 weight 1 scheduler-policy customer-group-type1
At the level-2 scheduler policy configuration, the only thing that changes is the scheduling type
from strict to fair weighted (when no explicit weight value is set, the default is 1).
Brocade(config)# hqos scheduler-policy customer-group-type1 level level-2
Brocade(config-hqos-scheduler-customer-group-type1)# shaper-rate 20000
Brocade(config-hqos-scheduler-customer-group-type1)# shaper-burst-size 10
Brocade(config-hqos-scheduler-customer-group-type1)# scheduler-type weighted
Brocade(config-hqos-scheduler-customer-group-type1)# scheduler-flow Customer1
scheduler-input 3 scheduler-policy customer-type1
Brocade(config-hqos-scheduler-customer-group-type1)# scheduler-flow Customer2
scheduler-input 2 scheduler-policy customer-type1
At the last level, each customer employs a strict scheduler amongst its 4 priority queues with no
shapers (open shapers set to 10Gbps).
Brocade(config)# hqos scheduler-policy customer-type1 level level-3
Brocade(config-hqos-scheduler-customer-type1)# shaper-rate 20000
Brocade(config-hqos-scheduler-customer-type1)# shaper-burst-size 10
Brocade(config-hqos-scheduler-customer-type1)# scheduler-type strict
Brocade(config-hqos-scheduler-customer-type1)# scheduler-flow CoS1
scheduler-input 3 scheduler-policy Q-7-6
Brocade(config-hqos-scheduler-customer-type1)# scheduler-flow CoS2
scheduler-input 2 scheduler-policy Q-5-4
Brocade(config-hqos-scheduler-customer-type1)# scheduler-flow CoS3
scheduler-input 1 scheduler-policy Q-3-2
Brocade(config-hqos-scheduler-customer-type1)# scheduler-flow CoS4
scheduler-input 0 scheduler-policy Q-1-0
Brocade(config)# hqos queue-policy queue-default
Brocade(config)# shaper-rate 10000000
Brocade(config)# shaper-burst-size 10
Binding Policy to interface and applying mapping condition for PBB
Refer to “Binding a policy to an interface and applying a mapping condition” on page 186 for
additional information on binding a policy to an interface and applying a mapping condition.
Binding the mappings to HQoS PBB port is similar to the Local VPLS HQoS model. The only
difference is you must add the "ISID" as the customer match condition.
Brocade(config)# interface ethernet 1/1
Brocade(config-if-e10000-1/1)# hqos service-policy output pbb-port