Bug ID 922297: TMM does not start when using more than 11 interfaces with more than 11 vCPUs

Last Modified: Nov 07, 2022

Bug Tracker

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

Known Affected Versions:
13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 13.1.3.3, 13.1.3.4, 13.1.3.5, 13.1.3.6, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.0.1, 14.0.1.1, 14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 14.1.2.7, 14.1.2.8, 14.1.3, 14.1.3.1, 14.1.4, 15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.4, 15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 16.0.0, 16.0.0.1, 16.0.1, 16.0.1.1

Fixed In:
16.1.0, 16.0.1.2, 15.1.3, 14.1.4.1, 13.1.4

Opened: Jun 30, 2020
Severity: 3-Major

Symptoms

TMM may not start when using more than 11 network interfaces with more than 11 vCPUs configured. You see the following log entries in /var/log/tmm: -- notice ixlv(1.1)[0:5.0]: Waiting for tmm10 to reach state 1... In the TMM log for that TMM, you can see that it is waiting for tmm0, e.g.: -- notice ixlv(1.10)[0:6.0]: Waiting for tmm0 to reach state 2...

Impact

TMM does not start.

Conditions

-- BIG-IP Virtual Edition (VE). -- More than 11 interfaces configured. -- More than 11 vCPUs configured.

Workaround

Configure fewer network interfaces or vCPUs.

Fix Information

Fixed a TMM startup deadloop stuck issue (when there are more than 10 interfaces and tmms/vCPUs).

Behavior Change