Enterprise QoS Solution Reference Network Design Guide
Enterprise QoS Solution Reference Network Design Guide
Enterprise QoS Solution Reference Network Design Guide
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Chapter 1 Quality of Service <strong>Design</strong> Overview<br />
Version 3.3<br />
What is the Cisco <strong>QoS</strong> Toolset?<br />
However, it is important to remember where Auto<strong>QoS</strong> came from. Auto<strong>QoS</strong> tools are the result of Cisco<br />
<strong>QoS</strong> feature development coupled with Cisco <strong>QoS</strong> <strong>Design</strong> <strong>Guide</strong>s based on large-scale lab-testing.<br />
Auto<strong>QoS</strong> VoIP is the product of the first <strong>QoS</strong> <strong>Design</strong> <strong>Guide</strong>, one of the most popular/downloaded<br />
technical white papers ever produced within Cisco. Auto<strong>QoS</strong> <strong>Enterprise</strong> is the result of the strategic <strong>QoS</strong><br />
Baseline (discussed later in this document) coupled with the second generation <strong>QoS</strong> <strong>Design</strong> <strong>Guide</strong>.<br />
These latest <strong>QoS</strong> design documents represents the third-generation <strong>QoS</strong> <strong>Design</strong> <strong>Guide</strong>, which is<br />
essentially a proposed blueprint for the next version of Auto<strong>QoS</strong>.<br />
Figure 1-4 shows the relationship between Cisco <strong>QoS</strong> features, <strong>Design</strong> <strong>Guide</strong>s, and Auto<strong>QoS</strong>.<br />
Figure 1-4 Cisco <strong>QoS</strong> Feature, <strong>Design</strong> <strong>Guide</strong> and Auto<strong>QoS</strong> Evolution<br />
Data <strong>QoS</strong> Features<br />
(NBAR, DSCP-WRED)<br />
VoIP <strong>QoS</strong> Features<br />
(LLQ, LFI)<br />
Call Admission Control Tools<br />
Advanced Data <strong>QoS</strong> Features<br />
(Advanced Campus Policers)<br />
<strong>QoS</strong> Baseline<br />
<strong>QoS</strong> <strong>Design</strong> <strong>Guide</strong> v2<br />
(Voice, Video, Data)<br />
<strong>QoS</strong> <strong>Design</strong> <strong>Guide</strong> v1<br />
(VoIP Only)<br />
<strong>QoS</strong> <strong>Design</strong> <strong>Guide</strong> v3<br />
(Voice, Video, Data +<br />
DoS/Worm Mitigation)<br />
Auto<strong>QoS</strong>-<strong>Enterprise</strong><br />
(WAN Only)<br />
Auto<strong>QoS</strong> VoIP<br />
(Campus + WAN)<br />
After performing the calculations to provision the network with the required bandwidth to support voice,<br />
video and data applications, you must ensure that voice or video do not oversubscribe the portion of the<br />
bandwidth allocated to them. While most DiffServ <strong>QoS</strong> features are used to protect voice from data, Call<br />
Admission Control (CAC) tools are used to protect voice from voice and video from video.<br />
CAC tools fall into the following three main categories:<br />
Local—Local CAC mechanisms are a voice gateway router function, typically deployed on the<br />
outgoing gateway. The CAC decision is based on nodal information such as the state of the outgoing<br />
LAN/WAN link that the voice call traverses if allowed to proceed. Local mechanisms include<br />
configuration items to disallow more than a fixed number of calls.<br />
If the network designer already knows that no more than five VoIP calls will fit across the outgoing<br />
WAN link’s LLQ configuration because of bandwidth limitations, then it would be recommended<br />
to configure the local gateway node to not allow more than five simultaneous calls.<br />
Measurement-based—Measurement-based CAC techniques look ahead into the packet network to<br />
gauge the state of the network to determine whether or not to allow a new call. This usually implies<br />
sending probes to the destination IP address, which could be the terminating gateway or endpoint,<br />
or another device in between.<br />
<strong>Enterprise</strong> <strong>QoS</strong> <strong>Solution</strong> <strong>Reference</strong> <strong>Network</strong> <strong>Design</strong> <strong>Guide</strong><br />
119476<br />
1-9