HP 4400 HP B-series Fabric OS 7.0.0a Release Notes (5697-0881, June 2011) - Page 41

• When the LUN comes online and the clear-text host I/O starts, modify the LUN from cleartext to encrypted, 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 CTC 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 fail with a warning. 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. • LUN Size Expansion consideration (as an example for EVA LUNs): When an EVA LUN is encrypted, and then needs to be expanded using HP Command View, no additional configuration is required from the Encryption SAN Switch side. However, make sure not to change the LUN size while any re-key operation is in progress. • If an HA Cluster is configured within an Encryption Group with containers configured for auto failback mode, care must be taken to change the failback mode to "manual" before a firmware upgrade; this can be set back to "auto" once upgrade is done. See the 7.0.0a Encryption Admin Guide for additional recommendations and precautions to be followed during this process. • Avoid changing the configuration of any LUN that belongs to a CTC/LUN configuration while the rekeying process for that LUN is active. If you change the LUN settings during manual or auto, rekeying 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 rekeying processes running in all CTCs and corrupts any LUN engaged in a rekeying operation. There is no recovery for this type of failure. • If the data encryption group (Encryption Group) gets into a state where the Group Leader encryption switch reports that another encryption switch is NOT a member node of the encryption group, and the encryption switch member node still indicates that it IS part of the encryption group, the following recovery action can be performed to re-merge the nodes into the encryption group: 1. On the Group Leader encryption switch, execute the CLI cryptocfg -dereg -membernode command. 2. Wait for 30 seconds. 3. Execute the CLI cryptocfg -reg -membernode command. This is a rare situation that has been noted in a test environment where there were intermittent management network connectivity problems. • To remove access between a given initiator and target, you must not only remove the active zoning information between the initiator and target, but must also remove the associated CTCs, which in turn removes the associated frame redirection zone information. Make sure to back up all data before taking this action. • 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 CTC or LUNs failing and may cause the LUNs to be disabled. The user can check for outstanding zoning transactions by issuing the CLI cfgtransshow command : DCX_two:root> cfgtransshow HP B-series Fabric OS 7.0.0a Release Notes 41