Updated Date: 01/21/2007
This technical note documents the process of upgrading to BIG-IP software version 9.2.5 from BIG-IP software versions 4.5.x or 4.6.x using a PXE installation. 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 BIG-IP Configuration utility are:
Note that we recommend that you leave the browser cache options at the default settings.
Important: Popup blockers and other browser add-ons or plug-ins may affect the usability of the Configuration utility. If you experience issues with navigation, we recommend that you disable these types of browser plug-ins and add-ons.
This installation method is supported only on the following platforms:
Warning: If you plan to upgrade a system licensed for Link Controller (LC), Global Traffic Manager (GTM), or a combination Local Traffic Manager and Global Traffic Manager system, the BIG-IP unit you intend to upgrade must have a minimum of 768 MB of RAM. Originally, the BIG-IP 1000 (D39) and BIG-IP 2400 (D44) platforms were shipped with 512 MB of memory only.
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.2.5. If the system is currently running BIG-IP software versions 4.5 PTF-04 through 4.5.12, you can perform the upgrade using the BIG-IP version 9.2.5 Upgrade CD.
Warning: A valid service contract is required to complete this upgrade.
Warning: You must reactivate the license on the BIG-IP system you intend to upgrade before you begin the 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.2.5.
Important: You should perform the installation on the standby system in a redundant system. If you are satisfied with the results, failover and apply the upgrade to the other unit in the redundant system.
The BIG-IP version 9.2.5 Upgrade CD-ROM contains a special One-Time Conversion Utility (OTCU) for converting your current configuration during the upgrade. The OTCU parses pre-9.2.5 configuration files and uses the data to create a 9.2.5 configuration database. This conversion is necessary because the configuration files, file locations, and file formats in 4.5 versions are different in version 9.2.5.
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.12, you can upgrade directly to version 9.2.5, 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.2.5.
The process of upgrading to BIG-IP version 9.2.5 requires:
The following sections describe how to perform these tasks.
Before you upgrade to BIG-IP version 9.2.5, you need to save your version 4.5x or 4.6x configuration data. This file is used by the OTCU to convert the configuration files to the 9.2.5 configuration file format. In addition, this prevents loss of data if, for any reason, the version 9.2.5 upgrade is not successful.
Collect and archive the version 4.5.x or 4.6.x 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
Important: If you are upgrading a system that is using zone files with named, you must manually back up all necessary zone files and save them to a remote location. After the upgrade is complete, you can place them on the 9.x system. There is a new location on the 9.x 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 configuration, download the installation CD-ROM ISO image from http://tech.f5.com. For details about downloading the ISO image, see SOL167: Downloading software from F5 Networks.
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 all the following criteria:
Note: You must connect the installation server to the same network to which the management port on the BIG-IP unit is connected.
Note: If you are installing the software on a BIG-IP 1500 (C36), BIG-IP 3400 (C62), BIG-IP 6400 (D63), BIG-IP 6800 (D68), or BIG-IP 8400 platform by directly connecting the unit to the installation server, you must use an Ethernet cross-over cable to directly connect to the management interface. If you are installing the software on a BIG-IP 1000 (D39), BIG-IP 2400 (D44), BIG-IP 5100 or 5110 (D51) by directly connecting to the installation server, you can use a standard Ethernet cable to directly connect to the management interface.
Once you have designated a host, complete the following steps.
Select terminal type? [vt100]
Maintenance OS Options Serve Provide network installation services Install Install software onto hard disk Reboot Reboot to your current system Exit Exit to maintenance shell
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 installation server, you are ready to perform the network boot from the console of the platform on which you wish to install the software.
Note: You must connect the installation server directly to the management port on the BIG-IP unit, or to the network to which the management interface is connected.
bigpipe db boot.netreboot enable
rebootYou may receive the following message after you type the reboot command:
The requested operation is not supported by the hardware.If you see this error message, 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.
bigpipe db boot.netreboot enable
Press M or Control-SPACE to view menu.Let the timer count down to auto-select the installation options.
Terminal type? [vt100]
Note: The syslog option is not present when the controlling terminal is the console. You see this option only when you are performing the installation through an SSH connection.
The software takes only a few minutes to install. Once the installation is complete, the unit reboots to the installation in slot 0 or CF (compact flash). You can use the switchboot utility to specify which installation you want to boot by default. For more information about the switchboot utility, see the BIG-IP version 9.2.5 release notes.
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.2.5 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.x system (http://license.f5.com). For details, see Obtaining a version 9.x registration key.
After you install and license the 9.2.5 software, you can configure the 9.2.5 system from scratch, or you can convert the existing configuration you rolled forward on the system. If you want to configure the new software from scratch, you can skip converting the configuration using the OTCU. This section describes how the OTCU works.
To convert your existing 4.5.x or 4.6.x configuration files to 9.2.5 configuration files, you use the One-Time Conversion Utility (OTCU). The OTCU parses 4.5.x and 4.6.x configuration files and uses the data to create a 9.2.5 configuration database. Due to the complexity of the 9.2.5 release, and differences in the 4.5.x and 4.6.x and 9.2.5 feature sets (which depend 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.5.x and 4.6.x 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. To view an example of a converted file, see conversion example . The following notes are to help you understand the conversion process and interpret the output of the OTCU.
When you run the OTCU, the files in /otcu.ucs are untarred and placed in /var/tmp/otcu_4.5. These files remain in their original state. They are not altered during the conversion process. Selected files used for the upgrade are moved into /var/tmp/otcu_9.2.5. For example, /etc/hosts is moved to /var/tmp/otcu_9.2.5/etc/hosts . After the files are moved, they are converted as much as possible into the version 9.0 format and then placed in the version 9.0 system. After the conversion is complete, the /otcu.ucs is renamed to /renamed_otcu.ucs. Renaming the file prevents you from being prompted to run the OTCU every time you start the system.
During this process a log file is created and saved as /var/tmp/otcu.log. This file contains everything printed on screen during the installation. This information is useful for understanding what files are converted, and for reviewing or troubleshooting the resulting configuration. The files in /var/tmp/otcu_9.2.5 remain in the state they were in before being moved to the version 9.2.5 system.
If you want to refer to your 4.5.x and 4.6.x configuration files, these files are saved in /var/tmp/otcu_4.5. The /var/tmp/otcu_4.5_miscellaneous directory may contain some 4.5.x and 4.6.x files that are not carried forward during the conversion that may be of interest to you. This could include the 4.5.x and 4.6.x license file, inetd.conf file, openssl.conf file, or monitor files that were not converted. You can also find these with the rest of the files located in /var/tmp/otcu_4.5, however they are moved here for convenience.
Warning: You should run the OTCU only one time. If you need to run the OTCU again, we recommend that you reinstall version 9.2.5 and then run the OTCU.
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.2.5 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.5.x or 4.6.x configuration data to version 9.x.
Note: If at any point you want to go back to version 4.5.x or 4.6.x, you must re-install the 4.5.x or 4.6.x software. For information on how to install the 4.5.x or 4.6.x software, please refer to the associated release notes. For instructions on how to reinstall your previous 4.5.x or 4.6.x configuration files, see SOL1493: Backing up and restoring BIG-IP or 3-DNS configuration files.
If you skipped the step to consolidate profiles and rename virtual servers, profiles, pools, and snatpools, you can run the consolidation utility by typing the following command:
You can run the renaming utility by typing the following command:
Note: In order for the renaming to take effect, you must reload the configuration file.