HP Brocade 8/12c Fabric OS Encryption Administrator's Guide - Page 159

Adding an encryption engine to an HA cluster, Failover/failback policy configuration

Page 159 highlights

High availability cluster configuration 3 Adding an encryption engine to an HA cluster 1. Log in to the group leader as Admin or SecurityAdmin. 2. Enter the cryptocfg --add -haclustemember command. Specify the HA cluster name and the encryption engine node WWN. Provide a slot number if the encryption engine is a blade. The following example adds a Brocade FS8-18 in slot 5 to the HA cluster HAC2. SecurityAdmin:switch>cryptocfg --add -haclustermember HAC2 \ 10:00:00:60:5b:03:1c:90 5 EE Node WWN: 10:00:00:60:5b:03:1c:90 5 Slot number: 5Detected Add HA cluster member status: Operation succeeded. 3. Add another encryption engine before committing the transaction. NOTE You cannot add the same node to the HA cluster. Failover/failback policy configuration Failover/failback policy parameters as outlined in Table 5 can be set for the entire encryption group on the group leader. Use the cryptocfg --set command with the appropriate parameter to set the values for the policy. Policies are automatically propagated to all member nodes in the encryption group. TABLE 5 Group-wide policies Policy name cryptocfg --set parameters Description Failover policy -failbackmode auto | manual Heartbeat misses -hbmisses value Heartbeat timeout -hbtimeout value 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. 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 1-15 in integer increments only. Sets the time-out value for the Heartbeat in seconds. The default value is 2 seconds. Valid values are integers in the range between 1 and 30 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 counts 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 to 10 seconds is recommended. A smaller value may cause a node to be declared unreachable prematurely, while a larger value could result in inefficiency. Fabric OS Encryption Administrator's Guide 139 53-1002159-03

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282

Fabric OS Encryption Administrator’s Guide
139
53-1002159-03
High availability cluster configuration
3
Adding an encryption engine to an HA cluster
1.
Log in to the group leader as Admin or SecurityAdmin.
2.
Enter the
cryptocfg
--
add -haclustemember
command. Specify the HA cluster name and the
encryption engine node WWN. Provide a slot number if the encryption engine is a blade. The
following example adds a Brocade FS8-18 in slot 5 to the HA cluster HAC2.
SecurityAdmin:switch>
cryptocfg --add -haclustermember HAC2 \
10:00:00:60:5b:03:1c:90 5
EE Node WWN:
10:00:00:60:5b:03:1c:90 5
Slot number: 5Detected
Add HA cluster member status: Operation succeeded.
3.
Add another encryption engine before committing the transaction.
NOTE
You cannot add the same node to the HA cluster.
Failover/failback policy configuration
Failover/failback policy parameters as outlined in
Table 5
can be set for the entire encryption group
on the group leader.
Use the
cryptocfg
--
set
command with the appropriate parameter to set the values for the policy.
Policies are automatically propagated to all member nodes in the encryption group.
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 1-15 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 1 and 30 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
counts 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 to 10 seconds is
recommended. A smaller value may cause a node to be
declared unreachable prematurely, while a larger value
could result in inefficiency.