Last Modified: Jan 29, 2019
See more info
Known Affected Versions:
13.1.0, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 13.1.1, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124
Opened: Jan 15, 2018
Upgrading from a version of 13.0.0 other than the base build may result in failure depending on the values of the virtual address route-advertisement setting. If set to 'selective', 'any', or 'all', the configuration will fail to load after the upgrade with an error similar to the following example in the /var/log/ltm file: load_config_files: "/usr/bin/tmsh -n -g load sys config partitions all " - failed. -- Loading schema version: 13.0.0 Syntax Error:(/config/bigip.conf at line: 1790) invalid property value "route-advertisement":"selective"
Configuration will not load. If the unit being upgraded is a stand-alone unit, this will result in a traffic outage.
- Upgrading from a version of 13.0.0 other than the base (i.e. HF1 or later). - Upgrading to 13.1.0 or later. - At least one virtual address with its route-advertisement value set to 'selective', 'any', or 'all'.
If you become aware of this issue prior to upgrading: 1. Note any virtual address route-advertisement settings that are 'selective', 'any', or 'all'. 2. Change all of these values to either 'enabled' or 'disabled' (note that this will change the route advertisement behavior temporarily). 3. Perform the upgrade. The goal of this step is to have the BIG-IP system perform an installation while carrying forward the new, modified configuration. Note that if your chosen destination (i.e. HD1.3) already exists and contains the very software you want to install (i.e. 126.96.36.199), then you must first delete the destination before you can re-use it. This is because, by design, the BIG-IP system will not perform an installation if the desired software is already present in the destination boot location. Attempting such an installation would just result in the BIG-IP system immediately rebooting to activate that boot location, without performing any installation and thus defeating the point of this workaround. 4. Once the upgrade completes, change the route advertisement settings back to their original values. If you become aware of this issue after the upgrade has already failed: 1. Boot back into the old/working boot location. 2. Delete the boot location containing the failed installation. 3. Follow the procedure detailed under 'If you become aware of this issue prior to upgrading'.
Upgrades from 13.0.0 hotfix rollups involving certain virtual address route-advertisement settings no longer fail.