Best Practice for Sync Between Primary and Failover

I'm not quite sure I understand what you're trying to do.

 

By "synch", are you referring to configsync'ing or failover? Are you saying that once the new servers are added to the active BIG-IP, that you'd like to new configuration to get synched to the standby unit before doing something else? Please clarify.

 

 

Configsync is a "semi" blocking call, meaning that iControl will wait for as long as it can for configsync status before returning, but will cause an exception if the wait is longer than the webserver's response timeout. Configsync from the CLI/GUI is also a blocking call. Due to the nature of configuration synchronization, this process can't be non-blocking since we need to know that every aspect of configsync is successful or not synchronously, before something else that depends on the configuration is performed.

 

 

Loc