Once again.<br><br>The 6506/09/13 switch, running IOS, DOES NOT support auto qos.<br><br>Here is a working config:<br><br>
<p class="MsoNormal"><font face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial;">mls qos<br>interface range gi3/1 -
48<br>switchport access vlan 100<br>switchport voice vlan 400<br>mls qos trust
cos<br>mls qos trust extend cos
0<br>wrr-queue cos-map 1 1
1<br>wrr-queue cos-map 1 2
0<br>wrr-queue cos-map 2 1 2 3 4 6
7<br>wrr-queue cos-map 2 2
5<br>mls qos map cos-dscp 0 8 16 24 32 46
48</span></font></p><br><br><br>Jonathan<br><br><div><span class="gmail_quote">On 12/7/06, <b class="gmail_sendername">Andre Beck</b> <<a href="mailto:cisco-voip@ibh.net">cisco-voip@ibh.net</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Wed, Dec 06, 2006 at 09:12:55AM -0600, Jonathan Charles wrote:<br>> We are in the process of adding a new 6500 core and I am looking for a QoS<br><br>I wouldn't call that a core (phones are access), but anyway ;)<br>
<br>> config for VoIP... I will have some phones plugged into one blade, so I need<br>> the port configs as well... just looking for a sample, it is kind of<br>> difficult to pull out what I need from Cisco's web site...
<br><br>The basic problem here is that switches are not really flexible in their<br>QoS designs. They can do exactly what the ASICs were designed for, and<br>that sometimes requires a lot of reading for the user to understand, too.
<br><br>For the 3560/3750 there is a quite good description of how they work<br>in the manual, I assume that there will be even more and deeper for<br>the flagship. Don't expect to grok it in less than a day worth of<br>reading time, though.
<br><br>> For instance, I want to trust the DSCP markings of the phone and I want a<br>> priority queue for VoIP bearer traffic (dscp ef)...<br><br>I'd recommend to have a look into the "auto qos voip cisco-phone" and
<br>"auto qos voip trust" automation statements. They configure a rather<br>complicated global setup and apply everything needed to the interface<br>in the context of which they were called. The configuration that results
<br>from these statements should be studied, understand and then changed<br>according to local needs. For instance, the "cisco-phone" variant on<br>a switched port will generate statements for CoS trust, not DSCP trust.
<br>Further, it is a good question whether you need priority queuing at<br>all, at 100Mbps and especially 1Gbps, a shared or shaped queue with a<br>certain guaranteed bandwidth share will usually have low enough latency<br>
and jitter impact for VoIP to work perfectly. On the 3560/3750 e.g. the<br>auto qos statements do not generate any priority queueing on the egress<br>ports, they rather create a shaped queue with 10% guarantee of the total
<br>interface bandwidth. They use a priority queue in the ingress path though,<br>due to the switch design (potentially oversubscribed stack ring).<br><br>HTH,<br>Andre.<br>--<br> The _S_anta _C_laus _O_peration
<br> or "how to turn a complete illusion into a neverending money source"<br><br>-> Andre Beck +++ ABP-RIPE +++ IBH Prof. Dr. Horn GmbH, Dresden <-<br>_______________________________________________
<br>cisco-voip mailing list<br><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br><a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip
</a><br></blockquote></div><br>