Last Modified: Mar 31, 2026
Affected Product(s):
BIG-IP TMOS
Known Affected Versions:
21.0.0
Fixed In:
21.0.0.1
Opened: Dec 19, 2025 Severity: 2-Critical
BIG-IP VE or F5OS tenant fails to reach an operational state after cold boot. For example, after stopping and starting the VM, or power cycling the rSeries appliance. A message similar to the following is observed in /var/log/ltm: err mcpd[983]: 01070596:3: An unexpected failure has occurred, Can't load structure (global_sync_status.sync_status) status:52 transaction: 2, status: 52 - EdbStructData.cpp, line 39, exiting...
- MCPD starts but never becomes ready; the system remains INOPERATIVE - ecmd CPU utilization is elevated - Configuration management and control-plane services are unavailable due to MCPD not becoming ready - High CPU utilization by ecmd can impact overall system stability and resource availability
- BIG-IP VE or F5OS tenant running TMOS v21.0.0 - Cold boot of the BIG-IP VE or F5OS tenant - First startup of the BIG-IP VE or F5OS tenant ("cold boot")
From bash, delete the /var/db/mcpdb.bin and /var/db/mcpd.info files and reboot the BIG-IP VE or F5OS tenant: rm -fv /var/db/mcpdb.bin /var/db/mcpdb.info reboot MCPD will perform a full configuration load on the next startup and the system will return to operation. Note: In some cases the workaround may need to be applied more than once before a successful startup and configuration load will occur.
None