Filter
Top Products
Page 12 | AlliedWare Plus™ OS: Overview of QoS
Enabling QoS globally
Before configuring QoS, you need to enable it by entering the following command in global
configuration mode:
awplus(config)#mls qos enable
Initial mapping to queue based on tag
When packets arrive at a port, they are assigned to an egress queue. This is done by the
switch associating an egress queue marker with the packet. For tagged packets, the switch
decides the initial queue setting by looking at the packet’s CoS value (802.
1
p User Priority
field). For untagged packets, there is a default queue setting, which you can change.
Of course, this is just an initial egress queue value—the QoS processing can change it at the
Premarking (page 13) or Remarking (page 22) stages.
Tag g ed
packets
For tagged packets, the default mapping of packet CoS value to egress queue is:
To change this mapping for a CoS value, enter the following command in global configuration
mode:
awplus(config)#mls qos map cos-queue <cos> to <queue>
You need to enter this command for every CoS that you want to re-map.
To see the mapping, use the following command:
awplus#show mls qos maps cos-queue
Untagged
packets
For untagged packets, the switch determines the queue by looking at the value of the mls
qos queue command. This is an interface-mode command, so the queue is set on a per-port
basis. The default value is 2.
To change this, first enter interface mode for the desired port and then specify the desired
queue number. Use the following commands:
awplus(config)#interface <port-number>
awplus(config-if)#mls qos queue <0-7>
For example, to set the initial queue to 5 for untagged packets received on port
1
.0.
1
, use the
commands:
awplus(config)#interface port1.0.1
awplus(config-if)#mls qos queue 5
Untagged packets are also assigned a CoS value, 0 by default. To change this, first enter
interface mode for the desired port and then specify the desired CoS. Use the following
commands:
CoS: 0
1
234567
Queue: 2
11
34567