Note:

If you want to then switch back to the original admin console, you must recreate it as a replica administrative node, then fail over to it.

  1. Install the new replica administrative node.
  2. In the run.properties file, change the value for pa.operational.mode to CLUSTERED_CONSOLE_REPLICA.

    This property is case-sensitive.

  3. In the PingAccess admin console, edit the primary and replica host configuration and download the new replica node's bootstrap file:
    1. Click Settings and go to Clustering > Administrative Nodes.
    2. Change the Primary Administrative Node host name and port to the failed-over node.
    3. Remove the Replica Administrative Node public key, then change the Replica Administrative Node host name and port to point to the new replica node.
      Tip:

      If your key pair doesn't include a wildcard, you can use the same host name as the original console to avoid having to recreate the console key pair and the bootstrap.properties files for each engine.

    4. Click Save & Download to download the bootstrap file for the replica administrative node.
  4. Copy the downloaded file to the new replica administrative node's <PA_HOME>/conf directory and rename it to bootstrap.properties.
  5. Edit the <PA_HOME>/conf/run.properties file on the new replica administrative node and change the value of pa.operational.mode to CLUSTERED_CONSOLE_REPLICA.
  6. Start the new replica node.
  7. To verify that replication is complete, look for the message Configuration successfully synchronized with administrative node in the <PA_HOME>/log/pingaccess.log file.