topic Re: SAN Switch firmware update failing in HPE EVA Storage

SAN Switch firmware update failing

Jeremy C — Wed, 17 Oct 2012 14:16:06 GMT

Failed to access ftp://anonymous:@#.#.#.#/v7.0.2/release.plist
The server is inaccessible or firmware path is invalid. Please make sure the server name or IP address, the user/password and the firmware path are valid.

(I replaced the IP with #'s.)

I can do a configUpload so I know the switch can access the FTP site. I've repeatedly checked that I have the path right. I have identical (as far as I can tell) FTP sites on two servers. One is Windows 2003 and one is Windows 2008. The firmwareDownload will work from the Win2003 server but fails with the above message with the Win2008 server.

Does the firmwareDownload process do some unusual file searching of some sort that isn't supported on a Win2008 FTP site? The 2003 vs 2008 is the only difference I'm aware of.

I want to get rid of the 2003 server so that's why I'm not just using the 2003 server to do upgrades and getting on with my life.

Re: SAN Switch firmware update failing

Torsten. — Wed, 17 Oct 2012 14:20:08 GMT

What was the path you specified?

What kind of ftpd you are using?

Try ftp from a command line, look into the server log. Check the firewall.

Re: SAN Switch firmware update failing

Jeremy C — Wed, 17 Oct 2012 14:49:11 GMT

I've tried just about every possible path. The firmware was extracted to folder "v7.0.2" in the root of the FTP site. I've tried "v7.0.2", "/v7.0.2","v7.0.2/release.plist","/v7.0.2/release.plist","v7.0.2/","/v7.0.2/", etc.

FTP site is the one that is part of Windows 2008 / IIS.

I've tried FTP from command line. All seems right. I've done configUpload from the switch to the FTP site so the switch can definitely connect to the FTP site and write to it.

I've completely disabled Windows firewall.

From FTP log:

14:34:39 #.#.#.# [615]USER anonymous 331 0
14:34:39 #.#.#.# [615]PASS - 230 0
14:34:39 #.#.#.# [615]CWD /v7.0.2/SWBD64 250 0

Re: SAN Switch firmware update failing

Jeremy C — Wed, 17 Oct 2012 18:42:22 GMT

Solved.

The firmwaredownload process uses passive FTP. Those other ports that the passive FTP was trying to use were not open on the network. That's why configupload worked but not firmwaredownload.