Applies To:

Show Versions Show Versions

Manual Chapter: Deploying BIG-IP Virtual Edition in vCloud Director
Manual Chapter
Table of Contents   |   << Previous Chapter   |   Next Chapter >>

Deploy BIG-IP VE on vCloud Director

To create a BIG-IP® VE virtual appliance, download a template from F5® and deploy it in your environment.
  1. In a browser, open the F5 Downloads page (https://downloads.f5.com) and log in.
  2. On the Downloads Overview page, select Find a Download.
  3. Under Product Line, select BIG-IP v12.x/Virtual Edition.
  4. Under Name, select Virtual-Edition.
  5. If the End User Software License is displayed, read it and then click I Accept.
  6. Download the BIG-IP VE file package ending with -vCloud.zip.
  7. Extract the file from the Zip archive.
  8. Start the vSphere client and log in.
  9. Click Catalogs > My Organization's Catalogs and on the vApp Templates tab, click Upload.
  10. Browse for and select the extracted .ovf file, type a name for the template, and click Upload.
  11. Type a name and description for the vApp template.
  12. Select a virtual data center and catalog.
  13. Click Upload.
    Click Launch Uploads and Downloads Progress Window to track the progress.
  14. Click My Cloud > vApps .
  15. Click Add vApp from Catalog.
  16. Select My organization's catalogs or Public catalogs from the list, select a vApp template, and click Next.
  17. Read and accept the license agreement, and click Next.
    The Name and Location pane opens.
  18. In the Inventory Location area, select a folder name and click Next.
  19. Under Configure Virtual Machines, specify the full name and computer name for the vApp, and configure the network settings.
    1. Select the network for NIC0 from the list of networks.
      This network is used to manage the BIG-IP system. If you are using DHCP, you should have a DHCP server on this network.
      Note: The Select IP Assignment – Static settings have no effect; you will configure the IP address in BIG-IP VE after the VM is deployed.
    2. Select the networks for NIC1, NIC2, and NIC3.
    3. Click Next.
  20. Configure organizational settings, such as Fence vApp and IP persistence, and click Next.
  21. Verify the settings and click Finish to start deployment.
If you need to create a redundant configuration, place the two BIG-IP VE virtual appliances (the active-standby pair) on separate physical hosts. You can accomplish this in one of two ways:
  • Manually create a virtual machine peer on each host.
  • If you are using VMware Dynamic Resource Scheduler (DRS), create a DRS rule with the Separate Virtual Machine option that includes each BIG-IP VE in the pair.

Access the BIG-IP VE Configuration utility

If your network has DHCP, an IP address is automatically assigned to BIG-IP® VE during deployment. You can use this address to access the BIG-IP VE Configuration utility or tmsh command-line utility.

If no IP address was assigned, you can assign one.

Important: Do not use VMware tools to configure the IP address; the BIG-IP system will not use these changes.
  1. In the vSphere client, click Launch Virtual Machine Console.
    The console screen opens. After a few seconds, a login prompt appears.
  2. At the password prompt, type default.
  3. Type config and press Enter.
    The F5 Management Port Setup screen opens.
  4. Click OK.
  5. 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 show sys management-ip to confirm that the management IP address has been properly assigned.

You can now log into the BIG-IP VE Config utility, and license and provision BIG-IP VE.
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)