Dell POWEREDGE M1000E - Manual (Page 222)

194 Fabric OS Command Reference
53-1002746-01
cryptoCfg
2
To set the failback mode to manual failback:
SecurityAdmin:switch> cryptocfg --set -failbackmode manual
Set failback policy status: Operation Succeeded.
To set the heartbeat miss value to 3:
SecurityAdmin:switch> cryptocfg --set -hbmisses 3
Set heartbeat miss status: Operation Succeeded.
To set the heartbeat timeout value to 10 seconds:
SecurityAdmin:switch> cryptocfg --set -hbtimeout 10
Set heartbeat timeout status: Operation Succeeded.
To display encryption performance:
SecurityAdmin:switch> cryptocfg --perfshow
33 32 38 39 37 36 34 35 43 42 41 40
==================================================================
5.4m 5.1m 5.4m 47.5m 0 0 0 0 0 0 0 0
47 46 44 45 55 54 52 53 51 50 48 49 Total
==================================================================
0 0 0 0 0 0 0 0 0 0 0 0 75.6m
FUNCTION 3. High Availability (HA) cluster configuration
SYNOPSIS cryptocfg --help -hacluster
cryptocfg --create -hacluster HA_cluster_name
[node_WWN [slot]] [node_WWN [slot]]
cryptocfg --delete -hacluster HA_cluster_name
cryptocfg --add -haclustermember HA_cluster_name
node_WWN [slot] [node_WWN [slot]]
cryptocfg --remove -haclustermember HA_cluster_name
node_WWN [slot] [node_WWN [slot]]
cryptocfg --replace [-haclustermember HA_cluster_name]
current_node_WWN [slot] new_node_WWN [slot]
cryptocfg --show -hacluster -all | HA_cluster_name
DESCRIPTION Use these cryptoCfg commands to configure and manage High Availability (HA) clusters.
An 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.