Applies To:

Show Versions Show Versions

Manual Chapter: Upgrading from Versions 93x and 94x
Manual Chapter
Table of Contents   |   << Previous Chapter   |   Next Chapter >>

Upgrading from Versions 9.3.x and 9.4.x
and Reformatting for 10.1.x
Upgrading from version 9.3.x or 9.4.x comprises the same basic tasks as an upgrade between differing versions of 10.x software:
The image2disk utility performs software installation operations for installing this version of the software. You use the image2disk utility in the following situations:
Warning: Do not use the image2disk utility to install version 9.x software .im files. Depending on the operations you perform, doing so might render the system unusable. If you need to downgrade from version 10.x to version 9.x, use the image2disk utility to format the system for partitions, and then use a version 9.x installation method described in the version 9.x release notes to install the version 9.x software.
Upgrading version 9.3.x or 9.4.x systems or reformatting for version 10.1.x
If you plan to install this version of the software onto a BIG-IP system that is currently running version 9.3.x or 9.4.x, you must perform a one-time upgrade procedure to make your system ready for the 10.x installation process. During the upgrade process, you can decide to use partitions to maintain the version 9.3.x or 9.4.x software alongside version 10.x, or use volumes completely maintain an all-10.x system.
Important: Beginning with version 10.1.0, you must reformat the systems hard drive partitions even if you plan to maintain 9.x alongside 10.x. Partitions created using version 9.x or 10.0.x software do not accommodate the 10.1.x software. To maintain both versions, you use the image2disk utility to reformat the drive and install the 10.1.x software, and then complete a separate operation using a version 9.x installation method described in the version 9.x release notes. For more information, see To format the drive for volumes and install the software.
Most of the preparatory installation tasks for upgrading from version 9.3.x or 9.4.x are the same as those for using the Software Management screens to upgrade from version 9.6.x or earlier versions of 10.x. Before you start the system installation, ensure that the system meets the requirements listed in the information in Performing prerequisite tasks, and then continue with Performing system upgrade, following.
Once you complete the prerequisite tasks described in Performing prerequisite tasks, you can continue with this process to upgrade the software, or to reformat to the 10.1.x-size partition and install the software.
Important: You cannot use the image2disk utility to install to BIG-IP systems running version 9.2.x or earlier. You must first upgrade to version 9.3.x or 9.4.x. For information on upgrading, see the release notes for the associated software.
Before you can install the software, you must download the installation file. You can download the ISO installation image file from the F5 Networks Downloads site, at https://downloads.f5.com.
Once you have downloaded the file, use a copy utility applicable to your operating system to copy the ISO image to the /shared/images directory on the BIG-IP system.
If your system does not already have this directory, you must create it. If you create the directory, make sure to use the exact name /shared/images.
Note: You can also run the installation operation from /mnt/thumb/ on a thumb drive that contains the downloaded ISO image. For information on creating a thumb drive, see Appendix C, Creating a Bootable USB Thumb Drive.
To complete an upgrade from version 9.3.x or 9.4.x, you must have the upgrade and disk formatting utility on your system. The ISO installation file that you downloaded in the previous task, Downloading the installation file, contains the image2disk upgrade and disk formatting utility. You can copy the utility to your system from the command line by typing the following command:
The process copies over the image2disk utility, and then presents a status message, which lets you know that the im command is no longer supported, and tells you how to proceed.
When you prepare to install the 10.x software, you must decide whether you want to format the systems hard drive as volumes or partitions. If you plan a configuration that consists solely of 10.x software, we recommend that you use the volume disk-formatting scheme. If you plan to retain a 9.x version of the software on the BIG-IP system, however, you must use the partitions formatting scheme.
One advantage of using volumes is that you can create multiple volumes to maintain several versions of 10.x software. Another advantage to having multiple volumes is that a module might utilize a volume for caching or another purpose, as described in the modules configuration guide.
Important: Beginning with version 10.1, the software no longer fits in partitions created using the 9.x or 10.0.x formatting options. Although you can still use partitions to maintain version 9.x alongside 10.x, you must reformat the drive for the larger partition size.
You use the --format option of the imge2disk utility to format for partitions or volumes, and to convert from one type of disk management style to another (that is, from partitions to volumes, or vice versa), as you install the software. Also called logical volume management (LVM), volumes are supported on all platforms and modules that version 10.x supports. If you plan a configuration that consists solely of 10.x software, we recommend that you use the volume disk-formatting scheme.
The image2disk utility cannot run if the system hard drive contains low-level formatting errors. To recover a corrupted or damaged disk, you can use the diskinit utility, and then use the image2disk utility to install the software after formatting is complete. For information about the hard-drive recovery process, see Recovering blank or damaged hard drives.
Important: Some platforms, such as the BIG-IP 6900 and BIG-IP 8900, have multiple drives. For these platforms, formatting creates drives with designators MDn.n instead of HDn.n. The examples used throughout this chapter use HDn.n when specifying installation locations. When applicable, you should substitute MDn.n for installation.
To install the 10.x software and upgrade from version 9.3.x or 9.4.x, you specify the designator representing the installation location to upgrade to, the style of disk formatting, and the name of the downloaded .iso file. The basic syntax of the command is:
When you start an installation operation, the installer copies the currently active configuration and license into memory. If the operation migrates a configuration, as it does in the default case, the installer applies the license from the active location at the very end of the operation, using the configuration and license in memory.
You can find descriptions of each image2disk option in the man page for the utility, available at the command line by typing man image2disk.
Note: Once you have run the image2disk utility, the system prevents you from running it again unless you are also formatting the drive using the --format option. This is to prevent potential issues that might arise with a second installation operation. To repeat an installation operation without formatting, you can use the Software Management screens in the browser-based Configuration utility, or the b software commands on the command line. For information about using the Software Management screens, see Using Software Management screens. For information about using the b software commands, review the man page, available by typing the command man software at the system command line.
The examples in the following procedures show the commands to run to install the software and format the drive for volumes.
Warning: The reformatting operation erases all data on the disk. Before starting the reformatting operation, make sure to back up your configuration and store it in a secure, remote location.
Warning: Do not use the --nomoveconfig option described in the following procedure on systems with existing, running installations of Application Security Manager. Doing so removes all content from the associated database. Instead, ensure that the configuration on the source installation location matches the one on the destination. To do so, save the UCS configuration on the location you want to preserve, and apply that configuration to the destination before or after the installation operation.
The upgrade process installs the software on the inactive installation location (--instslot) that you specify. This process usually takes between three minutes and seven minutes.
The procedures for formatting the drive for partitions and installing the software are the same as those for volumes, except you substitute partitions for volumes.
Warning: If you are upgrading to BIG-IP version 10.1 or later and you plan to maintain a mixed 9.x and 10.x environment, you must reformat the drive for the larger, version 10.1.x partition size. You cannot simply upgrade to version 10.1.x if you are using partitions. The 10.1.x versions of the software do not fit in partitions created with version 9.x or 10.0.x disk formatting.
Once the installation process completes, reboot the system to complete the upgrade or installation operation. To do so, run the switchboot utility to boot to the installation location you upgraded. Once there, you can check that your configuration appears as you expect. The following example shows the commands to run.
Provision TMOS® modules
Table of Contents   |   << Previous Chapter   |   Next Chapter >>

Was this resource helpful in solving your issue?




NOTE: Please do not provide personal information.



Incorrect answer. Please try again: Please enter the words to the right: Please enter the numbers you hear:

Additional Comments (optional)