Manual Chapter : Deployment Best Practices

Applies To:

Show Versions Show Versions

BIG-IP AAM

  • 11.6.4, 11.6.3, 11.6.2, 11.6.1

BIG-IP APM

  • 11.6.4, 11.6.3, 11.6.2, 11.6.1

BIG-IP GTM

  • 11.6.4, 11.6.3, 11.6.2, 11.6.1

BIG-IP Analytics

  • 11.6.4, 11.6.3, 11.6.2, 11.6.1

BIG-IP LTM

  • 11.6.4, 11.6.3, 11.6.2, 11.6.1

BIG-IP AFM

  • 11.6.4, 11.6.3, 11.6.2, 11.6.1

BIG-IP PEM

  • 11.6.4, 11.6.3, 11.6.2, 11.6.1

BIG-IP ASM

  • 11.6.4, 11.6.3, 11.6.2, 11.6.1
Manual Chapter

Deployment Best Practices

Best practices for deploying BIG-IP VE on XenServer

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

Issue Recommendation
Redundant system configuration Run the two units of an active/standby pair on separate physical hosts by manually creating a virtual machine peer on each host.
Using XenMotion on live BIG-IP VE virtual machines Use XenMotion for live migration of BIG-IP® VE virtual machines on idle virtual machines only. Live migration of BIG-IP VE while the virtual machine is processing traffic could produce unexpected results.
Resource reservations BIG-IP VE is deployed with the hypervisor's default resource settings. The CPU reservation can be set only to the highest setting of the VCPU priority of the virtual machine.
Time synchronization Configure all BIG-IP VE systems to use an external time synchronization source. You can do this by configuring NTP within BIG-IP VE.
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.