HP StorageWorks 8/80 HP StorageWorks Fabric OS 6.2.0b release notes (5697-0352 - Page 27

Encryption behavior

Page 27 highlights

Remove Offline or inaccessible Devices Zone Admin Zone database summary ping Zone Admin Zoning Configure > Zoning Replace/Replace All zone members by selecting the offline devices from the zone tree. Offline devices have an unknown overlay badge with good visibility. Configure > Zoning Zoning report for both online and offline database Encryption behavior • HP recommends that the encrypted LUN containers be created when all the nodes/Encryption Engines (EE) in the Data Encryption Key (DEK)/High Availability Cluster (HAC) are up and enabled. • LUN configuration • The following process is to be used then when configuring a LUN for encryption: • Add the LUN as clear-text to the Crypto Target Container (CTC). • Once the LUN comes online and clear-text host I/O starts, modify the LUN from clear-text to encrypt, including the enable_encexistingdata option to convert the LUN from clear-text to encrypted. • An exception to this LUN configuration process:if the LUN was previously encrypted by the HP Encryption Switch or HP Encryption Blade, the LUN can be added to the Crypto Target Container with the -encrypt and -lunstate ="encrypted" options. • LUN configurations must be committed to take effect. No more than 25 LUNs can be added or modified in a single commit operation. Attempts to commit configurations that exceed 25 LUNs will fail with a warning. Note that there is also a five-second delay before the commit operation takes effect. Always ensure that any previously committed LUN configurations or LUN modifications have taken effect before committing additional LUN configurations or additions. All LUNs should be in an Encryption Enabled state before committing additional LUN modifications. • Avoid changing the configuration of any LUN that belongs to a Crypto Target Container/LUN configuration while the re-keying process for that LUN is active. If the user changes the LUN's settings during manual or auto, re-keying or First Time Encryption, the system reports a warning message stating that the encryption engine is busy and a forced commit is required for the changes to take effect. A forced commit command halts all active re-keying processes running in all Crypto Target Containers and corrupts any LUN engaged in a re-keying operation. There is no recovery for this type of failure. • To remove access between a given initiator and target, the user must not only remove the active zoning information between the initiator and target, but must also remove the associated Crypto Target Containers (CTCs), which will in turn remove the associated frame redirection zone information. • Before committing configurations or modifications to the CTC or LUNs on an HP Encryption Switch or HP Encryption Blade, make sure that there are no outstanding zoning transactions in the switch or fabric. Failure to do so results in the commit operation for the Crypto Target or LUNs failing and may cause the LUNs to be disabled. The user can check for outstanding zoning transaction by issuing the cfgtransshow CLI command: HP StorageWorks Fabric OS 6.2.0b release notes 27

  • 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

Configure > Zoning
Replace/Replace All zone
members by selecting the offline
devices from the zone tree.
Offline devices have an unknown
overlay badge with good
visibility.
Zone Admin
Remove Offline or inac-
cessible Devices
Configure > Zoning
Zoning report for both online and
offline database
Zone Admin
Zone database summary
ping
Zoning
Encryption behavior
HP recommends that the encrypted LUN containers be created when all the nodes/Encryption
Engines (EE) in the Data Encryption Key (DEK)/High Availability Cluster (HAC) are up and enabled.
LUN configuration
The following process is to be used then when configuring a LUN for encryption:
Add the LUN as clear-text to the Crypto Target Container (CTC).
Once the LUN comes online and clear-text host I/O starts, modify the LUN from clear-text
to
encrypt
, including the
enable_encexistingdata
option to convert the LUN from
clear-text to encrypted.
An exception to this LUN configuration process:if the LUN was previously encrypted by the HP
Encryption Switch or HP Encryption Blade, the LUN can be added to the Crypto Target Con-
tainer with the
–encrypt
and
–lunstate =“encrypted”
options.
LUN configurations must be committed to take effect. No more than 25 LUNs can be added
or modified in a single commit operation. Attempts to commit configurations that exceed 25
LUNs will fail with a warning. Note that there is also a five-second delay before the commit
operation takes effect.
Always ensure that any previously committed LUN configurations or LUN modifications have
taken effect before committing additional LUN configurations or additions. All LUNs should be
in an Encryption Enabled state before committing additional LUN modifications.
Avoid changing the configuration of any LUN that belongs to a Crypto Target Container/LUN
configuration while the re-keying process for that LUN is active. If the user changes the LUN
s
settings during manual or auto, re-keying or First Time Encryption, the system reports a warning
message stating that the encryption engine is busy and a forced commit is required for the changes
to take effect. A forced commit command halts all active re-keying processes running in all Crypto
Target Containers and corrupts any LUN engaged in a re-keying operation. There is no recovery
for this type of failure.
To remove access between a given initiator and target, the user must not only remove the active
zoning information between the initiator and target, but must also remove the associated Crypto
Target Containers (CTCs), which will in turn remove the associated frame redirection zone inform-
ation.
Before committing configurations or modifications to the CTC or LUNs on an HP Encryption Switch
or HP Encryption Blade, make sure that there are no outstanding zoning transactions in the switch
or fabric. Failure to do so results in the commit operation for the Crypto Target or LUNs failing
and may cause the LUNs to be disabled. The user can check for outstanding zoning transaction
by issuing the
cfgtransshow
CLI command:
HP StorageWorks Fabric OS 6.2.0b release notes
27