Updated Date: 01/13/2010
This technical note documents the process of upgrading to BIG-IP® software using the USB thumb drive. 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:
If you are unsure which platform you have, look at the sticker on the back of the chassis to find the platform number.
This section describes the requirements for the USB thumb drives supported by this installation method. In order to use a USB thumb drive for this method of installation, the device must meet the following requirements:
The device capacity and capabilities are described in the following table.
Note: While smaller capacity devices are supported, we recommend using a device with at least 1 GB capacity.
|Device Capacity||Device Capability|
|512 MB to 1 GB||Minimum space for BIG-IP product installation|
|1 GB or more||Recommended size for BIG-IP product installation|
This technical note describes how to create a bootable USB thumb drive and use it to install the BIG-IP software.
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: 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 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.
Before you begin the installation process, you might need to download the installation file from http://downloads.f5.com. For details about downloading the .iso file, 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 .iso file, you must load the installation image onto the thumb drive. You can use the mkdisk utility to create a bootable thumb drive containing a software installation image. You can then use that thumb drive as the installation source to install the software.
When you create a bootable thumb drive, you can use a BIG-IP system, or you can use a Linux workstation. The system you use to create a bootable thumb drive must meet a number of requirements, including non-TMOS™ system software and third-party utilities. For information about non-TMOS system software and third-party utilities, refer to the appropriate documentation.
To create a bootable thumb drive, the system you use must meet the following requirements:
To create the thumb drive
Note: The mkdisk utility offers VIPRION as one of the choices for the target of the thumb drive. The version 9.4.7 software does not support the VIPRION platform, but the utility does not prevent you from selecting the option.
You can use the newly created thumb drive to boot the target device. Place the thumb drive in the USB port of the target device and reboot it. The device automatically boots to the Maintenance OS on the thumb drive.
Note: This type of installation requires a serial console connected to the BIG-IP system. You must use the serial console to respond to the prompts presented by the installation script and to monitor the progress of the installation.
Terminal type? [vt100]Press the Enter key to use vt100 emulation, or type the name of the terminal emulator you are using. We recommend that you use vt100.
After the installation finishes, the BIG-IP system reboots and you lose connectivity to the BIG-IP system until reboot is complete.
Before you can configure the system, you must reactivate the license for the new 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.
For additional information, please visit http://www.f5.com