Manual Chapter : Updating a BIG-IP VE Virtual Machine

Applies To:

Show Versions Show Versions

BIG-IP AAM

  • 11.5.9, 11.5.8, 11.5.7, 11.5.6, 11.5.5, 11.5.4, 11.5.3, 11.5.2, 11.5.1

BIG-IP APM

  • 11.5.9, 11.5.8, 11.5.7, 11.5.6, 11.5.5, 11.5.4, 11.5.3, 11.5.2, 11.5.1

BIG-IP GTM

  • 11.5.9, 11.5.8, 11.5.7, 11.5.6, 11.5.5, 11.5.4, 11.5.3, 11.5.2, 11.5.1

BIG-IP Analytics

  • 11.5.9, 11.5.8, 11.5.7, 11.5.6, 11.5.5, 11.5.4, 11.5.3, 11.5.2, 11.5.1

BIG-IP LTM

  • 11.5.9, 11.5.8, 11.5.7, 11.5.6, 11.5.5, 11.5.4, 11.5.3, 11.5.2, 11.5.1

BIG-IP AFM

  • 11.5.9, 11.5.8, 11.5.7, 11.5.6, 11.5.5, 11.5.4, 11.5.3, 11.5.2, 11.5.1

BIG-IP PEM

  • 11.5.9, 11.5.8, 11.5.7, 11.5.6, 11.5.5, 11.5.4, 11.5.3, 11.5.2, 11.5.1

BIG-IP ASM

  • 11.5.9, 11.5.8, 11.5.7, 11.5.6, 11.5.5, 11.5.4, 11.5.3, 11.5.2, 11.5.1
Manual Chapter

About disk space changes

BIG-IP® VE can be deployed in a number of different disk space configurations. Because disk space can be a costly resource, it makes sense to install the smallest disk space configuration that is practical for your operation. If you opt for a smaller disk size, but later determine that you need additional space so you can install upgrades and hot fixes, or to run additional module combinations, you can increase the size of the disk space the BIG-IP VE uses to suit your needs.

Important: At the time of this release, decreasing the VE disk size is not supported. If you decide that you need a smaller disk size, first install a smaller disk size version of BIG-IP VE, and then increase the size to what you want. For example, you might install the 31Gb disk version of BIG-IP VE, but then decide you only need 20Gb. You could install the 7Gb version, and then increase the disk size to 20Gb.

Increasing the disk space allotted to the BIG-IP virtual machine

You can customize the amount of resources available by using a sequence of hypervisor-specific steps to increase the disk space the hypervisor uses, and follow those with a sequence of tmsh commands to increase the size of the directories that BIG-IP® VE uses.
  1. The process of expanding the virtual disk size of your hypervisor depends on which hypervisor you use. Consult your hypervisor documentation for specific instructions.
  2. After you complete the steps for expanding your hypervisor disk size, reboot the BIG-IP VE to see that new disk size.
    Important: Before the BIG-IP VE can use the additional disk space, you need to increase the size of the directories on the disk.
  3. Submit the following sequence of tmsh commands to schedule expansion of the directories in which you need more room.
    Tip:

    There are four disk directories that can be resized.

    • /config
    • /shared
    • /var
    • /var/log
    1. List the current size of the directories on your disk so you can determine which ones need to be resized.
      (tmsh show sys disk directory)
    2. Expand the size of the directories in which you need additional space.
      (tmsh modify sys disk directory <directory name> new-size <new directory size in 1KB blocks>)
      For example, use tmsh modify sys disk directory /config new-size 3145740 to increase the size of /config directory to 3145740 1KB blocks (or roughly 3,221,237,760 bytes).
    3. To confirm that the command you just submitted is properly scheduled, you can show the new list of directories again.
      (tmsh show sys disk directory)
    4. If you change your mind about a submitted size change, you can revoke that size change.
      (tmsh modify sys disk directory /config new-size 0)
      In this example, the size of the /config directory is left as is, revoking any scheduled size changes.
    After you submit this sequence of tmsh commands, the directory size changes will be scheduled. That is, the next time the BIG-IP VE is rebooted, the disk directories are re-sized.
  4. Reboot the BIG-IP VE.
    During the reboot, the directory size increases finish.

About updates to the BIG-IP VE virtual machine

