- @jescobedo There is more then one IP address used on a 9800 controller, if you change the address of the Wireless Management Interface (WMI) then all access points must restart and the controller discovery mechanism must be updated accordingly. AP address changes are better done with DHCP configuration changes for the access points (subnet) , because DHCP is the preferred mechanism for providing network addresses for access points.
M.
-- Let everything happen to you Beauty and terror Just keep going No feeling is final Reiner Maria Rilke (1899)
In this case client is using static IP addresses and we are moving them to DHCP. What I will be doing is use the current cfg file from the WLC and modified it to reflect the new IP addresses and break the HA SSO so I can update the both WLC with new hostnames and IP addresses.
IMO the answer of this question lies in the discovery mechanism your APs are using to find the WLC. If you are using DHCP Option 43/DNS - only , then post changing the WLC Hostname and WMI IP address, you can reload the APs in batches so that the APs can get the new WLC details through discovery process. Again if you have 100+ APs or APs scattered among lots of switches, this might not be a scalable solution. If you have done manual priming to tell APs which WLC to join, then create a script with command 'ap name <ap name> controller primary <new wlc name> <new wlc wmi address>' and run that script in WLC. To validate quickly you can run again 'show ap config general | in Cisco AP Name|Primary Cisco Controller Name|Primary Cisco Controller IP Address'. Once validated change the hostname and WMI IP address. If you are not doing anything and APs are finding WLC in local subnet, your job becomes easy. Assuming you will change the WLC WMI to an another IP on same subnet, then just change the WLC hostname and IP address. APs will figure out the WLC.
Learn, share, save
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
