Bug ID 1017513: Config sync fails with error Invalid monitor rule instance identifier or monitors are in a bad state such as checking

Last Modified: Nov 07, 2022

Bug Tracker

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

Known Affected Versions:
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.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 13.1.3.3, 13.1.3.4, 13.1.3.5, 13.1.3.6, 13.1.4, 13.1.4.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, 14.0.1.1, 14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 14.1.2.7, 14.1.2.8, 14.1.3, 14.1.3.1, 14.1.4, 14.1.4.1, 14.1.4.2, 14.1.4.3, 14.1.4.4, 15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.4, 15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 15.1.4, 15.1.4.1, 15.1.5, 16.0.0, 16.0.0.1, 16.0.1, 16.0.1.1, 16.0.1.2, 16.1.0, 16.1.1, 16.1.2

Fixed In:
17.0.0, 16.1.2.1, 15.1.5.1, 14.1.4.5, 13.1.5

Opened: May 11, 2021
Severity: 3-Major

Symptoms

If you remove or attach a different monitor to an fqdn pool, then perform a full config-sync, an error occurs: Load failed from /Common/bigip1 01070712:3: Caught configuration exception (0), Invalid monitor rule instance identifier: 58. This error can occur on FQDN nodes or regular nodes. It's the use of fqdn nodes that allows this issue to occur.

Impact

You might experience the following: -- Sync to the peer devices fails. -- Monitors may be stuck in an unexpected state such as down (even with a good reply) or checking even though an up or down response is received.

Conditions

-- BIG-IP device is configured with fqdn nodes/pools with monitors. -- Modify an fqdn pool to remove or attach a different monitor. -- Run the command: run cm config-sync to-group Failover -- Perform a full config-sync.

Workaround

Use incremental-sync. If incremental sync fails to correct the issue it can sometimes be recovered by running the following command: bigstart restart mcpd Note: Traffic disrupted while the system restarts.

Fix Information

None

Behavior Change