Bug ID 922317: Using the LSN::persistence_entry command in an iRule may cause crashes and/or stalled connections

Last Modified: Sep 13, 2023

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

Known Affected Versions:
11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3, 12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2, 12.1.0, 12.1.1, 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, 12.1.4, 12.1.4.1, 12.1.5, 12.1.5.1, 12.1.5.2, 12.1.5.3, 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.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 13.1.3.3, 13.1.3.4, 13.1.3.5, 13.1.3.6

Fixed In:
13.1.4, 12.1.6

Opened: Jun 30, 2020

Severity: 2-Critical

Symptoms

-- Stalled serverside connections visible in connection table. -- No traffic going out towards pool member. -- Sometimes tmm crashes may occur.

Impact

-- Traffic not reaching pool members. -- System disruption while tmm restarts in case of crash.

Conditions

The LSN::persistence_entry Tcl command is used inside of an iRule triggered by a serverside event, e.g., SERVER_CONNECTED.

Workaround

Do not use the LSN::persistence_entry command in iRules triggered by serverside events.

Fix Information

Traffic now reaches pool members, no stalled connections occur, and crashes are eliminated.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips