Create internal security key
To use the Drive Security feature, you can create an internal security key that is shared by the controllers and secure-capable drives in the storage array. Internal keys are maintained on the controller's persistent memory.
Before you begin
Secure-capable drives must be installed in the storage array. These drives can be Full Disk Encryption (FDE) drives or Federal Information Processing Standard (FIPS) drives.
The Drive Security feature must be enabled. Otherwise, a
Cannot Create Security Key dialog box opens during this task. If necessary, contact your storage vendor for instructions on enabling the Drive Security feature.
Note
If both FDE and FIPS drives are installed in the storage array, they all share the same security key.
About this task
In this task, you define an identifier and a pass phrase to associate with the internal security key.
Note
The pass phrase for Drive Security is independent from the storage array's Administrator password.
What happens next
You can now create secure-enabled volume groups or pools, or you can enable security on existing volume groups and pools.Note
Whenever power to the drives is turned off and then on again, all the secure-enabled drives change to a Security Locked state. In this state, the data is inaccessible until the controller applies the correct security key during drive initialization. If someone physically removes a locked drive and installs it in another system, the Security Locked state prevents unauthorized access to its data.
After you finish
You should validate the security key to make sure the key file is not corrupted.Give documentation feedback