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

A member node lost connection to the group leader, A member node lost connection to all other nodes

Get HP Brocade 8/12c PDF manuals and user guides View all HP Brocade 8/12c manuals
Add to My Manuals
Save this manual to your list of manuals

Page 235 highlights

Encryption group merge and split use cases 6 A member node lost connection to the group leader AssumeN1, N2 and N3 form an encryption group, and N2 is the group leader node. N3 and N1 are part of an HA cluster. Assume that N3 lost connection to the group leader node N2 but still maintains communications with other nodes in the encryption group. Impact Failover to N1 does not occur, because the isolated node and the encryption engines' encryption services continue to function normally. However the disconnect of N3 from the group leader breaks the HA cluster and failover capability between N3 and N1. You cannot configure any CryptoTargets, LUN policies, tape pools, or security parameters that would require communication with the isolated member node. In addition, you cannot start any re-key operations (auto or manual). Refer to the section "Configuration impact of encryption group split or node isolation" on page 222 for more information on which configuration changes are allowed. Recovery Restore connectivity between the isolated node and the group leader. No further intervention is required. A member node lost connection to all other nodes in the encryption group Assume N1, N2 and N3 form an encryption group and N2 is the group leader node. N3 and N1 are part of an HA cluster. Assume that N3 lost connection with all other nodes in the group. Node N3 finds itself isolated from the encryption group and, following the group leader succession protocol, elects itself as group leader. This action splits the encryption group into two encryption group islands. EG1 includes the original encryption group minus the member node N3 that lost connection to the encryption group. EG2 consists of a single node N3, which functions as the group leader. Both EG1 and EG2 are in a degraded state. Impact • The two encryption group islands keep functioning independently of each other as far as host I/O encryption traffic is concerned. • Each encryption group registers the missing members as "offline". • The isolation of N3 from the group leader breaks the HA cluster and failover capability between N3 and N1. • You cannot configure any CryptoTargets, LUN policies, tape pools, or security parameters on any of the group leaders. This would require communication with the "offline" member nodes. You cannot start any re-key operations (auto or manual) on any of the nodes. Refer to the section "Configuration impact of encryption group split or node isolation" on page 222 for more information on which configuration changes are allowed. Fabric OS Encryption Administrator's Guide 215 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
215
53-1002159-03
Encryption group merge and split use cases
6
A member node lost connection to the group leader
AssumeN1, N2 and N3 form an encryption group, and N2 is the group leader node. N3 and N1 are
part of an HA cluster. Assume that N3 lost connection to the group leader node N2 but still
maintains communications with other nodes in the encryption group.
Impact
Failover to N1 does not occur, because the isolated node and the encryption engines’ encryption
services continue to function normally. However the disconnect of N3 from the group leader breaks
the HA cluster and failover capability between N3 and N1.
You cannot configure any CryptoTargets, LUN policies, tape pools, or security parameters that
would require communication with the isolated member node. In addition, you cannot start any
re-key operations (auto or manual).
Refer to the section
“Configuration impact of encryption group split or node isolation”
on page 222
for more information on which configuration changes are allowed.
Recovery
Restore connectivity between the isolated node and the group leader. No further intervention is
required.
A member node lost connection to all other nodes in the encryption
group
Assume N1, N2 and N3 form an encryption group and N2 is the group leader node. N3 and N1 are
part of an HA cluster. Assume that N3 lost connection with all other nodes in the group. Node N3
finds itself isolated from the encryption group and, following the group leader succession protocol,
elects itself as group leader. This action splits the encryption group into two encryption group
islands. EG1 includes the original encryption group minus the member node N3 that lost
connection to the encryption group. EG2 consists of a single node N3, which functions as the group
leader. Both EG1 and EG2 are in a degraded state.
Impact
•
The two encryption group islands keep functioning independently of each other as far as host
I/O encryption traffic is concerned.
•
Each encryption group registers the missing members as “offline”.
•
The isolation of N3 from the group leader breaks the HA cluster and failover capability between
N3 and N1.
•
You cannot configure any CryptoTargets, LUN policies, tape pools, or security parameters on
any of the group leaders. This would require communication with the “offline” member nodes.
You cannot start any re-key operations (auto or manual) on any of the nodes. Refer to the
section
“Configuration impact of encryption group split or node isolation”
on page 222 for
more information on which configuration changes are allowed.