Last Modified: May 07, 2019
See more info
Known Affected Versions:
13.1.0, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 13.1.1, 18.104.22.168, 22.214.171.124, 126.96.36.199, 14.0.0, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168
Opened: Jun 18, 2018
The BIG-IP system fails to create a connection after 3WHS when using loose-init and hash persistence. This can happen if traffic is redirected from one BIG-IP system to another, with the second BIG-IP system failing to create the connection, causing an interruption of traffic on that connection.
Traffic fails when redirected from one BIG-IP system to another.
-- Virtual server configured with hash persistence. -- FastL4 profile with loose-init enabled.
There is no workaround other than to disable hash persistence.
A FastL4 connection no longer fails with loose-init and hash persistence enabled.