An Ethernet Interface Refusing To Take A Qos-Policy; Quick Start; Configuring Wfq - HP 7102dl - ProCurve Secure Router Configuration Manual

Setting Up Quality of Service

Quick Start

8-72
Using the percent remaining keywords helps to avoid this problem. The
Secure Router OS allocates bandwidth from only that which remains after low-
latency queues have been served. However, you can still make errors, so plan
carefully before configuring the map. (See "Allocating Bandwidth to a Class"
on page 8-26.)
A QoS map will also become inactive on an interface when the interface has
not been bound to a physical carrier line. The Secure Router OS will report
that the map is inactive because the interface has insufficient bandwidth.

An Ethernet Interface Refusing to Take a QoS-Policy

You must configure rate limiting in order to implement QoS on an Ethernet
interface. Use the traffic-shape rate command as described in "Configuring
Rate Limiting on an Ethernet Interface" on page 8-58.
Quick Start
This section provides the commands you must enter to quickly configure:
WFQ
CBWFQ
LLQ
Frame Relay fragmentation
QoS on Ethernet interfaces
Only a minimal explanation is provided. If you need additional information
about any of these options, check "Contents" on page 8-1 to locate the section
that contains the explanation you need.

Configuring WFQ

1. WFQ is enabled by default on all interfaces with an E1 data rate or less.
To re-enable WFQ on a connection on which it has been disabled, move
to the logical interface configuration mode context for the connection:
Syntax: interface <interface ID>
For example:
ProCurve(config)# int ppp 1