Cisco IE 3000, Руководство по настройке программного обеспечения

Страница: 672 / 874

36-12
Cisco IE 3000 Switch Software Configuration Guide
OL-13018-03
Chapter 36 Configuring QoS
Understanding QoS
As a frame is enqueued to a particular queue, WTD uses the frame’s assigned QoS label to subject it to
different thresholds. If the threshold is exceeded for that QoS label (the space available in the destination
queue is less than the size of the frame), the switch drops the frame.
Each queue has three threshold values. The QOS label is determines which of the three threshold values
is subjected to the frame. Of the three thresholds, two are configurable (explicit) and one is not (implicit).
Figure 36-6 shows an example of WTD operating on a queue whose size is 1000 frames. Three drop
percentages are configured: 40 percent (400 frames), 60 percent (600 frames), and 100 percent (1000
frames). These percentages mean that up to 400 frames can be queued at the 40-percent threshold, up to
600 frames at the 60-percent threshold, and up to 1000 frames at the 100-percent threshold.
In this example, CoS values 6 and 7 have a greater importance than the other CoS values, and they are
assigned to the 100-percent drop threshold (queue-full state). CoS values 4 and 5 are assigned to the
60-percent threshold, and CoS values 0 to 3 are assigned to the 40-percent threshold.
Suppose the queue is already filled with 600 frames, and a new frame arrives. It contains CoS values 4
and 5 and is subjected to the 60-percent threshold. If this frame is added to the queue, the threshold will
be exceeded, so the switch drops it.
Figure 36-6 WTD and Queue Operation
For more information, see the “Mapping DSCP or CoS Values to an Ingress Queue and Setting WTD
Thresholds” section on page 36-57 , the “Allocating Buffer Space to and Setting WTD Thresholds for an
Egress Queue-Set” section on page 36-61 , and the “Mapping DSCP or CoS Values to an Egress Queue
and to a Threshold ID” section on page 36-64 .
SRR Shaping and Sharing
Both the ingress and egress queues are serviced by SRR, which controls the rate at which packets are
sent. On the ingress queues, SRR sends packets to the internal ring. On the egress queues, SRR sends
packets to the egress port.
You can configure SRR on egress queues for sharing or for shaping. However, for ingress queues, sharing
is the default mode, and it is the only mode supported.
In shaped mode, the egress queues are guaranteed a percentage of the bandwidth, and they are
rate-limited to that amount. Shaped traffic does not use more than the allocated bandwidth even if the
link is idle. Shaping provides a more even flow of traffic over time and reduces the peaks and valleys of
bursty traffic. With shaping, the absolute value of each weight is used to compute the bandwidth
available for the queues.
In shared mode, the queues share the bandwidth among them according to the configured weights. The
bandwidth is guaranteed at this level but not limited to it. For example, if a queue is empty and no longer
requires a share of the link, the remaining queues can expand into the unused bandwidth and share it
among them. With sharing, the ratio of the weights controls the frequency of dequeuing; the absolute
values are meaningless. Shaping and sharing is configured per interface. Each interface can be uniquely
configured.
Co S 6-7
100%
60%
40%
1000
600
400
0
Co S 4-5
Co S 0- 3
86692