From: Mike Kraus \(mikraus\) (mikraus@cisco.com)
Date: Fri Jul 06 2007 - 10:02:32 ART
This is a good comparison point between the 3550's and the 3560's. On the 3550's you can have different buffer/threshold parameters per port.
*****
Ex. On 3550:
interface X/Y
wrr-queue queue-limit 40 30 20 10
- The above assigns 40% of the buffer space to queue 1, 30% to queue 2, 20% for queue 3, and 10% for queue 4 for that interface. Each interface can be configured independently.
******
Ex on 3560:
mls qos queue-set output 1 buffers 40 30 20 10
- The above assigns 40% of the buffer space to queue 1, 30% to queue 2, 20% for queue 3, and 10% for queue 4. Then you apply this to an interface.
interface X/Y
queue-set 1
- As a result this maps the defined queue-set to this port. In other words, you can only have two different sets of queues for each port (each port is either in queue 1 or queue 2. You are not able to have different buffer/threshold settings for each individual port. Now, for bandwidth on egress, that still is done on a port by port basis.
*****
Keep in mind, the normal comment that queue 4 of the 3550 is the priority queue, where queue 1 is the priority queue of the 3560. The queue-set concept applies only to the 3560 and applies to both buffers and thresholds. See slide 42 here for a comparison of WRR vs. SRR.
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of Jvrg Buesink
Sent: Friday, July 06, 2007 3:24 AM
To: Bit Gossip
Cc: groupstudy
Subject: Re: SRR qset-id
Hi
As far as I can remember you can set different for queue set 1 and queue set 2.
This means that by assigning queue set 1 to an interface x and queue set 2 to interface y, they have different SRR parameters (buffers etc), so more flexible.
Regards,
Jorg Buesink
CCIE#15032 [SP, R&S]
http://www.jorgbuesink.nl
This archive was generated by hypermail 2.1.4 : Sat Aug 18 2007 - 08:17:40 ART