Clustering IAPs
When IAPS are clustered together, they share the same configuration and offer the same wireless networks.
One IAP takes role as primary AP (virtual controller). If the primary fails, another IAP will take its place providing network stability.
You can configure the cluster from any of the IAP IP addresses.
The following are requirements to cluster IAPs.
- IAPs must be in the same VLAN and subnet. IAPs will not cluster if they are in a different network from each other.
- IAP cluster members must be from the same manufacturer. Dell PowerConnect W-IAPs only cluster with Dell PowerConnect W-IAPs, and Aruba IAPs only cluster with Aruba IAPS.
- IAPs must belong to the same region. US IAPs will not cluster with Rest of World IAPs.
- IAPs must be running the same code of firmware.
NOTE: If using the same class of IAPs, such as a 105 IAP clustering with another 105 IAP, they should synchronize the firmware automatically.
If using different classes such as a 105 IAP with a 225 IAP, you will need to manually update at least one IAP of each model.
If all of these conditions are met, IAPs will cluster automatically with each other by default. If powered on and able to reach each other, the IAPs will automatically cluster and choose their preferred primary AP, which acts as virtual controller. The first IAP to power on will act as primary AP. If you wish to alter which IAP acts as primary AP, perform the following before clustering.
- Click the access point in the web GUI.
- Click the Edit link
- In the General tab, under preferred primary, select Enabled.
- This IAP will then become primary AP and propagate its configuration to all other access points in the cluster.
If IAPs do not cluster together, ensure that auto join mode is not disabled (it is enabled by default).
- Navigate to System General > Show advanced options
- Select Enabled from Auto join mode if not already done
- Click ok