Brocade Fabric OS Encryption Administrator’s Guide Supporting HP Secure Key Manager (SKM) and HP Enterprise Secure Key Manager (ESKM) Environments (Supporting Fabric OS v7.2.0) - Manual (Page 220)

200 Fabric OS Encryption Administrator’s Guide (SKM/ESKM)
53-1002923-01
Data rekeying
3
Target: 50:06:01:60:30:20:db:34 50:06:01:60:b0:20:db:34
Target PID: 022900
VT: 20:00:00:05:1e:53:8d:cd 20:01:00:05:1e:53:8d:cd
VT PID: 06c001
Host: 10:00:00:00:c9:56:e4:7b 20:00:00:00:c9:56:e4:7b
Host PID: 066000
VI: 20:02:00:05:1e:53:8d:cd 20:03:00:05:1e:53:8d:cd
VI PID: 06c201
LUN number: 0x1
LUN serial number:
600601603FE2120014FC89130295DF1100010000000000000008000000000000
Rekey session number: 0
Percentage complete: 23
Rekey state: Write Phase
Rekey role: Primary/Active
Block size: 512
Number of blocks: 2097152
Current LBA: 488577
Operation succeeded.
Suspension and resumption of rekeying operations
A rekey may be suspended or fail to start for several reasons:
• The LUN goes offline or the encryption switch fails and reboots. Rekey operations are resumed
automatically when the target comes back online or the switch comes back up. You cannot
abort an in-progress rekey operation.
• An unrecoverable error is encountered on the LUN and the in-progress rekey 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 rekey initialization phase. The rekey
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 rekey
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 rekey operation.
After all errors have been corrected, you have two recovery options:
• Resume the suspended rekey session. All DEK cluster or HA cluster members must be online
and reachable for this command to succeed. If successful, this command resumes the rekey
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