Bug ID 437739: Only the first 12 tmms are monitored to detect looping.

Last Modified: Sep 13, 2023

Affected Product(s):
BIG-IP LTM(all modules)

Known Affected Versions:
11.0.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.5.1 HF1, 11.6.1 HF1, 11.5.1 HF2, 11.6.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.1 HF10, 11.5.1 HF11, 11.5.2 HF1, 11.6.2 HF1, 11.5.3 HF1, 11.5.3 HF2, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.1.0, 11.2.0, 11.2.1, 11.3.0, 11.4.0, 11.4.1

Fixed In:
11.5.0, 11.4.1 HF2, 11.4.0 HF6, 11.3.0 HF9, 11.2.1 HF10

Opened: Nov 13, 2013

Severity: 1-Blocking

Related Article: K14859


If a BIGIP has more than 12 tmms and one of the tmms above the 12th one loops due to a bug, it will loop indefinitely.


Traffic will no longer be accepted on that tmm that is looping indefinitely.


Another bug that causes a tmm to loop and it has to be a tmm greater than the 12th tmm.


Manually change /defaults/daemon.conf to have the correct stanzas for the remaining tmms. This change must be performed across every blade in the chassis. After performing the edit, load the changes into the running configuration via "tmsh load sys config partitions all", and then verify that sod is now correctly monitoring TMMs above tmm12, via a command such as: tmsh show sys ha-status all-properties | grep "daemon-heartbeat" | grep tmm

Fix Information

TMOS now monitors all tmms for looping/locked on systems with more than 12 tmms.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips