Bug ID 2172069: GTM topology regions updates do not take effect within tmm

Last Modified: Dec 19, 2025

Affected Product(s):
BIG-IP DNS, GTM(all modules)

Known Affected Versions:
17.1.3, 17.5.1.3

Opened: Dec 03, 2025

Severity: 3-Major

Symptoms

GTM topology regions updates do not take effect within tmm

Impact

GTM not answering with latest GTM topology region updates.

Conditions

Modifications made to gtm topology regions do not take effect when only one client is sending queries. Note that this issue is tmm-thread specific, meaning one or more tmm threads can get into this state, as long as DNS queries keep hitting the same tmm thread(s), coming from the same source IP address(es) This is a very unlikely scenario in most production environments, and is likely to only be seen during lab testing with client traffic from one or few IP addresses.

Workaround

Restart tmm, or perform the DNS lookup from a different client IP address (not the same address that the affected tmm thread previously processed a topology-based DNS query from)

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips