Bug ID 564248: Some persistence entries not remirrored after HA connection reestablished

Last Modified: Sep 13, 2023

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

Known Affected Versions:
11.0.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.5.1 HF1, 11.6.1 HF1, 11.5.1 HF2, 11.6.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.1 HF10, 11.5.1 HF11, 11.5.2 HF1, 11.6.2 HF1, 11.5.3 HF1, 11.5.3 HF2, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.1.0, 11.2.0, 11.3.0, 11.4.0, 11.5.0, 11.5.1, 11.5.2, 11.5.3, 11.5.4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10

Fixed In:
12.1.0

Opened: Dec 21, 2015

Severity: 3-Major

Symptoms

Any persistence entries created when the HA connection is down will not be mirrored, and will not be remirrored when the HA connection is reestablished.

Impact

When the HA connection is reestablished, the persistence entries are not remirrored. If using flow mirroring, the flows are still mirrored appropriately. (Remember that L7 flows are not remirrored if there is an HA connection drop at any time that data needs to be sent to the peer. This is by design for L7 flows. L4 flows will remirror.)

Conditions

Using either flow mirroring with persistence, or persistence mirroring (or both), in an active/standby or active/active pair, and incoming connections arrive when the HA connection is down. For example, the standby could be offline for maintenance, or the HA connection itself may have dropped.

Workaround

None

Fix Information

Persistence entries created when the HA connection is down are now marked for mirroring. They will be remirrored when the HA connection is reestablished.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips