Manual Chapter : Deploying BIG-IQ Virtual Edition

Applies To:

Show Versions Show Versions

BIG-IQ Centralized Management

  • 4.6.0
Manual Chapter

About VE XenServer deployment

To deploy the BIG-IQ® Virtual Edition (VE) system on XenServer, you perform these tasks:

  • Verify the host machine requirements.
  • Deploy a BIG-IQ® system as a virtual machine.
  • Deploy a BIG-IP® system.
  • After you have deployed the virtual machines, log in to the BIG-IQ VE system and run the Setup utility. Using the Setup utility, you perform basic network configuration tasks, such as assigning VLANs to interfaces.
  • Configure secure communication between the BIG-IQ system and the BIG-IP device.

Host machine requirements and recommendations

To successfully deploy and run the BIG-IQ® VE system, the host system must satisfy minimum requirements.

The host system must include these elements:

  • Connection to a common NTP source (this is especially important for each host in a redundant system configuration)
Important: The hypervisor CPU must meet the following requirements:
  • Use a 64-bit architecture.
  • Have support for virtualization (AMD-V or Intel VT-x) enabled.
  • Support a one-to-one thread-to-defined virtual CPU ratio, or (on single-threading architectures) support at least one core per defined virtual CPU.
  • Intel processors must be from the Core (or newer) workstation or server family of CPUs.

Deploying the BIG-IQ VE virtual machine

The first step in deploying BIG-IQ® Virtual Edition (VE) is to download the OVA file to your local system. Next, you can run the Deploy OVF Template wizard from within the XenServer XenCenter client. Follow the steps in this procedure to create an instance of the BIG-IQ system that runs as a virtual machine on the host system.

Important: Do not modify the configuration of the XenServer guest environment with settings less powerful than the ones recommended in this document. This includes the settings for the CPU, RAM, and network adapters. Doing so might produce unexpected results.
  1. In a browser, open the F5 Downloads page (
  2. Download the BIG-IQ v4.x/Virtual Edition file package.
    There are two options to choose from.
    Option Description
    Large: the file name ends in .LARGE - ide.ova The large option creates a 500GB disk footprint at installation. This choice supports larger log files required for data analytics.
    Normal: the file name ends in .ide.ova The standard option creates a 55GB disk footprint at installation. This choice should be the normal working BIG-IQ installation unless data analytics functionality is required.
  3. Extract the file from the Zip archive.
  4. Before starting the import wizard, review the prospective hypervisor environment for the following.
    • Make sure a DHCP server is active on the same network as the XenServer host before you start the XenCenter® OVF Appliance.
    • Make sure there are no firewall or other restrictions between the required ports for connectivity between the XenCenter Client and XenServer. For more information and networking requirements, refer to the XenServer Virtual Machine Installation Guide.
    • Make sure enough storage space is available on the XenServer for the F5 virtual machine.
  5. Start the XenServer XenCenter client and log in.
  6. From the XenCenter 6.0 File menu, click File > Import .
    The Import wizard starts.
  7. For the filename use the Browse button to locate the OVF file, open it, and then click Next.
    For example: \MyDocuments\Work\Virtualization\<F5_OVF_filename>
    This displays the End-User License Agreement (EULA).
  8. Read and accept the license agreement, and click Next.
    The Location window opens.
  9. Under Home Server, select the home server for the F5 VE virtual machine from the list, and click Next.
  10. On the Storage window, click Place imported virtual disks onto specified target SRs, select the 100 GB storage size and location for the F5 VE virtual machine, and then click Next.
  11. On the Networking window, assign the Management, Internal, External, and HA virtual machines to their respective Target Networks and click Next.
    Tip: There is no need to enter MAC addresses, MAC addresses will be assigned automatically.
  12. In the OS Fixup Settings window, make sure the Use Operating System Fixup check box is not selected and click Next.
    Important: The Use Operating System Fixup check box is selected by default.
  13. On the Transfer VM Settings window, click Next, then on the Finish window, review your settings before continuing. Click Finish.
    The progress bar and text in the Progress pane indicate when the F5 virtual machine creation is complete.

Powering on the virtual machine

You must power on the virtual machine before you can begin assigning IP addresses.
  1. In the XenCenter® client window, select the Server View.
  2. Select the virtual machine that you want to power on.
  3. Click the Start icon.
    Note: If you do not see the Start icon, look at the tool bar under the View menu.
    The status icon changes to indicate that the virtual machine is on. The virtual machine boots and becomes ready for configuration.

Assigning a management IP address to a virtual machine

The virtual machine needs an IP address assigned to its virtual management port.
Tip: The default configuration for new deployments and installations is for DHCP to acquire the management port IP address.
  1. In the XenCenter® client window, select the Server View.
  2. In the Resources pane, select the virtual machine to which you want to assign the management IP address.
  3. Click the Console tab.
    You might need to click the console area and press Enter to activate the console.
  4. At the local host login prompt, type root.
  5. At the password prompt, type default.
  6. Type config and press Enter.
    The F5 Management Port Setup screen opens.
  7. Click OK.
  8. If you want DHCP to automatically assign an address for the management port, select Yes. Otherwise, select No and follow the instructions for manually assigning an IP address and netmask for the management port.
Tip: F5 Networks® highly recommends that you specify a default route for the virtual management port, but it is not required for operation of the virtual machine.