Bug ID 724564: A FastL4 connection can fail with loose-init and hash persistence enabled

Last Modified: May 07, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP LTM(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, 13.1.1.2, 13.1.1.3, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4

Fixed In:
14.1.0, 13.1.1.4

Opened: Jun 18, 2018
Severity: 3-Major

Symptoms

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.

Impact

Traffic fails when redirected from one BIG-IP system to another.

Conditions

-- Virtual server configured with hash persistence. -- FastL4 profile with loose-init enabled.

Workaround

There is no workaround other than to disable hash persistence.

Fix Information

A FastL4 connection no longer fails with loose-init and hash persistence enabled.

Behavior Change