VMware Cloud Community
sullivanindy
Contributor
Contributor
Jump to solution

HP DL380 G8 6.0 to 6.5 Conflicting VIBs

Hi,

What is the easiest way to upgrade or fix the Incompatible VIB issues when using esxcli or updates manager? I have 3 HP DL380 G8s that I just upgraded to 6.0 from 5.1 via esxcli, Upgraded to 6.5 VCSA and thought I was almost doen and smoth sailing but keep getting the errors using latest 6.5 iso or HP 6.5 iso.. I would just boot from CD but do not have local access and my iLo doesnt have virtual media license..

When trying with updates manager and latest HP esxi 6.5 i get

The upgrade contains the following set of conflicting VIBs:

QLogic_bootbank_scsi-qla4xxx_634.0.5.0-1OEM.500.0.0.472560

VMware_bootbank_net-nx-nic_5.0.626-3vmw.500.0.0.472560

QLogic_bootbank_scsi-qla4xxx_634.0.5.0-1OEM.500.0.0.472560

Brocade_bootbank_scsi-bfa_3.0.0.0-1OEM.500.0.0.406165

QLogic_bootbank_net-qlcnic_5.0.750-1OEM.500.0.0.472560

Brocade_bootbank_scsi-bfa_3.0.0.0-1OEM.500.0.0.406165

QLogic_bootbank_scsi-qla4xxx_634.0.5.0-1OEM.500.0.0.472560

VMware_bootbank_net-nx-nic_5.0.626-3vmw.500.0.0.472560

QLogic_bootbank_net-qlcnic_5.0.750-1OEM.500.0.0.472560

0 Kudos
1 Solution

Accepted Solutions
sullivanindy
Contributor
Contributor
Jump to solution

So I was able to get it to work by taking that list removing the vibs with the

esxcli software vib remove

commands..

Just nerve racking to check to see if they might be something in use or not..

I really do not understand this, why cant the update be more dynamic and figure out what drivers are used or not and only apply what is needed like most every other upgrade out there? This really takes the automatic nature our of the update manager or maybe i'm missing something..

View solution in original post

0 Kudos
1 Reply
sullivanindy
Contributor
Contributor
Jump to solution

So I was able to get it to work by taking that list removing the vibs with the

esxcli software vib remove

commands..

Just nerve racking to check to see if they might be something in use or not..

I really do not understand this, why cant the update be more dynamic and figure out what drivers are used or not and only apply what is needed like most every other upgrade out there? This really takes the automatic nature our of the update manager or maybe i'm missing something..

0 Kudos