HP 7102dl - ProCurve Secure Router Configuration Manual page 397

Setting Up Quality of Service
Marking Packets with a ToS value
The specific type of service granted to packets with different ToS values has
only been loosely standardized. Devices in your network might use different
values than devices in an external network to which the router is forwarding
traffic. You can match the local network values and map them to values in the
external network that guarantee equivalent service.
For an example, your devices only support IP precedence. However, your ISP
allows you to mark packets for Expedited Forwarding. You could match the
QoS map entry to packets with an IP precedence of 5 and then set the value
to DSCP 46. Enter:
ProCurve(config-qos-map)# match precedence 5
Valid DiffServ (DSCP) values are from 0 to 63; valid IP precedence values are
from 0 to 7. You will learn how to set the new value in "Setting the ToS Value"
on page 8-50.
You can only match the entry to one value. If you want to map more than one
value to the new value, you must configure a QoS map entry for each original
value. (You should assign the QoS map the same name, but a different
sequence number.)
Marking Traffic According to Fields in the IP Header. You can mark
packets according to the source and/or destination IP addresses in IP headers.
For example, you could place mission-critical traffic from a specific network
into the AF31 class (DSCP 26). If your service provider has agreed to support
this DiffServ, it would grant these packets relatively more bandwidth and drop
them only after other packets are dropped.
You can also select traffic according to source and/or destination TCP or UDP
ports. For example, if your network uses a VoIP application that does not
automatically mark its signaling traffic, you could configure a QoS map entry
to match and mark packets destined to the port specified by your application.
You select the traffic to be marked by matching the QoS map entry to an
extended 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 header. You also use extended ACLs to
mark traffic destined to a specific TCP or UDP protocol port.
8-47