background image
1-12
Cisco AVVID Network Infrastructure Enterprise Quality of Service Design
956467
Chapter 1 Overview
What is the Quality of Service Toolset?
What is the Quality of Service Toolset?
As applications that are sensitive to packet loss, delay, and delay variation (jitter) are implemented in
Enterprise network environments, the ability to manage these sensitivities has become necessary. The
packet loss, delay, and delay variation requirements that VoIP, video, and mission-critical data
applications make of the network can be satisfied through the implementation of the QoS classification,
scheduling, provisioning, and management tools.
This section provides an overview of the following topics:
·
Classification Tools
·
Classification Recommendations
·
Scheduling Tools
·
Scheduling Recommendations
·
Provisioning Tools
·
Management Tools
Classification Tools
The first element to a QoS policy is to identify the traffic that is to be treated differently. Classification
tools mark a packet or flow with a specific priority. This marking establishes a trust boundary that must
be enforced. Classification set this boundary by examining any of the following:
·
Layer 2 Parameters (802.1Q Class of Service [CoS] bits, MAC address, Multiprotocol Label
Switching [MPLS] experimental values)
·
Layer 3 Parameters (IP Precedence, Differentiated-Services Code Points [DSCP],
Source/Destination IP address)
·
Layer 4 Parameters (TCP or UDP ports)
·
Layer 7 Parameters (application signatures)
Only after traffic can be positively identified can policies be applied. Best-practice design
recommendations are to identify and mark (with DSCP values) traffic as close to the source of the traffic
as possible. The network edge where markings are accepted (or rejected) is referred to as the
"trust-boundary." If markings and trusts are set correctly, then intermediate hops do not have to perform
detailed traffic identification, but can administer QoS policies based on these previously set DSCP
markings. This approach simplifies policy administration and reduces CPU overhead.
Classification should take place at the network edge, typically in the wiring closet or within the IP
phones or voice endpoints themselves.
There are several mechanisms that can be used for marking traffic, including:
·
Class of Service
·
Type of Service and Differentiated Services Code Points
·
Per-Hop Behaviors
·
Network-Based Application Recognition
Tip
For more information, see Classification in the Cisco IOS Quality of Service Solutions Configuration
Guide
, Release 12.2.