mobinqasim786
Enthusiast
Enthusiast

Dell PowerEdge R715 - ESXi 6.5 Upgrade Incompatible

Hi Guys,

I'm trying to upgrade ESXi 6.0 to ESXi 6.5 on Dell R715 using Dell Customized image, but it showing Incompatible as there's conflicting VIBs which I'd need to remove first.

The upgrade contains the following set of conflicting VIBs:

Micron_bootbank_scsi-mtip32xx-scsi_2.4.10-1OEM.500.0.0.472560

Brocade_bootbank_scsi-bfa_3.2.1.0-1OEM.500.0.0.472560

Brocade_bootbank_net-bna_3.2.0.0-1OEM.500.0.0.472560

Brocade_bootbank_net-bna_3.2.0.0-1OEM.500.0.0.472560

VMware_bootbank_net-qlge_2.0.0.54-1vmw.500.0.0.472560

Brocade_bootbank_scsi-bfa_3.2.1.0-1OEM.500.0.0.472560

VMware_bootbank_net-qlge_2.0.0.54-1vmw.500.0.0.472560

Micron_bootbank_scsi-mtip32xx-scsi_2.4.10-1OEM.500.0.0.472560

Is there a way to find out if there VIBs are in use before I remove them? NIC list command shows the below output.

[root@esx1:~] esxcli network nic list

Name    PCI Device    Driver  Admin Status  Link Status  Speed  Duplex           MTU  Description

------  ------------  ------  ------------  -----------  -----  ------  -----------------  ----  ------------------------------------------------------------

vmnic0  0000:01:00.0  bnx2                 Up            Up            1000  Full     9000  QLogic Corporation QLogic NetXtreme II BCM5709 1000Base-T

vmnic1  0000:01:00.1  bnx2                  Up            Up            1000  Full      9000  QLogic Corporation QLogic NetXtreme II BCM5709 1000Base-T

vmnic2  0000:02:00.0  bnx2                  Up            Up            1000  Full      9000  QLogic Corporation QLogic NetXtreme II BCM5709 1000Base-T

vmnic3  0000:02:00.1  bnx2                   Up            Up            1000  Full      9000  QLogic Corporation QLogic NetXtreme II BCM5709 1000Base-T

vmnic4  0000:06:00.0  bnx2x                   Up            Down             0  Half     1500  QLogic Corporation NetXtreme II BCM57710 10 Gigabit Ethernet

Regards,

Mobin

Tags (1)
14 Replies
mobinqasim786
Enthusiast
Enthusiast

Hi Guys,

Just for the update I went ahead and removed the conflicting VIBs, rebooted hosts and then ran upgrade using ESXi 6.5 Dell Customised Image. Everything went fine and no issues so far. I've also updated Critical/Non-Critical patches using Update Manager (Not via Dell updates)

BenMax
Contributor
Contributor

Same problem, same solution and same successful result for PowerEdge R710.

Apparently, QLogic driver VMware_bootbank_net-qlge_2.0.0.54-1vmw.500.0.0.472560 is a driver for FCoE cards.

Disclaimer : PowerEdge R710 are not officially supported.

0 Kudos
RGM_FOG
Contributor
Contributor

Hello,

I also have 2 R715 servers that I would like to upgrade to 6.5 and given there seems to be no effort from Dell to upgrade them in their ISO.... Could you please post all the steps needeed for the upgrade to work? sorry but I'm not used to remove vibs procedure and I also don't know if your system was hanging on boot when you had to apply this troubleshooting.

Thanks for your help.

0 Kudos
TomKalabis
Enthusiast
Enthusiast

ad a same problem with upgrading Fujitsu host from ESXi 6.0 to 6.5, check my post Smiley Happy

VMware vSphere 6.5 – Conflict VIBs when upgrading ESXi 6.0 to 6.5

0 Kudos
BenMax
Contributor
Contributor

Could you please post all the steps needeed for the upgrade to work?

See above or this one too

I also don't know if your system was hanging on boot when you had to apply this troubleshooting

Before upgrading, there is a compatibility check. So your system will not hang on if you stopped here. The only reason to continue is you have a lab and you are curious.:smileydevil:

Removing vibs from the list can be done at any moment. The point is to be sure you are removing a vib (that is to say a driver) you don't use.

When doing upgrade from command line, you notice after removing the conficting vibs that the command to upgrade only link the profile associated with the new iso image and the real upgrade is done during reboot process which can take some time.

More info here

In our case, after system reboot, the esx does not reconnect automatically to vcenter so we had to do it.

Enjoy !

0 Kudos
mattiamigliorat
Contributor
Contributor

I'm struggling too

After vCenter upgrade to 6.5.0e i'm trying to update my DELL PowerEdge R620 via Update Manager with DELL ISO.

After "scan" process it show an incompatible, but in the status details it shows:

The upgrade contains the following set of conflicting VIBs:

The upgrade contains the following set of conflicting VIBs:

No info about the responsible vib...

I'm searching for it but nothing...

Any idea?

SteveO808
Contributor
Contributor

mattiamigliorati,

I have the exact same problem, 4 out of 6 hosts are showing incompatible with a blank list of VIBs,  I have engaged support and they are not helping.  Any news on your end?

Steve

0 Kudos
hussainbte
Expert
Expert

How did you actually remove the conflicting VIBs?

If you found my answers useful please consider marking them as Correct OR Helpful Regards, Hussain https://virtualcubes.wordpress.com/
0 Kudos
SteveO808
Contributor
Contributor

Matt,

In my case the vua.log showed two vibs that were preventing the upgrade, both Brocade:

net-bna

scsi-bfa

0 Kudos
dekoshal
Hot Shot
Hot Shot

SSH to the ESXi server

1. Run Command to list the vib

   esxcli software vib list |less

   Identify the VIB name from this list

2. Run Command to remove the vi

    esxcli software vib remove <vib name >

If you found this or any other answer helpful, please consider the use of the Correct or Helpful to award points.

Best Regards,

Deepak Koshal

CNE|CLA|CWMA|VCP4|VCP5|CCAH

daphnissov
Immortal
Immortal

On your remove command, you must specify the -n flag and pass the VIB name as an argument:  esxcli software vib remove -n <VIB_name>

dekoshal
Hot Shot
Hot Shot

Correct, however it do not mention "-n" in the below reference doc and looks like command worked in this case.

ESXi 6.5 Upgrade OEM VIB Conflict | I'm All vIRTUAL

0 Kudos
daphnissov
Immortal
Immortal

Well, first of all, that's not a "reference doc", it's just someone's blog. Secondly, the author uses the parameter --vibname which is the same functionally as -n if you were to look up that esxcli namespace.

dekoshal
Hot Shot
Hot Shot

Alright. Well that was my reference doc for this thread. Thanks for clarification.

0 Kudos