Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP All
Known Affected Versions:
11.5.1 HF1, 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.1 HF10, 11.5.1 HF11, 11.5.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.5.0, 11.5.1, 11.5.2, 11.6.0, 11.6.1, 11.6.2, 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, 12.1.0 HF1, 12.1.0 HF2, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2
Fixed In:
12.0.0, 11.6.0 HF5, 11.5.3
Opened: Jan 20, 2015 Severity: 3-Major Related Article:
K16492
An HA failsafe triggering on a standby device that is marked as next active for a traffic group does not clear the next active setting for that device. This leaves the system in a state in which the device designated as next active cannot take over for the active device in the case of a failure.
A device marked as next active for a traffic group with a triggered HA failsafe does not take over a traffic group in the case of a failure on the active switch.
-- High availability (HA) setup with two or more devices in a device trust and device group. -- HA failsafes are configured on one or more devices in the device group. -- The HA failsafes are triggered on a device that is currently in the standby state and designated next active for a traffic group.
Workaround is to force the device in question offline, so that another device is marked as next active.
The system now correctly removes the next active setting for a device when it is in standby mode and an HA failsafe triggers. This causes a new device to be picked as next active if one is in standby mode and capable of running the traffic group.