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 2 Campus <strong>QoS</strong> <strong>Design</strong><br />

Catalyst MLS <strong>QoS</strong> Verification Commands<br />

Version 3.3<br />

Catalyst 3550—<strong>QoS</strong> Considerations and <strong>Design</strong><br />

The Catalyst MLS <strong>QoS</strong> verification commands for Conditionally-Trusted IP Phone + PC + Scavenger<br />

(Advanced) Model include the following:<br />

show mls qos<br />

show mls qos map<br />

show mls qos interface<br />

show mls qos interface policers<br />

show mls qos statistics<br />

show class-map<br />

show policy-map<br />

show policy interface<br />

Catalyst 3550—Queuing and Dropping<br />

Configuration<br />

This section includes the following topics:<br />

Configuration<br />

Advanced Tuning Options<br />

Catalyst MLS <strong>QoS</strong> Verification Commands<br />

Like the Catalyst 2950, the Catalyst 3550 supports a 1P3Q1T queuing model for all ports.<br />

GigabitEthernet ports have the additional option of being configured as 1P3Q2T, with either tail-drop or<br />

WRED thresholds. However, unlike the Catalyst 2950, the Catalyst 3550 queuing parameters are set on<br />

a per-interface basis and not globally. Nonetheless, uniform queuing policies can be expeditiously<br />

deployed via the interface range configuration command.<br />

The strict-priority queue is enabled on a per-interface basis on the Catalyst 3550 with the priority-queue<br />

out interface command. Bandwidth is allocated among the remaining queues via the wrr-queue<br />

bandwidth command. A twist with the Catalyst 3550 is that Queue 4’s WRR weight is set to 1<br />

(indicating that it does not participate in the WRR scheduler since it is configured as a strict-priority<br />

queue), instead of 0 (as is the case on the Catalyst 2950). Recommended remaining bandwidth<br />

allocations (after the PQ has been fully serviced) are 5% for the Scavenger queue (Q1), 25% for the<br />

Best-Effort queue (Q2), and 70% for the preferential application queue (Q3).<br />

Following this, CoS 1 (Scavenger/Bulk) would be assigned to Q1; CoS 0 (Best Effort) would be assigned<br />

to Q2; CoS values 2 (Transactional Data and <strong>Network</strong> Management), 3 (call signaling and<br />

Mission-Critical Data), 4 (Interactive and Streaming-Video, 6 (Internetwork Control) and 7 (<strong>Network</strong><br />

Control/Spanning-Tree) would be assigned to Q3; CoS 5 (voice) would be assigned to the strict-priority<br />

Q4. These assignments and allocations are illustrated in Figure 2-15 (the thresholds shown in Q1 and Q3<br />

are discussed shortly).<br />

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

2-41

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

Saved successfully!

Ooh no, something went wrong!