Configuring the Strict Priority Queue

It may be critical for certain types of traffic (e.g., voice traffic that is latency sensitive) to be scheduled for transmission as soon as they are enqueued. For this purpose, a queue can be designated as strict priority.

You can configure strict priority scheduling for any of the queues (for example, for queue 5 mapped to CoS 5-marked voice traffic). If strict priority is configured on a queue, Netvisor ONE gives this queue the highest possible priority over the other queues, therefore the strict priority queue is typically reserved for relatively low bandwidth traffic (such as VoIP).

Strict priority scheduling is not enabled by default, it has to be configured explicitly by the user.

For example, to configure strict priority for queue 5 on port 2, use the following command:

CLI (network-admin@switch) > port-cos-bw-modify port 2 cos 5 weight priority

CLI (network-admin@switch) > port-cos-bw-show port 2

switch      cos port min-bw-guarantee max-bw-limit weight   

----------- --- ---- ---------------- ------------ -------- 

<snip>

switch      5   2    0%               100%         priority 

You can also configure a second queue as strict priority, for example, queue 6. In that case, those two queues are scheduled using equal-weight round robin. Using multiple strict priority queues is generally not recommended (as they take precedence over all the other queues), but may be useful in certain cases.