Users Guide

NOTE: For more information on Encryption Key and Passphrase guidelines, click the icon on the Manage Encryption
Key page.
Creating An Encryption Key And Enabling LKM
To create an encryption key on the selected controller:
1. Select the Enable Local Key Management (LKM) option.
2. Type Encryption Key Identifier.
An Encryption Key Identifier can contain numerals, alphabets both lower and upper case are allowed, non-alphanumeric
characters, or a combination of any of these.
NOTE: For the Encryption Key Identifier and Passphrase guidelines, click the icon on the page.
3. Type a Passphrase.
A Passphrase must contain at least one numeral, alphabets both lower and upper case are allowed, and one non-
alphanumeric character (except space).
NOTE: Server Administrator Storage Management provides a suggested passphrase below the Passphrase text box.
4. If you want to save the Encryption Key credentials in a file on the managed node, select the Escrow check box.
The file is saved in the location C:\Windows for Microsoft Windows operating system and /var/log for Linux and ESXi
operating system which contains a filename as dellemc_<ControllerModel>_<SASAddress>.xml. The saved file contains
the information: SAS address, Encryption Key Identifier, Passphrase, and modified date. You can use this file for future
reference.
CAUTION:
It is important to understand that if you lose the Passphrase, you cannot recover it. If you move
the physical disks associated with the lost Passphrase to another controller or if the controller fails or is
replaced, you cannot access data from that disk.
NOTE: If Encryption Key Identifier or Passphrase contain special characters such as & , " , <, and >, in the file, they
are written as &amp; , &quot;, &lt; and &gt; respectively.
NOTE: If the system crashes while the file is created, the backup file is saved in the specified location.
5. Select the check-box indicating that you understand the implications of using a passphrase and click Apply Changes.
In the controller Information/Configuration page, the Encryption Key Present is set to Yes and the Encryption mode
is set to LKM.
Changing Or Deleting The Encryption Key
You can change an encryption key of a controller if the controller already has a configured encryption key. You can delete an
encryption key for encrypted controllers only if there are no encrypted virtual disks.
To change the encryption key, type the New Encryption Key Identifier and Passphrase. You are prompted to authenticate
the current Passphrase. Ensure that you read the note on the importance of passphrase and consequences of not saving the
same, before applying the changes.
When you change the encryption key, the existing configuration on the controller is updated to use the new encryption key.
If you have removed any of the encrypted drives previously, you must authenticate with the old passphrase to import the
encrypted drives.
When changing the encryption key, you can save the file details in the specified system location if the Escrow check box option
is selected. If you have already saved the encryption key credentials for a controller, the updates of the credentials for that
controller is overwritten to the file only if the file with combination of same controller model and SAS address otherwise the new
file is created. When the credentials are for a new controller with the unique SAS address details, then a new file is generated.
If Escrow check box is not selected then the file is not created for future references.
If you delete the encryption key, you cannot create encrypted virtual disks and all encrypted unconfigured self-encrypting drives
are erased. However, deleting an encryption key does not affect encryption or data in foreign disks. If you have saved the
encryption key credentials to a file, deleting the encryption key does not delete the file. Managing the file is the responsibility of
the administrator.
70
Controllers