How to configure Aruba controller clustering ArubaOS 8

How to configure Aruba mobility controller clustering

In this post, we will discuss how to configure controller clustering.

To form a cluster, we need to consider the following points:

All cluster members must have the same OS version.

We can’t form clusters with a virtual VMC and a hardware controller HMC.

Even though we can’t form clusters with different series models like 72XX and 70XX,

7200 Series controllers – Support for up to 12 nodes in a cluster.

7000 Series controllers – Support for a maximum of 4 nodes in a cluster.

9004 controllers – Support for a maximum of 4 nodes in a cluster.

9012 controllers – Support for a maximum of 4 nodes in a cluster

Mobility Controller Virtual Appliance – Support for a maximum of 4 nodes in a cluster.

Even with a 12-node cluster, the maximum supported APs and client counts are limited to 10K and 100K, respectively.

We can terminate RAP, CAP, and Mesh APs on cluster members.

Clustering has many benefits over the old HA method.

Clustering will provide you with a live device upgrade facility.

Clustering will provide AP and client load balancing.

Client Failover When a controller device fails, all the users fail over to their standby controller device seamlessly without any traffic disruption to their wireless connectivity.

Clustering provides seamless roaming.

We already have the controller added to MM and running. We will only do clustering configurations.

First, you need to create a profile and add a controller.

Here I have the user VRRP IP address for COA, but if you don’t have infrastructure setup with COA, then you can skip those configurations.

How to configure Aruba controller clustering ArubaOS 8
How to configure Aruba controller clustering ArubaOS 8
How to configure Aruba controller clustering ArubaOS 8

Specify the VRRP ID and key and click on submit and apply pending changes.

How to configure Aruba controller clustering ArubaOS 8

This feature supports CoA requests in a cluster using multiple VRRP instances.
The CoA request is not dropped when the UAC changes due to controller failure or client load balancing.

CoA is change of authorization, which is an extension to RADIUS attributes and capabilities.
CoA request messages are sent by a RADIUS server to a NAS device for dynamically modifying the existing session authorization attributes.
A CoA-Request contains the information for dynamically changing session authorizations.
If NAS is able to successfully change the authorizations of the user session(s), it responds with a CoA-ACK. Otherwise, it returns a CoA-NAK to the RADIUS server.

Multiple VRRP instances are created dynamically, with one instance per cluster node.
The cluster node is the master of that instance. In a cluster, the virtual IP of each VRRP instance is used as a NAS-IP when sending RADIUS requests to the RADIUS server.

The VRRP IDs for these instances are reserved and the reserved IDs range from 220 to 255.

for a cluster with 2 nodes, there are 2 VRRP instances and 2 virtual IP addresses. That is, One Virtual IP address for each VRRP instance.
The cluster uses the virtual IP for an instance as the NAS-IP in a RADIUS request. When the cluster node sends RADIUS requests on behalf of a client that is trying to authenticate a RADIUS server, It inserts the Virtual IP as the NAS-IP in that RADIUS packet.

Now we need to add cluster profile on each controller which is shown below.

How to configure Aruba controller clustering ArubaOS 8
How to configure Aruba controller clustering ArubaOS 8

it will take few min to show and synchronize the setting.

How to configure Aruba controller clustering ArubaOS 8
How to configure Aruba controller clustering ArubaOS 8

As we have discussed above, you can see two VRRP group instance has been created.

How to configure Aruba controller clustering ArubaOS 8
How to configure Aruba controller clustering ArubaOS 8

you can see, how your cluster is connected and other information.

How to configure Aruba controller clustering ArubaOS 8

Now we will configure the L2 redundancy.

How to configure Aruba controller clustering ArubaOS 8
How to configure Aruba controller clustering ArubaOS 8

We will use this IP address, 192.168.1.212, to terminate the AP on the controller ( Option 43 i.e. controller VIP 192.168.1.212 )

How to configure Aruba controller clustering ArubaOS 8
How to configure Aruba controller clustering ArubaOS 8

you can see here, Both Controller and conductor MM is exchanging the IPSEC packet(for data and communication).

How to configure Aruba controller clustering ArubaOS 8
How to configure Aruba controller clustering ArubaOS 8

Leave a Reply

Your email address will not be published. Required fields are marked *