Last Modified: Aug 19, 2026
Affected Product(s):
BIG-IP LTM
Known Affected Versions:
11.5.1, 11.5.1 hf1, 11.5.1 hf2, 11.5.1 hf3, 11.5.1 hf4, 11.5.1 hf5, 11.5.1 hf6, 11.5.1 hf7, 11.5.1 hf8, 11.5.1 hf9, 11.5.1 hf10, 11.5.1 hf11, 11.5.2, 11.5.2 hf1, 11.5.3, 11.5.3 hf1, 11.5.3 hf2, 11.5.4, 11.5.4 hf1, 11.5.4 hf2, 11.5.4 hf3, 11.5.4 hf4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10
Fixed In:
11.6.0
Opened: Jun 11, 2014 Severity: 3-Major Related Article:
K16230
Monitor instances for nodes and pool members are not re-enabled by an incremental sync. If you set a monitor to be disabled and then perform a sync, when you later set the monitor to enabled, a subsequent incremental sync does not update the monitor status to enabled.
The effect is that the monitor status does not update.
This occurs after disabling a monitor, syncing a configuration, enabling the monitor, and incrementally syncing the configuration.
You can work around this by forcing a full load sync from the active device. Either use 'Overwrite Configuration' on the Device Management Overview page, or the tmsh command 'modify cm device-group device_group_name> devices modify { current_device_name { set-sync-leader } }'.
Monitor instance is now correctly enabled or disabled after an incremental sync.