Administrator's Guide Supporting RSA Data Protection Manager (DPM) Environments (Supporting Fabric OS v7.2.0) Owner's manual

Fabric OS Encryption Administrator’s Guide (DPM) 187
53-1002922-01
Configuring LUNs for SRDF/TF or RP deployments
3
Alternatively, simply bringing the remote site LUNs online ensures the remote DEKs are
present. To bring the remote/R2 LUNs online, follow these steps:
a. Bring all target ports through which the remote LUNs are accessible online.
b. If not already created, add the remote/R2 CTCs for each path to each remote LUN.
FabricAdmin:switch> cryptocfg --create -container disk <remote target
container name> EE_node_WWN [EE_slot] target_PWWN target_NWWN [-initiator
initiator_PWWN initiator_NWWN [initiator_PWWN initiator_NWWN]...]
c. Add the remote/R2 LUNs to all of their respective CTCs.
FabricAdmin:switch> cryptocfg --add -LUN <remote container name> <remote
LUN ID> <initiator PWWN & NWWN> -lunstate encrypted -encrypt -newLUN
5. Commit the configuration.
6. Verify that the remote LUN states are “Encryption enabled” and their key IDs used for
encryption are the same as those used by the local/R1 LUNs.
7. Verify that the Replication LUN type of the local/R1 LUNs is “Primary” and that of the
remote/R1 LUNs is “Mirror.”
8. Take all remote target ports associated with CTCs through which the remote LUNs are
accessible offline.
NOTE
If the DEK is not synchronized between the local/R1 site and the remote/R2 site, the
remote/R2 LUN will automatically become disabled.
Configuring TimeFinder target devices
Use TimeFinder (TF) to create any desired target devices, such as snapshots, clones, or mirrors.
The TimeFinder source and destination devices must be the same size.
NOTE
You may skip this section if host access to a target device is not required.
1. Log in as Admin or FabricAdmin.
2. Create the containers for the target ports through which TimeFinder target LUNs will be made
accessible, and add all initiators that require access the target LUNs. If Target devices utilize
the same target ports/containers as the source devices, you may skip this step.
FabricAdmin:switch> cryptocfg --create -container disk <target container name>
<EE to own container> <target PWWN> <target NWWN> -initiator <initiator PWWN>
<initiator NWWN>
3. For each path to the target device/LUN, add the LUNs to their respective target containers. All
paths to the TimeFinder target LUN must be added to their containers with the
-newLUN
option.
FabricAdmin:switch> cryptocfg --add -LUN <target container name> <target LUN
ID> <initiator PWWN> <initiator NWWN> -newLUN -lunstate encrypted -encrypt