HA Server roles and states

The role of a server in a HA Pair will differ and depending on the state of the server will determine the HA commands that can be executed on the server.

HA servers can be in one of the following server roles and states:

Server role	Server state	Description
Primary PAM Server	Active	HA BAU A PAM Server becomes the Primary PAM Server when HA has been initialised. In BAU, the active server is where all the configuration is done, the server that will receive all user traffic, and replicate to the standby Secondary PAM Server.
	Demoted	Only a Primary PAM Server can be demoted. An active Primary server may need to be demoted in a HA Split Brain Scenario.
Secondary PAM Server	Standby	HA BAU A PAM Server becomes a standby Secondary PAM Server when HA is initialised on an Active Standalone PAM Server and it's joining code is entered to establish the HA Pair. In BAU, the standby server will receive information from the Active Primary server. The data replicated will allow it to take over operations if the Primary server should fail. Access is available to the Management Interface to allow HA commands to be run.
	Promoted Active	A standby Secondary server will be promoted to an active Secondary Server when you failover from an active Primary. The Promoted active Secondary server will take over operations and will receive all user connections.
Standalone PAM Server	Active	A server that has NOT been configured as a HA Pair will just be a standalone PAM Server. Two standalone servers are required to create a HA Pair and in BAU they should be setup with the following installation type: - Primary PAM Server: The server that will become the primary server should be installed as a Standalone (or HA Primary) installation type - Secondary PAM Server: The server that will become the standby server should be installed as a HA Secondary (or replacement Primary) installation type which displays a joining code See HA Pair installation process for more detail.