Oracle Key Manager (OKM) - Upgrade Path To OKM 3.1 and 3.2 For T4-1 and T7-1 SPARC KMA's Running OKM 3.0

Asset ID:	1-72-2241348.1
Update Date:	2018-02-14
Keywords:

Solution Type Problem Resolution Sure

Solution 2241348.1 : Oracle Key Manager (OKM) - Upgrade Path To OKM 3.1 and 3.2 For T4-1 and T7-1 SPARC KMA's Running OKM 3.0

Applies to:

Oracle Key Manager - Version 2.2 to 3.3 [Release 2.0 to 3.0]
Information in this document applies to any platform.

Symptoms

Customer has some OKM T4-1 SPARC servers, currently running OKM release 3.0 but having problems with replication from other KMAs in the cluster. Requesting help to upgrade to 3.1, the same OKM release as the other KMA servers in their cluster.

Cause

There was some confusion as to how the customer's T4-1, SPARC servers need to be upgraded.

Do they need to be upgraded from version 3.0 to 3.1 using a Flash drive or can the OKM patches be directly downloaded to these KMA servers and installed.

Can the customer's OKM Admin download and install the patches or is ACS or FSE required to do this upgrade using a flash drive.

Solution

The upgrade path from OKM 3.0 to 3.1 on T4-1 and T7 SPARC servers is 3.0 -> 3.0.1 -> 3.0.2 -> 3.1, 3.2 or 3.3

All of these releases are available through MOS - Patches & Updates tab.

Upgrade path from 3.0 to 3.1 on SPARC systems only is 3.0 -> 3.0.1 -> 3.0.2 -> 3.1, 3.2 or 3.3

OKM 3.0.1 via patch 20765138
OKM 3.0.2 via patch 20765012

OKM 3.1 via patch 23329696

OKM 3.2 via patch 24675127

OKM 3.2 GUI patch Windows = 24675082 Solaris = 24675109

OKM 3.3 via patch 25993042

OKM 3.3 GUI patch Windows = 25993070 Solaris = 25993063

Customer's OKM Admin can download and install the OKM firmware in the correct order for the T4-1 and T7 SPARC servers.

NOTE: Oracle Key Manager (OKM) - Any KMAs Running 3.x Code Version Prior To 3.1, will see an Error on Future OKM software downloads after November 12 2017 (Doc ID 2292422.1)

The X86 Servers, X2100 M2, X2200 M2 32 bit servers, require a Flash drive to upgrade, not only the OKM firmware but also upgrade the Operating System from Solaris 10 to Solaris 11.2 to go from OKM release 2.2 - 2.5 to 3.0.2.

NOTE: Firmware release 3.0.2 is the highest firmware version these KMA X2100 M2 and X2200 M2 32 bit servers can be upgraded to and this procedure must to be done by ACS or FSE.

NOTE: With the X2100 M2 and X2200 M2 (32 bit servers), version 3.0.2 is the FINAL release, which these 32 bit servers can be upgraded.

The x4170 M2 KMA 64 bit server, can be upgraded from 2.2 - 2.5 to 3.0.2 or 3.3 using a flash drive.

The X4170 is a 64 bit server and can be upgraded from 2.5.2 to 3.3 using a Flash drive, without having to preform the Signature Verification procedure.

The x4170 M2 server upgrade to 3.3 using a flash drive also needs to be completed by ACS or FSE.

References

<NOTE:2292422.1> - 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
<NOTE:1670840.1> - Oracle Key Manager - Migration Procedure for x86 KMA's (x2100, x2200, x4170) to version OKM 3.0.2
<NOTE: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
<NOTE:2127559.1> - 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

Attachments

This solution has no attachment