Dell PowerVault TL4000 Dell PowerVault ML6000 Encryption Key Manager User's - Page 79

Messages, Config File not Specified, Explanation

Get Dell PowerVault TL4000 PDF manuals and user guides View all Dell PowerVault TL4000 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 79 highlights

Table 6-1. Errors that are reported by the encryption key manager (continued) Error Number Description Action EE32 Keystore-related problem. Most likely cause is either that tape was encrypted using a different Encryption Key Manager with different keys or the key that was used to encrypt this tape has been renamed or deleted from the keystore. Issue list -keysym and ensure the request alias is in the keystore. EEE1 Encryption logic error: Internal error: Ensure that you are running the latest ″Unexpected error: EK/EEDK flags conflict version of the Encryption Key Manager with subpage.″ (refer to "Downloading the Latest Version | Key Manager ISO Image" on page 3-1 to | determine the latest version). Check the versions of drive or proxy server firmware and update them to the latest release, if needed. Enable debug on the key manager server. Try to recreate the problem and gather debug logs. If the problem persists, refer to "Contacting Dell" in the "Read this First" section at the front of this publication for information on getting technical assistance. EF01 Encryption Configuration Problem: ″Drive not configured.″ The drive that is trying to communicate with the Encryption Key Manager is not present in the drive table. Ensure that the config.drivetable.file.url is correct in the KeyManagerConfig.properties file, if that parameter is supplied. Run the listdrives command to check whether the drive is in the list. If not, configure the drive manually by using the adddrive command with the correct drive information or set the ″drive.acceptUnknownDrives″ property to true using the modconfig command. Enable debug tracing and retry the operation. If the problem persists, refer to "Contacting Dell" in the "Read this First" section at the front of this publication for information on getting technical assistance. Messages The following messages can be generated by the Encryption Key Manager and displayed on the admin console. Config File not Specified Text Configuration file not specified: KeyManager Configuration file not specified when starting EKM. Explanation The KMSAdmin command requires that the configuration file be passed in as a command-line parameter. Chapter 6. Problem Determination 6-9

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
Table 6-1. Errors that are reported by the encryption key manager (continued)
Error Number
Description
Action
EE32
Keystore-related problem.
Most likely cause is either that tape was
encrypted using a different Encryption Key
Manager with different keys or the key that
was used to encrypt this tape has been
renamed or deleted from the keystore. Issue
list -keysym
and ensure the request alias is
in the keystore.
EEE1
Encryption logic error: Internal error:
″
Unexpected error: EK/EEDK flags conflict
with subpage.
″
Ensure that you are running the latest
version of the Encryption Key Manager
(refer to “Downloading the Latest Version
Key Manager ISO Image” on page 3-1 to
determine the latest version). Check the
versions of drive or proxy server firmware
and update them to the latest release, if
needed. Enable debug on the key manager
server. Try to recreate the problem and
gather debug logs. If the problem persists,
refer to “Contacting Dell” in the “Read this
First” section at the front of this publication
for information on getting technical
assistance.
EF01
Encryption Configuration Problem:
″
Drive
not configured.
″
The drive that is trying to communicate with
the Encryption Key Manager is not present
in the drive table. Ensure that the
config.drivetable.file.url is correct in the
KeyManagerConfig.properties file, if that
parameter is supplied. Run the
listdrives
command to check whether the drive is in
the list. If not, configure the drive manually
by using the
adddrive
command with the
correct drive information or set the
″
drive.acceptUnknownDrives
″
property to
true using the
modconfig
command. Enable
debug tracing and retry the operation. If the
problem persists, refer to “Contacting Dell”
in the “Read this First” section at the front of
this publication for information on getting
technical assistance.
Messages
The following messages can be generated by the Encryption Key Manager and
displayed on the admin console.
Config File not Specified
Text
Configuration file not specified:
KeyManager Configuration file not
specified when starting EKM.
Explanation
The KMSAdmin command requires that the configuration file be passed in as a
command-line parameter.
Chapter 6. Problem Determination
6-9
|
|