HP StorageWorks 8/80 HP StorageWorks Fabric OS 6.2.0g release notes (5697-0035 - Page 27

• 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: DCX_two:root> cfgtransshow There is no outstanding zoning transaction • Each LUN is uniquely identified by the HP Encryption Switch or HP Encryption Blade using the LUN's serial number. The LUN serial numbers must be unique for LUNs exposed from the same target port. The LUN serial numbers must also be unique for LUNs belonging to different target ports in non-multipathing configurations. Failure to ensure unique LUN serial numbers results in non-deterministic behavior and may result in faulting of the HP Encryption Switch or HP Encryption Blade. • When creating an HA Cluster or Encryption Group with two or more HP Encryption Switch/Encryption Blades, the GE Ports (I/O sync links) must be configured with an IP address for the eth0 Ethernet interface using ipaddrset. In addition, both eth0 and eth1 Ethernet ports should be connected to the network for redundancy. These I/O sync links connections must be established before any Re-Key, First Time Encryption, or enabling EE for crypto operations. Failure to do so results in HA Cluster creation failure. If the IP address for these ports is configured after the EE was enabled for encryption, HP Encryption Switch needs to be rebooted and Encryption blades should be slotpoweroff/slotpoweron to sync up the IP address information to the EEs. If only one Ethernet port is configured and connected to a network, data loss or suspension of ReKey may occur when the network connection toggles or fails. HP StorageWorks Fabric OS 6.2.0g release notes 27