If my post was useful accept solution and/or give kudos.
Any opinions expressed here are solely my own and not necessarily that of HPE or Aruba.
Original Message:
Sent: Feb 26, 2025 11:19 AM
From: chulcher
Subject: Client Roaming - Multiple Clusters in Central
https://arubanetworking.hpe.com/techdocs/aos/aos10/migrate/
------------------------------
Carson Hulcher, ACEX#110
Original Message:
Sent: Feb 26, 2025 11:09 AM
From: ap1010
Subject: Client Roaming - Multiple Clusters in Central
Thanks Carson,
Will look into that. Any links on a guide for migrating AOS8 to 10 in Central?
Original Message:
Sent: Feb 26, 2025 11:02 AM
From: chulcher
Subject: Client Roaming - Multiple Clusters in Central
If you want an AP only deployment of greater than 128 APs, I would highly recommend looking at moving to AOS 10. You're already managed in Central, making the move should be relatively simple.
------------------------------
Carson Hulcher, ACEX#110
Original Message:
Sent: Feb 26, 2025 10:46 AM
From: ap1010
Subject: Client Roaming - Multiple Clusters in Central
Thanks Carson,
That is what I had understood as well, but when I brought this up with TAC on options for l2 roaming between clusters, I was directed to configure the L3 Mobility which I had doubts and hence brought this up in the community.
Original Message:
Sent: Feb 26, 2025 10:32 AM
From: chulcher
Subject: Client Roaming - Multiple Clusters in Central
The point of L3 mobility, which you are trying to configure here, is that the L2 domain and IP network is different for each of the clusters while the SSID is the same.
Also, you should never have multiple IAP clusters placing clients within the same L2 domain. Reusing the same VLAN ID shouldn't be an issue, but definitely should not have the same broadcast domain across multiple clusters.
------------------------------
Carson Hulcher, ACEX#110
Original Message:
Sent: Feb 26, 2025 10:25 AM
From: ap1010
Subject: Client Roaming - Multiple Clusters in Central
Thanks Carson,
If I am to use the client IP address, just trying to understand how that would work.
The SSID is the same over all 3 clusters, as well as the client subnets. So when adding the client subnets, out of the 3 VCs which VC do i use as I am not able to add the same client IP with the 3 VCs.
For Example :
SSID 1 : Subnet is 192.168.100.0/23 ( this SSID is over all 3 VCs )
I can add the subnet with the first VC, when trying to add the subnet with the 2nd VC I get the error "IP Address and Subnet Mask must be unique".
This is where I am doubting if the subnet is for the Clients or the subnet for the Access Points.

Original Message:
Sent: Feb 26, 2025 10:08 AM
From: chulcher
Subject: Client Roaming - Multiple Clusters in Central
Current URL: https://arubanetworking.hpe.com/techdocs/central/latest/content/nms/access-points/cfg/l3-mobility/ip_mobility.htm
As per the documentation, you use the client subnets.
Also, unless you are running on unsupported hardware, you'd probably be better off moving to AOS 10 where we can scale an AP only network to 500 APs / 5000 clients and not have to deal with L3 mobility between IAP clusters.
https://arubanetworking.hpe.com/techdocs/aos/aos10/design/ap-only/
------------------------------
Carson Hulcher, ACEX#110
Original Message:
Sent: Feb 25, 2025 11:56 AM
From: ap1010
Subject: Client Roaming - Multiple Clusters in Central
Hi, looking for some assistance in understanding the configuration to be done here to have seamless roaming for clients when there are multiple clusters.
I currently have 3 clusters, each with 80 or so access points. All access points broadcast the same SSID and clients joining the SSID get an IP from the same subnet.
As per this guide (Configuring Mobility for Clients), I would like to know what IP/Subnets I would add in the Subnet portion. Would it be the Subnet of the Access Points from all 3 clusters, or would it be the subnet the client receives after joining the SSID?
