Updated Date: 05/13/2007
This technical note documents the process of upgrading to BIG-IP software version 9.2 from BIG-IP software versions 9.0 through 9.1, 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 installation method 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.2. You need to perform a remote upgrade if you do not have direct access to the system. 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.
Important: You can only apply this upgrade to BIG-IP version 9.x systems.
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.
If the BIG-IP system is currently running version 9.0 through 9.1, you can upgrade directly to version 9.2, using the following procedure.
The process of upgrading to BIG-IP version 9.2 requires that you:
The following sections describe how to perform these tasks.
Before you upgrade to BIG-IP version 9.2, you need to save your version 9.x configuration data. Backing up your configuration prevents loss of data if, for any reason, the version 9.2 upgrade is not successful.
Collect and archive the version 9.x configuration files, by typing the following command.
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 9.2 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. In the event this process fails, you may need to use the remotely-stored file in order to restore your 9.x configuration data.
After you save the existing configuration, download the installation CD ROM ISO image from https://downloads.f5.com/. For details about downloading the ISO image, see SOL167: Downloading software from F5 Networks.
After you save the existing 9.x configuration and download the installation CD ROM, you need to copy the remote-install-22.214.171.124.4.im file from the root of the CD ROM to the /var/tmp directory on the BIG-IP system that you want to upgrade. The following example shows how you use the scp command to copy the file to a remote BIG-IP system, where <remote-upgrade>.im is the name of the remote upgrade IM you copied from the CD ROM, and the <bigipsystem> is the BIG-IP system to which you want to copy the IM file.
scp <remote-upgrade>.im root@<bigipsystem>:/var/tmp .
After you copy the remote upgrade IM file to the BIG-IP system you want to upgrade, use the CD ROM to create an installation server (this process is described in the following section).
Before you run the remote upgrade, you must designate and configure a remote host to be an installation server. The installation server 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), or BIG-IP 6800 (D68) 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.
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.2 software. Use the following procedure.
Terminal type? [vt100]Press Enter to continue, or type the terminal type you are using. We recommend that you use vt100.
Warning: You must license the version 9.2 software before you can run the OTCU or configure the system. If the entitlement check was successful, you can log in to the system. If it was not successful, you can log in to the Configuration utility and license the system as soon as the installation process is complete.
Before you can configure the system, you must license the version 9.2 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. 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.2 registration key should have been provided. The Configuration utility displays this registration key in the Base Registration Key box on the Licensing screen. 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.