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

Multi-Service IronWare QoS and Traffic Management Configuration Guide 129
53-1003037-02
Egress port and priority based rate shaping
4
Brocade(config)# interface ethernet 1/1
Brocade(config-if-e1000-1/1)# qos scheduler mixed 100 80 60 40 20
Syntax: qos scheduler mixed queue4-weight queue3-weight queue2-weight queue1-weight
queue0-weight
The queue4-weight variable defines the relative value for queue4 in calculating queue4’s allocated
bandwidth.
The queue3-weight variable defines the relative value for queue3 in calculating queue3’s allocated
bandwidth.
The queue2-weight variable defines the relative value for queue2 in calculating queue2’s allocated
bandwidth.
The queue1-weight variable defines the relative value for queue1 in calculating queue1’s allocated
bandwidth.
The queue0-weight variable defines the relative value for queue0 in calculating queue0’s allocated
bandwidth
The acceptable range for queuex-weight variables is 1-128.
Refer to “Calculating the values for WFQ Weight-based traffic scheduling” for information on
assigning queue0-weight to queue4-weight values.
Configuring egress unicast and multicast traffic scheduling
You can schedule the egress unicast and multicast traffic based on the allocated bandwidth. To
configure WFQ weight-based scheduling for an interface, enter the following commands.
Brocade(config)# interface ethernet 1/1
Brocade(config-if-e1000-1/1)# qos egress-weight unicast 1 multicast 3
Syntax: [no] qos egress-weight unicast unicast-weight-val multicast multicast-weight-val
The unicast unicast-weight-val variable specifies the allocated bandwidth for the egress unicast
traffic. The value ranges from 1 through 255.
The multicast multicast-weight-val variable specifies the allocated bandwidth for the egress
multicast traffic. The value ranges from 1 through 255.
Egress port and priority based rate shaping
Rate shaping is a mechanism to smooth out the variations in traffic above a certain rate. The
primary difference between rate shaping and rate limiting is that in rate limiting, traffic exceeding a
certain threshold is dropped. In rate shaping, the traffic that exceeds a threshold is buffered so
that the output from the buffer follows a more uniform pattern. Rate shaping is useful when
burstiness in the source stream needs to be smoothed out and a more uniform traffic flow is
expected at the destination.
NOTE
Because excess traffic is buffered, rate shaping must be used with caution. In general, it is not
advisable to rate shape delay-sensitive traffic.
Brocade devices support egress rate shaping. Egress rate shaping is supported per port or for each
priority queue on a specified port.