Last Modified: Jun 24, 2022
Known Affected Versions:
18.104.22.168, 22.214.171.124, 13.1.1, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168
15.0.0, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206
Opened: May 01, 2018 Severity: 3-Major
An incremental-sync from a modified-node that was set to 'user-down' causes the target-node on the target-device to have only a single monitor instance, rather than the several monitor instances that were present on the from-node. During the incremental sync, the system issues several messages similar to the following: err mcpd: 01070712:3: Caught configuration exception (0), Invalid monitor rule instance identifier: 24913.
After incremental-sync, a single monitor instance exists for the node on a 'backup' unit in an high availability (HA) configuration, rather than the several monitor instances that exist for that node on the 'active' unit; and that node session is 'enabled' (where the 'from-node' was 'disabled); and that node status may be 'up' (where the 'from-node' was 'user-down'), and later transition to 'down' from a monitor-fail. Thus, after incremental-sync, the target-node may then be 'down', while the active unit in the high availability (HA) configuration continues to function as expected.
-- In high availability (HA) configurations. -- A node is modified, and then manually set to 'user-down'. -- That node has more than one associated monitor. -- An incremental-sync occurs to the paired device.
There are several workarounds: -- Perform a 'full-sync' (rather than an 'incremental-sync'). -- Ensure the node is 'user-up' (not 'user-down') before the incremental-sync. -- Perform 'tmsh load sys config' on the target unit. In this case, the 'Invalid monitor rule instance identifier' messages will be seen, but the configuration will successfully load, and the target-unit will run correctly with the expected configuration.
An incremental-sync from a modified-node that was set to 'user-down' successfully replicates the several monitor instances on that node to the target-node on the backup device in an high availability (HA) configuration.