HP 8/8 Fabric OS Encryption Administrator's Guide v6.4.0 (53-1001864-01, June - Page 66

Swapping engines in an HA cluster, Failback option, Invoking failback, Failback

Page 66 highlights

2 Creating high availability (HA) clusters Swapping engines in an HA cluster Swapping engines is useful when replacing hardware. Swapping engines is different from removing an engine and adding another because when you swap engines, the configured targets on the former HA cluster member are moved to the new HA cluster member. To swap engines, select one engine from the right tree (see Figure 25) and one unclustered engine from the list on the left, and click the double-arrow button. NOTE The two engines being swapped must be in the same fabric. Failback option The Failback option determines the behavior when a failed encryption engine is restarted. When the first encryption engine comes back online, the encryption group's failback setting (auto or manual) determines how the encryption engine resumes encrypting and decrypting traffic to its encryption targets. • In auto mode, when the first encryption engine restarts, it automatically resumes encrypting and decrypting traffic to its encryption targets. • In manual mode, the second encryption engine continues handling the traffic until you manually invoke failback using the CLI or Management application, or until the second encryption engine fails. Invoking failback To invoke failback to the restarted encryption engine from the Management application, complete the following steps. 1. Select Configure > Encryption. The Encryption Center dialog box displays. 2. Select the group to which the encryption engine belongs from the Encryption Devices table, and click Properties. The Encryption Group Properties dialog box displays. 3. Click the HA Clusters tab. 4. Select the online encryption engine and click Failback. 5. Click OK on the Encryption Group Properties dialog box. 6. Click Close on the Encryption Center dialog box. 48 Fabric OS Encryption Administrator's Guide 53-1001864-01

  • 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

48
Fabric OS Encryption Administrator’s Guide
53-1001864-01
Creating high availability (HA) clusters
2
Swapping engines in an HA cluster
Swapping engines is useful when replacing hardware. Swapping engines is different from removing
an engine and adding another because when you swap engines, the configured targets on the
former HA cluster member are moved to the new HA cluster member.
To swap engines, select one engine from the right tree (see
Figure 25
) and one unclustered engine
from the list on the left, and click the double-arrow button.
NOTE
The two engines being swapped must be in the same fabric.
Failback option
The
Failback
option determines the behavior when a failed encryption engine is restarted. When
the first encryption engine comes back online, the encryption group’s failback setting (auto or
manual) determines how the encryption engine resumes encrypting and decrypting traffic to its
encryption targets.
In auto mode, when the first encryption engine restarts, it automatically resumes encrypting
and decrypting traffic to its encryption targets.
In manual mode, the second encryption engine continues handling the traffic until you
manually invoke failback using the CLI or Management application, or until the second
encryption engine fails.
Invoking failback
To invoke failback to the restarted encryption engine from the Management application, complete
the following steps.
1.
Select
Configure > Encryption
.
The
Encryption Center
dialog box displays.
2.
Select the group to which the encryption engine belongs from the
Encryption Devices
table,
and click
Properties
.
The
Encryption Group Properties
dialog box displays.
3.
Click the
HA Clusters
tab.
4.
Select the online encryption engine and click
Failback
.
5.
Click
OK
on the
Encryption Group Properties
dialog box.
6.
Click
Close
on the
Encryption Center
dialog box.