As Carson identified, you are running Instant cluster. Each Instant cluster needs to be in it's own VLAN. This can complicate your separation efforts.
Original Message:
Sent: Oct 10, 2025 02:25 AM
From: chulcher
Subject: Creating new cluster in Aruba Central
If the firmware version starts with 8, then you're running HPE Aruba Networking Instant AOS-8.
If you have questions about AOS 10 or about upgrading, please contact your local HPE Aruba Networking account team for some guidance. There are also some videos and other resources on the subject.
------------------------------
Carson Hulcher, ACEX#110
------------------------------
Original Message:
Sent: Oct 10, 2025 02:16 AM
From: yeowkm
Subject: Creating new cluster in Aruba Central
how do i check i am running on instantOS or AOS 10 ?
Original Message:
Sent: Oct 10, 2025 12:13 AM
From: chulcher
Subject: Creating new cluster in Aruba Central
If you're running that many APs in a single building and already using Central for management, then you should be looking at a migration to AOS 10 rather than continuing on InstantOS.
https://arubanetworking.hpe.com/techdocs/aos/aos10/migrate/
------------------------------
Carson Hulcher, ACEX#110
Original Message:
Sent: Oct 09, 2025 09:11 PM
From: yeowkm
Subject: Creating new cluster in Aruba Central
ours is hospital environment.
it started of with 50 AP303. due to increase demand for WIFI connections, we expanded to installing 1 AP in each patient room. now we have more than 170 units covering the whole building of 7 storeys. our firmware version for the AP is 8.6.0.xxx.
Original Message:
Sent: Oct 09, 2025 06:06 PM
From: ariyap
Subject: Creating new cluster in Aruba Central
Ideally it should be less than 128x APs in an Instant cluster. note that Instant cluster are running AOS8.x firmware not to be confused with AOS10 APs.
If you want to create two Instant clusters then you should create a second group with appropriate configuration and move your instant APs to the second group.
the main thing is that the two instant clusters should have different mgmt VLAN so that they do not have L2 adjacency, otherwise they will end up in the same cluster.
it is best to group the APs in a cluster based on geographical boundary.
------------------------------
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.