Updated Date: 07/20/2010
This technical note documents the process of performing a clean installation of the BIG-IP software version 9.3.1 using a CD mounted on an installation server. 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 browser-based 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 browser-based Configuration utility. If you experience issues with navigation, we recommend that you disable these types of browser plug-ins and add-ons.
[ Top ]
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.
[ Top ]
This technical note describes how to remotely upgrade the BIG-IP software to version 9.3.1. 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.
Important: 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 cannot upgrade to version 9.3.1 from versions 9.0 through 9.0.4. You must first upgrade to 9.0.5, or a later 9.x release.
Important: You should perform the installation on the standby unit in a redundant system. If you are satisfied with the results, initiate failover and apply the upgrade to the other unit in the redundant system.
[ Top ]
If the BIG-IP system is currently running version 9.x, you can upgrade directly to version 9.3.1, using the following procedure.
The process of upgrading to BIG-IP version 9.3.1 requires completing the following steps:
The following sections describe how to perform these tasks.
[ Top ]
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 9.x 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 configuration data. For more information about UCS archive files, see SOL4423: Overview of UCS archives.
[ Top ]
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.
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.
Note: If you are installing to a 2400 platform, see Installing to the 2400 platform for instructions for copying the installation image to the system.
[ Top ]
After you save the existing 9.x configuration and download the installation CD-ROM, you need to copy the remote-install-9.3.1.<build_number>.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).
[ Top ]
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), BIG-IP 6800 (D68), or BIG-IP 8400 (D84) 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 specify the IP address of the server, you need to enter only the last octet. When completing the lower and upper ranges for the clients, type the network numbers where the clients are situated.
[ Top ]
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.3.1 software. On the BIG-IP system, use the im command to extract the installation files from the IM package and run the installation script.
im remote-install-9.3.1.<build_number>.imThe installation script prompts you for the following information:
Terminal type? [vt100]Press the Enter key to continue, or specify the terminal type 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.3.1 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 browser-based Configuration utility and license the system as soon as the installation process is complete.
If you are installing to the 2400 platform, use this procedure to install the software.
scp root@<bigip_management_ip>:/<location> /<remote_upgrade>.im /var/ramfs/<remote_upgrade>.im
[ Top ]
Before you can configure the system, you must license the version 9.3.1 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.3.1 registration key should have been provided. The browser-based 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.
Note: If you create a stand-alone Global Traffic Manager installation or a Local Traffic Manager/Global Traffic Manager installation, after licensing the Global Traffic Manager, the system requests that you perform a software reboot. This statement is intended to indicate that you should restart the system (such as through the command bigstart restart before moving the system into a production environment.
[ Top ]
For additional information, please visit http://www.f5.com