Relocate the existing Controller or setup a new controller

[gamane]

Hi Everyone,

We have an existing Wireless Controller(AIR-CT5508-K9) in one of our Data center and this controller services 60 AP spreadout accross six different sites/ offices.

Note that the existing data center where the controller is located will be decomisionned so we are planning to relocate the existing controller or setup a new controller..

Question number 1: If we are to set up a another controller fron a new data center then copy the config from the existing controller then migrate the APs one by one to new controller, would this be feasible?

Question number 2: How long APs can function controller less?

Thanks,

gamane

[Rich R]

Basically, yes you can do that.  That's really what N+1 HA is.

I've already answered your question about configuring the AP pri/sec above:
https://community.cisco.com/t5/wireless/relocate-the-existing-controller-or-setup-a-new-controller/m-p/4841752/highlight/true#M256250
If you want to move them you change the primary and secondary WLC setting on the AP then wait for it to move or reset it to force it straight away.  If you want users to be able to roam properly between APs on both WLCs then you need mobility configured between the WLCs.

You probably need to read more about N+1 AP config:
https://www.cisco.com/c/en/us/td/docs/wireless/controller/8-5/config-guide/b_cg85/ap_connectivity_to_cisco_wlc.html#backup-controllers

[gamane]

@JPavonM @marce1000 @Rich R , Appreciate all your feedback from all my previous inquiries. Just a quick question though about this commands;

1.  AP#capwap ap controller ip address x.x.x.x and 
2. AP#capwap ap primary-base WLC x.x.x.x

Do both of this commands force an AP to join a controller? and whats the difference between the two commands?

Thanks,

gamane