Technical data

152 Fabric OS Encryption Administrator’s Guide (DPM)
53-1002720-02
High availability clusters
3
Policy Configuration Examples
The following examples illustrate the setting of group-wide policy parameters.
To set the failback mode to manual failback:
SecurityAdmin:switch> cryptocfg --set -failbackmode manual
Set failback policy status: Operation Succeeded.
To set the Heartbeat misses value to 3:
SecurityAdmin:switch> cryptocfg --set -hbmisses 3
Set heartbeat miss status: Operation Succeeded.
To set the Heartbeat timeout value to 3 seconds:
SecurityAdmin:switch> cryptocfg --set -hbtimeout 3
Set heartbeat timeout status: Operation Succeeded.
TABLE 5 Group-wide policies
Policy name cryptocfg --set parameters Description
Failover policy -failbackmode auto |
manual
Sets the failback mode. Valid values for failback mode are:
• auto - Enables automatic failback mode. Failback occurs
automatically within an HA cluster when an encryption
switch or blade that failed earlier has been restored or
replaced. Automatic failback mode is enabled by default.
• manual - Enables manual failback mode. In this mode,
failback must be initiated manually when an encryption
switch or blade that failed earlier has been restored or
replaced.
Heartbeat
misses
-hbmisses value Sets the number of Heartbeat misses allowed in a node that is
part of an encryption group before the node is declared
unreachable and the standby takes over. The default value is 3.
The range is 3-14 in integer increments only.
Heartbeat
timeout
-hbtimeout value Sets the time-out value for the Heartbeat in seconds. The
default value is 2 seconds. Valid values are integers in the range
between 2 and 9 seconds.
NOTE: The relationship between -hbmisses and -hbtimeout
determines the total amount of time allowed before a
node is declared unreachable. If a switch does not sense
a heartbeat within the heartbeat timeout value, it is
counted as a heartbeat miss. The default values result in
a total time of 6 seconds (timeout value of two seconds
times three misses). A total time of 6–9 seconds is
recommended. A smaller value may cause a node to be
declared unreachable prematurely, while a larger value
could result in inefficiency.