Last Modified: Nov 07, 2022
Affected Product:
See more info
BIG-IP MA-VE
Known Affected Versions:
11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.6.1, 11.6.1 HF1, 11.6.1 HF2, 11.6.2, 11.6.2 HF1, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3, 12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 12.1.5, 12.1.5.1, 12.1.5.2, 12.1.5.3, 12.1.6
Fixed In:
13.0.0
Opened: Jan 07, 2016
Severity: 3-Major
On Azure with 3.5GB 2vCPU configuration, only 1 tmm is started
Only allocating 1 tmm can cause under-utilized CPUs in VMs in public clouds when RAM is not multiple of 2GB/per CPU.
BIG-IP Virtual Edition in Public Clouds.
None.
The logic for determining number of CPUs to be used by BIGIP was changed to take into account different Cloud VE configurations like these: * 2 vCPU / 3.5 GB RAM * 4 vCPU / 7.0 GB RAM * 8 vCPU / 14.0 GB RAM Now BIG-IP will assume 1.5GB RAM/per CPU and better utilize above configuration using all available CPUs.
