Bug ID 714654: Creating static route for advertised dynamic route might result in dropping the tmrouted connection to TMM

Last Modified: Sep 11, 2019

Bug Tracker

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

Known Affected Versions:
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, 12.1.3.7, 12.1.4, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.1, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.0.1

Fixed In:
14.1.0, 13.1.1.2, 12.1.4.1

Opened: Apr 11, 2018
Severity: 3-Major

Symptoms

While creating a static route, tmrouted disconnects with error: existing entry is not a dynamic.

Impact

TMM's connection to tmrouted goes down, which results in loss of the dynamic route for TMM.

Conditions

Creating a static route for a network that already has an advertised dynamic route.

Workaround

There is no workaround other than not creating a static route for routes received through dynamic routing.

Fix Information

Creating static routes for advertised dynamic route no longer causes the tmrouted-to-TMM connection to drop.

Behavior Change