Bug ID 691589: When using LDAP client auth, tamd may become stuck

Last Modified: Sep 13, 2023

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

Known Affected Versions:
12.1.2, 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, 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

Fixed In:
14.0.0, 13.1.1.2, 12.1.4

Opened: Oct 30, 2017

Severity: 2-Critical

Symptoms

When a virtual server uses an LDAP auth profile for client authentication, the system can get into a state where all authentications time out. This condition persists until tamd restarts. Traffic analysis between the BIG-IP system and the LDAP server shows that the BIG-IP system makes a TCP handshake with the server, then immediately sends FIN. Tamd cores may be seen.

Impact

Authentication to the virtual server fails until tamd is restarted.

Conditions

-- Virtual server using LDAP auth profile. -- BIG-IP system makes a TCP handshake with the server, then immediately sends FIN.

Workaround

To recover, restart tamd by running the following command: bigstart restart tamd

Fix Information

tamd no longer becomes stuck when using LDAP client auth.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips