Bug ID 2199701: Big3d was stuck in high CPU after network disruption

Last Modified: Jul 28, 2026

Affected Product(s):
BIG-IP DNS, GTM, Link Controller(all modules)

Known Affected Versions:
17.5.1.3, 17.5.1.4, 17.5.1.5, 17.5.1.6, 17.5.1.8

Fixed In:
17.1.3.4

Opened: Jan 07, 2026

Severity: 3-Major

Symptoms

Big3d is consuming high CPU

Impact

Big3d is overloaded with high CPU usage

Conditions

Network disruption

Workaround

None

Fix Information

Some SSL sessions were being cached before a full and valid handshake was completed Issue in the SSL session cache lookup logic; the cache comparison did not fully validate that the session SNI matched the incoming connection During network-impact scenarios, monitor queues could already be full, and the system will no longer perform route checks that are not actionable because probes would be dropped

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips