With virtual controller (conductor), do you mean one IAP being the virtual controller? Or do you have a separate virtual controller?
Assuming all is Instant, any AP can be the VC; so if you remove the VC from the old building, another AP will take over; and regardless which IAP from the existing cluster you power up in the new building, it will become VC there. This works all nicely if you use DHCP in the untagged/native VLAN for your Instant APs. If you changed management VLAN, or use static IPs, that may be the reason for seeing problems. If APs are not showing up, make sure auto-join is enabled on your Instant cluster.
If you have a separate controller things are completely different; but your ask is not fully clear around that.
------------------------------
Herman Robers
------------------------
If you have urgent issues, always contact your HPE Aruba Networking partner, distributor, or Aruba TAC Support. Check
https://www.arubanetworks.com/support-services/contact-support/ for how to contact HPE Aruba Networking TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or HPE Aruba Networking.
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: Jan 07, 2025 12:21 PM
From: JustShawn
Subject: AP's not rejoining Conductor Network
Hello,
We have several IAP-305's that we had in an Instant Mode network all controller by a single Virtual Controller (Conductor). We recently moved our physical office location and many of the AP's were being used standalone to get us out to the Internet while we built up our new office space. Well now that our move is done, I brought the Conductor AP to the new office and tried getting the old AP's to connect to it so I could manage them all again, but they won't connect. The new office uses a different network subnet than our old office had so I direct connected to the Conductor AP via a PoE injector and updated it's IP addresses to work with the new subnet. I reset some of the AP's that were running stand alone and they are not provisioning with the Conductor. I looked at AP Provisioning logs on the Conductor yesterday and saw some mention of Image Failing which looked to be firmware related, so I downgraded the firmware and then factory reset another AP to see if it would provision properly and it looked like it was working, but that AP is still not showing up in the Conductor's Managed AP list. We don't use cloud management at all for these, just the Instant AP locally managed network setup and they were working together just fine before our move.
I appreciate any thoughts or input you can provide. Thanks