Deployment Guide

Egress QoS

The controller can provide basic egress quality of service (QoS) policies for packets and assign a priority based on match parameters

specified by the controller.

To enable QoS, use one flow to determine the egress port for the packet (for example, an L3 flow) and another flow such as an ACL flow

to determine the egress port for all packets matching the specified parameters. Using the Set Enqueue action, the controller specifies

the egress queue for received packets matching the specified parameters. You can configure queues and queue rates on individual ports or

for all physical ports in the OF instance.

There are four data queues available, from Q0 to Q3. The minimum rate of a queue is calculated using the default weights associated with

the queue. If you use legacy CLIs, there is no change in the rate. The following table displays the default weight assigned to each queue:

Table 6. — Default Weight Assigned to Queue

Queue Number Default Weight Percentage of port line rate

Q0 1 6.67%

Q1 2 13.33%

Q2 4 26.67%

Q3 8 53.33%

After the controller identifies the queues and their rates, it can install flows using the Set Enqueue command. For example, to send all

packets with the source IP address 1.1.1.1 from Queue 0, regardless of the egress port, the controller creates the following flow:

• Match parameters = Source IP 1.1.1.1

• Action = Set Enqueue

• Queue = 0

Caveats

• Ingress and egress QoS legacy commands are not supported.

• Queues and queue rates are based on default values. You must disable the instance before configuring queue and queue rates.

26 Egress QoS