Bug ID 522784: After restart, system remains in the INOPERATIVE state

Last Modified: Sep 13, 2023

Affected Product(s):
BIG-IP ASM, 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.6.0, 11.6.1, 11.6.2, 11.6.3,,,,, 11.6.4, 11.6.5,,,, 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 HF6, 11.5.4, 11.5.3 HF2

Opened: May 12, 2015

Severity: 1-Blocking


After restarting, it is normal for the system to remain in some state other than "Green/Active" for a few minutes while the system daemons complete their initialization. During this time the following advanced shell command may produce one or more lines of output: # bigstart status | grep waiting However, if this condition persists for more than five minutes after access to the root shell via the management interface is available, then you may be experiencing this defect.


As long as the system remains in the INOPERATIVE state, neither LTM nor ASM will function.


BIG-IP versions 11.5.x, 11.6.x or 12.0.x that have received the fix for bug 502443 but *not* 522784, may experience this issue. There are no officially supported BIG-IP releases that have this condition.


In order to work around this problem, de-provision ASM.

Fix Information

Resolves a deadlock at startup, when LTM and ASM are provisioned, that may occur as a result of the fix for 502443.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips