06-27-2011 12:46 PM - edited 07-03-2021 08:21 PM
Hi All,
I have to upgrade a couple of 4400s to support 1142 APs.
The controllers currently support 1131s, and are on version 4.0.179.11. (I know, way back there...)
Seeing this huge gap between the level we're on and the most current version, thought I'd better find out what's recommended.
The available MD versions are 4.2 and 6.0
The available 4.2 versions are:
4.2.209.0(md)
4.2.207.0(md) (AssureWave)
4.2.205.0 BOOT (md)
4.2.205.0(md) (AssureWave)
4.2.175.0(md) (AssureWave)
4.2.130.0(md)
The next MD release is 6.0.202.0
Any thoughts on choosing the version to upgrade to most sincerely appreciated!
06-27-2011 01:11 PM
You don't need to upgrade the BOOT.
Just go for the last 4.0 (4.0.219 if my memory serves well ?), then the last 4.2.209 and then 6.0.202 and you're good to go !
06-27-2011 03:02 PM
And why stop at 6.0.202.0? Why not go to 7.0.116.0?
06-30-2011 07:42 AM
Hi Nicolas (or anyone),
Can you provide any additional info about the purpose of the BOOT image?
Upgrade instructions (Document ID: 68835) say for versions 4.1 and higher you upgrade the BOOT image after upgrading the Primary image.
But, in the Download Software area for this device, some versions have BOOT images, others do not.
Can anyone help clarify?
Thx!
06-30-2011 03:56 PM
You are right. Not all versions of firmware have a boot image (aka bootstrap). Bootstraps are the first thing a WLC will run on before running the firmware. The bootstraps also contain "patches" and it's important to run every one of the them even though you are not using that particular version. For example if you settle with using 6.X firmware make sure you run every bootstrap from 4.X to 6.X.
06-30-2011 04:42 PM
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!
06-30-2011 04:48 PM
Try to load the new 7.0.116.0. Don't forget the bootstrap.
06-30-2011 05:05 PM
Just to clarify, you're saying skip 5.1.x, 5.2.x, and 6.x?
(I see there's a boot image for 5.2.157.0...)
Many thanks for the help...
06-30-2011 05:12 PM
Load the bootstraps up to 7.X. Try using the 7.0.116.0 firmware.
12-08-2011 02:25 AM
Hi Leo,
One question about this subject (if possible):
We need to upgrade from 4.2.207 to 6.0.202 (we can't go to 7.0.x because we have 2700 location appliance and this is not supported at 7.x). At 6.0.202 release notes said that is necesary to have bootstraps 5.2.157.0-ER.aes but this version is older (Release Date: 24/NOV/2008) than 4.2.205.0-ER.aes (Release Date: 13/MAY/2009) our installed version.
Is it possible to use 4.2.205 instead of 5.2.157?
Thanks in advance.
12-08-2011 02:42 PM
Upgrade ALL the bootstraps. It is recommended.
12-09-2011 05:19 AM
Thanks for the reply,
but in our situation (plannig to upgrade to 6.x) the last bootstrap version at Cisco is
SWISMK9-7-0-220-0-ER.aes.
Please, could you recommend us to upgrade to bootstap 7.0.220.0.ER or 5.2.157.0.ER?
Thanks again.
12-09-2011 04:00 PM
If it were me, I'd load both. The bootstrap doesn't dictate what firmware you are running.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide