Configuration synchronization, Overview of configuration synchronization, Config-sync sender and receiver – Brocade Virtual ADX Administration Guide (Supporting ADX v03.1.00) User Manual
Page 133: Chapter 5

Brocade Virtual ADX Administration Guide
121
53-1003249-01
Chapter
5
Configuration Synchronization
Overview of configuration synchronization
The configuration synchronization (Config-Sync) functionality ensures that the configurations of the
two Brocade Virtual ADX devices deployed in a High Availability (HA) pair are in synchronization with
each other. This helps ensure a smooth transition in the event of an HA failover.
Configuration synchronization comprises of two operations:
•
Full synchronization—Performed once for initial synchronization between two Brocade Virtual
ADX devices.
•
Incremental synchronization—Utilized to maintain synchronization during subsequent
configuration changes after full synchronization.
Config-Sync sender and receiver
For the purpose of configuration synchronization, the Brocade Virtual ADX may be configured in the
sender mode or receiver mode. The synchronization operation is always initiated from the sender
device to the receiver device. The configuration changes made on the receiver device are never
synchronized to the sender device.
The Brocade Virtual ADX checks for compatibility between the sender and the receiver devices. If
the compatibility check fails between the two devices, then the system prints a warning message.
The console prompt of the Brocade Virtual ADX is automatically updated to reflect its configuration
synchronization mode. The prompt changes to hostname-sender for the sender device and to
hostname-receiver for the receiver device.
The following cautionary message is displayed when you enter the configuration synchronization
mode on the receiver device:
“Caution: The changes made on this configuration receiver device do not get
synchronized to the peer configuration sender device. You can configure only the
unique items such as hostname, interface IP, and sym-priority on this unit, and
use the peer configuration sender unit to specify the remaining non-unique
configuration. Changes made on this device will not be synchronized.”