Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP All
Known Affected Versions:
10.2.4, 11.0.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, 11.5.1 HF1, 11.6.1 HF1, 11.5.1 HF2, 11.6.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 HF1, 11.6.2 HF1, 11.5.3 HF1, 11.5.3 HF2, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 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.2, 11.5.3, 11.6.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2
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 Article:
K17187
In a specific combination of events TMM may core.
Traffic disrupted while tmm restarts.
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.
Ensure correct routing to all destinations with reachable next hops.
TMM no longer cores when load balancing to a node's IP address in iRule, routed towards an unreachable nexthop.