APs not associating after WLC upgrade

[A_Marquez]

We upgraded our 5508 WLC from 8.3.143 to 8.5.151 base image which went fine, all of the APs rebooted and had the new image. I then realized we also needed the supplementary image for our one 1572 external AP and performed the same steps as I did with the base image but after rebooting the controller only around 40 out of 200 APs are currently associated with the controller. I've waited for a little over an hour now and still no change, any ideas as to why these APs suddenly won't associate now? They are all CAP3702I APs with the exception of the one 1572 that the supplemental image was downloaded to the controller for. 

[Scott Fella]

You try bouncing the ap port and or bouncing the wlc again?

[A_Marquez]

Haha when I'd seen you replied to this post too I figured that was gonna be asked. I did try rebooting the WLC and shutting/no shutting the ports but nothing changed. What the problem ended up being was that we have an A record in our DNS that points to a completely different controller at a location that the APs can't see. Once I changed that record to point to the  IP address of the controller at their same location the APs associated correctly...well most of them. I'm still having a hard time getting our 1572 to associate. 

It has an IP address and I can ping it fine from the controller and it even shows up in the controller under "show ap image all" but it still has the old 8.3.143 image so my guess is that it's not downloading the new image from the controller for some reason.

[Leo Laohoo]

---

@A_Marquez wrote:

but it still has the old 8.3.143 image so my guess is that it's not downloading the new image from the controller for some reason.

---

We've seen this behaviour before.  The only way to fix this is to remote into each APs and delete the old CAPWAP IOS folder.  

Remote into one of the APs and post the complete output to the command "dir".

[A_Marquez]

A simple reload managed to fix this AP as well. I forgot that shut/no shut won't accomplish that since it's connected to a PoE injector.