Bug ID 847325: Changing a virtual server that uses a OneConnect profile can trigger incorrect persistence behavior.

Last Modified: Jul 12, 2023

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

Known Affected Versions:
14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.1.0, 15.1.0.1

Fixed In:
16.0.0, 15.1.0.2, 15.0.1.3, 14.1.2.5

Opened: Nov 08, 2019

Severity: 3-Major

Symptoms

-- High tmm CPU utilization. -- Stalled connections. -- Incorrect persistence decisions.

Impact

-- High tmm CPU utilization. -- Stalled connections. -- Incorrect persistence decisions.

Conditions

-- A OneConnect profile is combined with certain persist profiles on a virtual server. -- The virtual server configuration is changed while there is an ongoing connection to the virtual server. Any connections that make a request after the configuration change can be affected. -- The persistence types that are affected are: - Source Address (but not hash-algorithm carp) - Destination Address (but not hash-algorithm carp) - Universal - Cookie (only cookie hash) - Host - SSL session - SIP - Hash (but not hash-algorithm carp)

Workaround

None.

Fix Information

Changing a virtual server that uses a OneConnect profile no longer triggers incorrect persistence behavior.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips