Bug ID 785017: Secondary blades go offline after new primary is elected

Last Modified: Sep 13, 2023

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

Known Affected Versions:
14.1.0,,,,,, 14.1.2,,,,,,,,, 14.1.3,, 15.0.0, 15.0.1,,,,, 15.1.0,,,,,, 15.1.1, 15.1.2,

Fixed In:
16.1.0, 15.1.3, 14.1.4, 13.1.4

Opened: May 22, 2019

Severity: 2-Critical


Secondary active blades go offline.


Cluster reduced to a single blade, which may impact performance.


-- Cluster with three or more active blades. -- Primary blade is rebooted. For example, on a 4-bladed system, after slot 1 (primary blade) was rebooted and slot 2 (secondary blade) takes over as primary, slots 3 and 4 both go offline due to high availability (HA) table, with the logs showing reason as 'waiting for configuration load'.



Fix Information


Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips