Fibre Channel (SAN)

Reply
Occasional Contributor
Posts: 5
Registered: ‎04-19-2013

Firmwaredownload failed. (0x15)

Brocade silkworm 3850
Current Version: FOS v4.4.0b

Trying to upgrade from v4.4.0b to v5.1.0

 

Failed to transfer package dir-1.0.4-3.ppc.rpm
Firmwaredownload failed. (0x15) Firmwaredownload failed due to network timeout

 

I'm trying to perform "firmwaredownload" from an FTP Server (Filezilla and Cerberus) but it keeps failing and giving the above error message. There's no firewall in between the swicth and the FTP server (directly connected the switch to the PC using RJ45 - no default gateway - swicth is 192.168.1.13 and FTP server is 192.168.1.55). Both Web Tools and CLI have the same result. 

The home directory of the ftp user is the folder that contains the unzipped package of v5.1.0. 

 

Snap 2013-12-14 at 19.52.21.png

 

 

Here's the FTP server side log:

 

[2013-12-14 19:48:54]:COMMAND [ 21] - PASS ***********
[2013-12-14 19:48:54]:CONNECT [ 21] - Native user 'ftpuser' authenticated
[2013-12-14 19:48:54]: REPLY [ 21] - [ftpuser] 230 Password Ok, User logged in - This is an UNLICENSED copy of Cerberus FTP Server Home edition

[2013-12-14 19:48:54]:COMMAND [ 21] - [ftpuser] TYPE I
[2013-12-14 19:48:54]: REPLY [ 21] - [ftpuser] 200 Type Binary

[2013-12-14 19:48:54]:COMMAND [ 21] - [ftpuser] CWD SWBD27
[2013-12-14 19:48:54]: REPLY [ 21] - [ftpuser] 250 Change directory ok

[2013-12-14 19:48:54]:COMMAND [ 21] - [ftpuser] PORT 192,168,1,13,4,67
[2013-12-14 19:48:54]: REPLY [ 21] - [ftpuser] 200 Port command received

[2013-12-14 19:48:54]:COMMAND [ 21] - [ftpuser] RETR release.plist
[2013-12-14 19:48:54]: REPLY [ 21] - [ftpuser] 150 Opening data connection

[2013-12-14 19:48:54]: SYSTEM [ 21] - [ftpuser] Successfully sent file 'T:\v510\SWBD27\release.plist' (2536 B sent)
[2013-12-14 19:48:54]: REPLY [ 21] - [ftpuser] 226 Transfer complete

[2013-12-14 19:48:54]:CONNECT [ 21] - The client closed the connection
[2013-12-14 19:48:54]:CONNECT [ 21] - Connection terminated
[2013-12-14 19:48:58]:CONNECT [ 22] - Incoming connection request on FTP interface 40 at 192.168.1.55
[2013-12-14 19:48:58]:CONNECT [ 22] - FTP connection request accepted from 192.168.1.13
[2013-12-14 19:48:58]:COMMAND [ 22] - USER ftpuser
[2013-12-14 19:48:58]: REPLY [ 22] - 331 User ftpuser, password please

[2013-12-14 19:48:58]:COMMAND [ 22] - PASS ***********
[2013-12-14 19:48:58]:CONNECT [ 22] - Native user 'ftpuser' authenticated
[2013-12-14 19:48:58]: REPLY [ 22] - [ftpuser] 230 Password Ok, User logged in - This is an UNLICENSED copy of Cerberus FTP Server Home edition

[2013-12-14 19:48:58]:COMMAND [ 22] - [ftpuser] TYPE I
[2013-12-14 19:48:58]: REPLY [ 22] - [ftpuser] 200 Type Binary

[2013-12-14 19:48:58]:COMMAND [ 22] - [ftpuser] PORT 192,168,1,13,4,69
[2013-12-14 19:48:58]: REPLY [ 22] - [ftpuser] 200 Port command received

