![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||||||
Solution Type Problem Resolution Sure Solution 2174730.1 : Oracle Key Manager (OKM) - After System Board Replacement X2100 M2 KMA Will Not Boot To Quick Start Menu
In this Document
Applies to:Oracle Key Manager - Version 2.3 and laterInformation in this document applies to any platform. SymptomsX2100 KMA Motherboard Replacement Problem The X2100 motherboards in our current spares pool (PN 375-3460) can have a network port configuration problem. After a the new system board is installed at the customer's site you may encounter 1 or more of these issues: 1) The KMA will go into an infinite loop involving 4 screens. It will attempt to bring up Solaris but the machine will panic and start over. CauseX2100 M2 System Boards in stock, have a different device configuration from what was originally manufactured for use with the preloaded KMA hard drives. SolutionNOTE: Not all x2100 m2 system board replacements are impacted by this issue. There have been circumstances that after a system board replacement, the KMA would not boot due to OS corruption and a standard x2100 m2 KMA hard drive (FRU 7045443) hard drive replacement successfully resolved the issue. Therefore, before proceeding with the below 3.0.2 upgrade procedure, the x2100 m2 KMA hard drive (FRU 7045443) should be replaced first, and if the issue persists then continue on with the below 3.0.2 upgrade recommendation. ** It will be required to upgrade the KMA to version 3.0.2 in order to workaround this issue. 1) Install the new motherboard. Set up the IP address for the maintenance port using the process in the ELOM Admin guide. 2) Load 3.0.2 version software onto the HDD using a flash drive that has the installation software on it. See below knowledge article for procedure: Oracle Key Manager - Migration Procedure for x86 KMA's (x2100, x2200, x4170) to version OKM 3.0.2(Doc ID 1670840.1) NOTE: The above knowledge article is Internal Only, as an Oracle Field Engineer will be required to perform the 3.0.2 upgrade. 3) Go through quickstart, and rejoin the KMA to the existing cluster. NOTE: It is fully supported to run KMA's in a mixed version cluster. For example, a KMA running 3.0.2 can join an existing KMA in a cluster running version 2.x. Attachments This solution has no attachment |
||||||||||||||||
|