OK, I was following that methodology, and making reasonable progress, but now I've run in to a mystery.
I got to 4.2.205.0, but new 1242 AP still wouldn't connect successfully to the controller.
I did "debug lwapp events enable", saw that the first error was "Refusing image download to AP 64:00:f1:d5:94:f5", googled that, found a forum message regarding that error when attempting to connect a 1252 that said you had to upgrade further.
Upgraded to 4.2.209.0, for which there is NOT an associated boot image.
1242 still wouldn't connect, so upgraded again to 5.0.148.0. Rebooted, now the 1242 AP connects.
I'm doing this with just 2 APs, a 1131 and a 1242. But I've been shutting down the ports they're on during image download and controller reboot.
So I shut down the AP ports, and proceed to download the 5.0.148.0 boot image. Reboot the controller, ssh in, do "sh sysinfo". Sadly, boot image is still reported as 4.2.205.0.
Thought maybe there was just a blip having to do with 5.0.148.0, so proceed with Primary and Boot image download and reboot for version 5.0.148.2.
In all cases the GUI shows appropriate messages before telling me to reboot, GUI also gives me the "Save and Reboot" button, the tftp server (tftpd32) says the file transfer was successful
However, no joy - still stuck on boot 4.2.205.0. Here's what "sh sysinfo" looks like:
Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 5.0.148.2
RTOS Version..................................... Linux-2.6.10_mvl401
Bootloader Version............................... 4.2.205.0
Build Type....................................... DATA + WPS
And here's "sh boot":
Primary Boot Image............................... Code 5.0.148.2 (active)
Backup Boot Image................................ Code 5.0.148.0
Any suggestions on what I can do to get the box to recognize the proper boot version? This is a 4402...
Thx!
