I found my answer in Cisco's documentation. http://www.cisco.com/en/US/docs/switches/lan/catalyst3560/software/release/12.2_50_se/configuration/guide/swqos.html#wp1284809
All four queues participate in the SRR unless the expedite queue is enabled, in which case the first bandwidth weight is ignored and is not used in the ratio calculation. The expedite queue is a priority queue, and it is serviced until empty before the other queues are serviced. You enable the expedite queue by using the *priority-queue out* interface configuration command. On Wed, Oct 20, 2010 at 3:12 PM, Ryan Jensen <[email protected]> wrote: > Hi all, > I have some confusion when it comes to egress queueing on the 3560. > Reading through the study guide, the command format is: *srr-queue > bandwidth {share|shape} **weight1 weight2 weight3 weight4* > I understand that the *weightX* values are relative, but i have some > confusion. My reading (CCIE Routing and switching Exam Certification Guide > 4th Ed) says "When you configure the priority queue, the switch ignores any > bandwidth values assigned to the priority queue in the *share *or > *shape*commands." And leaves it at that. Could I theoretically configure > somthing > that has weight 0 for Queue 1? Like: *srr-queue bandwidth shape 0 20 40 20 > * under an interface? How does the switch know how much weight to assign > to the PQ on egress? Is this determined by the queue-set configuration? (*mls > qos queue-set output 1 buffers 40 20 30 10*).What happens if I don't > assign a queue-set to an interface? Unfortunately I don't have any 3560s > available to test this with. Can anyone help? Thanks in advance. > >
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
