Netgear WC7520-Wireless Reference Manual - Page 161

Requirements and Restrictions for N:1 Redundancy

Get Netgear WC7520-Wireless PDF manuals and user guides View all Netgear WC7520-Wireless manuals
Add to My Manuals
Save this manual to your list of manuals

Page 161 highlights

ProSafe 20-AP Wireless Controller WC7520 has a redundancy relationship with a primary controller. You need a unique VRRP ID for each relationship. Each controller in the redundancy group has a unique controller IP address and a unique local IP address. Local addresses remain constant so a controller can always be identified before and after a failover. If the primary controller fails or is disconnected from the network, an automatic failover to the redundant controller occurs. The redundant controller then takes ownership of the controller IP address of the primary controller and takes over all functions of the primary controller. After a failover has occurred, there is no longer any redundancy available for the other primary controllers in the redundancy group. 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, wireless 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 need to be in the same management VLAN and IP subnet. • The primary controllers need to be stacked. • If three or four controllers are in the same redundancy group, you need to configure one controller as the redundant controller and all other controllers as primary controllers. • All controllers in the redundancy group need to run the same firmware version. If the firmware versions do not match, redundancy does not work. • The licenses on the redundant controller need to match those on the primary controller that has the largest number of licenses. For example, in a redundancy group with two primary controllers, if one primary controller has a license for 20 access points and the other primary controller has a license for 50 access point, the redundant controller needs to have a license for 50 access point. If the licenses do not match, redundancy does not work. • For the relationship of each primary controller with the redundant controller, you need to configure a unique VRRP ID, also in relation to any other VRRP IDs that might be used for other purposes in the network. You also need to configure a unique local controller IP address for each controller in the redundancy group. Managing Stacking and Redundancy 161

  • 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
Managing Stacking and Redundancy
161
ProSafe 20-AP Wireless Controller WC7520
has a redundancy relationship with a primary controller. You need a unique VRRP ID for each
relationship.
Each controller in the redundancy group has a unique controller IP address and a unique
local IP address. Local addresses remain constant so a controller can always be identified
before and after a failover. If the primary controller fails or is disconnected from the network,
an automatic failover to the redundant controller occurs. The redundant controller then takes
ownership of the controller IP address of the primary controller and takes over all functions of
the primary controller.
After a failover has occurred, there is no longer any redundancy available for the other
primary controllers in the redundancy group.
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, wireless 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 need to be in the same management VLAN and IP
subnet.
•
The primary controllers need to be stacked.
•
If three or four controllers are in the same redundancy group, you need to configure one
controller as the redundant controller and all other controllers as primary controllers.
•
All controllers in the redundancy group need to run the same firmware version. If the
firmware versions do not match, redundancy does not work.
•
The licenses on the redundant controller need to match those on the primary controller
that has the largest number of licenses. For example, in a redundancy group with two
primary controllers, if one primary controller has a license for 20 access points and the
other primary controller has a license for 50 access point, the redundant controller needs
to have a license for 50 access point. If the licenses do not match, redundancy does not
work.
•
For the relationship of each primary controller with the redundant controller, you need to
configure a unique VRRP ID, also in relation to any other VRRP IDs that might be used
for other purposes in the network. You also need to configure a unique local controller IP
address for each controller in the redundancy group.