Dell PowerConnect W Clearpass 100 Software 3.7 Deployment Guide - Page 353

Cluster Setup, Create New Cluster, Administrator > High Availability > Cluster, Configuration

Page 353 highlights

Table 27 Cluster Status Descriptions (Continued) The primary node is running, but the secondary node is down or stopped.  The secondary is no longer available. Check the Remote Status on the primary node to determine the cause of the problem.  To clear the error condition, bring the secondary node back online. The cluster will return to fault- tolerant mode automatically.  If the secondary node needs to be replaced, the cluster must be rebuilt. See "Recovering From a Hardware Failure" in this chapter. The secondary node is running, but the primary node is down or stopped.  The primary is no longer available. Check the Remote Status on the secondary node to determine the cause of the problem.  The cluster IP address is inaccessible and network services are unavailable.  Automatic failover will take place after the downtime threshold has been exceeded. The cluster services are starting. Check the detailed status information. The primary node is running, but a problem has been detected. Check the detailed status information. The primary node is running, but the secondary node is reporting a problem. Check the detailed status information. The cluster is recovering from a failure. Check the detailed status information. The cluster is currently being initialized. Check the detailed status information. Status call timed out. Server may be down. This message may be displayed if the node cannot be contacted. There may be a network issue affecting your management workstation, or the node may be offline.  Refresh your Web browser to check the connection to the node. If the problem persists, check the cluster status on the other node. Cluster Setup Before you begin, review this checklist to ensure you are prepared to set up a cluster:  You have two servers available.  Each server is powered up and connected to the same local area network.  Each server has a unique hostname.  Each server has a valid subscription ID and has been updated using the Plugin Manager. Ensure that the High Availability Services plugin has been installed along with any available plugin updates.  You are logged in as the administrator on each server.  You have determined the desired network configuration (virtual IP address) for the cluster. Click the Create New Cluster command link on the Administrator > High Availability > Cluster Configuration page to begin the process of creating a new cluster. Amigopod 3.7 | Deployment Guide High Availability Services | 353

  • 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
  • 393
  • 394
  • 395
  • 396
  • 397
  • 398
  • 399
  • 400
  • 401
  • 402
  • 403
  • 404
  • 405
  • 406
  • 407
  • 408
  • 409
  • 410
  • 411
  • 412
  • 413
  • 414
  • 415
  • 416
  • 417
  • 418
  • 419
  • 420
  • 421
  • 422
  • 423
  • 424
  • 425
  • 426
  • 427
  • 428
  • 429
  • 430
  • 431
  • 432
  • 433
  • 434
  • 435
  • 436
  • 437
  • 438

Amigopod 3.7
|
Deployment Guide
High Availability Services
|
353
Cluster Setup
Before you begin, review this checklist to ensure you are prepared to set up a cluster:
You have two servers available.
Each server is powered up and connected to the same local area network.
Each server has a unique hostname.
Each server has a valid subscription ID and has been updated using the Plugin Manager. Ensure that the
High Availability Services plugin has been installed along with any available plugin updates.
You are logged in as the administrator on each server.
You have determined the desired network configuration (virtual IP address) for the cluster.
Click the
Create New Cluster
command link on the
Administrator > High Availability > Cluster
Configuration
page to begin the process of creating a new cluster.
The primary node is running, but the secondary node is down or stopped.
The secondary is no longer available. Check the Remote Status on the primary node to determine
the cause of the problem.
To clear the error condition, bring the secondary node back online. The cluster will return to fault-
tolerant mode automatically.
If the secondary node needs to be replaced, the cluster must be rebuilt.
See
“Recovering From a
Hardware Failure”
in this chapter.
The secondary node is running, but the primary node is down or stopped.
The primary is no longer available. Check the Remote Status on the secondary node to determine
the cause of the problem.
The cluster IP address is inaccessible and network services are unavailable.
Automatic failover will take place after the downtime threshold has been exceeded.
The cluster services are starting.
Check the detailed status information.
The primary node is running, but a problem has been detected.
Check the detailed status information.
The primary node is running, but the secondary node is reporting a problem.
Check the detailed status information.
The cluster is recovering from a failure.
Check the detailed status information.
The cluster is currently being initialized.
Check the detailed status information.
Status call timed out. Server may be down.
This message may be displayed if the node cannot be contacted. There may be a network issue
affecting your management workstation, or the node may be offline.
Refresh your Web browser to check the connection to the node. If the problem persists, check the
cluster status on the other node.
Table 27
Cluster Status Descriptions (Continued)