Manual Chapter :
Deploying BIG-IP Virtual Edition in vCloud Director
Applies To:
Show VersionsBIG-IP AAM
- 12.1.4, 12.1.3, 12.1.2, 12.1.1, 12.1.0
BIG-IP APM
- 12.1.4, 12.1.3, 12.1.2, 12.1.1, 12.1.0
BIG-IP Analytics
- 12.1.4, 12.1.3, 12.1.2, 12.1.1, 12.1.0
F5 DDoS Hybrid Defender
- 12.1.0
BIG-IP LTM
- 12.1.4, 12.1.3, 12.1.2, 12.1.1, 12.1.0
BIG-IP AFM
- 12.1.4, 12.1.3, 12.1.2, 12.1.1, 12.1.0
BIG-IP PEM
- 12.1.4, 12.1.3, 12.1.2, 12.1.1, 12.1.0
BIG-IP DNS
- 12.1.4, 12.1.3, 12.1.2, 12.1.1, 12.1.0
BIG-IP ASM
- 12.1.4, 12.1.3, 12.1.2, 12.1.1, 12.1.0
Deploying 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.
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.
Accessing the BIG-IP VE management user interface
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 user interface or tmsh command-line
utility.
If no IP address was assigned, you can assign one by using the BIG-IP Configuration utility.
Important: Do not use
VMware tools to configure the IP address; the BIG-IP system will not use these
changes.
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
user interface, and license and provision BIG-IP VE.