Bump LW AP's From One Controller To Another... Quickly... Easily... and Gracefully
Okay... so this one might be a little more difficult to grasp, at least at first... Follow the instructions below and it should come together. This one took me a few tries before I got it right, but now it's my secret weapon when it comes to roaming LWAP's back and forth across WLC's, especially when I need to minimize end user detectability and do it very "gracefully".
Go into the WLC CLI and issue:
Sho ap summary
This will list all the AP’s currently associated to that controller
(If you do this in MS command prompt you can highlight and copy just the AP names from the output, leaving the rest)
Next, apply those ap names to the Excel sheet attached below and then edit it so you have:
1) new primary and/or secondary controller name and IP address
2) AP names copied from the controller pasted into the correct excel column
I use this often for roaming AP’s back and forth across controllers for things like code upgrades or for testing, and I never hear complaints from the users on the floor especially if I grab AP’s across different depts, so not all the AP’s in 1 area roam at the same time.
*** 1 thing to note, If the code level is different between the controllers, you should pre-load the new code onto the AP before making it roam. This will still cause an interruption (about 60 seconds) because the AP has to reboot, but it is much less than it downloading the new code and rebooting after the roam (several minutes).
***Also make sure you have enough room on the new controller for the AP’s to roam to or they’ll “hang” for a minute and eventually move to the secondary one :-)
Okay... so this one might be a little more difficult to grasp, at least at first... Follow the instructions below and it should come together. This one took me a few tries before I got it right, but now it's my secret weapon when it comes to roaming LWAP's back and forth across WLC's, especially when I need to minimize end user detectability and do it very "gracefully".
Go into the WLC CLI and issue:
Sho ap summary
This will list all the AP’s currently associated to that controller
(If you do this in MS command prompt you can highlight and copy just the AP names from the output, leaving the rest)
Next, apply those ap names to the Excel sheet attached below and then edit it so you have:
1) new primary and/or secondary controller name and IP address
2) AP names copied from the controller pasted into the correct excel column
- Now, Highlight 15 or 20 lines at a time and Copy and Paste the commands from the Excel sheet into the CLI of the controller. (For some reason it’ll paste it in a little strange, but the end result works. If you merge the cells together you’ll loose the ability to go back and edit the individual columns again later)
- The AP’s will then roam to their new primary controllers, and will do so quite gracefully. Sometimes it takes a couple minutes for the AP’s to roam, and I believe this is because they are trying to off-load their clients... Just give it a little patience.
- Then when you're done & you want to roam them back, you just edit the appropriate columns again, and do it once more, on the controller they are now associated to.
I use this often for roaming AP’s back and forth across controllers for things like code upgrades or for testing, and I never hear complaints from the users on the floor especially if I grab AP’s across different depts, so not all the AP’s in 1 area roam at the same time.
*** 1 thing to note, If the code level is different between the controllers, you should pre-load the new code onto the AP before making it roam. This will still cause an interruption (about 60 seconds) because the AP has to reboot, but it is much less than it downloading the new code and rebooting after the roam (several minutes).
***Also make sure you have enough room on the new controller for the AP’s to roam to or they’ll “hang” for a minute and eventually move to the secondary one :-)
XLS template below:
ap_primary_secondary_script_-_good_template-1.xls | |
File Size: | 39 kb |
File Type: | xls |