Loading...
Loading...
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.
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.
Click on a version to see all relevant bugs
F5 Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.