wlan poller used for migration working per AP

[majadobras]

Hello,

We have new cluster of 9800-80 controllers. We are migrating old APs from 8540 using wlan poller. However, when it comes to changing primary base and reload, we can see that primary base is set on APs and they reloaded, but only a few from a group actually migrate to new wlc. For example, we filter AP per name so that wlan poller applies commands on 10 APs. However, only 2 of them migrate to the new controller. When we repeat wlan poller, one more AP migrates and so on.

Filtering is done properly, we can see that when we test it with commands like 'show clock' and it is applied only on filtered set of APs.

Thanks!

[balaji.bandi]

what IOS XE code running on the Cat 9800 WLC and what AP Models you migrating ?

have you checked the one not Migrated in the Console Logs ? 

have this AP not moved to new WLC, still able to register with old WLC 8540 ?

[majadobras]

Cisco IOS XE Software, Version 17.09.03

For this specific occasion we migrated 10 x AIR-AP1832I-E-K9.

This is forwarded to all 10 APs using the poller:
capwap ap primary-base WLC9800-TKC x.x.x.x
%confirm% reload

Yes, the APs that are not moved to new WLC are still back in old WLC 8540. 
So in step by step it is something like: they all disappear from the old WLC 8540, only 1 or 2 are migrated on new one and the rest of them are back to old WLC 8540, in a short time. If you repeat the process again, then again 1 AP is migrated and the rest of them are not, and are back to old WLC. 

It is a strange behaviour then, we know that the poller is working, just not sure why is it selective and do it in batches. All AP models are the same.

[Leo Laohoo]

---

@majadobras wrote:
This is forwarded to all 10 APs using the poller:

capwap ap primary-base WLC9800-TKC x.x.x.x
%confirm% reload

---

I have successfully migrated 2000 x 4800 (batch 1) and another 5300 x 3700 (batch 2) from 8540 to 9800-80 and I've lost <5 x APs.  And I did all this without the use of the WLAN poller.  

The total outage time for migrating 4800 is 4 minutes and 45 seconds (per AP).  Each 2800/3800/4800/1560 takes 90 seconds to download the new IOS-XE firmware.

The outage time for migrating 3700 is about 24 minutes because of the "double download" bug.

If I use the WLAN Poller method, the outage time will take, I suspect, 11 minutes (minimum).  

My method are the following steps: 

1.  Instruct the WLC to tell the AP to manually upload the 17.9.3 firmware to each AP.  
2.  After the firmware has been uploaded, change the primary/secondary controller WLC details. 
3.  Immediately reboot the AP.

This means: 

1.  The AP will reboot into 17.9.3 (about 4 minutes and 45 seconds for COS AP)
2.  It will immediately join the new 9800 controller. 

[majadobras]

That's impressive. So I guess you've used a custom script for that? Do you have any online stuff that can help us achieve that? Thank you

[Leo Laohoo]

---

@majadobras wrote:
So I guess you've used a custom script for that?

---

Scripting?  Heck, no.  I wouldn't know how to write a script even if my life depended on it.  

---

@majadobras wrote:
Do you have any online stuff that can help us achieve that?

---

Yes, I have posted what I've done in this forum several times.   Here are the steps: 

1.  Download the file ap1g4-k9w8-tar.153-3.JPN2.tar and put in a TFTP server.  This file is only for the 1830.  (2800/3800/4800/1560 use a different file.)
2.  Get a list of APs.
3.  This step will tell the 8540 to instruct the AP to download the firmware but DO NOT reload: 

debug ap enable <AP NAME>
debug ap command "archive download-sw /no-reload tftp://<TFTP IP ADDRESS>/ap1g4-k9w8-tar.153-3.JPN2.tar" ap-name <AP NAME>

4.  Wait for the approximately 2 minutes. 
5.  Configure the new primary/secondary WLC details
6.  Instruct the 8540 to reboot the AP

config ap reset <AP name>
y

NOTE:  I do not have an idea if an 1830 will take 2 minutes to download the firmware so test this first before proceeding to the next steps.