Symantec Security 5600 Series, Security 5400 Series,Clientless VPN 4400 Series, Administration Manual

Page: 540 / 861

539 High availability and load balancing using clusters
Troubleshooting cluster configuration problems
Migrating a cluster configuration from a two member to three member cluster
You can restore a configuration from a two member cluster to three member cluster. The first step is to
backup the two-member cluster configuration using a backup password and restore the three member
cluster using the restore option in the System Setup Wizard.
Once you define the cluster configuration, you can add as many members to the new cluster that you
want. The first cluster member that you log on to has the restore image. This cluster member is used to
deploy the desired configuration to the other cluster members.
You can create a cluster in one of two ways:
■
Set up all cluster members, restore the image on the last member, and add all members to the
cluster.
■
Create a single cluster member using the backup image, set up all members, then go to the first
machine you set up and add all members using Tools > Cluster > Modify Cluster menu.
Related information
For further information related to this topic, see the following:
■
“Backing up and restoring cluster configurations” on page 534
Troubleshooting cluster configuration problems
You may encounter problems with cluster configuration at the following points:
At the beginning of the
configuration An error at the beginning of the configuration indicates problems with the cluster
member that is deploying the configuration, which is the first cluster member you
logged on to.
See “Errors on the cluster member that propagates the configuration” on page 540.
When you add a cluster
member An error that occurs when you add a cluster member indicates a problem qualifying the
remote security gateway as a cluster member.
See “Errors when adding a cluster member” on page 540.
When you complete the
cluster configuration Problems that occur when you complete the cluster configuration are usually due to
network interruptions. Because clustering depends upon communication between
cluster members, any interruption to network connectivity can cause all or part of the
cluster configuration to fail. For example, a cluster member who qualifies at the time you
add it, may not be able to join the cluster if a network interruption coincides with the
final step of cluster creation.
The Task/Status table at the bottom of the Clusters > Cluster Member Settings window
helps you identify these problems:
■
A red check in the left column warns you that a task has failed.
■
The Task column tells you where the failure occurred (the cluster member
experiencing the problem.)
■
The Status column indicates the kind of failure (for example, could not connect).
At any point during
configuration Security gateways do not meet the prerequisites to be a cluster member.
See “Cluster prerequisites” on page 511.