@cauliflower wrote:
Thanks Colin,
So are you saying that the AP will talk to the 'old' cluster address that it receives via DHCP, and only talk to a different cluster if it subsequently receives config (LMS IP or prov profile) from that cluster pointing it to the new cluster?
So would we configure a group on the existing cluster with a different provisioning profile/sys profile LMS address which points the AP to the new cluster? The AP would come up on the existing cluster as normal, and then be moved to the new cluster by that method? That could be fine I guess, it just wasn't quite how I was picturing it.
I was imagining a scenario where the AP would never talk to the existing cluster, it would just come up on the new cluster, but perhaps that's not the way to do this, or even possible.
A new AP will discover a controller using whatever method, DNS, DHCP option. If there is no LMS-IP in the AP group, it will stay on that controller/cluster. If there is an ip address in the LMS-IP in the ap-group, it will immediately go to the controller/cluster at that ip address.
The big question is, why would you want to redirect an AP to a foreign cluster? DHCP option 43 was built to direct an AP to its nearest local cluster when DNS is not specific enough....