HP ProCurve Secure 7102dl, Справочное руководство

Страница: 1398 / 1455

SROS Command Line Interface Reference Guide Quality of Service (QoS) Map Commands
5991-2114 © Copyright 2007 Hewlett-Packard Development Company, L.P. 1396
Functional Notes
QoS policies are configured in the SROS CLI to dictate the priority for servicing specified traffic types on a
particular interface. QoS policies contain at least one match reference (using the
match command) and
one or more action items (using the priority , bandwidth , or set commands).
The match command specifies the criteria used when determining whether incoming traffic is a candidate
for the QoS policy action items. Multiple match statements can exist within the same QoS policy, allowing
a single QoS policy to service various types of traffic.
For example, consider a network that contains Class A and Class B traffic that each require 25% of the
total allocated interface bandwidth.
ProCurve(config)# qos map MyMap 1
ProCurve
(
config-qos-map)# match list Class_A
ProCurve
(
config-qos-map)# match list Class_B
ProCurve
(
config-qos-map)# bandwidth percent 25
Alternately, the following configuration is also valid:
ProCurve(config)# qos map MyMap 1
ProCurve
(
config-qos-map)# match list Class_A
ProCurve
(
config-qos-map)# bandwidth percent 25
ProCurve(config)# qos map MyMap 2
ProCurve
(
config-qos-map)# match list Class_B
ProCurve(config-qos-map)# bandwidth percent 25
To remove a configured match statement, enter the entire match statement with a preceding no . For
example, to remove the match statements from the above configured QoS map:
ProCurve(config)# qos map MyMap 1
ProCurve
(
config-qos-map)# no match list Class_A
and
ProCurve(config)# qos map MyMap 2
ProCurve
(
config-qos-map)# no match list Class_B
Usage Examples
The following example configures QoS for a network with the following needs:
Reserve 15% of the line rate for routing traffic and L2 protocol traffic ( max-reserved-bandwidth = 85)
Line Rate = 512 kbps
Note
Each listed match statement is handled independently by the processor. Entering too many
match statements in a QoS policy can burden the processor.