Manual Chapter : Deployment Best Practices

Applies To:

Show Versions Show Versions

BIG-IP AAM

  • 11.5.9, 11.5.8, 11.5.7, 11.5.6, 11.5.5, 11.5.4, 11.5.3, 11.5.2, 11.5.1

BIG-IP APM

  • 11.5.9, 11.5.8, 11.5.7, 11.5.6, 11.5.5, 11.5.4, 11.5.3, 11.5.2, 11.5.1

BIG-IP GTM

  • 11.5.9, 11.5.8, 11.5.7, 11.5.6, 11.5.5, 11.5.4, 11.5.3, 11.5.2, 11.5.1

BIG-IP Analytics

  • 11.5.9, 11.5.8, 11.5.7, 11.5.6, 11.5.5, 11.5.4, 11.5.3, 11.5.2, 11.5.1

BIG-IP LTM

  • 11.5.9, 11.5.8, 11.5.7, 11.5.6, 11.5.5, 11.5.4, 11.5.3, 11.5.2, 11.5.1

BIG-IP AFM

  • 11.5.9, 11.5.8, 11.5.7, 11.5.6, 11.5.5, 11.5.4, 11.5.3, 11.5.2, 11.5.1

BIG-IP PEM

  • 11.5.9, 11.5.8, 11.5.7, 11.5.6, 11.5.5, 11.5.4, 11.5.3, 11.5.2, 11.5.1

BIG-IP ASM

  • 11.5.9, 11.5.8, 11.5.7, 11.5.6, 11.5.5, 11.5.4, 11.5.3, 11.5.2, 11.5.1
Manual Chapter

Best practices for deploying BIG-IP VE on Hyper-V

When deploying BIG-IP Virtual Edition (VE) on a Hyper-V 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.
Resource reservations BIG-IP VE is deployed with the hypervisor's default resource settings. The CPU reservation can be up to 100 percent of the defined virtual machine reserve.
Tagged packet transmission Tagged packets cannot be transmitted from the guest itself. For VLAN tagged packets, configure the VLAN tag on the hypervisor for the specific interface associated with the 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.