A device group is made up of four members: LTM-A, LTM-B, LTM-C, and LTM-D. An LTM Specialist makes a configuration change on LTM-B. Later, a different
LTM Specialist notices a "changes pending" message on all devices. When logged into LTM-D, the LTM Specialist attempts to config-sync to the device group.
The sync operation fails.
Why is the LTM Specialist on LTM-D unable to synchronize the configuration to the group?
In a device group using F5 LTM (Local Traffic Manager), the sync operation is controlled by the device that has the latest changes, determined by the highest commit-id. Because the configuration change was made on LTM-B, it has the highest commit-id, making it the only device eligible to initiate a config-sync. Attempting to sync from other devices, like LTM-D, will fail because LTM-D does not have the latest configuration changes.
D - Correct commit ID updates to determine which device has the latest configuration and is eligible to synchronize its configuration to the group. https://my.f5.com/manage/s/article/K13946