BIG-IP® VE updates within the same major version are installed in the same manner as updates to BIG-IP software already installed on BIG-IP hardware. You do not need to reinstall BIG-IP VE in the hypervisor guest environment to upgrade your system. To update a BIG-IP VE virtual machine, you can use the Software Management tool in the Configuration utility, or you can upgrade the software from the command line. The update procedure described in this guide uses the Software Management tool.

Downloading and importing a BIG-IP VE update

To install an update, BIG-IP software needs access to the ISO file. If the update is a hotfix, you need the ISO files for both the base version and the hotfix before you can successfully import and install a hotfix update.

  1. In a browser, open the F5 Downloads page (https://downloads.f5.com).
  2. Download the version's base ISO file, such as 11.5, and its associated MD5 checksum file.
    Tip: The location to which you download ISO files is not significant. Just make sure you can navigate to that location when you perform the import task.
  3. Download the update ISO file, such as Hotfix-BIGIP-11.5.1-511.0-HF3.iso, and its associated MD5 checksum file.
    Important: Before you perform the installation, F5 recommends testing the integrity of the ISO files to verify that you have downloaded clean copies. Use an MD5 verification program to ensure that the downloaded ISO file's checksums match the values in their corresponding MD5 files.
  4. On the Main tab, click System > Software Management > Image List > Import .
    The Import Software Image screen opens.
  5. Click Browse to navigate to the downloaded base level installation file.
  6. When the image name appears in the Software Image field, click Import to begin the operation.
    Important: Do not navigate away from this screen before the operation completes; the system might not import the image successfully. Wait for the operation to complete before continuing with any other work on the BIG-IP VE system.
    The system presents a progress indicator during the operation; when the import is complete, the Import page closes and the downloaded base image displays as an available image.
  7. Click the Hotfix List tab.
    The Available Images portion of the screen displays any hotfixes you've imported previously.
  8. At the right side of the screen, click Import.
    The Import Hotfix screen opens.
  9. Click Browse to navigate to the downloaded hotfix installation file.
  10. When the image name appears in the Software Image field, click Import to begin the operation.
    Important: Do not navigate away from this screen before the operation completes; the system might not import the image successfully. Wait for the operation to complete before continuing with any other work on the BIG-IP VE system.
    The system presents a progress indicator during the operation; when the import is complete, the Import page closes and the downloaded hotfix displays in the list of available images.

Installing a BIG-IP VE update

After you download and import the software installation image, you can initiate the installation operation. There are three boot locations on which you can install images on the BIG-IP system. The process for installing a hotfix or a base version is essentially the same.
  1. On the Main tab of the navigation pane, click System > Software Management .
    The Software Management Image List screen opens.
  2. In the Available Images area, select the software image you want to install and click Install.
    The Install Software Image popup screen opens.
  3. Select the disk you want to install the image on, and then type or select a volume name, and click Install.
    The upgrade process installs the software on the inactive disk location that you specify. This process usually takes between three and ten minutes.
    Tip: If there is a problem during installation, you can use log messages to troubleshoot a solution. The system stores the installation log file as /var/log/liveinstall.log.
    The software image is installed.
When the installation operation is complete, you can safely reboot the newly installed volume or partition.

Rebooting after a BIG-IP VE update

When the installation operation is complete, you can safely reboot into the newly installed volume or partition.

  1. On the Main tab of the navigation pane, click System > Software Management .
    The Software Management Image List screen opens.
  2. On the menu bar, click Boot Locations.
    The Boot Locations screen opens.
  3. In the Boot Location column, click the link representing the boot location you want to activate.
    The properties screen for the boot location opens.
  4. Click Activate.
    A confirmation screen opens.
  5. Click OK to initiate the reboot operation.
    The system presents progress messages during the restart operation.
When the BIG-IP® VE system reboot is complete, the system presents the login screen. To configure the system, log in using an account that has administrative permissions.

Upgrading BIG-IP VE from version 10.x to 11.x

When a new version is available, you can upgrade from BIG-IP® VE version 10.x to the BIG-IP VE version 11.x that is available for your hypervisor.
Note: The BIG-IP VE commands in this procedure are run using the BIG-IP command-line interface within the hypervisor.
  1. Download the base ISO files and MD5 files for versions 10.2.x and version 11 from the F5 Downloads page (https://downloads.f5.com), and verify the downloaded ISO files against their corresponding MD5 files.
    Important: If you are installing a hotfix, you must import the ISO for the base version of the hotfix before you can successfully import and install a hotfix update. For installation, you select only the hotfix image, but the base version of the hotfix must be in place before the hotfix can be applied to BIG-IP VE.
  2. Save a UCS file offline for the BIG-IP VE system you are upgrading.
    Important: An SCF will not suffice for this procedure.
  3. Required: Make sure to note the host name for UCS restoration.
    The command string tmsh list sys global-settings hostname will show you the active host name.
  4. In the VMware vSphere™ client, power off (shut down) the BIG-IP VE virtual machine.
  5. Take a snapshot and back up the BIG-IP VE virtual machine.
  6. Add a CD/DVD drive to the virtual machine using either a physical device or ISO file as appropriate.
  7. Configure the target virtual machine to boot from the 10.2.x ISO image as the virtual device default node.
    The virtual device node should be IDE, where (0:0) or (1:0) is bootable. The Connect at power on setting should remain selected.
  8. Remove the existing virtual disk labeled Hard disk 1.
    Important: Select Remove from virtual machine so that the disk is available for recovery purposes.
  9. Add a hard disk.
    1. Select Create a new virtual disk and make the disk size 100 GB.
      Important: Other sizes are not supported, and unexpected problems can occur if a size other than 100 GB is used.
    2. Select the Provision type.
      For production nodes, a Flat Disk/Thick Provision is preferred to a Thin Provision. For lab editions, a Thin Provision can be used.
    3. Select Create a new virtual disk.
      Use SCSI (0:0) for the Virtual Device node.
    4. After the Summary screen, click Finish.
    At this point the system has:
    • Configured a CD/DVD drive to attach when powering on the BIG-IP VE 10.2.x ISO image.
    • Removed the legacy 40 GB disk.
    • Created a new 100 GB disk.
  10. Select BIG-IP VE from the inventory panel and power it on.
  11. At the [VT100] prompt, press Enter.
  12. You are prompted for an unattended default installation; press Enter to continue.
     BIG-IP VE version 10.2.2 and later 10.x versions should proceed normally. Versions 10.2.0 and 10.2.1 will return the message: No configuration provided for hardware type Z100. For these versions, use the command diskinit --style volumes to format the volume, and then use the command image2disk --nosaveconfig --instslot HD1.1 to install the image.
    This will prepare the disk and automatically install the 10.2.x system onto boot volume HD1.1.
  13. When the installation is complete for version 10.2.2 and later, the system prompt shows this message: Remove media, then press [Enter] to reboot. Press Enter to reboot the machine. For versions 10.2.0 and 10.2.1, type reboot and press Enter.
  14. Boot into the 10.2.x BIG-IP VE system.
  15. Log in to the console and run config to configure the management port's IP address.
  16. Copy the 10.2.x and 11 ISO files to /shared/images.
  17. If a hotfix was installed, copy the hotfix ISO file to /shared/images, and then perform a live installation of the hotfix onto the system's HD1.2. When finished, reboot into the hotfix image before restoring the UCS.
  18. Copy the UCS to /var/local/ucs/ on the BIG-IP VE.
  19. Run the command tmsh modify sys global-settings hostname xxx.xxx, where xxx.xxx is the previously collected host name.
  20. Restore the UCS. For example, if the UCS is named webfarm1.ucs and is stored in /var/local/ucs, then the restoration command is tmsh load sys ucs webfarm1.
    At this point, the system is active with the 10.2.x configuration restored.
  21. Perform a live installation of BIG-IP VE 11 on the system.
  22. When the live installation is complete, halt and power off the BIG-IP VE virtual machine.
  23. Within the hypervisor, open the guest settings for the BIG-IP VE.
  24. Remove the previously added CD/DVD drive.
  25. Adjust the memory reservation from 2 GB to 4 GB to match the memory configuration.
    Important: BIG-IP VE version 11 includes new high-availability features. You should consider adding another VMXNET3 network interface at this point in order to avoid a reboot at a later time.
  26. Power on the BIG-IP VE virtual machine.
    The BIG-IP VE virtual machine will boot into version 11.