Removing the conflicting VIB stated in the Update Manager.

[ankitrtr]

Hello Guys,

While upgrading my Esxi host in VCenter 6.5 my update manager gives me an incompatible error stating " The upgrade contains the following set of conflicting VIBs: Intel_bootbank_net-ixgbe_3.19.1-1OEM.500.0.0.472560 ". When I run the command esxcli network nic list I see that ixgbe is used by two of my NIC's . Will it be safe to  remove this vib ?

I have attached the screenshot below.

Thank you

[Vijay2027]

Network config will be lost if you remove the vib. What is the image profile?

esxcli softwrae profile get

[vijayku]

The issue is that you already have Intel_bootbank_net-ixgbe_3.19.1-1OEM.500.0.0.472560 installed on the esxi as evident from the snapshot. You need to create a new image profile from the same update package after removing the conflicting vib and than use the new update package for installation.  View vSphere ESXi Image Builder Installation and Usage  for complete instructions.

[IRIX201110141]

Why not updating your VIB to a more rescent one first and than performing the host update in general? The Intel nic looks very familar and i think we have 3 dozem of them in our dell 6.5 hosts.

Regards,

Joerg

[ankitrtr]

The image profile is ESXi-5.0.0-469512

[a_p_]

Wow, you're still running the ESXi 5.0 GA version that was released in 2011.

Please note that this ESXi version isn't supported by vCenter 6.5.

I'd suggest that you either reinstall the host - if it is supported by ESXi 6.5 at all - or upgrade it manually from the command line.

If you need assistance with this, please provide details, like the server vendor/model, RAID controller, network adapters, ..., and whether you have locally stored VMs on that host.

André

[bryanvaneeden]

As far as my own experiences go; If you remove the VIB, you're gonna have a bad day.

If you want to remove them, you can easily do this over multiple hosts in 1 go, I actually wrote a blog post for this a while ago which you might be able to use:

https://vcloudvision.com/2018/12/21/remove-vibs-through-powercli/

Anyway, a.p. is also correct that 5.0 is not supported anymore in a vCenter 6.5 environment, so you should indeed upgrade the host or create a lower version vCenter specifically for this purpose.

I am wondering how it's possible you even have the 5.0 ESXi hosts in your vCenter 6.5, I didn't think it would even accept them. 5.5 is the minimum version for vCenter 6.5.

[ankitrtr]

Its the image profile not the esxi. My esxi is on 5.5.0

[Vijay2027]

Ideally image profile and esx-base should be same. I would suggest to go for a re-install rather than fixing image profile db.

[bryanvaneeden]

Aah yes I see that now in the screenshot, I'm sorry about that. I got confused because you mentioned version 5.0 as your image profile.

What you can do is either create a new image profile with autodeploy/image builder:

Using vSphere ESXi Image Builder with the vSphere Web Client

OR

Just re-install the host with the ISO you want and use update manager to bring it to the most recent version.That should do the trick.