Last Modified: Nov 07, 2022
See more info
Known Affected Versions:
11.0.0, 11.1.0, 11.2.0, 11.2.1, 11.3.0, 11.4.0, 11.4.1, 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.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9
Opened: Oct 28, 2013
10.x users were allowed to save UCS files without a hostname set. When rolling forward to 11.x, a 10.x UCS with no hostname fails.
Upgrade to 11.x releases fails because the config fails to load. The system posts an error message similar to the following: 'Oct 27 10:03:05 localhost err mcpd: 01070734:3: Configuration error: Invalid create, modify, or delete for sys_device objects in the root folder. Oct 27 10:03:06 localhost err load_config_files: "/usr/libexec/bigpipe base daol" - failed. -- BIGpipe unknown operation error: 01070734:3: Configuration error: Invalid create, modify, or delete for sys_device objects in the root folder. Reading configuration from /config/bigpipe/low_profile_base.conf. Reading configuration from /config/bigpipe/config_base.conf. Reading configuration from /config/bigpipe/bigip_sys.conf. Reading configuration from /config/bigpipe/bigip_base.conf. Loading the configuration ... Oct 27 10:03:06 localhost err mcpd: 01070422:3: Base configuration load failed.'
This occurs when a UCS was saved in a 10.x release when the hostname of the system was blank.
In the configuration that fails the upgrade, perform one of the following procedures: Option I: 1. Manually add a hostname to the config in /config/bigip_base.conf. 2. Run the command 'tmsh load sys config'. Option II: 1. In the 10.x UCS, add the HostName field in config/BigipDB.dat. 2. On the 11.x BIG-IP system, run the command 'tmsh load sys ucs <10.x-ucs>'
UCS files saved in a 10.x release with a blank system hostname can now be rolled forward to 11.6.0.