Updated Date: 06/10/2008
This technical note documents the process of upgrading to BIG-IP® software using the local installation procedure. For information about installing the software, please refer to the instructions below.
The minimum system requirements for this release are:
Note: The 520/540 platform must meet certain requirements in order to support this version of the BIG-IP software. For more information, including memory requirements, see 520/540 Platform: Installing the BIG-IP software.
Warning: If you plan to upgrade a system licensed for Link Controller, Global Traffic Manager, 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 only 512 MB of memory.
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 might affect the usability of the browser-based 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 that contain hard drives:
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 copy an installation manager (IM) file of the BIG-IP software to the hard drive of the unit you want to upgrade. You can perform a local upgrade if you have direct access to the system. We recommend using the local upgrade if you have a direct connection to the unit you want to upgrade.
Warning: Version 4.5.x or 4.6.x installation. You cannot upgrade directly to this version from BIG-IP version 4.x. You must first upgrade to version 9.2.x, or an earlier version of 9.3.x or 9.4.x.. For details about these installation methods, see the release notes for the associated release.
Warning: Version 9.0.x or 9.1.x installation. You cannot upgrade directly to this version from BIG-IP versions 9.0.x through 9.1.x. You must first upgrade to version 9.2.x, or an earlier version of 9.3.x or 9.4.x. For details about these installation methods, see the release notes for the associated release.
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.
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.
Important: Each unit in a redundant system must be running the same version of the software.
Important: We recommend that you run the MD5 checksum on any ISO image or IM upgrade file you download. For information about MD5 checksums, see the section Verifying the MD5 checksum of the installation file in the appropriate installation release note.
Important: If you are upgrading from 9.2.x, and you have a Global Traffic Manager unit that belongs to a sync group, you must remove the unit from the sync group before you install the software or apply the upgrade. Failure to do so may cause irrevocable damage to the units in the sync group that are running older versions of the software. Once you have upgraded all units to the same version, you can then re-create the sync group. For details on removing a unit from a sync group, see the product documentation. Once you have removed the unit from the sync group, you can proceed with the installation or upgrade. Note that this is for upgrades from 9.2.x only.
Note: We recommend installing Global Traffic Manager or Link Controller on the hard drives of BIG-IP systems. Although installation on some CompactFlash® drives is supported in most cases, it is not recommended.
The process of upgrading requires completing the following steps:
The following sections describe how to perform these tasks.
Before you upgrade to this version of the software, you need to save your current BIG-IP system configuration data. Backing up your configuration prevents loss of data if, for any reason, the upgrade is not successful.
Collect and archive the existing configuration files, by typing the following command. Note that to have the installer automatically load the configuration file during startup, you must name the file config.ucs and store it in 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 upgraded system. There is a new location on the version 9.x system for these files: /var/named/config/namedb.
Important: It is critical that you back up the archived configuration files to a secure remote location. In the event installation fails, you might need to use the remotely stored file in order to restore your previous configuration data. For more information about UCS archive files, see SOL4423: Overview of UCS archives.
After you save the existing configuration, download the installation file local-install-<version_number>.im file from the F5 Networks downloads site. For details about downloading the ISO image, see SOL167: Downloading software from F5 Networks.
Note: Before you continue, we recommend downloading the associated MD5 checksum file and performing the MD5 checksum operation to ensure that the file downloaded correctly. For more information about running the MD5 checksum, see Verifying the MD5 checksum of the installation file.
After you save the existing configuration and download the local installation package, you need to copy the local-install-<version_number>.im file to the /var/tmp directory on the BIG-IP system that you want to upgrade. The following example shows how to use the scp command to copy the file to the BIG-IP system, where <local-install>.im is the name of the local install IM, and the <bigipsystem> is the BIG-IP system to which you want to copy the IM file.
scp <local-install>.im root@<bigipsystem>:/var/tmp .
After you copy the local installation IM file to the BIG-IP system you want to upgrade, you can run the im command to extract the installation files from the local installation IM file.
Now that you have copied the installation package to the target system, you are ready to install the software. On the BIG-IP system, use the im command to run the installation script. Note that in previous versions you had to extract the script. That step is no longer necessary. The im command extracts the script and begins the installation.
After the installation is complete, the BIG-IP system reboots and you lose connectivity to the BIG-IP system.
For additional information, please visit http://www.f5.com