Brocade Communications Systems Encryption Switch Service Manual Page 207

  • Download
  • Add to my manuals
  • Print
  • Page
    / 326
  • Table of contents
  • TROUBLESHOOTING
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 206
Fabric OS Encryption Administrator’s Guide (DPM) 189
53-1002720-02
SRDF/TF/RP manual rekeying procedures
3
Configuring SRDF Gatekeeper LUNs
Gatekeeper LUNs used by SYMAPI on the host for configuring SRDF using in-band management
must be added to their containers with a LUN state of cleartext, encryption policy of cleartext, and
without the
-newLUN option.
SRDF/TF/RP manual rekeying procedures
The following topics describe encryption rekeying procedures relative to SRDF, TF, and RP.
TF snapshot rekeying details
In TimeFinder environments, rekeying a source LUN which has one or more snapshot target devices
will result in full copy outs of the source devices to the target devices.
When source LUNs are rekeyed, the target snapshot LUNs will continue to utilize the older/original
DEK and therefore use of the refreshDEK command is not required. However, if an existing target
LUN/snapshot is recreated, then the refreshDEK command must be used on every path/container
which has access to the target device. The refreshDEK command forces the Brocade Encryption
Switch to re-read the metadata on the target LUN and then updates the FPGA tables for the LUN if
the DEK in the metadata has changed.
FabricAdmin:switch> cryptocfg --refreshDEK <target_container> <target LUN ID>
<initiator PWWN>
NOTE
Manual rekeying is supported for TimeFinder snapshot target device LUNs using the
-
include_mirror option; however, it would defeat the purpose of using snapshot LUNs because
rekeying them would cause all blocks of the snapshot to be allocated to the virtual device (i.e. the
source and snap LUNs would have the same number of blocks).
TF clone/mirror rekeying details
Manual rekeying is supported for TimeFinder source LUNs and is not supported for target devices
(clone, mirror) unless the source to target connection is first split.
1. Log in as Admin or Fabric Admin.
2. Split the TF source/target LUN pair ensuring the data synchronization from the source LUN to
the destination LUN has been stopped.
NOTE
During all rekeying operations, data synchronization between the source and target LUN must
be stopped.
3. During the rekeying operation, if desired, you can enable the target ports so the target LUNs
can be accessed by the hosts in read-only mode.
4. Issue a manual rekey request for the source LUN.
FabricAdmin:switch> cryptocfg --manual_rekey <source container> <source LUN
ID> <initiator PWWN>
Page view 206
1 2 ... 202 203 204 205 206 207 208 209 210 211 212 ... 325 326

Comments to this Manuals

No comments