Updated Date: 09/21/2010
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 BIG-IP version 9.4.2.
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 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, 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 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 section describes the requirements for the USB mass storage devices supported by this installation method. In order to use a USB mass storage device 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 remotely upgrade the BIG-IP software to version 9.4.2. You might 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.2.x, 9.3, 9.4, or 9.4.1 systems.
Warning: Version 4.5.x or 4.6.x installation. You cannot upgrade directly from BIG-IP version 4.x to 9.4.2. You must first upgrade to a 9.2.x or 9.3 version. 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: 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.
If the BIG-IP system is currently running version 9.2.x, 9.3, 9.4, or 9.4.1, you can upgrade directly to version 9.4.2, using the following procedure.
The process of upgrading to BIG-IP version 9.4.2 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 files from http://downloads.f5.com. If you plan to load the installation image from a Windows-based system, download the CD-ROM ISO image. If you plan to load the installation image from the BIG-IP, download the local installation IM file. For details about downloading these files, 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.
If you download the CD-ROM ISO image, burn the image onto a CD-ROM before you continue to the next task.
After you save the existing configuration and download the installation CD-ROM ISO image (to use from Windows-based systems) or the local installation IM package (to use from BIG-IP systems), you need to load the installation image onto the USB mass storage device from the CD-ROM. You can do this from a Windows-based system or a BIG-IP system.
The Windows-based system must be Windows 2000 or later.
With BIG-IP systems, you can use the umdinstall command to transfer the installation image to the USB mass storage device. You can use either the CD-ROM ISO image or the local installation IM package copied to the hard drive of the BIG-IP system.
Using the BIG-IP system to load the installation files onto a USB mass storage device
After you have loaded the installation image onto the USB mass storage device, you are ready to install the software. Use the following procedure.
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 is complete, the BIG-IP system reboots and you lose connectivity to the BIG-IP system.
Warning: You must license the version 9.4 software before you can configure the system. If the entitlement check was successful, you can log on to the system. If it was not successful, you can log on to the Configuration utility and license the system as soon as the installation process is complete.
Before you can configure the system, you must reactivate the license for the version 9.4.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.
For additional information, please visit http://www.f5.com