Users Guide

After you delete the encryption key, all the SEDs that are not part of the virtual disks are secure-erased. For more information, see the
Online Help.
Deleting Encryption Key Using RACADM
To delete an encryption key by running a RACADM command, use the following syntax:
racadm raid deletesecuritykey:RAID.ChassisIntegrated.1-1
For more information, see the Chassis Management Controller PowerEdge VRTX RACADM Command Line Reference Guide.
Encrypting Virtual Disks
You can encrypt virtual disks created on SEDs after conguring an encryption key on the controller. Whenever you perform an encryption, a
message is logged in the CMC Log. You can encrypt virtual disks:
• Security key is congured on the controller.
• All the drives on the virtual disk are SEDs.
Encrypting one virtual disk enables encryption on all the virtual disks on the same disks group.
You must have the Chassis Conguration Administrator privilege to encrypt virtual disks.
Encrypting Virtual Disks Using CMC Web Interface
To encrypt an existing virtual disk:
1 In the left pane, click Storage > Virtual Disks > Manage.
2 From the Virtual Actions drop-down, select Encrypt Virtual Disk and click Apply.
NOTE
: The Encrypt Virtual Disk option is available only if unsecure virtual disks are congured in the SED.
Encrypting Virtual Disks Using RACADM
To encrypt virtual disks by running a RACADM command, use the following syntax:
racadm raid encryptvd:Disk.Virtual.0:RAID.ChassisIntegrated.1-1
For more information, see the Chassis Management Controller PowerEdge VRTX RACADM Command Line Reference Guide.
Unlocking Foreign Conguration
Drives which are part of secure virtual disks are called secured drives. Secured drives can be migrated from one controller to another
controller. If a dierent encryption or security key is congured for the destination controller, the security status of these drives is displayed
as ‘locked’ and cannot be seen as part of ‘preview foreign cong’. The ‘Import foreign cong’ does not detect these foreign drives.
While running the unlock command, provide the source controller passphrase and key ID for these drives. Even after unlocking, the ‘foreign
controller key’ still secures these drives. However, you can see these drives while searching for foreign drives in the existing ‘preview
foreign cong’. You can import or clear the foreign conguration on these secure drives.
If foreign drives with dierent security keys are migrated from more than one controller, then unlock and import or clear the set of drives
from one foreign controller before unlocking the drives migrated from another controller. This action ensures that unlock is not allowed on a
controller, if the controller has drives that are unlocked but not imported or cleared.
Managing Chassis Storage
203