
UNSOLVED
M
MattTopping
5 Posts
0
4920
August 24th, 2016 02:00
R320 Lifecycle Controller/Firmware issues
Hi
I am trying to update the firmware on a hex-core R320 through the lifecycle controller, but keep getting an error message:
'Firmware Update
FTP authentication failed. Enter the correct user name and password and retry.'
I have never needed a username or password before, or with any other servers - I get the option to continue without the catalogue downloading, but obviously this just leads to a lot of failed firmware downloads.
I have this error connecting to 'ftp.dell.com' or 'ftp.us.dell.com'
When testing the network connection to ftp.dell.com, the server fails again, returning this message
'Network connection test failed.
Gateway IP: Packets sent 4 = 4, Received =4, Loss - 0%
DNS IP: Packets sent 4 = 4, Received =4, Loss - 0%
Server IP: 143.166.147.76 Packets sent 4 = 4, Received =0, Loss - 100%'
I get the same message when connecting to ftp.us.dell.com, with the Server IP of 143.166.135.76 instead.
When I try entering 'default' into the address field, the network connection test is successful, yet I am still unable to connect to the ftp server, getting a LNK0002 error (Unable to resolve host name.) This is despite 'default' having worked before, and on other servers.
What is odd is that the server has full internet connectivity when running linux or windows, and when I have tried updating the firmware on another R320 it connected to Dells FTP server fine.
If it weren't for the normal internet connectivity when out of lifecycle controller I would have suspected a hardware issue - but I am only seeing this problem in the LCC. Equally, if it was more than one machine that was unable to connect, I would suspect Dells ftp server, but other R320s i have tried connect fine.
Any ideas/solutions would be great - I know I will probanbly be able to do a firmware update through repository manager or by downloading the firmware exe on a windows install, but I would like to get the LCC working, or at least know why it is not!
I am connecting via DHCP, and if I try NIC2 I get the same errors. If I go to view current versions, the server can find them fine as well. I also updated the NIC firmware yesterday on Windows.
Firmware revisions =
Bios 1.4.6
BP12G+ 0:1
Broadcom Gigabit Ethernet BCM5720 20.2.17
Broadcom Gigabit Ethernet BCM5720 20.2.17
Dell OS Driver Pack 16.01.08
Enterprise UEFI Diagnostics 4225A2, 425.4 4225A2
Integrated Dell Remote Access Controller 1.30.30
Lifecycle Controller 1.1.0.1108, A00 1.1.0.1108
Perc H310 Mini 20.11.0-0002
UPDATE: I have also encountered this error on a quad core R320 this morning - but I have also been able to update the firmware on another 320 hex core as well....
Responses (1)
Solutions (0)

MattTopping
5 Posts
2980
0
Posted August 25th, 2016 02:00
Manually updating the firmware through Windows seems to have worked fine for the 320 Hex, I am yet to try on the 320 Quad core. Can you think of any reason that the issue would have arisen in the first place? Would be good to have a record of why etc in case it happens in future! I'll update this post when the 320 quad core has been tested.