Bug ID 751021: One or more TMM instances may be left without dynamic routes.

Last Modified: Oct 16, 2023

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

Known Affected Versions:
11.5.0, 11.5.1, 11.5.2, 11.5.3, 11.5.4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 11.6.0, 11.6.1, 11.6.2, 11.6.3,,,,, 11.6.4, 11.6.5,,,, 12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2, 12.1.0, 12.1.1, 12.1.2, 12.1.3,,,,,,,, 12.1.4,, 12.1.5,,,, 12.1.6, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0,,,,,,,,, 13.1.1,,,,, 13.1.3,,,,, 14.0.0,,,,,, 14.0.1,, 14.1.0,,,,,, 14.1.2,,,,,,,,, 14.1.3,, 15.0.0, 15.0.1,,,,

Fixed In:
15.1.0, 14.1.4,

Opened: Nov 26, 2018

Severity: 3-Major


Inspecting the BIG-IP's routing table (for instance, using tmsh or ZebOS commands) shows that dynamic routes have been learnt correctly and should be in effect. However, while passing traffic through the system, you experience intermittent failures. Further investigation reveals that the failures are limited to one or more TMM instances (all other TMM instances are processing traffic correctly). The situation does not self-recover and the system remains in this state indefinitely. An example of a traffic failure can be a client connection reset with cause 'No route to host'. If the client retries the same request, and this hits a different TMM instance, the request might succeed.


Traffic fails intermittently, with errors that point to lack of routes to certain destinations.


This issue is known to occur when all of the following conditions are met: - The system is a multi-blade VIPRION or vCMP cluster. - The system just underwent an event such as a software upgrade, a reboot of one or more blades, a restart of the services on one or more blades, etc.


You can try to temporarily resolve the issue by restarting the tmrouted daemon on all blades. To do so, run the following command: # clsh "bigstart restart tmrouted" However, there is no strict guarantee this will resolve the issue, given the nature of the issue. Alternatively, you could temporarily replace the dynamic routes with static routes.

Fix Information

All TMM instances across all blades now properly learn dynamic routes.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips