Bug ID 999901: Certain LTM policies may not execute correctly after a system reboot or TMM restart.

Last Modified: May 29, 2024

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

Known Affected Versions:
13.1.3,,,,,,, 13.1.4,, 13.1.5,, 14.0.0,,,,,, 14.0.1,, 14.1.0,,,,,, 14.1.2,,,,,,,,, 14.1.3,, 14.1.4,,,,,, 15.0.0, 15.0.1,,,,, 15.1.0,,,,,, 15.1.1, 15.1.2,, 15.1.3,, 15.1.4,, 15.1.5, 16.0.0,, 16.0.1,,, 16.1.0, 16.1.1, 16.1.2,

Fixed In:

Opened: Mar 05, 2021

Severity: 1-Blocking

Related Article: K68816502


After a system reboot or TMM restart, LTM policies referencing an external data-group may not execute correctly, regardless of a successful matching condition. This can cause a wide range of issues, including misrouted traffic, unshaped traffic, the bypassing of ASM, or complete traffic failure (based on the policy actions). Note that if a virtual server references multiple LTM policies, and only some of those policies reference an external data-group, all LTM policies attached to the virtual server will be affected.


LTM policies may be unable to execute the appropriate action on a successful matching condition, leading to a wide range of traffic-impacting consequences.


-- LTM policy with an external data-group configured on a virtual server. -- System reboot or TMM restart.


Remove and re-add the affected policy to the desired virtual-server. Alternatively, to fix a wider number of affected virtual servers in one go, reload the system configuration by executing 'tmsh load sys config'.

Fix Information

TMM now loads LTM policies with external data-groups as expected.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips