Manual Chapter : Prerequisites for BIG-IP Virtual Edition on Hyper-V

Applies To:

Show Versions Show Versions

BIG-IP AAM

  • 13.1.1, 13.1.0

BIG-IP APM

  • 13.1.1, 13.1.0

BIG-IP Analytics

  • 13.1.1, 13.1.0

BIG-IP LTM

  • 13.1.1, 13.1.0

BIG-IP AFM

  • 13.1.1, 13.1.0

BIG-IP PEM

  • 13.1.1, 13.1.0

BIG-IP DNS

  • 13.1.1, 13.1.0

BIG-IP ASM

  • 13.1.1, 13.1.0
Manual Chapter

Host CPU requirements

The host hardware CPU must meet the following requirements.

  • The CPU must have 64-bit architecture.
  • The CPU must have virtualization support (AMD-V or Intel VT-x) enabled.
  • The CPU must support a one-to-one, thread-to-defined virtual CPU ratio, or on single-threading architectures, support at least one core per defined virtual CPU.
  • If your CPU supports the Advanced Encryption Standard New Instruction (AES-NI), SSL encryption processing on BIG-IP® VE will be faster. Contact your CPU vendor for details about which CPUs provide AES-NI support.

Host memory requirements

The number of licensed TMM cores determines how much memory the host system requires.

Number of cores Memory required
1 2 Gb
2 4 Gb
4 8 Gb
8 16 Gb

Virtual machine memory requirements

The guest should have a minimum of 4 GB of RAM for the initial 2 virtual CPUs. For each additional CPU, you should add an additional 2 GB of RAM.

If you license additional modules, you should add memory.
Provisioned memory Supported modules Details
4 GB or fewer Two modules maximum. AAM can be provisioned as standalone only.
4-8 GB Three modules maximum.

BIG-IP® DNS does not count toward the module limit.

Exception: Application Acceleration Manager™ (AAM®) cannot be provisioned with any other module; AAM is standalone only.

8 GB Three modules maximum. BIG-IP DNS does not count toward the module-combination limit.
12 GB or more All modules. N/A
Important: To achieve licensing performance limits, all allocated memory must be reserved.

Virtual machine storage requirements

The amount of storage you need depends on the BIG-IP modules you want to use, and whether or not you intend to upgrade.

Note: These values apply to BIG-IP VE 13.1.0.2 and later.
Provisioned storage Supported modules Details
9 GB (LTM_1SLOT) Local Traffic Manager™ (LTM®) module only; no space for LTM upgrades. You can increase storage if you need to upgrade LTM or provision additional modules.
40 GB (LTM) LTM module only; space for installing LTM upgrades. You can increase storage if you decide to provision additional modules. You can also install another instance of LTM on a separate partition.
60 GB (ALL_1SLOT) All modules except Secure Web Gateway (SWG); no space for installing upgrades. The Application Acceleration Manager™ (AAM®) module requires 20 GB of additional storage dedicated to AAM. If you are not using AAM, you can remove the datastore disk before starting the VM.
82 GB (ALL) All modules except SWG and space for installing upgrades. The Application Acceleration Manager™ (AAM®) module requires 20 GB of additional storage dedicated to AAM. If you are not using AAM, you can remove the datastore disk before starting the VM.

For production environments, virtual disks should be deployed Thick (allocated up front). Thin deployments are acceptable for lab environments.

Note: To change the disk size after deploying the BIG-IP system, see Increase disk space for BIG-IP VE.

Virtual machine network interfaces

When you deploy BIG-IP® VE, a specific number of virtual network interfaces (vNICs) are available.

For Hyper-V, three virtual NICs are required, at a minimum. More NICs are required if the high availability option is configured.

Each virtual machine can have a maximum of 8 virtual NICs. If you have a legacy virtual NIC, you can use it for management access and still have 8 NICs for dataplane. (The legacy NIC is not supported for the dataplane.) For peak performance, F5® does not recommend using legacy NICs.