Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.

Dell PowerEdge FN I/O Module Command Line Reference Guide 9.10(0.0)

PDF

strict-priority unicast

Configure a unicast queue as a strict-priority (SP) queue.

Syntax strict-priority unicast queue number
Parameters
unicast number Enter the keyword unicast then the queue number. The range is from 1 to 3.
Defaults none
Command Modes CONFIGURATION
Supported Modes Full–Switch
Command History
Version Description
9.9(0.0) Introduced on the FN IOM.
8.3.16.1 Introduced on the MXL 10/40GbE Switch IO Module.
Usage Information

After you configure a unicast queue as strict-priority, that particular queue, on the entire chassis, is treated as a strict-priority queue. Traffic for a strict priority is scheduled before any other queues are serviced. For example, if you send 100% line rate traffic over the SP queue, it starves all other queues on the ports on which this traffic is flowing. To assign the strict priority schedule type to egress queues, use the scheduler strict command in QOS-POLICY-OUT mode. The system OS does not support bandwidth configuration on strict priority scheduler queues.

When you enable ETS, the egress QoS features in the output QoS policy-map (such as strict priority unicast <0-3> and scheduler strict), default scheduler for egress queues are superseded by ETS configurations. This is to provide compatibility with DCBX. Therefore, Dell Networking OS recommends disabling ETS when you wish to apply these features exclusively. After you disable ETS on an interface, the configured parameters are applied.


Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\