Unsolved
This post is more than 5 years old
3 Posts
0
3036
June 8th, 2018 08:00
OME 2.4 System Update fails from local Dell Repository
We can successfully deploy firmware updates from OpenManage Essentials 2.4 when the catalog source is set to the online source "http://downloads.dell.com/catalog/catalog.cab". When the catalog source is set to "Use repository manager file", the updates fail, with this error:
Results: Access to the download site is no longer available. Please verify the connectivity.
Package(s) unavailable
The iDrac job queue reflects the failure as well, which suggests that OME and the target are communicating properly.
(Data Center Version)Dell Repository Manager v2.2.0 is installed on the same Windows Server 2012 R2 server that has Dell OpenManage Essentials, and neither installation displayed any errors during installation. Independently, they seem to function as expected. I created one repository for firmware updates applicable to the PowerEdge models in our data center. I have created catalog files for the entire repository, and as a test, for a specific PowerEdge model (R620). When OME is set to use either catalog, system updates fail.
It seems like it might be one of these factors at this point; but I'll admit that I've only been using OME for 10 days; so I'd appreciate any input:
1. Windows firewall may need additional rules to allow use of the local repository. I have added 12+ inbound rules based on the available documentation; and communication with the discovered devices seems to be satisfactory. The Dell troubleshooting tool does not report any problem when I run it against a target iDrac ip.
2. I am not creating the catalog files properly.
3. I missed a basic configuration requirement when I installed the Dell Repository Manager.
Thank you.
DELL-Shivendra K
2 Intern
•
685 Posts
0
June 15th, 2018 06:00
Hi, thanks for the query.
I would suggest to look at the repository created using DRM. Make sure the catalog file and the supporting packages are downloaded appropriately in required directory structure. If you have selected not to download the packages during repository creation, make sure the catalog points to ftp.dell.com as base location.
Senthil_N
29 Posts
0
June 26th, 2018 11:00
Hi Donald,
I tried same way, creating Repository catalog for R620 and imported to OME. I am not seeing this issue.
Can you please share catalog.xml fails for you to import.
Thanks,
Senthil
Donald Palzere
3 Posts
0
August 17th, 2018 11:00
Thank you, for your response.
I created a directory off the root of C; and created a sub-directory under that (e.g. C:\Dell\DellUpdates). The update files and the catalog files are stored in that directory, and the catalog imports into Dell OpenManage Essentials (OME) without error. If I set the OME catalog source to Dell's downloads, the updates are found and deployed to the servers without error; so I may not have properly updated the repository this month. Clearly I didn't properly configure the repository; and I may create a another one, unless you have some additional suggestions.
Thanks again.
Donald Palzere
3 Posts
0
August 31st, 2018 07:00
After working with a very knowledgeable engineer at Dell Server Support, I opted to uninstall the Dell Repository Manager; and set the Catalog Source in DellEMC OpenManage Essentials (OME) to point to Dell's online source.
The engineer explained that OME will only download the update files that are required; based on the servers registered with OME; so that when updates are pushed from OME, the server acts as the source, and does not pull the updates from Dell's online source every time. If a particular update has not been pushed from OME, it will download it one time to it's source directory for use in the future; but once downloaded, it is saved locally on the server for future use. This is a much simpler and reliable solution.