Applies To:

Show Versions Show Versions

Manual Chapter: Deployment Best Practices
Manual Chapter
Table of Contents   |   << Previous Chapter   |   Next Chapter >>

Best practices for deploying BIG-IP VE on vCloud™ Director

When deploying BIG-IP® Virtual Edition (VE) on a vCloud™ Director host, use these best practices.

Issue Recommendation
Redundant system configuration Run the two units of an active/standby pair on separate physical hosts. You can accomplish this in two ways: either manually create a virtual machine peer on each host, or, if you are using VMware Dynamic Resource Scheduler (DRS), create a DRS rule with the option Separate Virtual Machine that includes each unit of the BIG-IP® VE redundant pair.
Live migration of BIG-IP VE virtual machines Perform live migration of BIG-IP VE virtual machines on idle BIG-IP VE virtual machines only. Live migration of BIG-IP VE while the virtual machine is processing traffic could produce unexpected results.
Resource reservations By default, BIG-IP VE is deployed with a 2000 or 4000 MHz CPU, and 2, 4, or 8 GB of memory reservation. Together, these reservations typically prevent system instability on heavily loaded hosts and are considered minimal. The CPU reservation can be up to 100 percent of the defined virtual machine hardware. For example, if the hypervisor has a 3 GHz core speed, the reservation of a virtual machine with 2 CPUs can be only 6 GHz or less.
Disable hyper-threading on older processors F5 Networks recommends turning off Hyper-Threading Technology when using host machines with Intel® Pentium® 4 era processors. Doing so will prevent possible timing issues with BIG-IP VE.
Important: Production licenses are not supported on Pentium 4 processors.
Table of Contents   |   << Previous Chapter   |   Next Chapter >>

Was this resource helpful in solving your issue?

NOTE: Please do not provide personal information.

Additional Comments (optional)