In my case I was facing the same issue as everyone.
My_switch#copy tftp://18.104.22.168/sx300_fw-1413.ros image
Copy: Illegal software format
I was upgrading from 22.214.171.124 directly to the 1.4
After I download from the Cisco web site the intermediate version I can got sucessfull
Thanks a lot.
Jesus Christ. After hours of frustration I found your post. I was about to RMA this piece of crap. Upgrading firmware should not be this frustrating in 2017.
Wow I bought the switch with old firmware (need 100mb not GB) and I've spent many hours trying to solve this upgrade problem. Never in all the switches and firewalls I have programed have I had this much trouble.CLI, TFTP, HTTP it doesn't matter except for the boot code. You must have V126.96.36.199 installed before updating to V1.4.7.06.
Once I realized that you have to expand the ' 1 ' to get to download the V1.3 FW, then things started going right.
Many thanks to support community.
Thank you. I was having the same issue and had to step upgrade several times. Another reason I prefer enterprise switches over SMB ones. Unfortunately I still have some out there.
I understand that current upgrade it is a bit complicated but it is not always going to be the same challenge. Such a caution is usually communicated in release notes.
The reason for this is to accommodate bigger firmware with more additional features :-)
Same Problem here, I have an old 1.3.x on my SG300-28.My Problem is now, that I cant find the 188.8.131.52 Firmware, it Looks like Cisco has removed it from the download.
Without the iterim release, I can't upgrade anymore...
Anyone know where I can download the 184.108.40.206 or can send it to me?
Thanks for the info above. I was able to install the V220.127.116.11 ros file via http/https but cannot upload the boot loader via that option.
Our boot version is 1.1 and want to update it to 1.3.506 before 1.4x. I tried TFTP and entered the ip of the server and file name of the rfb in UNC format. I got the message download in progress, processing data banner, but copy failed TFTP server unreachable.
What is the easiest way to get the boot loader updated? The files are on the file server or could be located anywhere that's easiest
I'd recommend you always use the CLI to TFTP.. Seems to be easier on the SMB boxes. For example if your TFTP server was 10.7.8.9..
copy tftp://10.7.8.9/my_boot.rfb boot
Make sure your TFTP Server service is running on your server too, and that you don't have any Windows firewalls blocking TFTP. Solarwinds.net do a great free TFTP server if you need one.
I am following the same steps that you have mentioned and I am able to transfer some firmware file data but after exact same amount to byte transfer it stops working and gives me illegal software format error.
Could you please help me to find out the cause of this issue?