Configuration synchronization allows you to designate a master vRouter that can synchronize defined portions of the configuration with a remote standby system. The master system dispatches locally generated configuration commands (set, delete, commit, and so on) to the remote standby system; the commands are dispatched from the master system when the configuration change is committed.

The master system uses the REST API of the vRouter to propagate commands to the remote systems; for this reason, the remote system must have HTTPS enabled to participate.

When setting up the master and standby systems on the network, keep in mind that the vRouter does not prevent you from setting up mis-synchronization scenarios that can result in network problems. Take care to avoid scenarios that cause network problems. For example:

• Configuration information that is unique to a system should not be synchronized between systems because synchronizing this information can cause problems on the network. Examples of configuration that should be excluded from synchronization include interface, IP addresses, and VRRP priorities.
• Avoid setting up two master systems to synchronize each other.
• Avoid setting up two master systems so that both synchronize the same configuration on a third system.

Note that some configuration items are not allowed to be synchronized because synchronizing them would damage your system configuration. The two items that cannot be synchronized are the system config-sync configuration node itself and the service https configuration node. Disallowed configuration items do not appear in the configuration tree when excluded items are listed.

Note also that only one sync-map can be defined for the standby system.

Finally, avoid direct modification of the configuration on the standby system in areas contained in the sync-map as this may result in conflicts and commit failures during the synchronization process.