WLC 5508 Failure to upgrade code - Page 2

pallipton · ‎12-15-2010

Hi,

I'm trying to upgrade a WLC 5508 and I'm getting the following errors:

TFTP Code transfer starting.

TFTP receive complete... extracting components.

Failure while validating the signature!

TFTP Failure while storing in flash!

The image is good and for the right model. Does anyone have any ideas?

RICHARD DUNN · ‎09-19-2011

I'm trying to go from 6.0.199.0 to 7.0.116.0 using tftpd32, and no, I didn't know you could/had to upgrade the bootloader. Thanks for the reply. I'll check into it.

Kayle Miller · ‎09-20-2011

Richard,

If you goto the CLI and do a show sysinfo it should give you a print out of the Bootloader version aswell as the firmware version. Then check the cisco support site for the latest firmware that has an -ER attached to the filename. That's the Emergency bootloader upgrade. If it was an older 6.x install from the start that could be the problem.

Hope this helps.

RICHARD DUNN · ‎09-20-2011

The bootloader version is 1.0.1.

firmware version FPGA 1.3, ENV 1.6, USB Console 1.27

The search for "emergency" or "er" at Cisco support turns up nothing

Leo Laohoo · ‎09-20-2011

Ok. That's bizarre. I must've been seriously mistaken when I thought the 5508 has a bootstrap available. Unfortunately for me, it doesn't.

Sorry Richard. I should've been more careful.

Can you check if the file you've downloaded is the correct one? Can you compare hash?

Kayle Miller · ‎09-21-2011

Leolaohoo,

I agree completely. I thought there was a bootloader as well.

I'd start looking at checksums next then.

Sorry

RICHARD DUNN · ‎09-21-2011

OK, I'm game. I'll try it, but I have no idea how to do that. I don't understand though why after almost 30 years in this business I would now have to check a hash. Anybody know how to do this?

Leo Laohoo · ‎09-21-2011

OK, I'm game. I'll try it, but I have no idea how to do that. I don't understand though why after almost 30 years in this business I would now have to check a hash. Anybody know how to do this?

Try Hash Tab (attached).

Kayle Miller · ‎09-22-2011

Richard,

a really stupid question, have you tried rebooting the controller and then immediately attempting to upgrade the firmware?

also have you tried going to 7.0.98.0 first then to the 7.0.116.0?

RICHARD DUNN · ‎09-22-2011

Not a stupid question. I was on the phone with Cisco all day. They tried everything, including an RTOS file download, which we attempted by 'ing the boot sequence with no luck. Bottom line is they are going to RMA me another (3rd) controller. I'll update this thread when I see what happens with it. Thanks all, for your input.

sean.pedersen · ‎09-22-2011

We're having the same problem. We have two 5508s, one of which is fine, the other is having the exact same issue as the OP described. We're trying to upgrade from 6.0.199.4 to 7.0.166.

* Multiple copies of 7.0.116 have been downloaded and verified on multiple machines.
* Also downloaded and attempted the last three code revisions with no success.
* MD5 hash matches.
* Multiple TFTP daemons used; SolarWinds, tftpd32, etc. Tried FTP as well.
* Tried from the GUI and the CLI.
* Tried an update and immediate reboot, no effect.
* Tried to hard boot the device (power switch off/on), no effect.

Sysinfo:

Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 6.0.199.4
Bootloader Version............................... 1.0.1
Field Recovery Image Version..................... 6.0.182.0
Firmware Version................................. FPGA 1.3, Env 1.6, USB console 1.27
Build Type....................................... DATA + WPS

...[truncated]...

Last few lines of a transfer debug:

*Jun 18 23:41:24.371: TFP End: 95403984 bytes transferred (0 retransmitted packets)
*Jun 18 23:41:24.371: tftp rc=0, pHost=[redacted] pFilename=/AIR-CT5500-K9-7-0-116-0.aes
pLocalFilename=/mnt/download/local.tgz
*Jun 18 23:41:24.372: tftp = 6, file_name=/AIR-CT5500-K9-7-0-116-0.aes, ip_address=10.52.15.100, msg=Unknown error - refer to log
*Jun 18 23:41:24.372: upd_get_code = 6 (target=268435457 msg=Unknown error - refer to log)
*Jun 18 23:41:24.372: RESULT_STRING: TFTP receive complete... extracting components.
*Jun 18 23:41:24.372: RESULT_CODE:6
TFTP receive complete... extracting components.
*Jun 18 23:41:27.065: Still waiting! Status = 2
*Jun 18 23:41:28.373: RESULT_STRING: Failure while validating the signature!
Failure while validating the signature!
*Jun 18 23:41:30.065: Still waiting! Status = 2
*Jun 18 23:41:32.375: RESULT_STRING: TFTP Failure while storing in flash!
*Jun 18 23:41:32.375: RESULT_CODE:7
TFTP Failure while storing in flash!
*Jun 18 23:41:33.065: Still waiting! Status = 2
*Jun 18 23:41:36.065: Still waiting! Status = 1
*Jun 18 23:41:36.376: ummounting: cwd = /mnt/application
*Jun 18 23:41:36.673: finished umounting

Cisco was not able to offer any advice other than an RMA. Unfortunately, we're stuck in limbo at the moment as the device waits for finance approval to join our current SNTP contract. Also working with the seller to obtain a replacement, but hoping to find a solution that doesn't require either.

Kayle Miller · ‎09-23-2011

Sean,

Are these new 5508's or have they been in production for awhile? If they have been in production for awhile have you previously been able to upgrade code on them??

The reason I am asking is this is beginning to sound like it might be a hardware revision issue with a batch of the controllers; or some funky bug in the code that doesn't like something on these controllers. I know there was an issue at one point where the code didn't like an AP mac address. So it could be something unique to those controllers.

sean.pedersen · ‎09-23-2011

They were purchased new and unopened, but the one that has issues we know was originally purchased in some format (by a distributor, etc.) around May 2010, acording to Cisco. I have the chassis next to me; I wasn't able to find anything obvious like a hardware revision number that might be useful.

Kayle Miller · ‎09-23-2011

I'd love to get my hands on one of these and dig into it a little, I have 2 coming and will have to see if they behave the same.. As I haven't seen one experience this to this level yet.

sean.pedersen · ‎09-23-2011

I wish we had the luxury of keeping this one around to fiddle with or to hand over to our ESE. We've also worked with a few of Cisco's wireless specialists on the west coast; they'd probably also like to have a look at it. Unfortunately, with just about everything here and elsewhere, we have to have a working solution up ASAP so this one has to go back.

RICHARD DUNN · ‎09-23-2011

I recieved 2 new in the box whose serial numbers were 4 characters apart, that would not upgrade or take an RTOS file. I just recieved my third from Cisco. I'll let you know how I make out.