Last Modified: May 14, 2019
See more info
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, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124
14.0.0, 126.96.36.199, 188.8.131.52
Opened: Nov 15, 2017
Related AskF5 Article: K05186205
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).
TMM restarts, resulting in a failover and/or traffic outage.
-- 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).
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.
TMM now properly manages routing information for active connections.