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

Last Modified: May 14, 2019

Bug Tracker

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

Known Affected Versions:
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.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5

Fixed In:
12.0.0, 11.6.0 HF6, 11.5.3 HF2

Opened: May 13, 2015
Severity: 3-Major
Related AskF5 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