Bug ID 753594: In-TMM monitors may have duplicate instances or stop monitoring

Last Modified: Nov 07, 2022

Bug Tracker

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

Known Affected Versions:
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, 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

Fixed In:
15.0.0, 14.1.3.1, 13.1.3

Opened: Dec 19, 2018
Severity: 3-Major

Symptoms

Most monitored resources (such as pools) report messages similar to the following: Availability : unknown Reason : The children pool member(s) either don't have service checking enabled, or service check results are not available yet. A fraction of the monitored resources report the correct status based on the state of the resource. Enabling bigdlog may show instances of messaging containing 'tmm_mid=x:0' (where x can be values like 0, 1, 2 etc.), for example, it is tmm_mid=1:0 in the following example: [0][11288] 2019-03-08 10:03:04.608: ID 10859 :(_do_ping): post ping, status=UNKNOWN [ tmm?=true td=true tr=false tmm_mid=1:0 addr=::ffff:1.2.37.44:443 mon=/Common/https fd=-1 pend=0 #conn=0 up_intvl=5 dn_intvl=5 timeout=16 time_until_up=0 immed=0 next_ping=[1552068189.684126][2019-03-08 10:03:09] last_ping=[1552068184.684909][2019-03-08 10:03:04] deadline=[1552067610.048558][2019-03-08 09:53:30] on_service_list=True snd_cnt=119 rcv_cnt=0 ] The following error might appear in /var/log/ltm: -- failed to handle TMA_MSG_DELETE message: MID 0, error TMA_ERR_INVALID_MID(Monitor ID is invalid or unused)

Impact

Some monitors may be executed multiple times per configured interval on a resource, and some monitors may not be executed at all against resources.

Conditions

-- Configure In-TMM monitoring with a sufficiently large number of monitored objects. -- Modify monitors while pool members are in an offline state or perform rapid modification of In-TMM monitors.

Workaround

Switch to traditional bigd monitoring instead of In-TMM: tmsh modify sys db bigd.tmm value disable

Fix Information

Rapid modification of in-TMM monitors no longer leaves old monitor instances behind.

Behavior Change