Applies To:Show Versions
BIG-IQ Centralized Management
- 6.0.1, 6.0.0, 5.4.0, 5.3.0, 5.2.0
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)
- 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.
- In a browser, open the F5 Downloads page (https://downloads.f5.com).
- On the Downloads Overview page, select Find a Download.
- Under Product Line, select Centralized Management.
- Under Name, select the release you want to install.
- If the End User Software License is displayed, read it and then click I Accept.
Determine which BIG-IQ v5.x/Virtual Edition file package to download.
- If you are installing a BIG-IQ, download the file name that ends in ide.ova or -scsi.ova
- If you are installing a Data Collection Device, download the file name that ends in LARGE-ide.ova or LARGE-scsi.ova
The BIG-IQ file package creates a 95GB disk footprint at installation.
The Data Collection Device file package creates a 500GB disk footprint at installation.
- Extract the file from the Zip archive.
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.
- Start the XenServer XenCenter client and log in.
From the XenCenter 6.x File menu, click .
The Import wizard starts.
For the file name 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).
Read and accept the license agreement, and click Next.
The Location window opens.
- Under Home Server, select the home server for the F5 VE virtual machine from the list, and click Next.
- On the Storage window, click Place imported virtual disks onto specified target SRs, select the 100 GB storage size (for Data Collection Devices, select 500 GB) and location for the F5 VE virtual machine, and then click Next.
On the Networking window, assign the Management, Internal, External, and HA
virtual machines to their respective Target Networks and click
Tip: There is no need to enter MAC addresses, MAC addresses will be assigned automatically.
In the OS Fixup Settings window, make sure the
Use Operating System Fixup check box is cleared, and
Important: The Use Operating System Fixup check box is selected by default.
On the Transfer VM Settings window, click Next, then on
the Finish window, review your settings before continuing.
Note: The recommended settings in production scenarios are 4 CPU and 16 GB RAM as minimum, or 8 CPU and 32 GB RAM for better performance. A lower setting of 2 CPU and 4 GB RAM can be used for evaluation purposes, but as of version 5.2.0 is deprecated and no longer supported.
The progress bar and text in the Progress pane indicate when the F5 virtual machine creation is complete.
Power on the BIG-IQ VE virtual machine
- In the XenCenter client window, select the Server View.
- Select the virtual machine that you want to power on.
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.
There are two default accounts used for initial configuration and setup:
- The root account provides access locally, or using SSH, or using the F5 Configuration utility. The root account password is default.
- The admin account provides access through the web interface. The admin account password is admin.
You should change passwords for both accounts before bringing a system into production.
Accessing the BIG-IQ VE management user interface
If no IP address was assigned, you can assign one by using the BIG-IQConfiguration utility.
- In the XenCenter client screen, select the Server View.
- In the Resources pane, select the virtual machine.
Click the Console tab.
You might need to click the console area and press Enter to activate the console.
- At the local host login prompt, type root.
- At the password prompt, type default.
Type config and press Enter.
The F5 Management Port Setup screen opens.
- Click OK.
- 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.
You can use a hypervisor generic statement, such as tmsh list sys management-ip to confirm that the management IP address has been properly assigned.