- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - VMware
- >
- vibsdepot.hpe.com and VUM
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-17-2022 08:02 AM - last edited on 10-28-2022 02:14 AM by support_s
10-17-2022 08:02 AM - last edited on 10-28-2022 02:14 AM by support_s
vibsdepot.hpe.com and VUM
Wondering what I am missing here. I have been using http://vibsdepot.hpe.com/index.xml and http://vibsdepot.hpe.com/index-drv.xml as download sources in VUM since forever, and they are still showing as Connected sources in VUM Patch setup screen. Are these still the correct download sources for HPE components?
However, I am noting recently that new drivers, iSUT, amsd, etc. are not showing up as available in VUM despite configuring VUM for daily syncs with the download sources . In fact, the latest HPE update that appears in my VUM is "sutComponent_701.2.9.2.3-0" version 2.9.3 dated 5/24/2022 - obviously there have been many HPE components released since then, including iSUT 3.0.0 dated 9/29/2022 The latest amsd showing in my vLCM is amsdComponent_701.11.8.1.2-1 dated 2/19/2022 yest clearly there have been other amsd releases since that date, like 701.11.8.5 (28 Sep 2022) .
Why am I not seeing these newer components being downloaded from the HPE download sources? I *AM* getting all recent updates from the other four VMware download sources in my vLCM VUM sources list, as I show VMware patches and components as new as 10/05/2022.
Yes, I have already reset my VUM database per https://kb.vmware.com/s/article/2147284 and pulled everything in fresh. The 5/24/2022-dated "sutComponent_701.2.9.2.3-0" Host Extension Enhancement is still the latest thing it is pulling in from the HPE download sources after the VUM refresh.
Any ideas? Help? I should not have to download these components manually and upload them into my VUM database when I've already configured and connected vLCM/VUM to the HPE download sources.
- Tags:
- bios
- Operating System
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-19-2022 02:24 AM
10-19-2022 02:24 AM
Re: vibsdepot.hpe.com and VUM
I have the exact same problem. Have tried a variety of things. Me too facing the similar issues.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-28-2022 02:12 AM
10-28-2022 02:12 AM
Re: vibsdepot.hpe.com and VUM
Hello James,
Greetings of the day,
We would request you to open a support case with HPE-VMware Support in order to troubleshoot this further.
Regards,
RRT
I am an HPE Employee
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]