The Dell Catalogs and their update frequency and location have been a mystery to me this last week.
Trying this method www.hypervisor.fr/ update my system from DRAC shows that the ftp.dell.com/Catalog.xml.gz file is from 5/23/2016. It tells me the latest R730 BIOS is 2.0.2, when in fact the latest bios is actually 2.1.7.
However, LCC, DRM, OME all show that the latest bios is 2.1.6 (because the catalogs haven't been refreshed).
The problem that bothers me is that there are at least two catalog locations. ftp.dell.com/Catalog.xml.gz (older) and ftp.dell.com/catalog/Catalog.xml.gz (which is what LCC, DRM, OME all seem to use).
The problem with using the catalog in the root directory with iDRAC is that it's older (why is this even in a different location?)
If I try and use the one in /catalog/ iDRAC cannot update, it says the updates fail instantaneously in the Job Queue. I believe this is because when you try and update, it uses the current catalog location in as the root folder, so it's looking for /catalog/FOLDER123123123/UPDATEFILE.EXE and it doesn't exist, because it's not meant to be under the catalog folder. It seems the DRAC updater logic uses the catalog folder as relational to the firmware, when it should just be looking for ftp.dell.com/FOLDER123123123/UPDATEFILE.exe (but it doesn't).
If I try and use DRAC to do "bulk updates" to firmware instead of LCC, OME, DRM like so : www.hypervisor.fr/
I'm met with failures that the updates cannot be found.
I believe that is because DRAC tries to fetch the update in relation to the catalog. If I fetch the catalog from ftp.dell.com/Catalog.xml.gz the updates are found (although old, because this catalog is OLDER than the one LCC/DRM/OME uses which are found in ftp.dell.com/catalog/Catalog.xml.gz I do not want to use it (it's 'fresh')
If I tell DRAC the catalog location is /catalog/Catalog.xml.gz it fetches a new catalog (indicates BIOS 2.1.6 is newest), but when I stage those updates they fail in the Job queue IMMEDIATELY.
If I stage the updates from ftp.dell.com/Catalog.xml.gz they succeed. Looking at the paths in the XML catalog file it appears they are relative to the catalog location and not 'full paths'.