HP 8/8 Fabric OS Encryption Administrator's Guide v6.4.0 (53-1001864-01, June - Page 224

6 MPIO and internal LUN states MPIO and internal LUN states The Internal LUN State field displayed within the cryptocfg -show -LUN command output does not indicate the host-to-storage path status for the displayed LUN, but rather the internal LUN state as known by the given encryption engine. Due to the transparent and embedded nature of this encryption solution, the host-to-storage array LUN path status can only be displayed by using host MPIO software. For example, assume there are two paths from a host through two encryption switches to a LUN configured within an active/passive storage array. If the LUN is trespassed, and the active and passive paths to the LUN are swapped, the host MPIO software will continue to indicate that only one path is active to the LUN, but the Brocade encryption switch internal LUN states for both paths will now likely be displayed as Encryption Enabled. In active/passive storage array environments, for troubleshooting purposes, you may want to update the encryption engine Internal LUN States to match those of their host MPIO path states. You can do this by running the cryptocfg -discoverLUN command for the encryption engines that own paths to the LUN in question. This command forces a LUN discovery, causing the encryption engine's Internal LUN State to be updated. Suspension and resumption of re-keying operations A re-key may be suspended or fail to start for several reasons: • The LUN goes offline or the encryption switch fails and reboots. Re-key operations are resumed automatically when the target comes back online or the switch comes back up. You cannot abort an in-progress re-key operation. • An unrecoverable error is encountered on the LUN and the in-progress re-key operation halts. The following LUN errors are considered unrecoverable: SenseKey: 0x3 - Medium Error. SenseKey: 0x4 - Hardware Error. SenseKey: 0x7 - Data Protect. • An unrecoverable error is encountered during the re-key initialization phase. The re-key operation does not begin and a CRITICAL error is logged. All host I/O comes to a halt. All cluster members are notified. • For any unrecoverable errors that may occur during any other phase of the process, the re-key operation is suspended at that point and a CRITICAL error is logged. All cluster members are notified. Host I/O to all regions of the LUN is halted. Only READ operations are supported for the scratch space region of the LUN used for storing the status block of the re-key operation. Once all errors have been corrected you have two recovery options: • Resume the suspended re-key session. All DEK cluster or HA cluster members must be online and reachable for this command to succeed. If successful, this command resumes the re-key sessions from the point where it was interrupted. 1. Enter the cryptocfg --resume_rekey command, followed by the CryptoTarget container name, the LUN number and the initiator PWWN. FabricAdmin:switch>cryptocfg --resume_rekey my_disk_tgt 0x0 \ 10:00:00:05:1e:53:37:99 Operation Succeeded 2. Check the status of the resumed re-key session. 206 Fabric OS Encryption Administrator's Guide 53-1001864-01