Brocade Communications Systems Encryption Switch Service Manual Page 295

  • Download
  • Add to my manuals
  • Print
  • Page
    / 326
  • Table of contents
  • TROUBLESHOOTING
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 294
Fabric OS Encryption Administrator’s Guide (DPM) 277
53-1002720-02
MPIO and internal LUN states
6
5. Synchronize the crypto configurations across all member nodes.
FabricAdmin:switch> cryptocfg –-commit
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 <crypto target container name> 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 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.
Once 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.
Page view 294
1 2 ... 290 291 292 293 294 295 296 297 298 299 300 ... 325 326

Comments to this Manuals

No comments