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

Last Modified: Oct 21, 2018

Bug Tracker

Affected Product:  See more info
BIG-IP TMOS(all modules)

Known Affected Versions:
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.1

Fixed In:
14.0.0, 13.1.1.2

Opened: Oct 11, 2017
Severity: 2-Critical

Symptoms

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

Impact

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

Conditions

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

Workaround

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