Cisco CiscoWork QoS Policy Manager 4.1.2 User Guide
![Cisco](https://files.manualsbrain.com/attachments/7380d0050044647c30f5c24bbbf5d0c0b6d9bb84/common/fit/150/50/faa183d287233c52228cfea3dbc2a127fe780f60564fcb0955d9c3d1cd23/brand_logo.png)
Chapter 2 Planning for Quality of Service
What Types of Quality of Service Does QPM Handle?
2-12
User Guide for QoS Policy Manager 3.0
78-12542-01
•
•
Link Fragmentation and Interleaving (LFI): Reducing Delay and Jitter on
Lower Speed Links, page 2-25
Lower Speed Links, page 2-25
•
•
Related Topics
•
•
•
•
•
•
•
Distributed Weighted Fair Queuing (DWFQ): High Speed WFQ for VIP Interfaces
On devices with IOS software versions that do not support class-based QoS,
class-based queuing features are implemented through distributed WFQ (DWFQ).
class-based queuing features are implemented through distributed WFQ (DWFQ).
With DWFQ, packets are assigned to different queues based on their QoS group
or the IP precedence in the ToS field. QoS groups allow you to customize your
QoS policy. A QoS group is an internal classification of packets used by the router
to determine how packets are treated by certain QoS features, such as DWFQ and
committed access rate (CAR).
or the IP precedence in the ToS field. QoS groups allow you to customize your
QoS policy. A QoS group is an internal classification of packets used by the router
to determine how packets are treated by certain QoS features, such as DWFQ and
committed access rate (CAR).
Like class-based QoS queuing, DWFQ uses WFQ processing to give higher
weight to high priority traffic, but derives that weight from classes that you create.
These classes are similar to custom queues—they are policy-based, identify traffic
based on the traffic’s characteristics (protocol, source, destination, and so forth),
and allocate a percentage of the interface’s bandwidth to the traffic flow.
weight to high priority traffic, but derives that weight from classes that you create.
These classes are similar to custom queues—they are policy-based, identify traffic
based on the traffic’s characteristics (protocol, source, destination, and so forth),
and allocate a percentage of the interface’s bandwidth to the traffic flow.