Updated Date: 04/03/2009
This technical note documents the process of upgrading a 520/540 (D35) platform to the BIG-IP® software version 9.4.3 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 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 technical note describes how to upgrade to version 9.4.3 on the 520/540 platform. The 520/540 platforms are not switch-based platforms. Some BIG-IP system features and requirements are slightly different, or are not supported, on the 520/540 platforms. The following section describes these features.
When you install BIG-IP version 9.4.3 on a 520/540 platform, the interface 1.1 is converted to the management interface. The minimal configuration is two built-in interfaces; however, we recommend that you add network interface cards (NICs) to bring the total number of interfaces to at least three.
The minimum memory supported is 512 MB. Most 520 platforms shipped with only 256 MB of RAM. The recommended amount of RAM is 1 GB. To avoid complications stemming from combining dissimilar brands of DIMMs, if you upgrade the memory on a unit, we recommend that you discard the old DIMMs and replace them with a single 512 MB or 1024 MB DIMM.
BIG-IP Link Controller and BIG-IP Global Traffic Manager/Local Traffic Manager combination installations require a minimum of 768 MB of memory. However, the recommended amount of RAM is 1 GB.
The front panel LED behavior is the same as version 9.x behavior. For more information, see SOL4263: Change in Behavior: New front panel LED indicator behavior in BIG-IP version 9.x.
The behavior described in this section applies to BIG-IP 9.x installations. In some cases, the behavior does not occur until after you install the software.
For details about obtaining supported network interface cards, SOL2306: Network interfaces cards supported by the F5 Networks PXE network boot server.
Some switch-based BIG-IP system features are not supported on the 520/540 platforms. This section describes these features and their behavior.
The following add-in hardware cards are not supported in this release on the 520/540 platforms:
Link Aggregation Control Protocol (LACP) and spanning tree protocol (STP) are not supported on the 520/540 platform. LACP switchboard fail-safe is not active on these platforms. The HA Table displays the switchboard fail-safe entry as disabled. LACP is enforced when the user attempts to set lacp_enable 'true' on a trunk.
STP is enforced by the global stp mode command setting. The allowed modes are passthru and disabled. Note that you can view and modify the other STP-related parameters without affecting system operation. These include the following commands: bigpipe stp, bigpipe stp instance, bigpipe interface stp, bigpipe auto edge, and bigpipe interface link type.
Most of the bigipipe commands are supported fully by the 520/540 platform, with the following exceptions:
|daemon||Displays the bcm56xxd. Not functional.|
|db boot.netreboot||Cannot enable. Not functional.|
|ha table||Displays switchboard failsafe as disabled. Not functional.|
|interface [stp | auto edge | link type ]||Can be configured. Has no effect.|
|interface pause||Not supported|
|mirror||Port mirror not supported and gives an error when configured.|
|stp||Cannot set mode. Not functional.|
|stp instance||Can be configured. Not functional.|
|trunk||Cannot enable lacp.|
Quiet boot is supported. You can set this variable using the bigdb boot.quiet setting. The D35 Tyan 2515 motherboard does not support a CMOS setting for quiet boot, so you must use the BIOS setup utility to configure the BIOS quiet boot setting.
The bigpipe command netboot enable | disable is not supported on the 520/540 platform. You must use the front panel Netboot button.
You cannot configure port mirroring on the 520/540 platform.
You can use the command bigpipe baud rate to modify the current serial console (ttyS0), and the grub baud rate setting. This baud rate is maintained across reboots and power cycles. However, the Tyan 251x BIOS does not support a CMOS setting for baud rate. As a result, for the PXE installation, you must use the BIOS baud rate setting (default 19200) for the serial console.
There is no sensor support for chassis fan, chassis power supply, chassis temperature, and CPU status.
If the BIG-IP system is currently running version 9.2.x, 9.3, 9.3.1, 9.4, 9.4.1, or 9.4.2, you can upgrade directly to version 9.4.3, using the following procedure.
Warning: 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.
The process of installing the BIG-IP version 9.4.3 software 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 must 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.
Before you begin the installation process, download the installation CD-ROM ISO image 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.
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:
Note: You must connect the installation server to the same network to which the management port on the BIG-IP unit is connected.
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.
After you designate and configure a remote host to be a PXE 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 PXE server directly to the management port on the BIG-IP unit, or to the network to which the management interface is connected.
bigpipe db boot.netreboot enable reboot
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.
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 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® media drive). 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.
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:
After you run this utility and add an IP address, net mask, and gateway to your management port, you can log on to the Configuration utility (graphical user interface), and license the unit.
Before you can convert your configuration files or configure the system, you must license the 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 4.5.x or 4.6.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.
For additional information, please visit http://www.f5.com