Asset ID:	1-71-1291456.1
Update Date:	2011-04-18
Keywords:

---

Solution Type  Technical Instruction Sure

Solution  1291456.1 :   KMS/OKM - Joining a KMA Running on OKM 2.3 to a Mixed Version Cluster  

In this Document
  Goal
  Solution

---

Applies to:

Oracle Key Manager - Version: 1.1.0 to 2.3 - Release: 1.0 to 2.0
Sun StorageTek Crypto Key Management System - Version: Not Applicable and later    [Release: N/A and later]
Oracle Key Manager - Version: 2.3 and later    [Release: 2.0 and later]
Information in this document applies to any platform.

Goal

A KMA running OKM 2.3 can be added to the KMA Cluster regardless of what KMS/OKM versions the KMAs are running.




The rules for joining 2.3 KMA to a mixed version cluster are listed below.

NOTE:
Information in this document applies to X2100/x2200 and X4170 servers
 

Solution

1.  A KMA running OKM 2.3 can join other KMAs in a cluster if these KMAs are running
     KMS/OKM version 2.x.x.

2.  A KMA running OKM 2.3 that is trying to join a cluster running KMS's at different levels,
     must join the KMA with the lowest KMS version in the cluster.

     For example:  In a cluster with 2.0.2, 2.1 and 2.2.1 KMAs,  join 2.3 KMA to the 2.0.2 KMA.

3.  When a KMA running OKM 2.3 joins a cluster, the KMA it joins must be running the highest
     replication level supported for that version.  Otherwise, an error during the  join process will be
     reported.  

     For example: If joining a 2.2.1 KMA,  this KMA should be running KMS 2.2.1 with
     replication version 11.


    

Example Problem:

KMA running 2.3 failed to join a cluster which was running an incorrect replication version. (not the latest supported by that cluster) The replication version was corrected and the KMA failed to join again.

Solution:

- Wait until the replication lag of all KMAs is near zero.

- Delete the 2.3 KMA name and create the name again.

- Rejoin the 2.3 KMA.


         

   

Attachments

This solution has no attachment