OKM 3.0 - Replacing Hard Drive In NS T4-1 KMA Which Is In A Mixed Cluster Including 2.x KMA's May Fail To Join The Existing Cluster

Asset ID:	1-71-2181897.1
Update Date:	2018-02-16
Keywords:

Solution Type Technical Instruction Sure

Solution 2181897.1 : OKM 3.0 - Replacing Hard Drive In NS T4-1 KMA Which Is In A Mixed Cluster Including 2.x KMA's May Fail To Join The Existing Cluster

Applies to:

Oracle Key Manager - Version 3.0 and later
Information in this document applies to any platform.

Goal

When replacing an NS T4-1 KMA hard drive, the replacement code level will be at the 3.0 base version. If the site had previously upgraded to the OKM 3.1 version, and if they are running in a mixed cluster consisting of 2.x KMA's (x86) then they may be vulnerable to the following Service Bulletin:

Oracle Key Manager (OKM) - Technical Service Bulletin - Joining Any Pre OKM 3.1 KMA's To An Existing Pre OKM 3.1 KMA Cluster May Cause An Interruption In Service (Doc ID 2127559.1)

Solution

The recommendation in this scenario is as follows:

1) Replace the HDD following normal procedures. Reference the following knowledge article:

How to replace Oracle Key Manager hard drive in X2100, X2200, X4170, NS T4-1, or Sparc T7-1 KMA server (Doc ID 1492060.1)

2) Go through QuickStart initializing its own cluster (instead of joining it to the existing cluster)

Reference the Oracle Key Manager Installation and Service Manual (QuickStart Wizard starting on page 47):

Oracle Key Manager Installation and Service Manual

3) Upgrade this KMA to the latest OKM 3.1. Note that since this KMA is running OKM 3.0, they must first upgrade to OKM 3.0.1 before upgrading to OKM 3.0.2. The upgrade path would be:

OKM 3.0.0 --> OKM 3.0.1 --> OKM 3.0.2 --> OKM 3.1 or 3.2

NOTE: Customers will need to submit a Service Request with Oracle Support in order to pursue this upgrade path, please see the following known upgrade issue impacting all pre OKM 3.1 versions after Nov 12th 2017:

Oracle Key Manager (OKM) - Any KMA Running 3.x Code Version Prior To 3.1 Will Get An Error On Future OKM Software Downloads After November 12 2017 (Doc ID 2292422.1)

4) Through the ILOM redirection, log into the OKM console as a Security Officer and perform a reset to default factory settings.

5) After the reset procedure is complete, join this KMA into the existing cluster, following normal procedures. Follow the "Adding KMAs to the Cluster" section of the Oracle Key Manager Installation and Service Manual (page 113):

Oracle Key Manager Installation and Service Manual

Attachments

This solution has no attachment