BIG-IQ Virtual Edition (VE) is a version of F5 BIG-IQ Centralized Management that runs as a virtual machine on specifically-supported hypervisors. BIG-IQ VE emulates a hardware-based BIG-IQ system running a VE-compatible version of BIG-IQ software.
Each time there is a new release of BIG-IQ Virtual Edition (VE) software, it includes support for additional public and private cloud products. The Virtual Edition and Supported Hypervisors Matrix on the AskF5 website, support.f5.com , details which are supported for each release.
The OpenStack virtual machine guest environment for the BIG-IQ Virtual Edition (VE), at minimum, must include:
Before you can deploy a BIG-IQ VE in the OpenStack environment, you must have the following environmental elements in place:
In addition, you might wish to define the following optional environmental elements:
To successfully deploy and run the BIG-IQ VE system, the host system must satisfy minimum requirements.
The host system must include these elements:
If the new instance requires further customization to comply with your business processes, you can use the Next and Back buttons to access the remaining pages and specify additional detail. Otherwise, this instance is ready to launch.
After the system completes the initialization process, two built-in user accounts are enabled that provide you with the access you need to complete initial configuration and setup:
You can use the shell command tmsh list sys management-ip to confirm that the management IP address has been properly assigned.
To verify that the MTU setting is causing the issue, you can log in to the BIG-IQ using SSH and run the following command: ifconfig eth0 mtu 1450. Then try connecting to the BIG-IQ again using your browser. If you can connect successfully, then you know that the MTU setting is the issue, and you need to permanently modify the MTU setting to make sure the user interface performs properly.
If you change the MTU value on the BIG-IQ using the command line, the value resets to 1500 whenever the VE reboots. So you need to edit the custom configuration file so that any time the VE restarts, the config file sets the correct value.