HP 4400 Release Note page 32

If writes are done to a LUN that is undergoing first time encryption or rekeying, you may see
failed I/Os. HP recommends that host I/O operations are quiesced and not started again
until rekey operations or first time encryption operations for the LUN are complete.
When all nodes in an EG (HA Cluster or DEK Cluster) are powered down (due to catastrophic
disaster or a power outage to the data center) and later nodes come back online (in the event
of the Group Leader (GL) node failing to come back up or the GL node being kept powered
down) the member nodes lose information and knowledge about the EG. This leads to no
crypto operations or commands (except node initialization) being available on the member
nodes after the power-cycle. This condition persists until the GL node is back online.
Workaround. In the case of a datacenter power down, bring the GL node online first,
◦
before the other member nodes are brought back up.
In the event of the GL node failing to come back up, the GL node can be replaced with
a new node. The following are the procedures to allow an EG to function with existing
member nodes and to replace the failed GL node with a new node
Make one of the existing member nodes the Group Leader node and continue operations:
◦
1.
2.
Replace the failed GL node with a new node:
◦
1.
2.
3.
4.
The Encryption SAN Switch and Encryption FC blade do not support QoS. When using
encryption or Frame Redirection, participating flows should not be included in QoS Zones.
With Windows and Veritas Volume Manager/Veritas Dynamic Multipathing, when LUN sizes
less than 400 MB are presented to the Encryption SAN Switch for encryption, a host panic
can occur. Fabric OS 6.2.2e does not support this configuration.
To clean up the stale rekey information for the LUN, use one of the following methods:
Method 1
◦
1.
2.
◦ Method 2
1.
2.
32
On one of the member nodes, create the EG with the same EG name. This will make
that node the GL node and the rest of the Crypto Target Container configurations
will remain intact in this EG.
For any containers hosted on the failed GL node, issue cryptocfg --replace
to change the WWN association of containers from the failed GL node to the new
GL node.
On the new node, follow the switch/node initialization steps.
Create an EG on this fresh switch/node with the same EG name as before.
Perform a configdownload to the new GL node of a previously uploaded
configuration file for the EG from an old GL Node.
For any containers hosted on the failed GL node, issue cryptocfg --replace
to change the WWN association of containers from failed GL node to the new GL
node.
Modify the LUN policy from encrypt to cleartext and commit. The LUN will become
disabled.
Enable the LUN using cryptocfg --enable
clear-text to encrypt with enable_encexistingdata to enable the first time
encryption and do commit. This clears the stale rekey metadata on the LUN and the
LUN can be used again for encryption.
Remove the LUN from Crypto Target Container and commit.
Add the LUN back to the Crypto Target Container with LUN
State="clear-text", policy="encrypt" and enable_encexistingdata
set for enabling the First Time Encryption and commit. This clears the stale rekey
metadata on the LUN and the LUN can be used again for encryption.
LUN. Modify the LUN policy from