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. 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 upgrade the BIG-IP software to version 9.0.1. If the system is currently running BIG-IP software versions 4.5 PTF-04 through 4.5.10, you can perform the upgrade using the BIG-IP version 9.0.1 Upgrade CD.
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: If you are running BIG-IP version 4.6 or later software, you must revert to version 4.5.10 or earlier software before you apply the version 9.0.1 upgrade. (The minimum supported version is version 4.5.4.) Once you have installed a 4.5.x version of the BIG-IP software, you can proceed with the version 9.0.1 upgrade. When you revert to the 4.5.x software, you lose any features introduced in the 4.6 software.
The BIG-IP version 9.0.1 Upgrade CD ROM contains a special One-Time Conversion Utility (OTCU) for converting your 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 obtain a version 9.0 registration key using the dossier on the 4.5x system you want to upgrade.
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.
Before you perform a network boot from a CD, you must designate and configure a remote host to be a Pre-boot Execution Environment (PXE) server. This remote host must meet the following criteria:
Note: You must connect the PXE server to the MGMT (3.1) port on the switch.
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:
Select installation option:
1 Setup server to provide network installation
2 Install software onto hard disk
3 Reboot to your current system
4 Boot to maintenance kernel
Enter choice ?
Use existing DHCP server on subnet [no]?
IP network [10.1.10]?
IP address of server 10.1.10[n] ?
Lower range for clients 10.1.10.[n] ?
Upper range for clients 10.1.10.[n] ?
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.
After you designate and configure a remote host to be a PXE server, you are ready to perform the network boot from the console of the platform on which you wish to install the software.
bigpipe global net_reboot enable
rebootIf you receive the following message after you type the reboot command, use a paperclip to push the RESET button on the front panel of the IP Application Switch. Then, within ten seconds, use a paperclip to push the NETboot button.
The requested operation is not supported by the hardware.
The software takes only a few minutes to install. Once the installation is complete, the unit reboots as a version 9.0.1 system with no configuration.
After you complete the installation of the software, and before you license the software, run the config command to configure an IP address, net mask, and gateway on the management port (MGMT). The config command is a command line utility created for this purpose. You can run the config command from the serial console you used during installation.
To run the config command, type the following command:
After you run this utility and add an IP address, net mask, and gateway to your management port, you can log in to the Configuration utility (graphical user interface) and license the unit.
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. If you do not already have a registration key, you can obtain one using the dossier from a licensed 4.5x system (http://license.f5.com). For details, see Obtaining a version 9.0x registration key.
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 4.5x 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 4.5x 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 and converted during the OTCU 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.