All Instant APs in an Instant Cluster in the same subnet need to run the same firmware release.
If you have to run different firmware releases, you will need separate clusters (so separate VLANs), or (some of) the APs will need to be converted to standalone mode (and managed independently).
What you see and describe follows these expectations.
------------------------------
Herman Robers
------------------------
If you have urgent issues, always contact your Aruba partner, distributor, or Aruba TAC Support. Check
https://www.arubanetworks.com/support-services/contact-support/ for how to contact Aruba TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.
In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
------------------------------
Original Message:
Sent: Aug 10, 2022 12:37 PM
From: Robert Großmann
Subject: Aruba IAP 635: How to choose the right IAP VC?
Hello,
We do have a IAP Virtual Cluster with around 100 IAP-215.
Now we have buyed 4 new Aruba AP-635.
With the first 635 I have created a new IAP VC, because it is not possible to use both series in one VC (210 Series stucks at SW 8.6, 630 Series requires 8.9).
But the other 635 does not join the new VC, but it looks like the AP tries to join the VC but fails because of the SW.
I disabled autojoin, but now the the message on the old VC is auto-join disabled. Thats right, I want to join the 635 APs at the new VC.
Old and new VC are in the same subnet, I do not want to add a new WLAN Management Network along our network.
When I open the 635 ip adress in a browser i get redirected to the old VC ip address.
Using the cli i got the promt:
94:64:24:c7:54:a2# conf t
Configuration is not allowed when CLI is running in a degraded state.
Anyone an idea how to add the new APs to the new IAP VC instead of the old, while using the same network (vlan/subnet)?
If it is anyhow possible to get out of the degraded state to configure the VC key and name manually, that would be a great step for a solution.
Using a separate network the AP is joing the new VC, but switching the VC and member AP back to the regular vlan, I got the same behaviour as described above :-(
Thanks and kind regards
Robert