[2013-12-14 19:48:58]:COMMAND [ 22] - [ftpuser] RETR dir-1.0.4-3.ppc.rpm
[2013-12-14 19:48:58]: ERROR [ 22] - Unable to connect : Only one usage of each socket address (protocol/network address/port) is normally permitted.
[2013-12-14 19:48:58]:SUGGEST [ 22] - For help see http://www.cerberusftp.com/support/faq/initialsetup.htm#Q3
[2013-12-14 19:48:58]: REPLY [ 22] - [ftpuser] 425 Unable to open the data connection

[2013-12-14 19:48:58]:CONNECT [ 22] - The client closed the connection
[2013-12-14 19:48:58]:CONNECT [ 22] - Connection terminated
[2013-12-14 19:48:58]:CONNECT [ 23] - Incoming connection request on FTP interface 40 at 192.168.1.55
[2013-12-14 19:48:58]:CONNECT [ 23] - FTP connection request accepted from 192.168.1.13
[2013-12-14 19:48:58]:COMMAND [ 23] - USER ftpuser
[2013-12-14 19:48:58]: REPLY [ 23] - 331 User ftpuser, password please

[2013-12-14 19:48:58]:COMMAND [ 23] - PASS ***********
[2013-12-14 19:48:58]:CONNECT [ 23] - Native user 'ftpuser' authenticated
[2013-12-14 19:48:58]: REPLY [ 23] - [ftpuser] 230 Password Ok, User logged in - This is an UNLICENSED copy of Cerberus FTP Server Home edition

[2013-12-14 19:48:58]:COMMAND [ 23] - [ftpuser] TYPE I
[2013-12-14 19:48:58]: REPLY [ 23] - [ftpuser] 200 Type Binary

[2013-12-14 19:48:58]:COMMAND [ 23] - [ftpuser] PORT 192,168,1,13,4,71
[2013-12-14 19:48:58]: REPLY [ 23] - [ftpuser] 200 Port command received

[2013-12-14 19:48:58]:COMMAND [ 23] - [ftpuser] RETR dir-1.0.4-3.ppc.rpm
[2013-12-14 19:48:58]: ERROR [ 23] - Unable to connect : Only one usage of each socket address (protocol/network address/port) is normally permitted.
[2013-12-14 19:48:58]:SUGGEST [ 23] - For help see http://www.cerberusftp.com/support/faq/initialsetup.htm#Q3
[2013-12-14 19:48:58]: REPLY [ 23] - [ftpuser] 425 Unable to open the data connection

[2013-12-14 19:48:58]:CONNECT [ 23] - The client closed the connection
[2013-12-14 19:48:58]:CONNECT [ 23] - Connection terminated
[2013-12-14 19:48:58]:CONNECT [ 24] - Incoming connection request on FTP interface 40 at 192.168.1.55
[2013-12-14 19:48:58]:CONNECT [ 24] - FTP connection request accepted from 192.168.1.13
[2013-12-14 19:48:58]:COMMAND [ 24] - USER ftpuser
[2013-12-14 19:48:58]: REPLY [ 24] - 331 User ftpuser, password please

[2013-12-14 19:48:58]:COMMAND [ 24] - PASS ***********
[2013-12-14 19:48:58]:CONNECT [ 24] - Native user 'ftpuser' authenticated
[2013-12-14 19:48:58]: REPLY [ 24] - [ftpuser] 230 Password Ok, User logged in - This is an UNLICENSED copy of Cerberus FTP Server Home edition

[2013-12-14 19:48:58]:COMMAND [ 24] - [ftpuser] TYPE I
[2013-12-14 19:48:58]: REPLY [ 24] - [ftpuser] 200 Type Binary

[2013-12-14 19:48:58]:COMMAND [ 24] - [ftpuser] PORT 192,168,1,13,4,73
[2013-12-14 19:48:58]: REPLY [ 24] - [ftpuser] 200 Port command received

[2013-12-14 19:48:58]:COMMAND [ 24] - [ftpuser] RETR dir-1.0.4-3.ppc.rpm
[2013-12-14 19:48:58]: ERROR [ 24] - Unable to connect : Only one usage of each socket address (protocol/network address/port) is normally permitted.
[2013-12-14 19:48:58]:SUGGEST [ 24] - For help see http://www.cerberusftp.com/support/faq/initialsetup.htm#Q3
[2013-12-14 19:48:58]: REPLY [ 24] - [ftpuser] 425 Unable to open the data connection

[2013-12-14 19:48:58]:CONNECT [ 24] - The client closed the connection
[2013-12-14 19:48:58]:CONNECT [ 24] - Connection terminated

 

I don't know if this is a problem on the swicth or the PC where the FTP Server is running. However I did modify the Windows Registry to ensure it is not a "TCP/IP port exhaustion" issue.

 

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Tcpip\Parameters\MaxUserPort 65534 (Maximum number of ports)

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Tcpip\Parameters\TcpTimedWaitDelay 30 (30 secs)

 

 

Does anyone have any idea why it is failing?

 

Valued Contributor
Posts: 761
Registered: ‎06-11-2010

Re: Firmwaredownload failed. (0x15)

Hi,

 

try a different laptop, Ftp server application to see if there could be the issue.

You can also download a new version of the Code, or a different one, just in case the code could be corrupt.

 

On the other hand, could you please post the output of "ifmodeshow eth0" to see how the management port is configured?

 

 

 

Rgds,

Felipon

Frequent Contributor
Posts: 104
Registered: ‎07-27-2009

Re: Firmwaredownload failed. (0x15)

The issue is that the FTP server only allows a very limited number of active session from this user or ip address. Make sure that both have at least the abiltiy to open 10 active sessions. Remember that each filedownload uses a new ftp session and it is not streamed via an MGET.

 

Even though the user may have logged of after the first file-download it may wel be that the socket is still open. I've used Cerberus in the past but I'm not 100% sure where to set this anymore.

 

Let me know if this solves the problem.

New Member
Posts: 1
Registered: ‎01-17-2017

Re: Firmwaredownload failed. (0x15)

Hi Solomon, may I know the cause if you got the issue sorted out? 

 

Thanks. 

Broadcom Moderator
Posts: 105
Registered: ‎04-27-2009

Re: Firmwaredownload failed. (0x15)

Hi muthugt,

 

it appears that there has never been any solution posted however the replys from the other contributors sound logical to me.

Since it was always failing with the same rpm right away it appears to be related to the ftp software and open connections.

 

Generally when firmwaredownloads are failing what you can do from a switches perspective is to check the ifmodesettings (FD vs. HD e.g.) or if network errors are incrementing on the management ethernet interface. That's the reason in most of the cases.

 

TL

If this provided you with a solution to this issue, please mark it with the button at the bottom "Accept as solution".

Any and all information provided by me is not reviewed, approved or endorsed by Brocade and is provided solely as a convenience for Brocade customers. All systems and all networks are different and unique. If you have a service affecting network problem, please open a TAC service request for service through Brocade, or through your OEM equipment provider.
Broadcom Moderator
Posts: 455
Registered: ‎03-29-2011

Re: Firmwaredownload failed. (0x15)

Hi,

 

this is a ftp server issue. Notice that the first file retrieval from the ftp server (release.plist in green) work correct.

 

The second fails, since probably the ftp server is re-using the same portnumber - it is configured in active mode.

First things to try is that no firewall is blocking on the ftp server.

Secondary, try to switch over the ftp server to passive mode.

Third, see the following for hints concerning the errors

 

https://blogs.msdn.microsoft.com/dgorti/2005/09/18/only-one-usage-of-each-socket-address-protocolnetwork-addressport-is-normally-permitted/

 

I have tested different ftp server under windows and in the end I stuck to filezilla ftp server.




If this provided you with a solution to this issue, please mark it with the button at the bottom "Accept as solution".


Any and all information provided by me is not reviewed, approved or endorsed by Brocade and is provided solely as a convenience for Brocade customers. All systems and all networks are different and unique. If you have a service affecting network problem, please open a TAC service request for service through Brocade, or through your OEM equipment provider. If this provided you with a solution to this issue, please mark it with the button at the bottom "Accept as solution"

Join the Community

Get quick and easy access to valuable resource designed to help you manage your Brocade Network.

vADC is now Pulse Secure
Download FREE NVMe eBook