Bug ID 1112537: LTM/GTM config instantiated in a certain way can cause a LTM/GTM monitor to fail to delete.

Last Modified: Dec 13, 2023

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

Known Affected Versions:
13.1.0,,,,,,,,, 13.1.1,,,,, 13.1.3,,,,,,, 13.1.4,, 13.1.5,, 14.1.0,,,,,, 14.1.2,,,,,,,,, 14.1.3,, 14.1.4,,,,,,, 14.1.5,,,,,, 15.1.0,,,,,, 15.1.1, 15.1.2,, 15.1.3,, 15.1.4,, 15.1.5,, 15.1.6,, 15.1.7, 15.1.8,,, 15.1.9,, 16.1.0, 16.1.1, 16.1.2,,, 16.1.3,,,,,, 17.0.0,,

Fixed In:
17.1.1, 16.1.4, 15.1.10

Opened: Jun 07, 2022

Severity: 3-Major


Upon attempting to delete a LTM or GTM monitor, the system returns an error similar to the following example, even though the monitor being deleted is no longer in use anywhere: 01070083:3: Monitor /Common/my-tcp is in use.


LTM or GTM monitor no longer in use anywhere cannot be deleted from the configuration.


-- The configuration was loaded from file (for example, as restoring a UCS archive would do). -- A BIG-IP Administrator deletes all objects using the monitor, and then attempts to delete the monitor itself.


Run one of the following sets of commands (depending on the affected module) and then try to delete the monitor again: tmsh save sys config tmsh load sys config tmsh save sys config gtm-only tmsh load sys config gtm-only

Fix Information

Unused monitors can now be deleted correctly.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips