Bug ID 694656: Routing changes may cause TMM to restart

Last Modified: May 14, 2019

Bug Tracker

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

Known Affected Versions:
11.4.1, 12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5

Fixed In:
14.0.0, 13.1.0.6, 12.1.3.7

Opened: Nov 15, 2017
Severity: 2-Critical
Related AskF5 Article:
K05186205

Symptoms

When routing changes are made while traffic is passing through the BIG-IP system, TMM might restart. This isn't a general issue, but can occur when other functionality is in use (such as Firewall NAT).

Impact

TMM restarts, resulting in a failover and/or traffic outage.

Conditions

-- Routing changes occurring while BIG-IP is active and passing traffic. -- Dynamic routing, due to its nature, is likely increase the potential for the issue to occur. -- Usage of Firewall NAT functionality is one specific case known to contribute to the issue (there may be others).

Workaround

If dynamic routing is not in use, avoiding static route changes may avoid the issue. If dynamic routing is in use, there is no workaround.

Fix Information

TMM now properly manages routing information for active connections.

Behavior Change