Bug ID 525958: TMM may crash if loadbalancing to node's IP in iRule routed towards an unreachable nexthop.

Last Modified: Apr 10, 2019

Bug Tracker

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

Known Affected Versions:
10.2.4, 11.0.0, 11.1.0, 11.2.0, 11.2.1, 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.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, 11.4.1 HF10, 11.2.1 HF16, 10.2.4 HF13

Opened: Jun 01, 2015
Severity: 3-Major
Related AskF5 Article:
K17187

Symptoms

In a specific combination of events TMM may core.

Impact

Traffic disrupted while tmm restarts.

Conditions

This occurs when the following conditions are met: - Load balancing a flow to an ip_tuple (e.g., the Tcl 'node' command). - That address is not directly connected. - The matched route is a gateway pool that contains a pool member that is not reachable.

Workaround

Ensure correct routing to all destinations with reachable next hops.

Fix Information

TMM no longer cores when load balancing to a node's IP address in iRule, routed towards an unreachable nexthop.

Behavior Change