particularly if you are rebuilding the cluster. If in doubt, it is recommended that you
perform a complete backup of both nodes prior to initializing the cluster.
Several status messages and a progress meter will be displayed while the cluster is
initialized, which may take several minutes depending on the amount of data to be
replicated.
Once the initialization process completes, you will be returned to the High Availability
start page, where the cluster status will be displayed as:
The cluster is running normally.
Cluster deployment
After setting up a cluster, you must make appropriate configuration changes for your
network to take advantage of the cluster's fault tolerance.
The principal configuration change required is to replace the IP address of a single
Amigopod server with the virtual IP address of the cluster.
•
NAS devices and other RADIUS clients should be configured with the cluster IP
address.
•
Operators should use the cluster's IP address when provisioning guest accounts.
•
Configure NAS devices to redirect visitors to the cluster's IP address for web login
pages. Only the IP address in the redirection URL should be changed; the remainder of
the redirection URL should not be altered.
The network administrator should use the node IP addresses to perform system
administration tasks on each node, including managing the cluster itself.
Cluster maintenance
Use the Cluster Maintenance command link to access maintenance functions related to
the cluster.
The maintenance commands that are available on this page will depend on the current
state of the cluster as well as which node you are logged into.
NOTE
Some maintenance commands are only available on the secondary node. Other commands
may change the active state of the cluster. For this reason it is recommended that cluster
maintenance should only be performed by logging into a specific node in the cluster using
its IP address.
Recovering from a failure
From a cluster maintenance perspective, there are two kinds of failure:
•
A temporary outage is an event or condition that causes the cluster to fail-over to the
secondary node. Clearing the condition allows the cluster's primary node to resume
operations in essentially the same state as before the outage.
Amigopod |Technical Note
High Availability Deployment Guide
|15
Need help?
Do you have a question about the PowerConnect W Clearpass 100 Software and is the answer not in the manual?