Bug ID 910653: iRule parking in clientside/serverside command may cause tmm restart

Last Modified: Sep 13, 2023

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

Known Affected Versions:
12.1.3,,,,,,,, 12.1.4,, 12.1.5,,,, 12.1.6, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0,,,,,,,,, 13.1.1,,,,, 13.1.3,,,,,,, 13.1.4,, 13.1.5,, 14.0.0,,,,,, 14.0.1,, 14.1.0,,,,,, 14.1.2,,,,,,,,, 14.1.3,, 15.0.0, 15.0.1,,,,, 15.1.0,,,,,, 15.1.1, 15.1.2,, 16.0.0,, 16.0.1

Fixed In:
16.1.0,, 15.1.3, 14.1.4

Opened: May 20, 2020

Severity: 2-Critical


If an iRule utilizing the clientside or serverside command causes parking to occur while in the clientside/serverside command (table or after commands, for example), the connection is aborted while parked, and a subsequent iRule event attempts to run (CLIENT_CLOSED, for example), tmm may restart.


Traffic disrupted while tmm restarts.


-- iRule using clientside or serverside command. -- Use of commands that may park while in the clientside/serverside command. -- Flow is aborted while iRule is parked. -- iRule also has CLIENT_CLOSED or SERVER_CLOSED event handler. For more information on the conditions that trigger iRule parking, see K12962: Some iRules commands temporarily suspend iRules processing, available at https://support.f5.com/csp/article/K12962.


You can use either of the following workarounds: -- Rework iRules to avoid use of clientside/serverside command. -- Eliminate parking within the clientside/serverside commands.

Fix Information

iRule parking in clientside/serverside command no longer causes tmm to restart.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips