Configuration Synchronization across BIG IPs

Ciao Krodriç, Sync-only HA groups do not sync traffic objects (such as VIPs, pools, etc.), only non traffic objects. This behavior is by design.

Given the diagram, I'm assuming BIG-IP-C is some kind of Disaster Recovery node.

Have you considered how you're going to move user connections from the existing cluster to BIG-IP-C when it's going Active? 

How about active sessions & persistency tabls - do you have any session mirroring currently in place on A and B? 

Finally, do you see any impacts in including it into the existing HA Group? This would be the easiest way in my opinion, and it also helps you with easier management of the two points above (if you have applicatns that require it). 

Otherwise, you would need to perform this task manually. In my opinion the best way to work with configuration files is creating .scf or .ucs archives on the BIG-IP device and use it to import the full configuration on the peer node (like you would do with a RMA unit).

Hop this helps,

CA