Hi
I can find the following in the Aruba Instant Manual:
Each Instant AP model has a minimum required software version. When a new Instant AP is added into an
existing cluster, it can join the cluster only if the existing cluster is running at least the minimum required
version of that Instant AP. If the existing cluster is running a version prior to the minimum required version of
the new Instant AP, the new Instant AP will not come up and may reboot with the reason Image sync fail. To
recover from this condition, upgrade the existing cluster to at least the minimum required version of the new
Instant AP first, and add the new Instant AP. For more information about supported Instant AP platforms,
refer to the Aruba Instant Release Notes
azar.
So the cluster has to be updated to 8.4.0.0 in order for the new AP to be able to join. The problem for you here is that your older IAP 135 cannot be updated to 8.4.0.0. I don't see this model in the list of supported platforms for 8.4.0.0
Maybe the only solution is to put all the IAP515 on a different subnet and manage them as a separate cluster
omegleshagle.
------------------------------
Linda Xlie
------------------------------
Original Message:
Sent: Oct 08, 2021 02:12 AM
From: Shivam Ojha
Subject: Iap 315 and 515 joining same virtual cluster
Hello team,
I want to know if Aruba 315 and 515 will join the cluster.
And what are the range of firmware which will join the same cluster?
------------------------------
Shivam Ojha
------------------------------