Bug ID 523125: Disabling/enabling blades in cluster can result in inconsistent failover state

Last Modified: Aug 19, 2026

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

Known Affected Versions:
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.5.10, 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: May 13, 2015

Severity: 3-Major

Related Article: K17350

Symptoms

Not all blades in the cluster agree about the high availability (HA) status.

Impact

When the blades disagree about active/standby state, traffic might be disrupted.

Conditions

Disabling and enabling blades in a chassis that is configured to use HA Groups can sometimes result in a blade staying in standby even though the other blades in the chassis have gone active.

Workaround

None.

Fix Information

Disabling/enabling blades in cluster no longer results in inconsistent failover state.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips