List of SyntaxSRX Series
QFX Series and OCX Series
EX Series (Except EX4300)
M320, MX Series, T Series, and PTX Series
QFX Series and OCX Series
EX Series (Except EX4300)
M320, MX Series, T Series,
and PTX Series
Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 8.5.
Statement introduced in Junos OS Release 9.0 on EX Series switches.
The policing-priority option was introduced in Junos OS Release 9.5.
Statement introduced in Junos OS Release 11.1 on QFX Series switches.
Statement updated in Junos OS Release 11.4.
The spu-priority option was introduced in Junos OS Release 11.4R2.
Statement introduced in Junos OS Release 12.1 on PTX Series routers.
The no-loss option was introduced in Junos OS Release 12.3 on QFX Series switches.
Statement introduced in Junos OS Release 14.1X53-D20 on OCX Series switches.
Change from two to four queues made in Junos OS Release 12.3X48-D40 and in Junos OS Release 15.1X49-D70.
The pfc-priority statement was introduced in Junos OS Release 17.4R1 on QFX Series switches.
The medium-high and medium-low priorities for spu-priority were deprecated and medium priority was added in Junos OS Release 19.1R1.
Command used to associate forwarding classes with class names and queues with queue numbers.
SRX Series Devices
All traffic traversing the SRX Series device is passed to an SPC to have service processing applied. Junos OS provides a configuration option to enable packets with specific Differentiated Services (DiffServ) code points (DSCP) precedence bits to enter a high-priority queue, a medium-priority queue, or a low-priority queue on the SPC. The Services Processing Unit (SPU) draws packets from the highest priority queue first, then from the medium priority queue, and last from the low priority queue. The processing of the queue is weighted-based not strict-priority-based. This feature can reduce overall latency for real-time traffic, such as voice traffic.
Initially, the spu-priority queue options were "high" and "low". Then, these options (depending on the devices) were expanded to "high", "medium-high", "medium-low", and "low". The two middle options ("medium-high" and "medium-low") have now been deprecated (again, depending on the devices) and replaced with "medium". So, the available options for spu-priority queue are "high", "medium", and "low".
We recommend that the high-priority queue be selected for real-time and high-value traffic. The other options would be selected based on user judgement on the value or sensitivity of the traffic.
M320, MX Series, and T Series Routers and EX Series Switches
For M320, MX Series, and T Series routers, and EX Series switches only, you can configure fabric priority queuing by including the priority statement. For Enhanced IQ PICs, you can include the policing-priority option.
The priority and policing-priority options are not supported on PTX Series routers.
EX Series Switches
For the EX Series switches, this statement associates the forwarding class with a class name and queue number. It can define the fabric queuing priority as high, medium-high, medium-low, or low.
Map one or more forwarding classes to a single output queue. Also, when configuring DSCP-based priority-based flow control (PFC), map a forwarding class to a PFC priority value to use in pause frames when traffic on a DSCP value becomes congested (see Configuring DSCP-based PFC for Layer 3 Untagged Traffic for details).
Switches that use different forwarding classes for unicast and multidestination (multicast, broadcast, and destination lookup fail) traffic support 12 forwarding classes and 12 output queues (0 through 11). You map unicast forwarding classes to a unicast queue (0 through 7) and multidestination forwarding classes to a multidestination queue (8 through 11). The queue to which you map a forwarding class determines if the forwarding class is a unicast or multidestination forwarding class.
Switches that use the same forwarding classes for unicast and multidestination traffic support eight forwarding classes and eight output queues (0 through 7). You map forwarding classes to output queues. All traffic classified into one forwarding class (unicast and multidestination) uses the same output queue.
You cannot configure weighted random early detection (WRED) packet drop on forwarding classes configured with the no-loss packet drop attribute. Do not associate a drop profile with lossless forwarding classes.
If you map more than one forwarding class to a queue, all of the forwarding classes mapped to the same queue must have the same packet drop attribute (all of the forwarding classes must be lossy, or all of the forwarding classes mapped to a queue must be lossless).
OCX Series Switches
OCX Series switches do not support the no-loss packet drop attribute and do not support lossless forwarding classes. On OCX Series switches, do not configure the no-loss packet drop attribute on forwarding classes, and do not map traffic to the default fcoe and no-loss forwarding classes (both of these default forwarding classes carry the no-loss packet drop attribute).
On switches that do not use the Enhanced Layer 2 Software (ELS) CLI, if you are using Junos OS Release 12.2, use the default forwarding-class-to-queue mapping for the lossless fcoe and no-loss forwarding classes. If you explicitly configure the lossless forwarding classes, the traffic mapped to those forwarding classes is treated as lossy (best effort) traffic and does not receive lossless treatment.
On switches that do not use the ELS CLI, if you are using Junos OS Release 12.3 or later, the default configuration is the same as the default configuration for Junos OS Release 12.2, and the default behavior is the same (the fcoe and no-loss forwarding classes receive lossless treatment). However, if you explicitly configure lossless forwarding classes, you can configure up to six lossless forwarding classes by specifying the no-loss option. If you do not specify the no-loss option in an explicit forwarding class configuration, the forwarding class is lossy. For example, if you explicitly configure the fcoe forwarding class and you do not include the no-loss option, the fcoe forwarding class is lossy, not lossless.
Range: 0 through 7.
This option is supported only on SRX5400, SRX5600, and SRX5800 devices.
AppQoS forwarding classes must be different from those defined for interface-based rewriters.
The default priority is low.
The spu-priority option is supported only on the SRX5000 line of devices.
The remaining statements are explained separately. See CLI Explorer for details.
Required Privilege Level
interface—To view this statement in the
interface-control—To add this statement to the configuration.