HP 7102dl - ProCurve Secure Router Configuration Manual page 373

You would enter these commands to match classes to the four simple
AF PHBs:
ProCurve(config)# qos map Class 11
ProCurve(config-qos-map)# match dscp 10
ProCurve(config)# qos map Class 12
ProCurve(config-qos-map)# match dscp 18
ProCurve(config)# qos map Class 13
ProCurve(config-qos-map)# match dscp 26
ProCurve(config)# qos map Class 14
ProCurve(config-qos-map)# match dscp 34
This example only shows how to define what traffic is placed in the class.
When actually configuring CBWFQ, you would set the bandwidth for the class
at the same time. See "Allocating Bandwidth to a Class" on page 8-26.
Classifying Traffic According to IP Header Fields. You can classify
packets according to the fields in their IP headers—that is, according to their
source and destination IP addresses, port number, and protocol. This method
of classifying traffic mimics simple WFQ. However, you can place traffic to
and from an entire range of addresses in the same class. One of the
shortcomings of WFQ is that the more subqueues an interface supports, the
less that interface can grant higher priority subqueues significantly greater
bandwidth. Dividing traffic into a small number of classes alleviates this
problem.
You classify traffic in this way by matching the QoS map entry to an extended
access control list (ACL). The ACL actually selects the traffic. An extended
ACL can define traffic according to its source and destination IP address, as
well as a variety of fields in the IP, TCP, or UDP headers.
To classify traffic:
1. Configure an ACL.
a. Create an extended ACL—QoS maps can only use extended ACLs.
b. Add any necessary deny entries to the ACL.
c. Add permit entries for the source and/or destination addresses of
traffic in the class.
2. Match the QoS map entry to the ACL.
Configuring an ACL. Create an ACL by entering this command from the
global configuration mode context:
Syntax: ip access-list extended <listname>
Setting Up Quality of Service
Configuring CBWFQ
8-23