Applies To:

BIG-IP ASM

This technical note documents the process of performing a clean installation of the BIG-IP software version 9.3 using a CD mounted on an installation server. For information about installing the software, please refer to the instructions below.

The supported browsers for the browser-based Configuration utility are:

Microsoft® Internet Explorer®, version 6.x

Mozilla® Firefox®, version 1.5x

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.

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.

About the BIG-IP version 9.3 installation

This technical note describes how to create a clean installation of the BIG-IP software to version 9.3.

Important: A valid service contract is required to complete this installation.

Warning: You must reactivate the license on the BIG-IP system on which you intend to install before you begin the installation.

Important: You cannot upgrade to version 9.3 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.

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 .

Designating and configuring a remote host to be a Pre-boot Execution Environment (PXE) server

Before you perform a network boot from a CD, you must designate and configure a remote host to be a Pre-boot Execution Environment (PXE) server. This remote host must meet all the following criteria:

Contain a CD-ROM drive.

Support a CD-ROM boot.

Reside on the same network as the one to which the BIG-IP management interface is connected.

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:

Insert the CD into the drive on the installation server and reboot the host system from the CD-ROM drive.The following message displays:

Select terminal type? [vt100]

Press the Enter key to use vt100 emulation, or type the name of the terminal emulator you are using.

If your subnet consists only of the server and the target BIG-IP unit, or is otherwise a private subnet, use the default IP addresses provided.

If other units share the subnet and there is a possibility of conflict, substitute the appropriate unique IP addresses and ranges. When you have finished entering the addresses, they are displayed and you are prompted to accept or reject them.

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.

If the settings displayed are correct, type yes. If they are not, type no to have the system prompt you to re-enter the addresses.

Finally, the system prompts you to specify the protocol you want to use to transfer the installation files. The default protocol is HTTP; however, you can also transfer the files using NFS.

Booting the target system from the remote PXE server

After you designate and configure a remote host to be a installation server, you are ready to perform the network boot from the console of the platform on which you wish to install the software.

Note: You must connect the installation server directly to the management port on the BIG-IP unit, or to the network to which the management interface is connected.

First, select the method you want to use to net boot the unit. The method you use depends on the hardware platform.

BIG-IP 1000 (D39), 2400 (D44), 5100 and 5110 (D51)With these platforms, you can set the unit to power up and boot from the network.

If the unit is powered down, power it up, and within the first ten seconds use a paperclip to push the NETboot button on the front panel.

If the unit is started and running, type the following two commands in sequence:

bigpipe db boot.netreboot enable
reboot

You might receive the following message after you type the reboot command:

The requested operation is not supported by the hardware.

If you see this error message, use a paperclip to push the RESET button on the front panel. Then, within ten seconds, use a paperclip to push the NETboot button.

BIG-IP 1500 (C36), 3400 (C62), 6400 (D63), 6800 (D68), 8400 (D84)With these platforms, the unit must be turned on before you can set it to boot from the network.

If the unit is started and running, type the following two commands in sequence:

bigpipe db boot.netreboot enable
reboot

Another way you can put the unit in network boot mode is by using the Lights-Out Management system. This method is useful if you are having difficulty booting up the system, or you cannot run the bigpipe db boot.netreboot enable command. To boot from the network using the Lights-Out Management system, use this process from the serial console:

After the system reboots, it attempts to discover the installation server.

Once the installation server is found, the system presents the following prompt:

Press M or Control-SPACE to view menu.

Let the timer count down to auto-select the installation options. After the timer counts down, the installer prompts you for the terminal type.

Terminal type? [vt100]

Press the Enter key to continue, or specify the terminal type you are using. We recommend that you use vt100.

The system posts a number of messages, and then installation starts. Once installation starts, you can use the arrow and Tab keys to navigate the presented options. You can select an option from a menu using the Enter key or the highlighted character key, and you can toggle select boxes on or off using the spacebar.

Respond to the installation script prompts for the following information:

You can specify a syslog server if you want a log of the installation process. Type the IP address of the syslog server you want to use, or continue without typing an IP address if you do not want to specify a syslog server.

Note: The syslog option is not present when the controlling terminal is the console. You see this option only when you are performing the installation through an SSH connection.

After the syslog screen, you are prompted for an installation server URL or path.The installation script provides the information about the installation server you created. We recommend you use the installation server found by the installation script. The format for the URL is: http://<installserver>/cdserver or nfs://<installserver>/cdserver

You are then prompted for the installation location. An installation location is a portion of a drive with adequate space required for an installation. If the hardware supports multiple installation locations, you can create more than one installation by installing the software on each location. At boot time, you can select which installation you want to boot. To install on multiple installation locations, follow the on-screen instructions.

Next, you have the option to roll forward any supported configurations (config.ucs files) found on the system. For clean installations, you can skip this step.

After responding to each prompt, review the installation options you have selected. Select Yes on the final BIG-IP system installation screen to begin installing.

The software takes only a few minutes to install. Once the installation is complete, the unit reboots to the installation in slot 0 or CF (CompactFlash®). You can use the switchboot utility to specify which installation you want to boot by default. For more information about the switchboot utility, see Using the switchboot utility .

Adding an IP address to the management interface using the config command

After you complete the installation of the software, and before you license the software, run the config command to configure an IP address, net mask, and gateway on the management port (MGMT). The config command is a command line utility created for this purpose. You can run the config command from the serial console you used during installation.

To run the config command, type the following command:

config

After you run this utility and add an IP address, net mask, and gateway to your management port, you can log on to the browser-based Configuration utility, and license the unit.

Licensing the software using the Configuration utility

Before you can convert your configuration files or configure the system, you must license the version 9.3 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. If you do not already have a registration key, you can obtain one using the dossier from a licensed version 4.x system (http://license.f5.com).

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.