| Asset ID: |
1-72-1587186.1 |
| Update Date: | 2013-09-30 |
| Keywords: | |
Solution Type
Problem Resolution Sure
Solution
1587186.1
:
Oracle Key Manager: AFTER UPGRADING VERSION 2.5.2 SYSTEM DID NOT REBOOT- SYSTEM DOWN
| Related Categories |
- PLA-Support>Sun Systems>TAPE>Backup Software-Filesystems>SN-TP: Encryption
|
In this Document
Created from <SR 3-7777853849>
Applies to:
Oracle Key Manager - Version 2.1 to 2.5.2 [Release 2.0]
Information in this document applies to any platform.
Symptoms
When resetting the KMA to Factory Defaults on all 6 KMA's that I have upgraded to OKM 2.5.2, the following are the messages on the eLOM Console:
OKM: Console unavailable during reset
OKM: services stopped. Re-creating LiveUpgrade inactive partition. Do NOT interrupt…
OKM: Inactivate partition re-created
OKM: wiping the other partitions…
OKM: resetting the system configuration …
svc.startd The system is coming down. Please wait…
svc.startd 65 system services are now being stopped.
OKM: stopping services…
OKM: services stopped. Re-creating LiveUpgrade inactive partition. Do NOT interrupt…
OKM: Inactivate partition re-created
OKM: wiping the other partitions…
OKM: resetting the system configuration …
svc.startd The system is coming down. Please wait…
svc.startd 65 system services are now being stopped.
OKM: stopping services…
OKM: services stopped. Re-creating LiveUpgrade inactive partition. Do NOT interrupt…
OKM: Inactivate partition re-created
OKM: wiping the other partitions…
OKM: resetting the system configuration …
svc.startd The system is coming down. Please wait…
svc.startd 65 system services are now being stopped.
The KMA starts up successfully after the reset process. However, both inactive and active partitions now show OKM 2.5.2.
It used to be that the old OKM version is kept in the inactive partition.
Changes
Upgraded KMA to OKM 2.5.2 and the KMA firmware to version 3d16.
Cause
During reset to factory defaults, the copy of the previous OKM release is removed. ( This is a change in the OKM 2.5.2 Software Upgrade functionality. )
If the KMA does not come up after the reset, disk issue may be preset that caused the KMA to crash.
Solution
During reset to factory defaults, if the "LiveUpgrade inactive partition" messages are occurring, wait until the system is restarted.
If the KMA is not coming up try to ssh to the ELOM console and run 'start /SP/AgentInfo/console. If the boot command fails with "Kernel must be loaded" error, the KMA system disk should be replaced.
Attachments
This solution has no attachment
