IBM L5U, Maintenance Information

Page: 270 / 295

A-4
TS3400 Tape Library Maintenance Information
5 EE 27 Encryption -
Unauthorized Request
- dSK EKM Key usage error. An invalid
Drive Session Key (dSK) was
used or a valid dSK was used
incorrectly. This could be an
unauthorized attempt to
access data. 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 Session Keys
are correct.
5 EE 28 Encryption -
Unauthorized Request
- eAK EKM Key usage error. An invalid
External Authentication Key
(eAK) was used or a valid
eAK was used incorrectly.
This could be an
unauthorized attempt to
access data.
Note: A private key is needed
for External Authentication.
Retry the command if
necessary. If the problem
persists, ensure that the
External Authentication Keys
are correct.
5 EE 29 Encryption -
Authentication Failure EKM This indicates that a
corrupted or incorrectly
signed message was detected.
Potential causes: invalid
signature on a message, EKM
code bug, tape drive code
bug, drive hardware problem
(unlikely). This could be an
unauthorized attempt to
access data. Retry the command if
necessary. If the problem
persists, ensure that the
signatures are correct. If the
problem still persists, use tape
drive diagnostics to ensure
that the tape drive encryption
hardware is functional.
5 EE 2B Encryption - Key
Incorrect An incompatible key was
written in a non-supported
format.
Note: This is expected to be a
rare occurrence.
Ensure that the encryption
keys are correct, then retry the
command. If the problem
persists, obtain a drive dump
and EKM (or application if no
EKM is involved) traces, then
refer to your EKM
documentation.
5 EE 2C Encryption - Key
Wrapping Failure EKM The EKM has a problem that
resulted in building the
Session Encrypted Data Key
(SEDK) incorrectly.
Note: The SEDK is a structure
used to wrap a key or keys to
send them to the tape drive.
This will typically be reported
with ASC/ASCQ EE 0F, so
this sense is typically only
found in internal logging.
If a higher version of EKM is
available, update the EKM. If
the problem persists, obtain a
drive dump and EKM (or
application if no EKM is
involved) traces, then refer to
your EKM documentation.
Table A-1. Encryption sense data (continued)
SK ASC ASCQ Description Impact Explanation Customer Action Required