Rejoining isolated read-write master back to cluster

The master server, which was isolated from Multi-Master cluster, and configured as read-write master, can rejoin the cluster when connectivity/network issues are resolved. The data from isolated read-write master is merged to the primary database of the cluster during rejoin process.

Before you begin

Before you rejoin isolated read-write master to the cluster, review the considerations and restrictions that are listed in the Requirements and considerations for multi-master configuration topic.

About this task

The rejoining operation checks for possible conflicts between the data of isolated read-write master and primary master of the cluster. A conflict report is generated to show the conflicts, if any. The isolated read-write master can rejoin the cluster only after all conflicts are resolved. For more information about how to view and resolve the conflicts, see Viewing conflicts report.

Procedure

  1. Go to the appropriate page.
    Graphical user interface
    1. Log on to the graphical user interface of isolated master.
    2. Click the Join back this master to Multi-Master cluster link in the notification area on the IBM Security Key Lifecycle Manager welcome page.
    3. On the Confirm dialog, read the confirmation message before you rejoin master to the cluster.
    4. Click OK to start the rejoin process.
    REST interface
    1. Open a REST client.
    2. Obtain a unique user authentication identifier to access IBM Security Key Lifecycle Manager REST services. For more information about the authentication process, see Authentication process for REST services.
    3. To run Join Back Cluster REST Service, send the HTTP GET request. Pass the user authentication identifier that you obtained in Step b along with the request message as shown in the following example.
      GET https://localhost:<port>/SKLM/rest/v1/ckms/config/nodes/joinBackTheCluster
      Content-Type: application/json
      Accept : application/json
      Authorization: SKLMAuth userAuthId=139aeh34567m
      Accept-Language : en
  2. If any conflicts arise during the rejoin process, the Conflicts with MM Cluster window is displayed. See the Viewing conflicts report topic for more information.
  3. If no data conflicts, the progress dialog box appears. When the process is complete, a message box is displayed to indicate that the rejoin operation is complete.
  4. Click Close.
  5. Restart the server. For instructions about how to stop and start the server, see Restarting the IBM Security Key Lifecycle Manager server.