29-18
Catalyst 2960 Switch SoftwareConfiguration Guide
78-16881-01
Chapter29 Co nfiguring QoS
Understanding QoS
ID 1 and ID 2. The drop threshold for threshold ID 3 is p reset to the queue-full state, and you cannot
modify it. For more information about how WTD works, see the “Weighted Tail Drop” section on
page 29-12.

Shaped or Shared Mode

SRR services each queue-set in shared or shaped mode. You map a port to a queue-set by using the
queue-set qset-id interface configuration command. You assign shared or shaped weights to the port by
using the srr-queue bandwidth share weight1 weight2 weight3 weight4 or the srr-queue bandwidth
shape weight1 weight2 weight3 weight4 interface configuration command. For an explanation of the
differences between shaping and sharing, s ee the “SRR Shaping and Sharing” section on page 29-12.
The buffer allocation together with the SRR weight ratios control how much data can be buffered and
sent before packets are dropped. The weight ratio is the ratio of the frequency in which the SRR
scheduler sends packets from each queue.
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.
You can combine the commands described in this section to prioritize traffic by placing packets with
particular DSCPs or CoSs into certain queues, by allocating a large queue size or by servicing the queue
more frequently, and by adjusting queue thresholds so that packets with lower priorities are dropped. For
configuration information, see the “Configuring Egress Queue Characteristics” section on page 29-62.
Note The egress queue default settings are suitable for most situations. You should change them only when
you have a thorough understanding of the egress queues and if these settings do not meet your QoS
solution.
Packet Modification
A packet is classified, policed, and queued to provide QoS. Packet modifications can occur during this
process:
•For IP and non-IP packets, classification involves assigning a QoS label to a packet based on the
DSCP or CoS of the received packet. However, the packet is not modified at this stage; only an
indication of the assigned DSCP or CoS value is carried along. The reason for this is that QoS
classification and forwarding lookups occur in parallel, and it is possible that the p acket is forwarded
with its original DSCP to the CPU where it is again processed through software.
•During policing, IP and non-IP packets can have another DSCP assigned to them (if they are out of
profile and the policer specifies a markdown DSCP). Once again, the DSCP in the packet is not
modified, but an indication of the marked-down value is carried along. For IP packets, the packet
modification occurs at a later stage; for non-IP packets the DSCP is converted to CoS and used for
queueing and scheduling decisions.
•Depending on the QoS label assigned to a frame and the mutation chosen, the DSCP and CoS values
of the frame are rewritten. If you do not configure the mutation map and if you configure the port to
trust the DSCP of the incoming frame, the DSCP value in the frame is not changed, but the CoS is
rewritten according to the DSCP-to-CoS map. If you configure the port to trust the CoS of the
incoming frame and it is an IP packet, the CoS value in the frame is not changed, but the DSCP might
be changed according to the CoS-to-DSCP map.