Bug ID 764897: Connection mirroring fails over to primary address when it becomes available

Last Modified: Jan 20, 2023

Bug Tracker

Affected Product:  See more info
BIG-IP LTM(all modules)

Known Affected Versions:
14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.0.1, 14.0.1.1, 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, 14.1.2.5, 14.1.2.6, 14.1.2.7, 14.1.2.8, 14.1.3, 14.1.3.1, 14.1.4, 14.1.4.1, 14.1.4.2, 14.1.4.3, 14.1.4.4, 14.1.4.5, 14.1.4.6, 14.1.5, 14.1.5.1, 14.1.5.2, 14.1.5.3, 15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.4

Fixed In:
15.1.0

Opened: Mar 25, 2019
Severity: 3-Major

Symptoms

In a BIG-IP high availability (HA) configuration with connection mirroring, where the system has failed over to a secondary mirroring address, the system will fail back over to the primary address once it becomes available again.

Impact

Mirrored connections on the peer unit are cleared when the failover back to the primary mirroring address occurs.

Conditions

-- Two BIG-IP devices configured for HA. -- Connection mirroring enabled. -- Have a primary and secondary mirroring address. -- Primary address is down, then comes online.

Workaround

None.

Fix Information

Mirroring address remains on the secondary system (until a failover causes it to switch back to the primary).

Behavior Change