IBM System Storage TS3400 Tape Library Maintenance Information page 269

Table A-1. Encryption sense data (continued)
SK ASC ASCQ
0 EF 13 Encryption - Key
Translate
6 EE 18 Encryption - Changed
(Read)
6 EE 19 Encryption - Changed
(Write)
5 EE 23 Encryption - Key
Conflict
5 EE 25 Encryption - Key
Format Not
Supported
5 EE 26 Encryption -
Unauthorized Request
- dAK
Description Impact
EKM
EKM
EKM
EKM
Explanation
This is not an error (if the tape
drive and proxy are
configured correctly). It is
sense data used to initiate a
key translation request to the
application/system key path.
Information Only - SCSI Unit
Attention - encryption
characteristics (key, method,
etc.) were changed prior to a
read operation.
Information Only - SCSI Unit
Attention - encryption
characteristics (key, method,
etc.) were changed prior to a
write operation.
An attempt was made to
reuse a previously used Data
Key Index (Dki). This is also
known as a 'key collision'.
Note: This is expected to be a
rare occurrence. It is only
used in a multi-key
environment.
The tape drive received a
corrupted or unrecognized
message from the EKM. The
most likely causes are an
EKM code bug or
incompatible code versions
on the drive and EKM.
Note: This is expected to be a
rare occurrence.
Key usage error. An invalid
Drive Authentication Key
(dAK) was used or a valid
dAK was used incorrectly.
This could be an
unauthorized attempt to
access data.
Appendix A. Encryption Sense Data
Customer Action Required
none - key translation has
been requested (in-band)
none - retry the command if
necessary.
none - retry the command if
necessary.
Retry the command if
necessary. If the problem
persists, obtain a drive dump
and EKM (or application if no
EKM is involved) traces, refer
to your EKM documentation.
Retry the command if
necessary. If the problem
persists, verify the EKM and
drive code versions are
compatible. As an example, if
the EKM code were updated
to include a new function but
the drive code version does
not recognize the new EKM
function then the code
versions are incompatible. If
the problem still persists,
obtain a drive dump and
EKM (or application if no
EKM is involved) traces, refer
to your EKM documentation.
Retry the command if
necessary. This sense may be
reported following the service
replacement of a tape drive. If
so then it may be
automatically corrected to
support the new tape drive. If
the problem persists, ensure
that the Drive Authentication
Keys are correct.
A-3