Netgear WC7500-Wireless User Manual - Page 298

Requirements and Restrictions for N:1 Redundancy, Example of an N:1 Redundancy Configuration

Page 298 highlights

ProSAFE Wireless Controller When the primary controller that went down and for which the redundant controller took over comes back up and is stable, a switchback occurs automatically, in which case ownership of the controller IP address is returned to the primary controller that came back up. The redundant controller reassumes its passive position, and redundancy is once again available for all primary controllers in the redundancy group. Note: When a redundancy failover occurs, WiFi clients might experience a service interruption of a few seconds. Requirements and Restrictions for N:1 Redundancy These are the requirements and restrictions for N:1 redundancy to function correctly: • All controllers in a redundancy group must be in the same management VLAN and IP subnet. • The primary controllers must be stacked. • If three or four controllers are in the same redundancy group, you must configure one controller as the redundant controller and all other controllers as primary controllers. • All controllers in the redundancy group must run the same firmware version. If the firmware versions do not match, redundancy does not work. • The licenses on the redundant controller must match those on the primary controller that supports the largest number of licenses. For example, in a redundancy group with two primary controllers, if one primary controller supports a license for 10 access points and the other primary controller supports a license for 50 access points, the redundant controller must support a license for 50 access points. If the licenses do not match, redundancy does not work. • For the relationship of each primary controller with the redundant controller, you must configure a unique VRRP ID that is also different from any other VRRP IDs that might be used for other purposes in the network. You also must configure a unique local controller IP address for each controller in the redundancy group. • When a failover occurs and the redundant controller takes over for a primary controller, redundancy is no longer available for the other primary controllers in the redundancy group. Example of an N:1 Redundancy Configuration The following figure shows an N:1 configuration with three stacked controllers and one redundant controller before a failover occurs. Manage Stacking and Redundancy 298

  • 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

Manage Stacking and Redundancy
298
ProSAFE Wireless Controller
When the primary controller that went down and for which the redundant controller took over
comes back up
and
is stable, a switchback occurs automatically, in which case ownership of
the controller IP address is returned to the primary controller that came back up. The
redundant controller reassumes its passive position, and redundancy is once again available
for all primary controllers in the redundancy group.
Note:
When a redundancy failover occurs, WiFi clients might experience a
service interruption of a few seconds.
Requirements and Restrictions for N:1 Redundancy
These are the requirements and restrictions for N:1 redundancy to function correctly:
All controllers in a redundancy group must be in the same management VLAN and IP
subnet.
The primary controllers must be stacked.
If three or four controllers are in the same redundancy group, you must configure one
controller as the redundant controller and all other controllers as primary controllers.
All controllers in the redundancy group must run the same firmware version. If the
firmware versions do not match, redundancy does not work.
The licenses on the redundant controller must match those on the primary controller that
supports the largest number of licenses. For example, in a redundancy group with two
primary controllers, if one primary controller supports a license for 10 access points and
the other primary controller supports a license for 50 access points, the redundant
controller must support a license for 50 access points. If the licenses do not match,
redundancy does not work.
For the relationship of each primary controller with the redundant controller, you must
configure a unique VRRP ID that is also different from any other VRRP IDs that might be
used for other purposes in the network. You also must configure a unique local controller
IP address for each controller in the redundancy group.
When a failover occurs and the redundant controller takes over for a primary controller,
redundancy is no longer available for the other primary controllers in the redundancy
group.
Example of an N:1 Redundancy Configuration
The following figure shows an N:1 configuration with three stacked controllers and one
redundant controller before a failover occurs.