ES3528M_52M MG.pdf - Edge-Core

Class of Service Configuration
3
Values to Egress Queues” on page 3-185, the traffic classes are mapped to one of
the eight egress queues provided for each port. You can assign a weight to each of
these queues (and thereby to the corresponding traffic priorities). This weight sets
the frequency at which each queue will be polled for service, and subsequently
affects the response time for software applications assigned a specific priority value.
Note: This switch does not allow the queue service weights to be set. The weights are
fixed as 1, 2, 4, 8, for queues 0 through 3 respectively.
Command Attributes
• Interface – Select port or trunk as an interface.
• WRR Setting Table 12 – Displays a list of weights for each traffic class (i.e., queue).
• Weight Value – Set a new weight for the selected traffic class. (Range: 1-15)
Web – Click Priority, Queue Scheduling. Select the required interface, highlight a
traffic class (i.e., output queue), enter a weight, then click Apply.
Figure 3-118 Configuring Queue Scheduling
CLI – The following example shows how to display the WRR weights assigned to
each of the priority queues.
Console#show queue bandwidth 4-262
Queue ID Weight
-------- ------
0 1
1 2
2 4
3 8
Console
Layer 3/4 Priority Settings
Mapping Layer 3/4 Priorities to CoS Values
This switch supports one method of prioritizing layer 3/4 traffic to meet application
requirements. Traffic priorities can be specified in the IP header of a frame using the
number of the TCP port. When these service is enabled, the priorities are mapped to
12. CLI shows Queue ID.
3-189