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-72-1548343.1
Update Date:2014-09-04
Keywords:

Solution Type  Problem Resolution Sure

Solution  1548343.1 :   KMS 1.2/T10000A - Failed To Create Tokens After Tape Drive Replacement  


Related Items
  • Sun StorageTek T10000A Tape Drive
  •  
  • Sun StorageTek Crypto Key Management System
  •  
Related Categories
  • PLA-Support>Sun Systems>TAPE>Backup Software-Filesystems>SN-TP: Encryption
  •  




In this Document
Symptoms
Changes
Cause
Solution
References


Created from <SR 3-6596648561>

Applies to:

Sun StorageTek Crypto Key Management System - Version All Versions and later
Sun StorageTek T10000A Tape Drive - Version Not Applicable and later
Information in this document applies to any platform.

Symptoms

KMS 1.2 Failed to enable encryption on T10000A

1. Drive crypt LED states “Amber Flashing”
2. Token states L0: OFF / L1:Green OFF / L2: Green OFF / L3: OFF / L4: Green ON / L5: Amber Flashing / L6: Green On / L7: Green ON
3. Ping works for drive and token.
    Drive is requesting EKT with amber led flashing but EKT token has NO device key to enable drive encryption.
4. Initialized token to be as NKT but GUI is in a hung state and cannot create EKT

Changes

Drive was replaced

Cause

EKT can not be created from KMS GUI while accessing Token menu.
The KMS GUI was in a hung state.

This problem may be related to a known KMS 1.2 problem reported in Bug 15394756 - SUNBT6553888 KMS GUI Hangs During Offline Token Write

Solution

Write the device key to token (EKT/NKT) using the CLI write_token command:
write_token -t e -r -l  token_ID  drive_name

 

References

<NOTE:1266718.1> - KMS 1.x - Unable to Write Token

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