Topic Includes: I bricked my SRW2024 switch by installing the 1.2.2b firmware straight-away.
I was able to "unbrick" it yesterday. I found a version of the 1.0.0.86 code on some obscure FTP server. Additionally, I used a very old Compaq Armada laptop running XP32 to connect to the SRW2024 switch (via hyperterminal) and a native COM port versus a USB to COM port connection that was on a Vista32 machine that was much newer. MSDOS, Xmodem, Ymodem, Zmodem will always have their usefulness (yes, this does show my age).
The long transfer time went A-OK and I'm not certain if it was the native COM port, older OS, or what that made it succeed. The filename was runtop-10086.ros. Also available were runtop-10059 and runtop-10057. But, I knew that my original was 10086.
After the xmodem download, the switch went through its routine (unpacking, EEPROM erasure, reprogramming, the whole bit) and everything went back to the way it was. This means the console screen went back to:
Versions:
Boot Version: 1.0.0.03 (Date: 08-Jun-2004, Time: 09:48:10)
Software Version: 1.0.0.86 (Date: 03-Oct-2005, Time: 15:00:31)
Hardware Version: 00.00.03
Plus, all of my settings were intact (userID, PW, switch name, etc).
NOW, after all of this hassle, what is the correct way to upgrade the software of this switch?
I see in the Web UI under "Maintenance -> File Download" a check box for "Firmware." Looks good.
A TFTP server IP address is needed. No problem. A source file name is needed. OK. Destination file name and the choices are "SOFTWARE IMAGE" OR "BOOT CODE" in the drop-down selection box. So, which gets sent FIRST (the boot code file and what is that?) and then reboot and upgrade the software image to the 1.2.2b version? Is that the correct procedure and what are the files?
Now, after all of this, if the new boot code and new software do not provide for better reliability (this thing has been rock solid with the 1.0.0.86 code), functionality, security, and then speed, I'll just leave it at 1.0.0.86.
Let me know what you think.
Thanks.
