![vmware vsphere 6.5 appliance error 500 vmware vsphere 6.5 appliance error 500](https://www.kieri.com/wp-content/uploads/2019/06/vcsa-upgrade-screen-8-temporary-network.jpg)
In my case, it returned “net-mst”) esxcli network nic list (This command above shows the VIB package that the Mellanox driver is inside of.
![vmware vsphere 6.5 appliance error 500 vmware vsphere 6.5 appliance error 500](https://www.techcrumble.net/wp-content/uploads/2017/10/psc01time.png)
I SSH’ed in to the host and ran the following commands: esxcli software vib list | grep Mell In my case, since they were not being used, uninstalling them would not effect the system. If you are using the drivers that are causing the conflict, DO NOT REMOVE them as it could disconnect all network interfaces from your host. I checked the host to see if I was even using the Mellanox drivers, and thankfully I wasn’t and could safely remove them. Remove the conflicting VIBs or use Image Builder to create a custom ISO.” The fix I successfully upgraded one of my hosts without any issues, however after scanning on my second host, it reported the upgrade as incompatible and stated: “The upgrade contains the following set of conflicting VIBs: Mellanox_bootbank_net.XXXXversionnumbersXXXX.
![vmware vsphere 6.5 appliance error 500 vmware vsphere 6.5 appliance error 500](https://3rxsdqm2iblvg8du1xff1z16-wpengine.netdna-ssl.com/wp-content/uploads/2016/01/ESXi-User.png)
It was easy enough to download the customized HPE installation image from VMware’s website, I then loaded it in to VMware Update Manager on the vCenter appliance, created a baseline, and was prepared to upgrade the hosts. I also have always used the HPE customized ESXi image for installs and upgrades. In my test environment, I run 2 x HPE Proliant D元60p Gen8 servers. The issueĪfter successfully completing the migration from vCenter 6.0 (on Windows) to the vCenter 6.5 Appliance, all I had remaining was to upgrade my ESXi hosts to ESXi 6.5.
#Vmware vsphere 6.5 appliance error 500 how to#
This post will go in to detail as to what causes it, and how to resolve it. This is due to conflicting VIBs on your ESXi host. Remove the conflicting VIBs or use Image Builder to create a custom ISO." When upgrading VMware vSphere and your ESXi hosts to version 6.5, 6.7, or 7.0, you may experience an error similar to: "The upgrade contains the following set of conflicting VIBs: Mellanox_bootbank_net.XXXXversionnumbersXXXX.