Last Modified: May 14, 2019
See more info
Known Affected Versions:
13.1.0, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 13.1.1, 126.96.36.199
Opened: Oct 11, 2017
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".
TMM no longer crashes when an invalid persistence mode is used. Instead the LSN::persistence command returns an error.