We have a small vSphere Environment using the Essentials edition. We have no Update Manager. To update we (virtually – using iLO) mount the installation .iso, boot from it and choose “upgrade” in the installation process. This process always worked fine – so far.
Attempting to upgrade from HP vSphere 5.5 to HP vSphere 5.5 U1 ends with the following error:
Errors/Warnings during system scan
CONFLICTING_VIBS ERROR […] Remove the conflicting vibs or use Image Builder to create a custom ISO providing newer versions of the conflicting vibs
[Broadcomm_bootbank_net-bnx2_2.2.5dv55-10OEM.550.0.0.1331828]
The current version 5.5 is a HP custom ISO as well as the version 5.5 U1 I tried to upgrade to.
This appears to me very similar to https://communities.vmware.com/thread/482105., which is marked solved although it appears to me it is more a workaround used there.
Any ideas? Do I have to wait for an updated version from HP?
My ESXi Hosts is Dell R7x0,
http://kb.vmware.com/kb/2036167
Maybe You can try:
esxcli software vib list | grep -i "Broadcomm_bootbank_net-bnx"
esxcli software vib remove -n "Broadcomm_bootbank_net-bnx"
Hi
Welcome to communities.
Could you please share log file from below path
/etc/vmware/oem.xml.
Thanks for your help...(also to TiGiZhu)
There you go:
<config>
<welcomePageLink>
<en>
<context>You are running HP Customized Image ESXi 5.5.0 version 5.71.3 based on ESXi 5.5.0 Vmkernel Release Build 1331820.</context>
<text></text>
<url></url>
<docroot></docroot>
</en>
</welcomePageLink>
</config>
+1 for this issue.
I am having the exact same problem and also upgrading from 5.5.0 to 5.5.0 U1 on the HP image.
Same problem here.
Same problem here.
Errors/Warnings during system scan
CONFLICTING_VIBS ERROR […] Remove the conflicting vibs or use Image Builder to create a custom ISO providing newer versions of the conflicting vibs
[Broadcomm_bootbank_net-bnx2_2.2.5dv55-10OEM.550.0.0.1331828]
Are you all using the HP 5.5 U1 ISO released in March 2014? Or the just recently released updated June 2014 HP 5.5 U1 ISO?
http://h18004.www1.hp.com/products/servers/software/vmware-esxi/driver_version.html
The March ISO contains the driver net-bnx2 - Version - 2.2.4f.v55.3, which is older than the reported driver in the message above. This might be the reason it refuses to update.
So make sure you're using the recent June HP ISO:
https://my.vmware.com/web/vmware/details?downloadGroup=HP-ESXI-5.5.0U1-GA&productId=353
Name: VMware-ESXi-5.5.0-Update1-1746018-HP-5.74.27-Jun2014.iso
Release Date: 2014-06-17
Build Number: 1746018-5.74.27
Same problem.
June HP iso v5.5u1 includes older boradcom drivers than v5.5 and v5.1u2....
Actually using the March2014 version is may be the solution. but not tried.
MKguy schrieb:
Are you all using the HP 5.5 U1 ISO released in March 2014? Or the just recently released updated June 2014 HP 5.5 U1 ISO?
http://h18004.www1.hp.com/products/servers/software/vmware-esxi/driver_version.html
The March ISO contains the driver net-bnx2 - Version - 2.2.4f.v55.3, which is older than the reported driver in the message above. This might be the reason it refuses to update.
So make sure you're using the recent June HP ISO:
I used the latest version, June 2014.
VMware-ESXi-5.5.0-Update1-1746018-HP-5.74.27-Jun2014.iso
Thank you for your thread. I too was having the same exact issue and was losing my mind for the last two days and with pure luck I ended up here. I started a support request with VMWare but whatmyki's suggestion in the post you linked helped me resolve the issue. You need to install the broadcom offline bundle he mentioned, reboot and then try to apply the iso. As he mentioned make sure you use the "install" switch and not update switch or it will not work. I did not use the iso but the zip and I also used VUM so hopefully it works for you.
I think the HP June bundle is buggy and hopefully with enough people posting about this, HP will resolve the issue.
Download this, and inside the zip file is the offline bundle:
I have opened a support case with HP to make them aware of the issue.
Thanks a lot Chris,
Please update this thread if you get any news from HP
+1
I tried to update via esxcli to apply the most recent patch (ESXi510-201406001) to my ESXi with HP Custom ISO (VMware-ESXi-5.1.0-Update2-1483097-HP-5.66.28-Jun2014.iso) and ran into problems too:
~ # esxcli software vib update --depot=/vmfs/volumes/nas1/ESXi510-201406001.zip
[DependencyError]
VIB Broadcom_bootbank_scsi-bnx2i_2.7a.03.v50.2-1OEM.500.0.0.472560 requires com.broadcom.cnic-9.2.0.0, but the requirement cannot be satisfied within the ImageProfile.
VIB VMware_bootbank_net-bnx2x_1.61.15.v50.3-1vmw.510.0.11.1063671 requires com.broadcom.cnic_register-9.2.1.0, but the requirement cannot be satisfied within the ImageProfile.
VIB VMware_bootbank_net-cnic_1.10.2j.v50.7-3vmw.510.0.0.799733 requires com.broadcom.cnic_register-9.2.1.0, but the requirement cannot be satisfied within the ImageProfile.
i also have this issue with VMware-ESXi-5.5.0-Update1-1746018-HP-5.74.27-Jun2014.iso
Same for me. Hope HP can do something for that.
Same problem here.
I was running HP customized 5.1 U2 and wanted to upgrade to 5.5 U1A.
I was forced to upgrade to 5.5 U1 ( not A ) because of this problem.
Everyone says that it's because some kind of bnx2 driver downgrade from HP in 5.5 U1A, but I really don't undestand that, because
Now ( 5.5 U1 ) I have
net-bnx2 2.2.4f.v55.3-1OEM.550.0.0.1331820 Broadcom VMwareCertified 2014-07-02
bnx2: net driver for VMware ESX
Broadcom NetXtreme II Gigabit Ethernet Driver
release-date : 2013-12-11T08:38:59.768585+00:00
And in 5.5 U1A there is :
vib20\net-bnx2\Broadcom_bootbank_net-bnx2_2.2.5d.v55.2-1OEM.550.0.0.1331820.vib
release-date : 2014-03-27T00:14:07.331201+00:00
I suppose 2.2.5d is greater that 2.2.4f ??
Or the letter is more important than the third number? anyway the release date is greater. Don't know what are the vmware rules.
Actually the problem is NOT the net-bnx2 package, but the net-cnic package it depends on. Or to be more precise, it looks like a problem during the ESXi update procedure to interpret version numbers correctly.
You can see that if you check the esxupdate.log or manually try to update net-bnx2 it with the --update option:
# esxcli software vib update --vibname net-bnx2 --dry-run --depot /tmp/BCM-NetXtremeII-4.0-offline_bundle-1796156.zip
[DependencyError]
VIB Broadcom_bootbank_net-bnx2_2.2.5d.v55.2-1OEM.550.0.0.1331820 requires misc-cnic-register = 1.7a.02.v55.1-1OEM.550.0.0.1331820, but the requirement cannot be satisfied within the ImageProfile.
Please refer to the log file for more details.
So our net-bnx2 driver needs at least misc-cnic-register = 1.7a.02.v55.1-1OEM.550.0.0.1331820, but that package is in the bundle. Hm.
Next step, what net-cnic version do I currently have on my host?
# esxcli software vib list | grep -i net-cnic
net-cnic 1.72.52.v55.1-1vmw.550.0.0.1331820 VMware VMwareCertified 2013-11-21
Ok, we got 1.72.52.v55.1-1vmw.550.0.0.1331820 here. So the battle boils down to version string 1.7a vs. 1.72. Might be a bit ambiguous.
Now let's ask our ESXi host about what he assumes is the newer driver (make sure you scroll to the right to the Status column):
# esxcli software sources vib list -d /tmp/BCM-NetXtremeII-4.0-offline_bundle-1796156.zip
Name Version Vendor Creation Date Acceptance Level Status
------------------ ---------------------------------- -------- ------------- ---------------- ---------
net-cnic 1.7a.05.v55.3-1OEM.550.0.0.1331820 Broadcom 2014-03-04 VMwareCertified Downgrade
scsi-bnx2i 2.7a.03.v55.2-1OEM.550.0.0.1331820 Broadcom 2014-01-31 VMwareCertified Downgrade
net-bnx2x 1.7a.10.v55.1-1OEM.550.0.0.1331820 Broadcom 2014-03-04 VMwareCertified Downgrade
scsi-bnx2fc 1.7a.08.v55.1-1OEM.550.0.0.1331820 Broadcom 2014-04-17 VMwareCertified Downgrade
misc-cnic-register 1.7a.02.v55.1-1OEM.550.0.0.1331820 Broadcom 2013-12-21 VMwareCertified Downgrade
net-bnx2 2.2.5d.v55.2-1OEM.550.0.0.1331820 Broadcom 2014-03-27 VMwareCertified Update
Oops! All drivers contained in the bundle except net-bnx2 are actually being interpreted as version downgrades! Which is not quite correct though. The host doesn't see any need to update these packages with the --update switch
# esxcli software vib update --vibname net-cnic --dry-run -d /tmp/BCM-NetXtremeII-4.0-offline_bundle-1796156.zip
Installation Result
Message: Dryrun only, host not changed. The following installers will be applied: []
Reboot Required: false
VIBs Installed:
VIBs Removed:
VIBs Skipped: Broadcom_bootbank_net-cnic_1.7a.05.v55.3-1OEM.550.0.0.1331820
So what's basically happening causing these errors everybody has is:
Apparently the ESXi updater gets confused by the ambiguous 1.7a vs 1.72 version strings conundrum. I don't know what's the general industry standard on versioning when it involves letters, so either VMware/Broadcom/HP messed up when naming these new versions or the ESXi updater is buggy when interpreting them.
So the best way to handle this issue currently is forcing the installation of the newer complete Broadcom bundle manually prior to the actual ESXi update with the --install switch like:
# esxcli software vib install -d /tmp/BCM-NetXtremeII-4.0-offline_bundle-1796156.zip
Excelent explanation!
Now everything is clear.
We just ran into the same error. We called HP and got a really poor tech. He said "We don't support upgrades, wipe the host and install from scratch". Since we have lots of remote locations, this wasn't even reasonable. We hung up and did our own work starting with powering off the vm's and putting the host in maintenance mode. Then the following steps were done via ILO on a local pc in the remote location:
1) Log into the host (we did this from the console via ESXi Shell)
2) Remove all broadcom components. The order of removal was important due to dependencies. We tried removing just bnx2 and bnx2x but got the error again, so we took them all out
esxcli software vib remove --vibname=net-bnx2
esxcli software vib remove --vibname=net-bnx2x
esxcli software vib remove --vibname=net-tg3
esxcli software vib remove --vibname=scsi-bnx2fc
esxcli software vib remove --vibname=scsi-bnx2i
esxcli software vib remove --vibname=net-cnic
esxcli software vib remove --vibname=misc-cnic-register
3) Reboot host to iso
4) Run the upgrade, preserve datastore -> reboot host
5) Remediate via the vsphere client if necessary. We did
6) Exit maintenance mode, start vm's and the upgrade is complete!