| Asset ID: |
1-71-2058964.1 |
| Update Date: | 2017-05-17 |
| Keywords: | |
Solution Type
Technical Instruction Sure
Solution
2058964.1
:
Oracle Key Manager - Why Are Newly Added OKM 3.x KMA's Not Issuing Encryption Keys After Joining An Existing 2.x KMA Cluster?
| Related Categories |
- PLA-Support>Sun Systems>TAPE>Backup Software-Filesystems>SN-TP: Encryption
|
In this Document
Created from <SR 3-11309255501>
Applies to:
Oracle Key Manager - Version 2.0.0 and later
Information in this document applies to any platform.
Goal
It has been observed that when joining new OKM 3.x KMA's into an existing 2.x KMA cluster, the new OKM 3.x KMA's will not issue encryption keys to the tape agents.
Solution
There have been occurrences where when the new OKM 3.x KMA's join an existing cluster the tape drives (potentially due to down rev drive code) may not update their KMA cluster profiles, or encounter timeouts. Therefore the new OKM 3.x KMA's will not serve keys to the tape drives.
The workaround is to re-enroll all the tape drives to the new OKM 3.x KMA's.
To potentially avoid the issue all tape drive code should be up to date, prior to joining any new KMA's into an existing cluster.
Attachments
This solution has no attachment
