I am in the same boat as you. I have all HP hosts DL380s. I migrated my test hosts to my vCenter 5.5 U1 server, and went to perform the upgrade on the hosts from 5.1. I first had to apply the latest patches on 5.1, which then allowed me to upgrade the host to 5.5.0. I then had another series of patches that I applied (assuming I had to do that before upgrading to 5.5.1). After applying those, I still have 5.5.1 as an incompatible upgrade.
The upgrade contains the following set of conflicting VIBs:
Remove the conflicting VIBs or use Image Builder.....
So, I was at least able to make it to 5.5.0, but no further. Both the 5.5.0 and 5.5.1 ISOs used are the HP OEM ISOs.
I have bnx2_2.2.4f.v55.3 currently installed.
HP has bnx2_2.2.3t.v55.7 as downloadable under the vSphere 5.5 section.
VMware under the HCL has multiple versions including my current version and the bnx2_2.2.5d.v55.2.
Since this is test, I will play around with it some more and see what I can figure out.
Update: From Release Notes of 5.5 U1b
When you perform an upgrade scan of ESXi 5.x hosts that belong to an HA cluster, Update Manager might report the compliance status of the hosts as Incompatible and might not allow the hosts to be remediated. The Incompatible compliance status is because of the way the FDM (HA) agent is installed on ESXi 5.x hosts. Starting with vSphere 5.0, the FDM agent is installed on ESXi hosts as a VIB. When a VIB is installed or updated on an ESXi host, a flag is set to signify that the bootbank on the host has been updated. Update Manager checks for this flag while performing an upgrade scan or remediation and requires this flag to be cleared before upgrading a host. The flag can be cleared by rebooting the host.
Workaround: Reboot hosts that report the compliance status as Incompatible. Run the upgrade scan or remediation again after the host is back online.
Going to give this a try and I will let you know how it goes.
Firstly thanks for replying. An update on where Im at
On reading your post I came intot the office this morning and the first thing I did was download the HP 5.5.0 GA ISO to use instead of the HP 5.5u1 ISO. When I use this one the upgrade happens without any errors or compatibility issues. After pushing out 5.5GA, there were a number of critical and no-critical patches to install, one of which was Update 1..... test host is now at 5.5 Update 1 with all patches installed.
Im not sure who updates the custom ISOs whether its VMWare or HP but looks like somebody messed up with this driver in the HP 5.5u1 custom ISO.
Thanks for the update, and I would agree that something is a little off maybe with the HP OEM 5.5u1 ISO. Maybe its good for building a new host from scratch rather than upgrading? Also, due to sleep/coffee deprivation (at least that is what I am going to go with), my systems were up to date as well after running the patches post the 5.5.0 upgrade. I should have checked my build numbers more closely. Glad we were able to work through this together!
I'm having the exact same issues here. I don't actually have update manager - had never heard of it before this post - is it included with enterprise and where would I get it from?
As I don't have update manager, I need to update to 5.5.0 U1 manually(from 5.5.0) but booting the host from the ISO, then selecting to update. I use the HP custom image to do this on our GEN8 server and I get the error as above(or very similar)
Has anyone managed to find a workaround for this? When I list the VIBs on the host, there isn't one that matches the error so I cannot manually uninstall it.
Update Manager is part of the vCenter Server install. The documentation can be found here: vSphere Update Manager Documentation. Basically it just requires a small database and a bit of disk for storing the patches and updates. On the documentation page is a sizing calculator to determine how much you will need for your environment. Once it is installed though, it makes updating and upgrading your hosts pretty painless. You just add the plugin to your vCenter client, and you will see a new tab for Update Manager. From there you can scan your hosts to see what patches you need and apply them. You can also upload the ISO or ZIP images for vsphere and use that upgrade your hosts. As for the issue that you are having though, I am not sure. I would have to play around a bit with the image builder first (haven't used it before) to determine what needs to be done to make a custom ISO for installing.
Just to let you know that I also faced the same issue. I wanted to update a HP host from v5.1u2 to v5.5u1 and got the same vibs conflicting error.
I was able to update to v.5.5 but I am getting the same error when trying to apply the v5.5u1 after that.
I am not using Vsphere Update Manager so I have to apply the updates by booting CD/USB.
This is definitively because some Broadcom drivers in v5.5u1 are older than those included in v5.5 and even in v5.1u2...
I will try to report this somewhere to hopefully get a 5.5u2 soon...
I've been hitting the same issue using update manager using the v5.5u1 HP Customised ISO. The method below seems to workaround the issue.
With 5.5 installed, manually INSTALL (not UPDATE, as this fails due to a dependancy) the lastest Broadcom drivers using cli etc.
# esxcli software vib install --depot=/tmp/BCM-NetXtremeII-4.0-offline_bundle-1796156.zip
Once rebooted, try the upgrade to 5.5u1 again. You shouldn't see the validation errors like those described in the original post.
Hope this helps somebody out.
Thank you whatmyki! This has worked for me on G6 and Gen8's but I'm having an issue with G7's. Not all the NIC's are showing up. I've tried upgrading the Emulex firmware with no luck.
just got off the phone with HP, here's their solution
- Download BCM-NetXtremeII-4.0-1796156.zip from link http://vibsdepot.hp.com/hpq/jun2014/esxi-550-devicedrivers/
- Copy the zip file to /tmp folder on ESXi 5.5
- Login to Esxi 5.5 server ssh console with root privileges and change directory to tmp.
/tmp # unzip BCM-NetXtremeII-4.0-1796156.zip
/tmp # esxcli software vib install --depot=/tmp/BCM-NetXtremeII-4.0-offline_bundle-1796156.zip
- Reboot server.
- Try to upgrade ESXi 5.5 server to ESXi 5.5 Update01.
Hopefully this is a workaround rather than a solution from HP!
FYI - VMware have published a KB on this: http://kb.vmware.com/kb/2082027
I also have a case open with HP - and so far there seems to be a bit of to and fro as to who / where the fix will be implemented, but the last I heard is that QLogic are going to Rev the driver version to work around this, which then HP need to bundle into their ISO and test / release.
For the time being, I have either resorted to using the March HP ISOs, or removed the VIBs prior to upgrading with the June image.
I'll chase HP today and see where the progression is for a replacement ISO and post back.
Any luck on this? I am up against the same problem and now I have different builds in my server farm
they wont give you a new ISO. you just download the updated driver, and build your own ISO using the VMware documentation
Nothing yet... I was told by HP TSE he would have update for me in 24 to 48 hours...
I've also got my VMware TAM on the case to see if he can find any further info. Will let you know when I hear more.