Bug ID 688246: An invalid mode in the LSN::persistence command causes TMM crash

Last Modified: Jul 12, 2023

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

Known Affected Versions:
13.1.0,,,,,,,,, 13.1.1

Fixed In:

Opened: Oct 11, 2017

Severity: 2-Critical


When an iRule is triggered and the LSN::persistence command is passed an invalid persistence mode, TMM will crash.


TMM restarts. Traffic is interrupted. It is likely that the iRule will be triggered again causing repeated crashes.


An iRule using the LSN::persistence command with an invalid persistence mode that is attached to a Virtual Server and is triggered by traffic.


The persistence mode must be set to one of "none", "address", "address-port" or "strict-address-port".

Fix Information

TMM no longer crashes when an invalid persistence mode is used. Instead the LSN::persistence command returns an error.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips