Bug ID 473200: Renaming a virtual server causes unexpected configuration load failure

Last Modified: Nov 07, 2022

Bug Tracker

Affected Product:  See more info
BIG-IP All(all modules)

Known Affected Versions:
11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 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.10, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4

Fixed In:
12.0.0, 11.6.0 HF5, 11.5.2

Opened: Jul 26, 2014
Severity: 3-Major
Related Article:


Manually renaming a virtual server causes unexpected configuration load failure.


Cannot reload configuration. The system posts the following error: 01020056:3: Error computing object status for virtual_server broken (old_virtual_server_name). Unexpected Error: Loading configuration process failed.


This occurs when all the following conditions are met: -- The BIG-IP system configuration containing a virtual server that was renamed by editing bigip.conf manually -- The virtual server has an empty pool, or has a pool with pool members and a monitor.


Note: Traffic may be temporarily disrupted while the updated configuration loads. Perform any one of the following: -- Remove the pool assignment from the virtual before renaming. -- Ensure the pool contains members before renaming. If the pool has a monitor, temporarily remove the monitor and add it back after renaming. To load the updated configuration, after renaming, issue 'bigstart restart'.

Fix Information

Manually editing the system configuration and renaming a virtual server with an empty pool no longer causes an unexpected error when reloading the configuration.

Behavior Change