Is there any way for LCC, on a 14G server, to get current firmware? If I use FTP, the only server that seems to work is ftp.dell.com, and that is showing me firmware versions that are older than the server even came with, from six months ago. The website shows me new firmware is available for my server, so it would sure be nice if LCC could pull it.
I tried HTTP-based download with both updates.dell.com and downloads.dell.com, given there's conflicting information online about what is correct, with and without catalog in the file path box, and neither is able to pull anything, so I must be missing some combo of options. Switching to https does produce an accept certificate dialog so it is connecting, it just doesn't retrieve the catalog.
I checked ftp.dell.com/catalog/catalog.cab and downloads.dell.com/catalog/catalog.cab. I show both were updated 11/8/2018. The catalogs on our FTP site are not constantly updated with the latest updates. It takes time to create the catalogs and publish them, so updates that are released just before the catalog are not likely going to be included.
If you are wanting to apply an update that is newer than what is available in the catalog then you will need to either use Dell EMC Repository manager to create your own catalog or apply the updates directly. You can find more information about DRM on the DRM support page. The download should be on the system support page.
In my case a new R940 came with a BIOS version several months newer than what the LCC catalog says is current, while there's an even newer version available. Just frustrating that LCC can't be configured to do the same lookup based on service tag that a human would go do, and then get all the accurate version downloads.
Thanks for the tip on DRM. I tried the link you sent, chose Repository Manager, then 3.1 version. For some reason, the resulting page is a video about how to install Dell Threat Defense and has nothing to do with repository manager. I click to the Downloads tab of that page, and it tells me:
Downloads can be found with the supported hardware platform. Please use the following link to select the appropriate platform.
I do that, and I'm back to where I started. Looks like I can download it if I go into a specific server we have. I just downloaded DRM 3.1, installed on RHEL 7, ran it, set the repository type to Integration and pointed it at the same R940 iDRAC, it logged in, determined the server version and service tag, and added the repository. I told it download, and it did so, and what I end up with is the same useless files the LCC combo produces.
DRM downloaded enterprise catalog 18.11.00 from wherever it connects, and here it is telling me BIOS 1.4.9 is current. That version is from July. The server came with 1.5.4 which the website doesn't even acknowledge the existence of. 1.5.6 is current, which neither LCC or DRM seem to have any knowledge of. LCC is apparently pulling its info from the same source than DRM is.
I start over again and create a manual repository, then specify add bundle, no base catalog, add an R940 server, choose OS-independent, add the components BIOS, raid, network, memory. Same exact result; click download and you get the same out of date versions, so it's completely useless.
Have I missed a step somewhere that should be downloading current versions like what you'd get manually using the support site?
This is almost laughable that a $35k server requires hours of pointless activity only to determine that the only method of updating the hardware that actually works properly is to have a human go enter a service tag, click through each firmware/bios/driver trying to figure out if the hardware needs the update or not, download the .exe version of the update if one is available since that's the only type you can load via the iDRAC, but in many cases one isn't available, and since the server runs vmware, that means an even more ridiculous process of updating is needed, which is to boot off a CentOS Live DVD, start up a browser, download the linux version of the update, run it from the live DVD, reboot back to LCC or vmware depending on if there are more updates left to perform.
In my particular case the whole reason I'm going through this exercise is because the version of the Mellanox firmware on the cards my server came with have known bugs that impact me in a severely negative way. So it appears my only choice is to incur hours of operational expense per server just to update firmware on Dell servers, which certainly reduces the value proposition.
You are choosing the option to use a catalog. That uses a catalog that is updated on the same schedule as the catalog the iDRAC/LCC uses. There are several catalog versions that our various utilities use, but they are all typically updated at the same time. If you choose that option it is going to have the same files available.
If you choose the Import option at the top you can add a DUP file to the bundle you have created. That is how you add updates that are not yet in the catalog.
Great, appears it did. Spent 30 minutes writing it out.
Short version; DRM downloads the exact same useless versions from months ago, so it does not appear to be a viable solution to LCC not getting up to date information.
Daniel My
12 Elder
•
6204 Posts
1783
0
Posted November 20th, 2018 13:00
Hello
I checked ftp.dell.com/catalog/catalog.cab and downloads.dell.com/catalog/catalog.cab. I show both were updated 11/8/2018. The catalogs on our FTP site are not constantly updated with the latest updates. It takes time to create the catalogs and publish them, so updates that are released just before the catalog are not likely going to be included.
If you are wanting to apply an update that is newer than what is available in the catalog then you will need to either use Dell EMC Repository manager to create your own catalog or apply the updates directly. You can find more information about DRM on the DRM support page. The download should be on the system support page.
http://www.dell.com/openmanagemanuals/
Thanks