A configuration change is made on the standby member of a device group.

The BIG-IP system uses a centralized management framework to ensure that all devices within a Sync-Failover group share a consistent configuration. When an administrator makes a change on any member of the group—whether it is the active or the standby device—the system detects a " ConfigSync " mismatch. The " Device Management > > Overview " screen tracks these changes by comparing the commit ID and timestamps of the configurations across all peers.

If a change is made on the standby member, that device now possesses a more recent configuration than the other members of the group. Consequently, the BIG-IP GUI will display a status of " Changes Pending " and suggest a Recommended Action to resolve the discrepancy. In this scenario, the correct action is to Synchronize the standby member configuration to the group. This push operation will copy the updated configuration from the standby device to the active device (and any other peers), bringing the entire cluster back into a " In Sync " status. It is important to note that BIG-IP allows bi-directional synchronization; you do not have to be on the active device to push a configuration. However, administrators must be cautious: choosing Option C (Synchronizing the active member to the group) would overwrite the changes just made on the standby device with the older configuration from the active device, effectively reverting the changes. The Recommended Action always points toward the direction that propagates the most recent change to the rest of the group.