Bug ID 533658: DNS decision logging can trigger TMM crash

Last Modified: Apr 10, 2019

Bug Tracker

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

Known Affected Versions:
11.3.0, 11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.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.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.6.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

Fixed In:
12.0.0, 11.6.1, 11.5.4 HF2, 11.4.1 HF10

Opened: Jul 15, 2015
Severity: 2-Critical
Related AskF5 Article:
K05114001

Symptoms

Applying load balance decision logging to the DNS profile can cause TMM to crash when a query is load balanced to a last resort pool that is unavailable.

Impact

Traffic disrupted while tmm restarts.

Conditions

-- DNS logging is enabled and log profile set on the DNS profile. -- A Wide IP is configured with a last resort pool. -- The last resort pool is unavailable. -- A query is load balanced to the last resort pool.

Workaround

Disable decision logging for the DNS profile, or discontinue use of the last resort pool feature.

Fix Information

DNS decision logging no longer causse TMM to crash when a last resort pool is configured for a Wide IP, that last resort pool is unavailable, and a query is load balanced to that last resort pool.

Behavior Change