Bug ID 571651: Reset Nitrox3 crypto accelerator queue if it becomes stuck.

Last Modified: Sep 13, 2023

Affected Product(s):
BIG-IP All(all modules)

Known Affected Versions:
11.5.4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.6.0, 11.6.1, 11.6.2, 11.6.3,, 12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2, 12.1.0, 12.1.1, 12.1.2, 12.1.3,,,,,, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0,,,,,,,, 14.0.0,,,,

Fixed In:,,,, 11.5.9

Opened: Feb 03, 2016

Severity: 2-Critical

Related Article: K66544028


Certain configuration parameters used during an SSL handshake can elicit a 'queue stuck' message from the accelerator. When this happens, the /var/log/ltm log file will contain a message similar to the following: 'n3-cryptoX request queue stuck'.


In-flight and queued contexts for the specific accelerator are dropped. After device recovery, new requests will be accelerated.


The BIG-IP system uses Nitrox 3 encryption hardware to perform SSL encryption. An SSL handshake sent to the BIG-IP system is incorrectly configured or contains bad information.


Disable crypto acceleration.

Fix Information

The crypto accelerator is gracefully reset when the accelerator stalls due to a misconfigured request. Note: This issue resolution is limited to SSL handshake issues, and is not a resolution for all possible causes of a 'queue stuck' event.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips