ESX4.1 using VUM for installing offline bundles

[Bas Vinken]

Hi,

At last VMware vCenter Update Manager 4.1 is able to import patches and
extensions manually by using an offline bundle.
I tried to import hp-nmi-bundle-1.0.02.zip and hp-esxi4.1uX-bundle-1.0.zip.
The import of hp-nmi-bundle-1.0.02.zip was successful but import of hp-esxi4.1uX-bundle-1.0.zip wasn't.
During the process I received the following error: Cannot find patch metadata.
The VUM log file showed the following error: Failed to download metadata zip file: C:\WINDOWS\TEMP\offlineBundleolmysbed.tmp\metadata.zip
Since the import of hp-nmi-bundle-1.0.02.zip went flawlessly is suspect there's something wrong with the hp-esxi4.1uX-bundle-1.0.zip.
Can someone tell me if I’m doing something wrong or if that's not the case fix the bundle ?

[Jan Soska]

Hello,
no experience with this, but try "old-fashioned" way of implementing it - described in instalation manual...

Jan

[Michal Kapalka (mikap)]

hi,

probably you downloaded it from this location :

http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=15351&prodSeriesId=1121516&swItem=MTX-b98795300e7947d88f19ab56d6&prodNameId=3288134&swEnvOID=4091&swLang=8&taskId=135&mode=4&idx=1

did you checked the file integrity with the MD5 ???? maybe the file is corrupted ??

MD5 check sum : a4940fec94464de405a41110e4f274ae

mikap

[Bas Vinken]

I'm able to install the hp-esxi4.1uX-bundle-1.0.zip if I use the vihostupdate.pl method.
But if you have to upgrade 2+ servers this method is cumbersome.
According to VMware the VUM method should also work. I can use the VUM method for the import of hp-nmi-bundle-1.0.02.zip so why not for the import of hp-esxi4.1uX-bundle-1.0.zip ?

[Wichers]

Bas,


This realy is a pain. I have also posted here.
http://forums13.itrc.hp.com/service/forums/questionanswer.do?admit=109447627+1280825526944+28353475&threadId=1439290

Seems like for now the NMI drivers can be deployed via VUM, but not the CIM providers.

As an alternative, it would be very nice if HP provided an host upgrade package for VUM 4.1, which upgrades to ESXi version 4.1 with CIM and NMI.

Until then, it's vihostupdate.pl.....

[AaronK]

I am also very interested in having this able to be imported into VUM.

Aaron

[AaronK]

OK!
I figured out how to 'fix' this (although not sure of the supportability of it...

Basically, the vmware.xml file inside of the metadata.zip file (inside the hp-esxi4.1uX-bundle-1.0.zip file) has some invalid and missing information.

I changed the following and rezipped everything up and now it imports and can be used just fine in VUM!!!

This line is wrong:
hpq-esxi4.1uX-bundle-1.0
Should be this (to match the name of the zip)
hp-esxi4.1uX-bundle-1.0

This is wrong:
May 29, 2009

Should be: 2010-06-07T00:26:57

Relative Paths are missing: should be
cross_oem-hp-smx-provider_410.02.07.60-235786.vib

cross_oem-vmware-esx-drivers-char-hpilo_400.8.5.0.1VMW-164009.vib>

I've attached my custom vmware.xml if you want to see it (and compare)

AK

[Allen Crawford]

Thanks for the find, this works well for me too. The only issue I've found so far is when upgrading to ESXi 4.1. I had an ESXi 4.0 U2 host with the HP CIM providers version 1.4 installed. After the upgrade to 4.1, the old 1.4 providers not only were still there, but would show up twice on a "vihostupdate" or "Get-VMHostPatch" query as follows:

hpq-esxi4.0u2X-bundle-1.4 8/10/2010 1:19:33 PM HP ESXi Bundle 1.4
hp-esxi4.0u2X-bundle-1.4 8/10/2010 1:19:33 PM HP ESXi Bundle 1.4

So I proceeded with my HP CIM/NMI baseline for ESXi 4.1 and after the subsequent reboot I now show this:

hp-esxi4.1uX-bundle-1.0 8/10/2010 1:08:33 PM HP ESXi Bundle 1.0
hpq-esxi4.0u2X-bundle-1.4 8/10/2010 1:19:33 PM HP ESXi Bundle 1.4
hp-esxi4.0u2X-bundle-1.4 8/10/2010 1:19:33 PM HP ESXi Bundle 1.4

So the new 1.0 providers for ESXi 4.1 are clearly installed, but it appears that so are the older ones--and it lists it twice now which it didn't do before the upgrade (note the "hp" vs. "hpq" prefix difference).

Are you seeing the same behavior?

[Allen Crawford]

Well, I also failed to mention another thing I just noticed wrong. The NMI driver isn't showing up on the query like it does on a freshly-built ESXi 4.1 server. My total output on an upgraded ESXi host is:

Id InstallDate Description
-- ----------- -----------
ESXi410-GA 8/10/2010 12:58:56 PM ESXi upgrade Bulletin
hp-esxi4.1uX-bundle-1.0 8/10/2010 1:08:33 PM HP ESXi Bundle 1.0
hpq-esxi4.0u2X-bundle-1.4 8/10/2010 1:19:33 PM HP ESXi Bundle 1.4
hp-esxi4.0u2X-bundle-1.4 8/10/2010 1:19:33 PM HP ESXi Bundle 1.4


On a freshly-built ESXi 4.1 server it looks like this:

Id InstallDate Description
-- ----------- -----------
hp-nmi-driver-1.0.02 8/5/2010 8:37:53 AM HP NMI Sourcing Driver for VMware ESX/ESXi 4.1
hpq-esxi4.1uX-bundle-1.0 8/5/2010 9:33:09 AM HP ESXi Bundle 1.0


Curious how things work for you.

[AaronK]

This looks about right.... FYI, I have a case open with HP on this issue right now, and it has been escalated..