HPE vipsdepot URLs in vSphere 7 needed?

[roland_geiser]

Hello

We are on vSphere 7 and do the upgrade procedure for our HPE ESXi Hosts by VUM and still use the update baselines. In the earlier releases, we entered the HPE URLs from the HPE vibsdepot (http://vibsdepot.hpe.com/index.xml, http://vibsdepot.hpe.com/index-drv.xml) in Lifecycle Manager. But now, all seems to be included in that baseline "Partner provided Addons for ESXi" and probably also the baseline "VMware Certified Async Drivers for ESXi":

 

How do you handle that? Do you still attach the HPE URLs in addition?

And when you want to upgrade the HPE specific drivers and tools (without upgrading the OS, so not using the HPE custom ISO). How do you make shure that you can filter only the HPE drivers/tool and only install/update these HPE related drivers/tools? So in principle update (the base is always a HPE custom image where all tools and drivers are present - so its mostly an update of them) all the tools/drivers that make the difference between the vanilla VMware Stock image and the HPE custom image by using lifecycle manager baselines. 

 

Best regards

Roland

[dstadelmann]

Hi  

With vSphere 7 we switched from VUM to Lifecycle Manager. In Lifecycle Manager you defined an image at cluster level. You will be also able to specify the HPE vendor add-on and also further components like HPE SCM. The benefit is, that all the catalogs are synced between VMware and HPE and then provided to you through Lifecycle Manager for selection. The packages are also checked for compatibility by Lifecycle Manager.

Regards

Daniel

[Casseau33]

Yeah I figured as much but that method of patching also comes with its own drawbacks / limitations such as a cluster needing to be all the same (hpe vs dell for instance). With that being said I cannot imagine there is no way to update HPE VIBS using baselines such as how we once did by tying it to vibsdepot. This works fine via DELL.

So hopefully someone out there can reply and let us know how this can be accomplished

Thanks

[Matt Purkis]

I am also getting the same

none of these work:

https://vibsdepot.hpe.com/index.html 

https://vibsdepot.hpe.com/index-drv.html

https://vibsdepot.hpe.com/index.xml

Any ideas ?

[ninjabrum]

It appears to be broken for well over a month.  You may want to open a ticket with HPE support to get an official answer.  All I can assume is that with the depreciation of baselines / VUM in favor of Lifecycle Manager images, they don't care to fix it.  You should be moving off baselines anyways.  They are going away soon.

[Casseau33]

A ticket with hpe is pointless. I tried.... They say to contact broadcom. To which I repeatedly told them broadcom has nothing to do with an hpe repo.

My work around is to simply upload the OEM zip to lcm manually.

As for moving away from baslines.. sure makes sense as it won't be an option in 9x. However it isn't that simple for companies that have a mix of hardware in the same cluster. Sure it isn't a best practice. But reality is a lot don't die to client requirements. 

Thanks