Bug ID 492978: All blades in a cluster remain offline after provisioning ASM or FPS

Last Modified: Sep 13, 2023

Affected Product(s):
BIG-IP ASM, FPS(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, 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

Opened: Nov 25, 2014

Severity: 2-Critical

Symptoms

After provisioning either ASM or FPS on a cluster, the system may reach a state in which the datasyncd process will keep all of the blades offline. The system will repeatedly switch the primary blade, but never successfully transition to online.

Impact

If this state is reached, all of the blades will remain offline and not handle incoming traffic until the entire chassis is rebooted.

Conditions

This is a rare scenario that may happen when provisioning either ASM or FPS on a cluster.

Workaround

If this scenario happens, the workaround is to reboot the entire chassis, or individually reboot all of the blades roughly at the same time.

Fix Information

Fixed a rare scenario in which all the blades in a cluster remain offline after provisioning either ASM or FPS.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips