Start a Conversation

Unsolved

This post is more than 5 years old

31491

March 29th, 2006 01:00

PowerConnect 5324 Copy Config via TFTP Error

​ First, a configuration file is saved over TFTP to the desktop. This is successful. ​
​ Next, this same configuration file is copied to startup via TFTP onto another PC5324 fresh out of the box, which only has the minimum configuration established on the console to communicate with a TFTP server. I've seen this on other units, including over the web interface, so this is a firmware problem. ​
​ ​
​ The following is the console log: ​
​ ​
​ console# copy tftp://192.0.10.55/Dell0325.cfg startup-config ​
​01-Jan-2000 01:32:49 %TFTP-A-TftpTxERROR: An error message was sent: 0 y application> ​
​... ​
​Copy: Error in configuration download Line: 3 Command: spanning-tree bpdu filter ​
​ing ​
​ console# 01-Jan-2000 01:32:53 %COPY-W-TRAP: The copy operation has failed ​
​ ​
​ Next the offending line of text is removed from the configuration file and the copy reattempted: ​
​ ​
​ console# copy tftp://192.0.10.55/Dell0325fix.cfg startup-config ​
​!!...! ​
​Copy: 10497 bytes copied in 00:00:12 [hh:mm:ss] ​
​ console# 01-Jan-2000 01:38:16 %COPY-W-TRAP: The copy operation was completed suc ​
​cessfully ​
​ console# ​
​ ​
​ Finally, the deleted setting must be manually entered and the configuration saved. ​
​ ​
​ What follows is the first 10 lines of the configuration file (before fixing): ​
​ ​
​ spanning-tree mode rstp ​
​spanning-tree priority 45056 ​
​spanning-tree bpdu filtering ​
​spanning-tree pathcost method long ​
​interface ethernet g1 ​
​spanning-tree disable ​
​exit ​
​interface ethernet g2 ​
​spanning-tree disable ​
​exit ​
​ ​
​ A firmware fix would be appreciated as I will eventually need an automated way of setting up switches. ​
​ ​

March 29th, 2006 13:00

Thanks for the problem report.  We will look into this issue and will track it in our bug tracking system.

Cuong.

13 Posts

May 2nd, 2006 20:00

Was this issue fixed in the new April firmware release for the 5324?  It wasn't mentioned in the release notes.  I haven't decided if we are ready to upgrade to the new firmware, but if this was fixed then I would upgrade immediately.

May 3rd, 2006 14:00

Sorry the last FW release did not address this problem.  However we have escalated this issue and hopefully it will be addressed soon.

Cuong.

13 Posts

February 7th, 2007 21:00

Has this been addressed in the December FW release?  I heard another release is due out very soon, will it be addressed in that one?

626 Posts

February 8th, 2007 13:00

I just tried it and it has been fixed.
 
Firmware release v2.0.0.39 and boot code v1.0.2.02
No Events found!

Top