Bob,

I emailed you a document I wrote on the firmware update procedure. It includes some nice screenshots and the step-by-step procedure. Please post any replies regarding this procedure or problems to this forum thread.

Thanks Greg.  I was entering  the actual path of the .fir file in the TFTP Path/Filename option instead of just the filename.  I was not sure how the switch and the TFTP server were interactiing.  Thanks again.  Bob

Message Edited by scottrob on 04-05-2004 06:54 AM

Bob,

Any chance you could send me your firmware upgrade document? (remove the nospam from the address)

Thanks.

Hunter
phf12@nospammcsdk12.org

Greg,

I noticed that your upgrade instructions mention that switches are optimally upgraded when not stacked. Is it possible to upgrade them as a stack or not?

Hunter

The 3024/3048 switches cannot be updated as a stack. The firmware will not propogate from the root switch to the leaf switches in the stack. The only way to update the firmware for all switches in a stack is to unstack them and update each switch individually.

Note:  Using different firmware revisions in a stack can cause unwanted and unpredictable behavior.

The 3324/3348 family of switches has the ability to copy firmware images directly to any stack member or propogate the firmware image from the master switch to any leaf switch in the stack.

Can you send a copy to me, too?  Thanks.

 

Robspam@igive.com

 

Please remove spam.

This is a great document, thanks for sending it along.  Couple of questions:

1) Just to be sure, same basic instructions will work for 5224 Switch?

2) You specify both a null modem connection AND an ethernet connection.  Is that necessary? 

Thanks again.

Rob

1)  The firmware procedure is different for the 3248/5212/5224 models. With those models, you first copy the firmware to the flash via TFTP, then configure the switch to boot to the new firmware. The 3024/3048/5012 models actually boot from the TFTP server, then write the image to the flash.  If you have further questions/problems updating the firmware on a 5224, please submit a new post with a modified subject line.

2)  Since the switch must reboot to the TFTP server, the ethernet connection is absolutely necessary. The null modem cable is not necessary, but is recommended as it is the only way to view the output from the switch during the boot process. If any errors are reported and/or the firmware update fails, this is the only way to view the output.

Worked like a charm.  I think a big part of it was the TFTP server you recommend.

 

Thanks.

Can I get a copy of the 3048 firmware upgrade guide as well?

jackson@nospamonesullivan.com

please remove nospam

Thanks!

 

 

Hi, Greg.

Would you please send me the instructions file for updating the PowerSwitch 3048 firmware? We can't get it to go, and there were tantalizing mentions of a tftp server to use, and NOT putting a pathname with the filename.

 

Hi Greg

I am another who would appreciate a copy of the firmware update doc for a 3048.

regards

mark.window@maryborough.qld.gov.au

The 5.1.4 firmware is the original firmware shipped when the 3024/3048/5012 switches released to sales. It is not available for download, and I would not recommend using this firmware revision.

In order to stack a 3048 with a 3024, the 3048 must be the master of the stack and all switches must have at least 5.2.5 firmware.

Greg-

We are adding a 3048 to a stack of 3024s. The 3048 has a newer firmware version, but we would like to retain the 5.1.4 firmware on the stack, rather than unstacking everything and flashing each 3024. Is there any way for us to download 5.1.4 to flash the 3048 back to the earlier version? If the answer is yes, could you give me the link and send me your firmware flashing document? Also, could you confirm that we can add the 3048 to the top of the 3024 stack? Thank you.

Sincerely,

Vince Ribas (vribasNOSPAM@merrimackcounty.net)

Greg-
We may be going with a 3024 to avoid rebuilding the stack. Can you tell me why we should move to a higher firmware level? Everything is working fine, so what benefit will we get that will offset the considerable downtime of breaking the stack, flashing several devices multiple times, and rebuilding the stack?

Thanks,

Vince