Bug ID 533966: Double loopback nexthop release might cause TMM core.

Last Modified: Jul 18, 2026

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

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.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, 11.6.1, 11.6.1 hf1, 11.6.1 hf2, 11.6.2, 11.6.2 hf1, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3

Fixed In:
11.5.4

Opened: Jul 16, 2015

Severity: 3-Major

Symptoms

TMM might restart after logging an 'Assertion "nexthop ref valid" failed' message.

Impact

Traffic disrupted while tmm restarts.

Conditions

Traffic is sent from one tmm to a tunnel in another tmm, but the tunnel does not exist.

Workaround

None.

Fix Information

There is no longer a TMM crash due to an extra loopback nexthop release.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips