Brocade Fabric OS Command Reference Manual v6.2.0 (53-1001186-01, April 2009)

128 Fabric OS Command Reference
53-1001186-01
cryptoCfg
2
-srcfile filename
Specifies the file name when restoring the master key from a file in the
predetermined directory on the switch. Use this operand when the master key
was backed up to a file rather than to a key vault. The -keyID and the -srcfile
operands are mutually exclusive.
--show -groupcfg Displays the group-wide encryption policy configuration. This command is
valid on all member nodes and on the group leader.
--show -groupmember
Displays detailed information for all encryption group members or for a single
member. This command is valid on all member nodes and on the group
leader. The following required operands are mutually exclusive:
-all Displays information on all nodes in the existing encryption group.
node_WWN Displays information on a single specified node. The node is identified by its
node WWN.
Function 3. High Availability (HA) cluster configuration
Synopsis cryptocfg --help -hacluster
cryptocfg --create -hacluster HA_cluster_name [node_WWN [slot_number]] [node_WWN
[slot_number]]
cryptocfg --delete -hacluster HA_cluster_name
cryptocfg --add -haclustermember HA_cluster_name node_WWN [slot_number] [node_WWN
[slot_number]]
cryptocfg --remove -haclustermember HA_cluster_name node_WWN [slot_number] [node_WWN
[slot_number]]
cryptocfg --replace [-haclustermember HA_cluster_name] current_node_WWN [slot_number]
new_node_WWN [slot_number]
cryptocfg --show -hacluster -all | HA_cluster_name
Description Use these cryptoCfg commands to configure and manage High Availability (HA) clusters.
A HA cluster consists of two encryption engines configured to host the CryptoTargets and to provide
the active/standby failover and failback capabilities in a pair-wise relationship in a single fabric.
The encryption engines that are part of an HA cluster must belong to the same encryption group
and be part of the same fabric.
Failure to ensure that HA cluster members are part of the same encryption group dissolves the HA
cluster and the encryption engines lose their failover capability.
The HA cluster configuration must be performed on the group leader. Configuration changes must
be committed before they take effect. Use the cryptocfg --commit command to commit a new
configuration or a configuration change. Refer to section “5. Transaction management” for more
information. Any operation related to an HA cluster performed without a commit operation will not
survive across switch reboots, power cycles, CP failover, or HA reboots.