Bug ID 600570: VE License may enforce improper TMM count

Last Modified: Apr 10, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP VE(all modules)

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, 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, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1

Fixed In:
13.1.0

Opened: Jun 21, 2016
Severity: 3-Major

Symptoms

If a BIG-IP VE license enforces a number of TMM instances less than the system would otherwise run, and that license limit is not a power of two (e.g. 1, 2, 4, 8, 16), the BIG-IP system will incorrectly start with a non-power of two number of TMMs.

Impact

This results in traffic disruption and connection failures where traffic leaves one TMM, but returns and is not processed by a different TMM.

Conditions

Certain license combinations can result in the BIG-IP VE system starting with a non power of two number of TMMs.

Workaround

Set the "provision.tmmcount" DB key to the next lower power of two (1, 2, 4, 8, 16) from the count listed in the license.

Fix Information

None

Behavior Change