Primary Node Failure; Secondary Node Failure - Aruba Networks PowerConnect W Clearpass 100 Software Deployment Manual

SNMP server settings ( See

The set of currently installed plugins ( See

Web Login pages ( See

Certain configuration items are not replicated. These are:
HTTP Proxy settings (

Network interface configuration (

chapter)
RADIUS dictionary entries ( See

SSL certificate settings ( See

Subscription IDs in Plugin Manager ( See

System hostname ( See


Primary Node Failure

If the cluster's primary node fails, the cluster status will be displayed on the secondary node as:
The secondary node is running, but the primary node is down or stopped.
While the primary node is down, the cluster is in a failed state and cannot deliver network services. If the
primary node recovers within the downtime threshold, the cluster will automatically return to the normal
state and network service will be restored.
An automatic failover will be initiated after the primary node has been offline for the downtime threshold,
which is 30 seconds by default.
Once failover has occurred, the cluster status will be displayed on the secondary node as:
The secondary node has taken over the cluster services because the primary node is down.
In the failover state, the secondary node will assume control of the cluster and will take over the cluster's IP
address. This will restore network service for clients of the cluster. Replication will stop as there is no
longer a primary node.
While the primary node is offline, the cluster will no longer be fault-tolerant. A subsequent failure of the
secondary node will leave the cluster inoperable.
See "Recovering From a Temporary Outage"
this state.
The secondary node has taken over the cluster services. The primary node is back online, but the
cluster needs to be recovered.
In this state, the primary node was offline for a period of time greater than the downtime threshold, and
then recovered. The cluster has failed over to the secondary node.
In this state, the cluster is not fault-tolerant. A subsequent failure of the secondary node will leave the
cluster inoperable.
Recovering the cluster is required for replication to resume and return the cluster to a fault-tolerant state.
See "Recovering From a Temporary Outage"
state.

Secondary Node Failure

If the cluster's secondary node fails, the cluster status will be displayed on the primary node as:
The primary node is running, but the secondary node is down or stopped.
ClearPass Guest 3.9 | Deployment Guide
"SNMP Configuration"
"Plugin Manager"
"Web Logins" in the RADIUS Services chapter)
"HTTP Proxy Configuration"
"Viewing Network Interface Settings"
"Dictionary" in the RADIUS Services chapter)
"SSL Certificate" in the Administrator Tasks chapter)
"Managing Subscriptions"
"Viewing or Setting System Hostname"
in this chapter for instructions on recovering a cluster in this
in the Administrator Tasks chapter)
in the Administrator Tasks chapter)
in the Administrator Tasks chapter)
in the Administrator Tasks chapter)
in the Administrator Tasks chapter)
in this chapter for instructions on recovering a cluster in
in the Administrator Tasks
High Availability Services | 429