This post is more than 5 years old
19 Posts
0
33428
PowerConnect 3424 showing Access error: "request entity too large" on Web admin after firmware 2.0.x upgrade
When I upgrade this old switch to any FW version over 1.0.1.13 (2.0.x+) I receive this error when I try to go to the web admin page: "Access error: request entity too large" and I get this in the console: "GOAHEADG: received illegal length ..." I've tried many of the FW version 2.0.X and I've even tried both ways to copy the file, XModem and TFTP, but they all end the same error. All I do is downgrade to the 1.0.1.13 FW and all is fine. Am I missing something? I guess we really don't need the new FW as we haven't experienced any issues with these switches, but I was wanting to get us to the latest version since we've been outdated for quite some time. Any advice?
Thanks in advance.
sdfjksfdjnksfds
19 Posts
1
April 30th, 2012 23:00
Never mind, looks like it was an issue with IE on the computer I was using. I incidentally tried connecting to a PC2848 and I got the same error but I know I was able to connect using other computers without any problem. I installed Chrome and it worked. Yet again IE lax / wrong web standards strike again. Thanks for your help.
DELL-Willy M
802 Posts
0
April 27th, 2012 17:00
Have you also updated the boot code?
NOTE: When the new firmware version 2.0.0.34 is downloaded to the PowerConnect 3424/3448/3424P/3448P, Please make sure you also download the new boot code v 1.0.1.01.
NOTE: If you are trying upgrade from 1.0.1.13 or below, please make sure software version 2.0.0.34 is downloaded to the PowerConnect 34XX series, along with new boot code version 1.0.1.01. New firmware and new boot code must upgrade at the same time. Failure to download the new boot code results in the system rebooting continuously. This will require an XMODEM download of the previous version of software (PowerConnect_34XX-10113.ros) using XMODEM and the Startup Menu to recover.
PowerConnect_34XX_boot-10101.rfb
It should be available once the firmware download is extracted.
Boot Image Download
Loading a new boot image from the TFTP server and programming it into the flash updates the
boot image. The boot image is loaded when the device is powered on. A user has no control over
the boot image copies. To download a boot image through the TFTP server:
1 Ensure that an IP address is configured on one of the device ports and pings can be sent to a
TFTP server.
2 Ensure that the file to be downloaded is saved on the TFTP server (the rfb file).
3 Enter the show version command to verify which software version is currently running on the
device. The following is an example of the information that appears:
console# show version
SW version 1.0.0.30 (date 27-Jan-2005 time 13:42:41)
Boot version 1.0.0.05 (date 27-Jan-2005 time 15:12:20)
HW version
4 Enter the copy tftp://{tftp address}/{file name} boot command to copy
the boot image to the device. The following is an example of the information that appears:
console# copy t176.215.31.3/332448-10018.rfb boot
Erasing file..done.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Copy: 2739187 bytes copied in 00:01:13 [hh:mm:ss]
Hope this helps,
sdfjksfdjnksfds
19 Posts
0
April 27th, 2012 18:00
Yes, I made sure to update the boot image as well and I did it through both the tftp and the xmodem methods just in case there was an error in one or the other. I did this through all the v2.0.x firmwares that I tried just to be sure.
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
May 1st, 2012 06:00
Thanks for the update, glad you were able to get it sorted.