Bug ID 475811: Mirrored flows with RAMcache might crash or leave zombie flows.

Last Modified: Nov 07, 2022

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

Known Affected Versions:
11.0.0, 11.1.0, 11.2.0, 11.3.0, 11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.10, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.6.1, 11.6.1 HF1, 11.6.1 HF2, 11.6.2, 11.6.2 HF1, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3

Fixed In:
12.0.0

Opened: Aug 16, 2014

Severity: 3-Major

Related Article: K33059673

Symptoms

When using mirroring with a RAMcache virtual server, it is possible for flows to be left on the standby. Flows of this type consume memory, leading to an eventual out-of-memory situation.

Impact

Aborted flows consume memory, leading to an eventual out-of-memory situation in which tmm might crash. Immediate termination of flows on the standby system causes the flow to not be mirrored; if failover occurs, affected open connections on the active system result in immediate client aborts.

Conditions

Using a mirrored virtual server with an acceleration policy (ramcache or WAM).

Workaround

Remove the acceleration profile, or clear the 'mirrored' flag on the virtual server.

Fix Information

Mirrored flows with RAMcache no longer crash or leave zombie flows, so that tmm no longer crashes.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips