Bug ID 890721: SSL Orchestrator sends reset to the client when an initial ingress data arrives 5 seconds after tcp connection establishment

Last Modified: Jan 26, 2023

Bug Tracker

Affected Product:  See more info
BIG-IP APM, SSLO(all modules)

Known Affected Versions:
14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 14.1.2.7, 14.1.2.8, 14.1.3, 14.1.3.1, 14.1.4, 14.1.4.1, 14.1.4.2, 14.1.4.3, 14.1.4.4, 14.1.4.5, 14.1.4.6, 14.1.5, 14.1.5.1, 14.1.5.2, 14.1.5.3, 15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.4, 15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 15.1.4, 15.1.4.1, 15.1.5, 15.1.5.1, 15.1.6, 15.1.6.1, 15.1.7, 15.1.8, 15.1.8.1, 16.0.0, 16.0.0.1, 16.0.1, 16.0.1.1, 16.0.1.2

Fixed In:
16.1.0

Opened: Mar 17, 2020
Severity: 3-Major

Symptoms

SSL Orchestrator sends reset to the client when an initial ingress data arrives 5 seconds after tcp connection establishment. Reset cause is "cl side error (No error)".

Impact

SSL Orchestrator/BIG-IP rejects the client connection.

Conditions

-- SSL Orchestrator is licensed and provisioned. -- Per-request policy is attached to virtual server.

Workaround

Modify 'tmm.access.prp_global_timeout' sys db value from default 5 seconds to some appropriate value like 30 or 60 seconds. Example: Following command sets this sys db variable value to 60 seconds. #tmsh modify sys db tmm.access.prp_global_timeout value 60

Fix Information

SSLo no longer rejects the client's connection if an initial ingress data arrives 5 seconds after tcp connection establishment and per-request policy execution has finished.

Behavior Change