Bug ID 1046917: In-TMM monitors do not work after TMM crashes

Last Modified: Feb 07, 2024

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

Known Affected Versions:
14.1.4,,,,,,, 14.1.5,,,,,, 15.0.0, 15.0.1,,,,, 15.1.0,,,,,, 15.1.1, 15.1.2,, 15.1.3,, 15.1.4,, 15.1.5,, 15.1.6,, 15.1.7, 16.0.0,, 16.0.1,,, 16.1.0, 16.1.1, 16.1.2,,, 16.1.3,,,,,, 17.0.0,,

Fixed In:
17.1.0, 16.1.4, 15.1.8

Opened: Sep 15, 2021

Severity: 3-Major


After TMM crashes and restarts, in-TMM monitors do not run. Monitored pool members are down.


Monitored pool members are offline.


-- In-TMM monitors are enabled. -- TMM exits abnormally, as a result of one of the following: + TMM crashing and restarting + TMM being sent a termination signal (i.e. using 'pkill' to kill TMM) Note: This issue does not occur if TMM is restarted using 'bigstart' or 'tmsh sys service'.


One of the following: 1. Do not use in-TMM monitors. 2. After TMM restarts, manually restart bigd: tmsh restart sys service bigd 3. Add an entry to /config/user_alert.conf such as the following, so that the system restarts bigd when TMM starts up. On an appliance or single-slot vCMP guest/tenant: alert id1046917 "Tmm ready - links up." { exec command="bigstart restart bigd" } On a VIPRION or multi-slot vCMP guest/tenant: alert id1046917 "Tmm ready - links up." { exec command="clsh --color=all bigstart restart bigd" } Note: This change must be made separately on each device in a ConfigSync device group.

Fix Information


Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips