Controller Based WLANs

Benefits of using RAP cluster support in 8.x

Aruba Employee

What are the advantages of configuring RAP for cluster support in 8.x?


Without Cluster

•  In earlier codes, RAP needed to be terminated on VRRP-IP or LMS/BKP-LMS needed to be configured for redundancy.
• Clients connected to the RAP will be deauthenticated when the AP fails over to a different controller.
• The above behavior impacts the client traffic.
• In addition to this, RAP needs to download entire configuration on every rebootstrap or failover.


With Cluster

Starting 8.x, RAPs support clustering which will help avoid the above scenarios.

• Classic cluster controller supports redundancy for both APs and clients
• Passive entry will be created on the standby controller when it is L2 connected.
• RAP will form tunnel with all the cluster members using same inner-ip for ease of management.
• Cluster is limited to max 4 nodes in case of RAP.

Client will not be deauthenticated when the RAP fails over and will continue to pass traffic since there was a dormant entry created on the standby controller.




Version history
Revision #:
1 of 1
Last update:
‎03-17-2017 04:09 PM
Updated by:



If we´re placing our RAPs on the internet and they reach central controllers via port forwards from public IPs on an external firewall. Will it be possible to utilize cluster functionality? Do we then specify the public IPs the RAPs need to use somewhere in the cluster configuration?




Search Airheads
Showing results for 
Search instead for 
Did you mean: 
Is this a frequent problem?

Request an official Aruba knowledge base article to be written by our experts.