Bug ID 973673: CPU spikes when the LDAP operational timeout is set to 180 seconds

Last Modified: May 29, 2024

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

Known Affected Versions:
15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 15.1.4, 15.1.4.1

Fixed In:
16.1.0, 15.1.5

Opened: Dec 14, 2020

Severity: 3-Major

Symptoms

By default, the LDAP operation timeout is 180 seconds, and this can cause CPU spikes.

Impact

High LDAP traffic load can cause cpu spikes and traffic disruption.

Conditions

-- BIG-IP configured with a per-request access policy. -- A high traffic load containing a lot of LDAP Auth and LDAP Query operations occurs.

Workaround

None

Fix Information

Reduced LDAP operational timeout to 50 sec for per-request based LDAP Auth and LDAP Query requests as accessV2 mpi request timeout is 60 sec only.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips