Configuration synchronization between the ha pairs, Error handling, Enabling configuration synchronization – Brocade Virtual ADX Administration Guide (Supporting ADX v03.1.00) User Manual
Page 136

124
Brocade Virtual ADX Administration Guide
53-1003249-01
Enabling configuration synchronization
5
•
”Full sync from hostname to hostname failed.”
•
”Incremental update from hostname to hostname started.”
•
”Incremental update from hostname to hostname done.”
•
”Incremental update from hostname to hostname failed.”
Configuration synchronization between the HA pairs
The config-sync sender mode is tightly bound to the Brocade Virtual ADX that maintains the VIP
ownership. If upon HA failover, the VIP ownership switches over to the peer device, then the peer
device is automatically promoted to the config-sync sender state. Due to this enhanced behavior,
the administrator can continue to make configuration updates on the current master device
without worrying about losing the updates post HA failover.
HA has the Hot-standby HA mode. The config-sync sender mode is tied to the hot (active) device,
and the standby device is designated as config-sync receiver. Upon HA failover, the config-sync
modes are reversed dynamically, and the new active device assumes config-sync sender mode. You
encounter an error if you try to configure a standby device as the sender device or the active device
as the receiver device.
NOTE
The close association between the config-sync sender device and the HA device, the administrator
manages the bulk of the configuration of the two devices using a single IP that is shared between
the two devices. For example, the ownership of a shared source-NAT IP is maintained by the current
master HA device. Hence, management requests on this IP address arrive on the current master
device.
NOTE
In a rare event where both devices in an HA pair are in standby mode due to the remain-standby
command, both devices remain in config-sync receiver mode.
Error handling
If the synchronization operation fails, you can troubleshoot the failures by reviewing the
combination of error messages logged on the system console and the syslog server.
If the failure is due to unavailability of any resource, or due to other dependencies, you must
manually resolve these dependencies, and manually issue the commands that failed on the
receiver device. All the error messages are captured and logged in the syslog for the receiver
device.
Enabling configuration synchronization
1. Define the sender and receiver configuration synchronization modes, on the two Brocade
Virtual ADX devices.
Virtual ADX(config)# config-sync mode sender
Syntax: config-sync mode sender
Virtual ADX(config)# config-sync mode receiver