19.07.2013 Views

Enterprise QoS Solution Reference Network Design Guide

Enterprise QoS Solution Reference Network Design Guide

Enterprise QoS Solution Reference Network Design Guide

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter 3 WAN Aggregator <strong>QoS</strong> <strong>Design</strong><br />

Version 3.3<br />

!<br />

!<br />

WAN Edge Classification and Provisioning Models<br />

random-detect dscp-based ! Enables DSCP-WRED for Bulk-Data class<br />

class Scavenger<br />

bandwidth percent 1 ! Scavenger class is throttled<br />

class class-default<br />

bandwidth percent 25 ! Fair-queuing is sacrificed for BW guarantee<br />

random-detect ! Enables WRED on class-default<br />

Note The Consistent <strong>QoS</strong> Behavior initiative will enable the configuration of a bandwidth statement along<br />

with fair-queue on any class, including class-default, on all platforms.<br />

Verification command:<br />

show policy<br />

<strong>QoS</strong> Baseline (11-Class) Model<br />

As mentioned in the overview, the <strong>QoS</strong> Baseline is a guiding model for addressing the <strong>QoS</strong> needs of<br />

today and the foreseeable future. The <strong>QoS</strong> Baseline is not a mandate dictating what enterprises must<br />

deploy today; instead, this strategic document offers standards-based recommendations for marking and<br />

provisioning traffic classes that will allow for greater interoperability and simplified future expansion.<br />

Building on the previous model, the <strong>Network</strong>-Control class is subdivided into the IP Routing and<br />

<strong>Network</strong>-Management classes.<br />

The Critical Data class also is subdivided further into the Mission-Critical Data and Transactional Data<br />

classes. Although DSCP-based WRED is enabled on the Transactional Data class, because packets for<br />

this class can be marked AF21 (or AF22, as in the case of dual-rate policers being deployed in the<br />

campus), it would be superfluous to enable DSCP-based WRED on the Mission-Critical Data class<br />

(WRED will suffice because all Mission-Critical Data class packets are marked to the same value: DSCP<br />

25).<br />

Finally, a new class is provisioned for Streaming-Video. Testing has shown that there is a negligible<br />

difference in enabling WRED on this UDP-based traffic class, so, although it remains an option, WRED<br />

is not enabled in these design examples.<br />

Figure 3-6 shows a sample WAN edge bandwidth allocation for a <strong>QoS</strong> Baseline Model (over a dual-T1<br />

link) and also shows how this model can be derived from the Five- and Seven-Class Models in a manner<br />

that maintains respective bandwidth allocations as consistently as possible. This increases the overall<br />

end-user transparency of such a migration.<br />

<strong>Enterprise</strong> <strong>QoS</strong> <strong>Solution</strong> <strong>Reference</strong> <strong>Network</strong> <strong>Design</strong> <strong>Guide</strong><br />

3-13

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!