29-9
Catalyst 2950 and Catalyst 2955 Switch Software Configuration Guide
78-11380-12
Chapter 29 Configuring QoS
Understanding QoS
Port Scheduling
Each port on the switch has a single receive queue buffer (the ingress port) for incoming traffic. When
an untagged frame arrives, it is assigned the value of the port as its port default priority. You assign this
value by using the CLI or CMS. A tagged frame continues to use its assigned CoS value when it passes
through the ingress port.
CoS configures each transmit port (the egress port) with a normal-priority transmit queue and a
high-priority transmit queue, depending on the frame tag or the port information. Frames in the
normal-priority queue are forwarded only after frames in the high-priority queue are forwarded.
The switch (IEEE 802.1P user priority) has four priority queues. The frames are forwarded to
appropriate queues based on the priority-to-queue mapping that you defined.
Egress CoS Queues
The switch supports four CoS queues for each egress port. For each queue, you can specify these types
of scheduling:
• Strict priority scheduling
Strict priority scheduling is based on the priority of queues. Packets in the high-priority queue are
always sent first, and packets in the low-priority queue are not sent until all the high-priority queues
become empty.
The default scheduling method is strict priority.
• Weighted round-robin (WRR) scheduling
WRR scheduling requires you to specify a number that indicates the importance (weight) of the
queue relative to the other CoS queues. WRR scheduling prevents the low-priority queues from
being completely neglected during periods of high-priority traffic. The WRR scheduler sends some
packets from each queue in turn. The number of packets it sends corresponds to the relative
importance of the queue. For example, if one queue has a weight of 3 and another has a weight of 4,
three packets are sent from the first queue for every four that are sent from the second queue. By
using this scheduling, low-priority queues have the opportunity to send packets even though the
high-priority queues are not empty.
• Strict priority and WRR scheduling
Strict priority and WRR scheduling, also referred to as strict priority queueing, uses one of the
egress queues as an expedite queue (queue 4). The remaining queues participate in WRR. When the
expedite queue is configured, it is a priority queue and is serviced until it is empty before the other
queues are serviced by WRR scheduling.
You can enable the egress expedite queue and assign WRR weights to the other queues by using the
wrr-queue bandwidth weight1 weight2 weight3 0 global configuration command.
To Next Page
Loading...
Need help?
General
