Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-1670840.1
Update Date:2017-10-17
Keywords:

Solution Type  Technical Instruction Sure

Solution  1670840.1 :   Oracle Key Manager - Migration Procedure for x86 KMA's (x2100, x2200, x4170) to version OKM 3.0.2  


Related Items
  • Oracle Key Manager
  •  
  • Sun StorageTek Crypto Key Management System
  •  
Related Categories
  • PLA-Support>Sun Systems>Sun_Other>Sun Collections>SN-OTH: TAPE-CAP VCAP
  •  




In this Document
Goal
Solution


Oracle Confidential INTERNAL - Do not distribute to customer (OracleConfidential).
Reason: Canned Action Plan

Applies to:

Oracle Key Manager - Version 2.0.0 and later
Sun StorageTek Crypto Key Management System - Version All Versions and later
Oracle Solaris on x86 (32-bit)

Goal

The purpose of this document is to provide Oracle Field Engineers and ACS Engineers with the procedure for upgrading x86 KMA's (x2100, x2200, x4170) to version OKM 3.0.2.

For KMA's running on the x86 platforms (x2100, x2200, x4170), the OKM 3.0.2 software is not available for download via My Oracle Support.  Also, the upgrade to 3.0.2 on x86 KMA's is not customer performable.  This is because the OKM 3.0.2 software only runs on the Solaris 11 platform, and the previous OKM 2.x versions run on Solaris 10.  There is no direct method to upgrade from a Solaris 10 system to a Solaris 11 system.

Therefore, either a badged Oracle Field Engineer or Advanced Customer Services (ACS) Engineer must be engaged in order to perform the OKM 3.0.2 upgrade.

NOTE: This procedure will also be needed in the event that an x86 KMA (x2100, x2200, x4170) has already been upgraded to OKM 3.0.2, however the hard disk drive in the KMA subsequently fails.  In the event of a hard disk drive failure, the Oracle Field Engineer should obtain the appropriate FRU prior to proceeding with the upgrade procedure to OKM 3.0.2.

X2100 M2 1TB Disk Drive with KMS preinstalled = FRU 7045443

X2200 M2 1TB Disk Drive with KMS preinstalled = FRU 7045444

X4170 M2 500GB Disk Drive 542-0371 with KMS 2.x = FRU 542-0410
NOTE: Disposal, and destruction, of the failed disk is the customer's responsibility since zeroization of the media typically will not be performed. No Failure Analysis will be performed on the FRU. However, the cover plate with the disk serial number should be removed and returned to logistics as proof of service.

 

Solution

DISPATCH INSTRUCTIONS
   WHAT SKILLS DOES THE FIELD ENGINEER/ADMINISTRATOR NEED?: Knowledge of Oracle Key Manager and X2100 / X2200 / 4170 platforms
   TIME ESTIMATE: 180 minutes
   TASK COMPLEXITY: 3

Oracle Badged FIELD ENGINEER / ACS Engineer INSTRUCTIONS

   PROBLEM OVERVIEW: Upgrade Procedure for x86 KMA's (x2100, x2200, x4170) to version OKM 3.0.2
   WHAT STATE SHOULD THE SYSTEM BE IN TO BE READY TO PERFORM THE RESOLUTION ACTIVITY?: KMA server should be powered down
   WHAT ACTION DOES THE FIELD ENGINEER / ACS Engineer NEED TO TAKE?:

The Field Engineer / ACS Engineer should navigate to the following knowledge article:
 
Oracle Key Manager - Migration Procedure for x86 KMA's (x2100, x2200, x4170) to version OKM 3.0.2 (Document 1670840.1) can be found at:
https://mosemp.us.oracle.com/epmos/faces/DocumentDisplay?id=1670840.1

Attached to the knowledge article are two documents:

1) The first document is the procedure which the FE should download in order to migrate the OKM 2.x x86 KMA's up to the 3.0.2 version, the file name is:

Procedure to migrate x86 KMA to OKM version 3.0.2

2) The second document is the procedure to download the OKM 3.0.2 software from the SAC software repository (sac.us.oracle.com) in order to create a bootable USB stick.  NOTE: This process is only required outside of the USA.  The file name is:

Create An OKM 3.0.2 USB Flash Drive


OBTAIN CUSTOMER ACCEPTANCE 

WHAT ACTION DOES THE FIELD ENGINEER/ADMINISTRATOR NEED TO TAKE TO RETURN THE SYSTEM TO AN OPERATIONAL STATE?: See action plan above.

DISCLOSURE: ALL USB IMAGES ARE NOT TO BE SAVED AND DISTRIBUTED TO CUSTOMERS OR ORACLE FIELD Engineers. ALL IMAGES ARE TO BE DESTROYED FROM LAPTOPS AND USB STICKS AFTER USE. ANY UNAUTHORIZED USE OF USB WILL BE REPORTED TO UPPER MANAGEMENT.


Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback