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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

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

Version 3.3<br />

rate 41000 bps<br />

Class-map: Call Signaling (match-any)<br />

251 packets, 142056 bytes<br />

30 second offered rate 3000 bps, drop rate 0 bps<br />

Match: ip dscp cs3<br />

0 packets, 0 bytes<br />

30 second rate 0 bps<br />

Match: ip dscp af31<br />

251 packets, 142056 bytes<br />

30 second rate 3000 bps<br />

Queueing<br />

Output Queue: Conversation 265<br />

Bandwidth 5 (%)<br />

Bandwidth 38 (kbps) Max Threshold 64 (packets)<br />

(pkts matched/bytes matched) 255/144280<br />

(depth/total drops/no-buffer drops) 0/0/0<br />

Class-map: class-default (match-any)<br />

51674 packets, 28787480 bytes<br />

30 second offered rate 669000 bps, drop rate 16000 bps<br />

Match: any<br />

Queueing<br />

Flow Based Fair Queueing<br />

Maximum Number of Hashed Queues 256<br />

(total queued/total drops/no-buffer drops) 36/458/0<br />

WAG-7206-Left#<br />

WAN Edge Link-Specific <strong>QoS</strong> <strong>Design</strong><br />

In Example 3-12, the Voice class map and Call-Signaling class map are receiving matches on their<br />

classification criteria (DSCP EF and DSCP CS3/AF31, respectively). However, because Cisco IP<br />

Telephony products currently mark Call-Signaling traffic to DSCP AF31, Call-Signaling traffic is<br />

matching only on DSCP AF31 in this example.<br />

The last line of every class map output is important because this line indicates whether any drops are<br />

occurring on this traffic class. In this example, there are no drops in the Voice or Call-Signaling classes,<br />

which is the desired behavior. A few drops are occurring in class-default, but this is expected when the<br />

interface is congested (which is the trigger to engage queuing).<br />

Also of note, and specific to this particular configuration, are the cRTP statistics included under the<br />

Voice class map. These cRTP statistics are displayed because class-based cRTP was enabled in this<br />

example (instead of enabling cRTP on the interface). Remember, cRTP must be enabled on both ends of<br />

the links for compression to occur; otherwise, these counters will never increment.<br />

Medium-Speed (£ T1/E1) Leased Lines<br />

Recommendation: MLP LFI is not required; cRTP is optional.<br />

Medium-speed leased lines (as shown in Figure 3-8) can use HDLC, PPP, or MLP encapsulation. An<br />

advantage of using MLP encapsulation is that future growth (to multiple T1/E1 links) will be easier to<br />

manage. Also, MLP includes all the security options of PPP (such as CHAP).<br />

Figure 3-8 Medium-Speed Leased Lines<br />

WAN Aggregator<br />

MLP T1/E1 Link<br />

Branch Router<br />

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

3-19

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

Saved successfully!

Ooh no, something went wrong!