Configuring CBWFQ
Overview
CBWFQ is an extension of WFQ that allows you to tailor a QoS policy to your
organization's needs. With CBWFQ, you control:
how traffic is divided into conversation subqueues
how much bandwidth is allocated to each subqueue
You exercise this control by defining classes. For each class, you specify the
traffic matching criterion and set a minimum guaranteed bandwidth. Each
interface implementing CBWFQ supports up to four classes.
WFQ automatically classifies traffic into conversations according to source
and destination IP address, port number, and protocol type. With CBWFQ, you
manually configure how traffic is classified. You define a class according to
IP header fields, and the interface places all traffic that fits that definition into
the same subqueue.
WFQ only looks at IP precedence to determine the bandwidth to allocate each
subqueue. With CBWFQ, you can specify the bandwidth for a class's subqueue
as an absolute value or as a percentage. The bandwidth is the minimum
guaranteed to the class; it may burst above this value. You can reserve up to
75 percent of the interface's bandwidth for all CBWFQ classes together.
Traffic that does not fall within a defined class is divided into subqueues using
typical WFQ, and is allocated its share of whatever remains of the connection's
bandwidth. Because classes may burst above their guaranteed bandwidth,
other traffic may be starved out of the connection.
Configuring Classes for CBWFQ
When you configure CBWFQ on the ProCurve Secure Router, you must
configure:
the criterion for a class
the absolute or relative bandwidth allocated to each class
On the ProCurve Secure Router, you define classes for CBWFQ in a QoS
map entry.
Setting Up Quality of Service
Configuring CBWFQ
8-19