WISM1 cannot upgrade firmware

Question

Hello,
I'm having an issue upgrading a Cisco WISM (just a WISM1), we had one of these line cards fail and we got a replacement.  The replacement comes with 2 firmware releases, one of which is the minimum required for compatibility with VSS on a 6500 (which we have.) 
Here's the information for the 6506:
Cisco IOS Software, s2t54 Software (s2t54-IPSERVICESK9-M), Version 15.1(1)SY, RELEASE SOFTWARE (fc2) <<< supports the WISM
The boot images the WLC came with are:
Primary Boot Image............................... Code 3.2.78.0
Backup Boot Image................................ Code 3.2.171.6 (active) <<< VSS compatibility on a 6500 series switch
(3.2.171.6 is the release which first supports VSS.  As you can see i've made this backup image active.)
I have been attempting to upgrade the firmware image, i've used several tftp servers (on different boxen, all with the host firewall disabled) - Pumpkin 2.7.3, the latest TFTPD32/64 and the latest (10.something, > 32 MB file support was introduced in an earlier release) Solarwinds TFTP server.  Neither of these work, it stops at 32 MB (with the possible exception of Pumpkin there is no question the latter support > 32 MB, I use these products all the time to upload larger IOS images and what-not.)
We're trying to get to 6.0.196.0, after failing I tried 4.2.176.0 as an intermediate upgrade instead but received the same error (below.)
Here's the debug log:
Thu Mar 13 19:38:29 2014: RESULT_STRING: TFTP Code transfer starting.
Thu Mar 13 19:38:29 2014: RESULT_CODE:1
TFTP Code transfer starting.
Thu Mar 13 19:38:32 2014: Still waiting!  Status = 2
Thu Mar 13 19:38:33 2014: Locking tftp semaphore, pHost=<omitted> pFilename=SWISMK9-4-2-176-0.aes
Thu Mar 13 19:38:33 2014: Semaphore locked, now unlocking, pHost=<omitted> pFilename=SWISMK9-4-2-176-0.aes
Thu Mar 13 19:38:33 2014: Semaphore successfully unlocked, pHost=<omitted> pFilename=SWISMK9-4-2-176-0.aes
Thu Mar 13 19:38:33 2014: TFTP: Binding to local=0.0.0.0 (***Is there some way to bind this to the WISM management IP?***) remote=<omitted>
<snip>
Thu Mar 13 19:20:14 2014:  33684480 bytes
Thu Mar 13 19:20:14 2014:  33715440 bytes
Thu Mar 13 19:20:14 2014:  33746400 bytes
Thu Mar 13 19:20:15 2014:  33777360 bytes
Thu Mar 13 19:20:15 2014:  33808320 bytes
Thu Mar 13 19:20:15 2014: TFP End: 516 bytes transferred (1 retransmitted packets)
Thu Mar 13 19:20:15 2014: tftp rc=0, pHost=172.31.118.250 pFilename=SWISMK9-4-2-176-0.aes
              pLocalFilename=/mnt/download/local.tgz
Thu Mar 13 19:20:15 2014: tftp = 6, file_name=SWISMK9-4-2-176-0.aes, ip_address=<omitted>, msg=Unknown error - refer to log
Thu Mar 13 19:20:15 2014: upd_get_code_via_tftp = 6 (target=268435457 msg=Unknown error - refer to log)
Thu Mar 13 19:20:15 2014: RESULT_STRING: TFTP receive complete... extracting components.
Thu Mar 13 19:20:15 2014: RESULT_CODE:6
TFTP receive complete... extracting components.
Thu Mar 13 19:20:17 2014: Still waiting!  Status = 2
Thu Mar 13 19:20:19 2014: RESULT_STRING: TFTP Failure while storing in flash!
Thu Mar 13 19:20:19 2014: RESULT_CODE:7
TFTP Failure while storing in flash!
Thu Mar 13 19:20:20 2014: Still waiting!  Status = 2
Thu Mar 13 19:20:23 2014: ummounting: <umount /mnt/download/>  cwd  = /mnt/application
Thu Mar 13 19:20:23 2014: finished umounting
Here are the settings i'm using (note that it's all at the TFTP root, the path is blank but it does grab the file ... using "./" as the path makes no difference.):
Mode............................................. TFTP
Data Type........................................ Code
TFTP Server IP................................... <omitted>
TFTP Packet Timeout.............................. 254 (not default, set for troubleshooting)
TFTP Max Retries................................. 254 (not default, set for troubleshooting)
TFTP Path........................................
TFTP Filename.................................... SWISMK9-4-2-176-0.aes
Again, it appears that the tftp server does not support files > 32 MB (the docs i've read say that this error message is supposed to indicate exactly that), but it 100% *does* support larger files.  What could be causing the transfer to time out?  Is there some limitation on the controller which prevents large files being delivered via TFTP (and if so, is there a way around that?)  Also, there seems to be no other alternative other than TFTP (at least with the release i'm currently stuck at) ... or is there?
Thanks,
Jim

Answer 1

HI,
1. First try with 3CDaemon , I normally do with this .
2. If still fails then use anouther laptop or computer.
Regards
Dont forget to rate helpful posts