Bug ID 720041: CPU Utilization Increases when SSL Session ID Persistence is enabled with HTTP/2 Profile

Last Modified: Jul 03, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP LTM(all modules)

Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.4, 14.1.0.5, 14.1.0.6

Opened: May 14, 2018
Severity: 4-Minor

Symptoms

When an HTTP/2 profile is applied to a virtual server, and SSL Session ID (SSID) persistence is enabled on the virtual server, CPU utilization jumps to 80%. TMM is found to consume most of the CPU cycles.

Impact

TMM consumes most of the CPU, and CPU utilization becomes 80%.

Conditions

-- An HTTP/2 VIP has a pool containing multiple members. -- A OneConnect profile is used (to force proxy_connect on every request). -- A client makes multiple requests on the same HTTP/2 connection (e.g., curl with nghttp support).

Workaround

To prevent this issue, add a new SSL persistence profile with 'match-across-virtuals enabled'.

Fix Information

None

Behavior Change