Symantec 10521146 Administration Guide - Page 292

Removing nodes from a failover group, Viewing incidents during failover, Edit Software Node

Page 292 highlights

292 Advanced configuration Establishing high availability failover Removing nodes from a failover group Symantec Network Security provides an efficient way to remove nodes from a failover group. To remove a node from a failover group 1 In the Network Security console, edit the active or standby objects to the network topology tree. 2 In Edit Software Node or Edit 7100 Series Node, under Failover Group Information, deselect Failover Group Member. 3 Click OK to save the changes to the topology tree. 4 Reset the Enable Watchdog Process parameter for this node to false. See "Setting Enable Watchdog Process" on page 294. Note: SuperUsers can remove nodes from a failover group; Administrators, StandardUsers, and RestrictedUsers cannot. See "User groups reference" on page 319 for more about permissions. Viewing incidents during failover Symantec Network Security provides the ability to view incidents from standby nodes during a failover. Enabling this feature causes incidents to load from all nodes in the cluster, including any standby nodes, and thus avoids dropping incidents. When a failover occurs, the incident table remains unchanged. However, this does not extend to the reporting feature, because reports are generated from active nodes only. In addition to viewing incidents from standby nodes during failover, the following includes characteristics of failover behavior: ■ Symantec Network Security maintains multiple nodes, each with its own unique ID number. One node in each failover group is recognized as active, the others as standby. Each node uses its own detection interface connections. ■ Each node stores duplicate data that the Network Security console handles according to the precedence order. For exclusive actions, all nodes within the group communicate to determine the active node. Both the primary node and the standby node detect and report on incidents and events. ■ The standby node processes the same data, performs the same analysis, and evaluates the same response rules as the active software or appliance node, but does not execute duplicate responses.

  • 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
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330
  • 331
  • 332
  • 333
  • 334
  • 335
  • 336
  • 337
  • 338
  • 339
  • 340
  • 341
  • 342
  • 343
  • 344
  • 345
  • 346
  • 347
  • 348
  • 349
  • 350
  • 351
  • 352
  • 353
  • 354
  • 355
  • 356
  • 357
  • 358
  • 359
  • 360
  • 361
  • 362
  • 363
  • 364
  • 365
  • 366
  • 367
  • 368
  • 369
  • 370
  • 371
  • 372
  • 373
  • 374
  • 375
  • 376
  • 377
  • 378
  • 379
  • 380
  • 381
  • 382
  • 383
  • 384
  • 385
  • 386
  • 387
  • 388
  • 389
  • 390
  • 391
  • 392

292
Advanced configuration
Establishing high availability failover
Removing nodes from a failover group
Symantec Network Security provides an efficient way to remove nodes from a
failover group.
To remove a node from a failover group
1
In the Network Security console, edit the active or standby objects to the
network topology tree.
2
In
Edit Software Node
or
Edit 7100 Series Node
, under
Failover Group
Information
, deselect
Failover Group Member
.
3
Click
OK
to save the changes to the topology tree.
4
Reset the Enable Watchdog Process parameter for this node to false.
See
²Setting Enable Watchdog Process³
on page 294.
Note:
SuperUsers can remove nodes from a failover group; Administrators,
StandardUsers, and RestrictedUsers cannot. See
²User groups reference³
on
page 319 for more about permissions.
Viewing incidents during failover
Symantec Network Security provides the ability to view incidents from standby
nodes during a failover. Enabling this feature causes incidents to load from all
nodes in the cluster, including any standby nodes, and thus avoids dropping
incidents. When a failover occurs, the incident table remains unchanged.
However, this does not extend to the reporting feature, because reports are
generated from active nodes only.
In addition to viewing incidents from standby nodes during failover, the
following includes characteristics of failover behavior:
Symantec Network Security maintains multiple nodes, each with its own
unique ID number. One node in each failover group is recognized as active,
the others as standby. Each node uses its own detection interface
connections.
Each node stores duplicate data that the Network Security console handles
according to the precedence order. For exclusive actions, all nodes within the
group communicate to determine the active node. Both the primary node
and the standby node detect and report on incidents and events.
The standby node processes the same data, performs the same analysis, and
evaluates the same response rules as the active software or appliance node,
but does not execute duplicate responses.