Brocade Fabric OS Encryption Administrator’s Guide Supporting HP Secure Key Manager (SKM) and HP Enterprise Secure Key Manager (ESKM) Environments (Supporting Fabric OS v7.2.0) - Manual (Page 196)

176 Fabric OS Encryption Administrator’s Guide (SKM/ESKM)
53-1002923-01
Crypto LUN configuration
3
Crypto LUN parameters and policies
Table 6 shows the encryption parameters and policies that can be specified for a disk or tape LUN,
during LUN configuration (with the cryptocfg
--
add
-
LUN command). Some policies are applicable
only to disk LUNs, and some policies are applicable only to tape LUNs. It is recommended that you
plan to configure all the LUN state and encryption policies with the cryptocfg
--
add
-
LUN
command. You can use the cryptocfg
--
modify
-
LUN command to change some of the settings,
but not all options can be modified.
NOTE
LUN policies are configured at the LUN level, but apply to the entire HA or DEK cluster. For multi-path
LUNs that are exposed through multiple target ports and thus configured on multiple CryptoTarget
containers on different encryption engines in an HA cluster or DEK cluster, the same LUN policies
must be configured. Failure to do so results in unexpected behavior and may lead to data corruption.
The tape policies specified at the LUN configuration level take effect if you do not create tape pools
or configure policies at the tape pool level. The Brocade encryption solutions supports up to a 1 MB
block size for tape encryption. Also, the Logical Block Address (LBA) 0 block size (I/O size from the
host) must be at least 1 K less than the maximum supported backend block size (usually 1 MB).
This is typically the case, as label operations are small I/O operations. If this support requirement
is not met, the Brocade encryption solution will not allow the backup operation to start to that tape.
NOTE
LBA 0 is not encrypted. Data sent to this block address is always sent as clear text.
TABLE 6 LUN parameters and policies
Policy name Command parameters Description
LUN state
Disk LUN: yes
Tape LUN: No
Modify? No
-
lunstate encrypted |
cleartext
Sets the Encryption state for the LUN. Valid values are:
•
cleartext - Default LUN state. Refer to policy configuration
considerations for compatibility with other policy settings.
•
encrypted - Metadata on the LUN containing the key ID of the
DEK that was used for encrypting the LUN is used to retrieve
the DEK from the key vault. DEKs are used for encrypting and
decrypting the LUN.
Key ID
Disk LUN: yes
Tape LUN: No
Modify? No
-
keyID Key_ID Specifies the key ID. Use this option only if the LUN was encrypted
but does not include the metadata containing the key ID for the
LUN. This is a rare case for LUNs encrypted in Native (Brocade)
mode.
Encryption
format
Disk LUN: yes
Tape LUN: yes
Modify? Yes
-
encryption_format native Sets the encryption format. The LUN is encrypted or decrypted
using the Brocade encryption format (metadata format and
algorithm). This is the default setting
Encryption
policy
Disk LUN: yes
Tape LUN: Yes
Modify? Yes
-
encrypt | -cleartext Enables or disables a LUN for encryption. Valid values are:
•
cleartext - Encryption is disabled. This is the default setting.
When the LUN policy is set to cleartext the following policy
parameters are invalid and generate errors when executed:
-
enable_encexistingdata -enable_rekey, and
-
key_lifespan.
•
encrypt - The LUN is enabled to perform encryption.