User is able to configure more than four queues on a RETH interface, but the SRX classifies all traffic as best effort. This is a limitation, and is as designed. In order to get Class-of-Service working with RETH or AE interface in a chassis cluster, it is necessary to re-configure the SRX with a maximum of four queues per RETH/AE interface. This article provides a configuration example.

Environment:

• High end devices configured in a chassis cluster


• Trying to set up > four queues on a RETH interface


• Able to set up > four queues on a standalone non-RETH interface

Class-of-Service is supported on RETH or AE interfaces on high end devices in a chassis cluster.  However, you can only configure up to four queues per RETH/AEinterface.  This is a limitation, and is as designed.  In order to get Class-of-Service working with RETH or AE interface in a chassis cluster, re-configure with a maximum of four queues per RETH/AEinterface.

Beginning with Junos OS 11.4R4, eight physical queues are supported for RETH interfaces in chassis cluster on High End devices.

By default, however, only four queues are enabled. Use the set chassis fpc x pic y max-queues-per-interface 8 command to enable eight queues explicitly at the chassis level.

The values of x and y depend on the location of the IOC and the PIC number, where the interface is located on the device on which CoS needs to be implemented. To find the IOC location, use the show chassis fpc pic-status or show chassis hardware commands.

Relevant Configuration:

Refer to the following document for more details on enabling eight queues and CoS configuratio:

Enabling Eight Queues on Redundant Ethernet Interfaces