Bug ID 431985: Monitor instance re-enable and incremental sync

Last Modified: Apr 10, 2019

Bug Tracker

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

Known Affected Versions:
11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4

Fixed In:
11.6.0, 11.5.1 HF5, 11.4.1 HF6

Opened: Sep 26, 2013
Severity: 3-Major
Related AskF5 Article:
K14639

Symptoms

Monitor instances for nodes and pool members are not re-enabled by an incremental sync. If you set a monitor to be user-down 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 on the receiving devices.

Impact

The effect is that the monitor status does not update on devices receiving a sync.

Conditions

This occurs only on devices receiving a sync after setting a monitor to user-down, syncing a configuration, enabling the monitor, and incrementally syncing the configuration.

Workaround

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 } }'.

Fix Information

Monitor instance is now correctly re-enabled, if it was previously user-down, on all devices after an incremental sync. In earlier versions it would only update properly on the source device of the sync.

Behavior Change