TMS zl Management and Configuration Guide ST.1.1.100430

8-12
High Availability
Configuring High Availability
Figure 8-3. System > Settings > High Availability on the Cluster Master
Whenever you make configuration changes to the master, you should synchro-
nize those changes to the participant. To remind you to complete this task,
you will be prompted to synchronize configuration changes each time you:
■ Click Save in the master’s Web browser interface
■ Enter write memory in the master’s CLI
Note that clicking Save or entering write memory indicates that the master’s
startup-config has been changed. If you then synchronize the master’s startup-
config with the participant’s, the participant will be automatically rebooted.
Because changing the master’s configuration and synchronizing those
changes to the participant force a reboot on the participant, you should
consider making all of your configuration changes before synchronizing the
cluster. You should also save the master’s configuration only if it has changed
because this action indicates the configuration has been changed and will
necessitate a reboot on the participant if you synchronize changes.
Note The Rebalance Now button will be available in a future version.
Verify Synchronization
After you have finalized your HA configuration and synchronized the cluster,
you can verify the synchronization and ensure that the participant is prepared
to act as the master in case the master fails. You can do this by comparing the
connections on the master and on the participant; connections that will fail
over from the master to the participant can be seen from the participant’s CLI.
(See Table 8-1, “Synchronization and Failover in HA Clusters,” on page 6 for
a list of these connections.)