Bug ID 526699: TMM might crash if BIG-IP DNS iRule nodes_up references invalid IP/Port.

Last Modified: Jul 13, 2024

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

Known Affected Versions:
11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.5.1 HF1, 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.1 HF10, 11.5.1 HF11, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 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.3 HF2, 11.4.1 HF10

Opened: Jun 05, 2015

Severity: 3-Major

Related Article: K40555016

Symptoms

A BIG-IP DNS system configured with an iRule that makes use of the command nodes_up in its ip_address :: port version might lead to a crash.

Impact

Traffic disrupted while tmm restarts.

Conditions

- BIG-IP DNS iRule processing traffic with nodes_up IP/Port command. - IP/Port references an invalid LTM virtual server. - Client sends requests to the BIG-IP DNS wide IP.

Workaround

Specify correct IP/Port in the nodes_up iRule command

Fix Information

TMM no longer crashes when using an incorrect IP/Port in a nodes_up BIG-IP DNS iRule.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips