TMS zl Management and Configuration Guide ST.1.1.100430

8-11
High Availability
Configuring High Availability
6. Under Cluster Information, assign the device to a cluster by selecting a
Cluster ID from the list. Both members must have the same cluster ID, and
each cluster must use a unique ID number.
7. For Multicast IP, accept the default multicast IP address (224.0.0.18 for the
HA data protocol) or, if you are already using this address on your network
for VRRP, type a new multicast IP address. Both members must have the
same multicast IP address.
8. For Device ID (under Device Information), select a number to identify the
module within the cluster. Each member must have a unique device ID.
9. For Device Priority, assign the device a priority, 1-255, in the cluster.
Remember, however, that the boot order determines which module
becomes the master.
10. Click Apply My Changes.
11. Click Save. You will be warned that HA will not be enabled until the
module is rebooted.
12. Click OK.
13. Click System > Maintenance and click the Reboot tab. Click the Reboot
button and click Save & reboot at the prompt.
Again, you should be careful about the order in which modules are
configured for HA and booted. The first module that boots with an HA
configuration becomes the master of the cluster. You may consider wait-
ing for the master to reboot before configuring the other module in the
cluster. See “Configuration and Boot Order for HA Members” on page 8-4
for more information.
14. Repeat these steps to configure HA on the intended participant.
Managing the HA Cluster
After you configure the HA cluster, access the master’s Web browser interface
to begin managing the cluster. You should first configure the settings you want
on the master, save these changes on the master, and then synchronize the
master’s startup-config with the participant’s startup-config. To synchronize
configurations, complete the following steps:
1. Click System > Settings > High Availability.
2. Click Sync Configuration Now to propagate the configuration you saved on
the master to the participant. After the changes are synchronized, the
participant will be automatically rebooted.