Last Modified: Jul 18, 2026
Affected Product(s):
BIG-IP GTM
Known Affected Versions:
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.5.3 hf2, 11.5.4, 11.5.4 hf1, 11.5.4 hf2, 11.5.4 hf3, 11.5.4 hf4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 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
Opened: Jun 05, 2015 Severity: 3-Major Related Article:
K40555016
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.
Traffic disrupted while tmm restarts.
- 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.
Specify correct IP/Port in the nodes_up iRule command
TMM no longer crashes when using an incorrect IP/Port in a nodes_up BIG-IP DNS iRule.