Bug ID 468517: Multi-blade systems can experience active/standby flapping after both units rebooted

Last Modified: Sep 13, 2023

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

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.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.2

Opened: Jun 23, 2014

Severity: 3-Major

Related Article: K16249

Symptoms

After rebooting multi-bladed BIG-IP systems configured for failover, one or more of the systems has some of its blades flap from active to standby.

Impact

Invalid redundant status.

Conditions

Rebooting systems fairly close in time from one another (about a minute apart). Traffic group must reference an HA group.

Workaround

Modify the traffic group to no longer reference an HA group: tmsh modify cm traffic-group traffic-group-1 ha-group none.

Fix Information

Multi-blade systems no longer experience active/standby flapping after both units are rebooted, so the following MCPD error message no longer occur at the secondary blades: err mcpd[6528]: 010717b5:3: HA group (HA) cannot be removed. It is used by traffic group (/Common/traffic-group-1 ).

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips