Recovering From A Temporary Outage; Recovering From A Hardware Failure - Aruba Networks PowerConnect W Clearpass 100 Software Deployment Manual

•
A hardware failure is a fault that to correct requires rebuilding or replacing one of
the nodes of the cluster.
The table below lists some system failure modes and the corresponding cluster
maintenance that is required.
Failure Mode
Software failure – system crash, reboot or hardware reset
Power failure
Network failure – cables or switching equipment
Network failure – appliance network interface
Hardware failure – other internal appliance hardware
Data loss or corruption

Recovering from a temporary outage

Use this procedure to repair the cluster and return to a normal operating state:
1. This procedure assumes that the primary node has experienced a temporary outage,
and the cluster has failed over to the secondary node.
2. Ensure that the primary node and the secondary node are both online.
3. Log into the secondary node. (Due to fail-over, this node will be assigned the cluster's
virtual IP address.)
4. Click Cluster Maintenance, and then click the Recover Cluster command link.
5. A progress meter is displayed while the cluster is recovered.
NOTE
The cluster's virtual IP address will be temporarily unavailable while the recovery takes
place.
6. Recovery is complete. The secondary node is now the new primary node for the
cluster. The cluster is back in a fault-tolerant mode of operation.
The Recover Cluster command will only work if the node that failed is brought back online
with the same cluster configuration. This is normally the case in all temporary outages. If
this is not the case, use the procedure described in section 0 to recover the cluster.
To return the primary node back to its original status as the primary node in the cluster,
you can use the Swap Primary Servers command described in section 0.

Recovering from a hardware failure

If the failed node has been replaced, the cluster configuration will no longer be present on
that node. To recover the cluster, first ensure that the replaced node is ready to rejoin the
cluster, then destroy the cluster and recreate it.
Use the following procedure to rebuild the cluster:
16| High Availability Deployment Guide
Maintenance
Temporary outage
Temporary outage
Temporary outage
Hardware failure
Hardware failure
Hardware failure
Amigopod |Technical Note