Updated Date: 09/08/2004
This technical note documents upgrading to BIG-IP software version 9.0.1 from BIG-IP software versions 4.5 PTF-04 through 4.5.10, using the remote upgrade procedure. For information about installing the software, please refer to the instructions below.
The minimum system requirements for this release are:
The supported browsers for the Configuration utility are:
This upgrade is supported only on the following platforms:
If you are unsure which platform you have, look at the sticker on the back of the chassis to find the platform number.
This technical note describes how to remotely upgrade the BIG-IP software to version 9.0.1. If you do not have direct access to the system, you need to perform a remote upgrade. The remote upgrade provides the ability to serve the installation files from a different network using HTTP. We recommend using the local upgrade if you have a direct connection to the unit you want to upgrade.
Warning: The BIG-IP system does not support upgrading from version 4.5 PTF-03 or earlier. If you are running BIG-IP software version 4.5 PTF-03 or earlier, you must upgrade to version 4.5 PTF-04, before you can upgrade to version 9.0.1.
Warning: You can only apply this upgrade to BIG-IP HA systems. The following software is not supported by this upgrade: BIG-IP versions 4.6 and later, the Link Controller, the eCommerce Controller, the Blade Controller, and the 3-DNS Controller.
Note: The BIG-IP 9.0.1 upgrade does not support upgrading from version 4.6 or later. If you are running BIG-IP software version 4.6 or later, you must downgrade to version 4.5 PTF-04, before you can upgrade to version 9.0.1. Any additional features added in version 4.6 will be lost during the downgrade.
The BIG-IP version 9.0.1 Upgrade CD ROM contains a special One-Time Conversion Utility (OTCU) for converting the current configuration during the upgrade. The OTCU parses pre-9.0.1 configuration files and uses the data to create a 9.0.1 configuration database. This conversion is necessary because the configuration files, file locations, and file formats in 4.5 versions are different in version 9.0.1.
Before you begin the upgrade process, you should save the dossier from the 4.5x system you want to upgrade. This is in the event that the entitlement process during the installation is not successful.
If the BIG-IP system is currently running version 4.5 PTF-04 through 4.5.10, you can upgrade directly to version 9.0.1, using the following procedure.
If you are running a pre-4.5 PTF-04 version of the BIG-IP software, you must first upgrade to version 4.5 PTF-04, and then upgrade to version 9.0.1.
The process of upgrading to BIG-IP version 9.0.1 requires you to do the following:
The following sections describe how to perform these tasks.
Before you upgrade to BIG-IP version 9.0.1, you need to save your version 4.5x configuration data. This file is used by the OTCU to convert your 4.5 configuration files to the 9.0.1 configuration file format. In addition, this prevents loss of data if, for any reason, the version 9.0.1 upgrade is not successful.
Collect and archive the version 4.5 configuration files, by typing the following command. Note that config.ucs is the name you must use for the UCS file and the file must be saved at the / partition.
bigpipe config save /config.ucs
Note: If you are upgrading a system that is using zonefiles with named, you must manually back up all necessary zonefiles and save them to a remote location. After the upgrade is complete, you can place them on 9.0 system. There is a new location on the 9.0 system for these files: /var/named/config/namedb.
Important: It is critical that you back up the archived configuration files to a remote location. If the upgrade process fails for any reason, you may need to use the remotely-stored file in order to restore your 4.5x configuration data.
After you save the existing 4.5x configuration, you need to copy the Upgrade_from_45-184.108.40.2069.2.im file from the /install directory on the 9.0.1 CD ROM to the /var/tmp directory on the target BIG-IP system.
Before you run the remote upgrade, you must designate and configure a remote host to be an installation server. The installation server must meet the following criteria:
Note: If you are connecting directly from one machine to another, you must use an Ethernet cross-over cable.
Once you have designated a host, complete the following steps:
Note: When you enter the IP address of the server, you need to enter only the last octet. When completing the lower and upper ranges for the clients, enter the network number(s) where the clients are situated.
Now that you have copied the remote upgrade package to the target system and configured an installation server, you are ready to install the 9.0.1 software. To install the new software, use the following procedure:
Before you can convert your configuration files or configure the system, you must license the version 9.0.1 software. To activate the license for the system, you must have a base registration key. The registration key is a 27-character string that lets the license server know which F5 products you are entitled to license. We recommed that you save a copy of the 4.5x dossier to another system before you begin the upgrade process. For details, see Saving a copy of the version 4.5x dossier. It is important to note that during the remote upgrade, the entitlement check contacts the F5 License Server and creates a license for the system.
During the remote upgrade entitlement check a 9.0.1 registration key should have been provided. The Configuration utility displays this registration key. You simply need to activate the license. Certain systems may require you to enter keys for additional modules in the Add-On Registration Key List box.
After you install and license the 9.0.1 software, you can configure the 9.0.1 system from scratch. If you want to configure the new software from scratch, you can use the Setup utility to configure the system.
To convert your existing 4.5 configuration files to 9.0 configuration files, you use the One Time Conversion Utility (OTCU). The OTCU parses 4.5x configuration files and uses the data to create a 9.0.1 configuration database. Due to the complexity of the 9.0.1 release, and differences in the 4.5x and 9.0.1 feature sets (which depends on your configuration), the OTCU may produce some unexpected results. We ask that you use the OTCU as a starting point for converting your 4.5x configuration files. Keep in mind that, in most cases, you will need to examine the resulting configuration files, troubleshoot the contents, and make adjustments where necessary. The following notes are to help you understand the conversion process and interpret the output of the OTCU.
To view an example of a converted file, see conversion example .
When you run the OTCU, the files in /otcu.ucs are converted and saved to /renamed_otcu.ucs. In addition, a log file is created and saved as /var/tmp/otcu.log. Information about the conversion is saved to /var/tmp/otcu_9.0. These log files are useful for understanding what files are converted, and for reviewing or troubleshooting the resulting configuration. If you want to refer to your 4.5x configuration files, these files are saved in /var/tmp/otcu_4.5. The /var/tmp/otcu_4.5_miscellaneous directory contains 4.5x files that are not carried forward during the conversion.
The following files are removed during the conversion:
/config/default_base.conf (no user alert)
/etc/ssh_host_key (no user alert)
/etc/ssh_host_key.pub (no user alert)
/etc/ssh_config (no user alert)
/etc/sshd_config (no user alert)
/etc/ssh3/hostkey (no user alert)
/etc/ssh3/hostkey.pub (no user alert)
/etc/ssh3/ssh3_config (no user alert)
/etc/ssh3/sshd2_config (no user alert)
/etc/snmptrap.conf (no user alert)
/etc/rc.local (no user alert)
/etc/syslog.conf (no user alert)
/etc/login.conf (no user alert)
/usr/local/www/bigipgui/.users (no user alert)
/config/bigconfig/slapd.txt (no user alert)
/etc/irs.conf, /etc/irs.conf.dns, /etc/irs.conf.nodns (no user alert)
The following files are moved forward with no conversion:
/root/.ssh/id_dsa.pub (no user alert)
/root/.ssh/id_dsa (no user alert)
/root/.ssh/identify.pub (no user alert)
/root/.ssh/identify (no user alert)
/root/.ssh/authorized_keys (no user alert)
/root/.ssh/authorized_keys2 (no user alert)
/root/.ssh/known_hosts (no user alert)
The following table lists the files that are moved during the conversion process.
|4.5x config files||9.0.1 conversion notes|
|/config/routes||Routes commands are converted to 9.0 bigpipe commands.|
|/config/bigconf/httpd.conf||The ServerName line from this file is inserted into the new httpd.conf located at /config/httpd/conf/httpd.conf.|
|/config/bigconfig/ssl.crl/||is moved to /config/httpd/conf/ssl.crl.|
|/config/bigconfig/ssl.crt/||is moved to /config/httpd/conf/ssl.crt.|
|/config/bigconfig/ssl.key||is moved to /config/httpd/conf/ssl.key.|
|etc/named.conf||is converted to BIND version 9, and references to 3-DNS are removed.|
|/etc/snmpd.conf||sysip is deleted and com2sec is changed to com2sec6.|
|/etc/snmpd.conf.disabled||sysip is deleted and com2sec is changed to com2sec6.|
Use the following procedure to convert your existing 4.5x configuration data to version 9.0.1:
The utility prompts you for the following information:
Once the 9.0 conversion is complete, the files are moved to their correct locations and loaded.
Note: If at any point you want to go back to version 4.5x, you must re-install the 4.5x software. For information on how to install the 4.5x software, please refer to the 4.5x release notes. For instructions on how to reinstall your previous 4.5x configuration files, see SOL1493.