Bug ID 778517: Large number of in-TMM monitors results in delayed processing

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, 13.1.3, 13.1.3.1, 13.1.3.2, 13.1.3.3, 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, 15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.4

Fixed In:
15.1.0, 14.1.2.7, 13.1.3.4

Opened: May 01, 2019
Severity: 3-Major
Related AskF5 Article:
K91052217

Symptoms

A monitor may continue to probe for a while after it has been removed from pool / member / node. Duplicate monitor instances may get created after associating a monitor to a server.

Impact

-- Monitor target may appear down when responding correctly. -- Monitor may continue to run after removed from pool / member / node. -- Increased monitoring load on server.

Conditions

Device has a large number of in-TMM monitors.

Workaround

Disable in-tmm monitors: tmsh modify sys db bigd.tmm value disable

Fix Information

Large numbers of in-TMM monitors are processed in a timely fashion.

Behavior Change