ESXi 6.0 to 6.5 upgrade - Conflicting VIBs in HP image

Upgrading HP 6.0 Image to 6.5 is listed as incompatible in VUM due to below VIB Conflicts

The upgrade contains the following set of conflicting VIBs:
Emulex_bootbank_scsi-lpfc820_8.2.4.151.65-1OEM.500.0.0.472560
Emulex_bootbank_scsi-lpfc820_8.2.4.151.65-1OEM.500.0.0.472560

Remove the conflicting VIBs or use Image Builder to create a custom upgrade ISO image that contains the newer versions of the conflicting VIBs, and try to upgrade again.

Fix

1) Look for the drivers first

[root@esx01:~] esxcli software vib list | grep  lpfc
lpfc                           11.4.199.0-1OEM.600.0.0.2768847        EMU              VMwareCertified   2018-06-01
scsi-lpfc820                   8.2.4.151.65-1OEM.500.0.0.472560       Emulex           VMwareCertified   2017-09-25

So I have ipfc and scsi-lpfc820 drivers installed. 

2) Check if it is in use

[root@esx01:~] esxcli network nic list
Name    PCI Device    Driver  Admin Status  Link Status  Speed  Duplex  MAC Address         MTU  Description
------  ------------  ------  ------------  -----------  -----  ------  -----------------  ----  -------------------------------------------------------------
vmnic0  0000:03:00.0  tg3     Up            Down             0  Half    a0:d3:c1:fb:fc:e0  1500  Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet
vmnic1  0000:03:00.1  tg3     Up            Down             0  Half    a0:d3:c1:fb:fc:e1  1500  Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet
vmnic2  0000:03:00.2  tg3     Up            Down             0  Half    a0:d3:c1:fb:fc:e2  1500  Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet
vmnic3  0000:03:00.3  tg3     Up            Down             0  Half    a0:d3:c1:fb:fc:e3  1500  Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet
vmnic4  0000:24:00.0  elxnet  Up            Up           10000  Full    c4:34:6b:1f:05:a8  1500  Emulex Corporation HP NC552SFP Dual Port 10GbE Server Adapter
vmnic5  0000:24:00.1  elxnet  Up            Up           10000  Full    c4:34:6b:1f:05:ac  1500  Emulex Corporation HP NC552SFP Dual Port 10GbE Server Adapter

[root@esx01:~] esxcfg-scsidevs -a
vmhba0  ata_piix          link-n/a  sata.vmhba0                             (0000:00:1f.2) Intel Corporation Patsburg 4 port SATA IDE Controller
vmhba1  hpsa              link-n/a  sas.5001438031025c30                    (0000:02:00.0) Hewlett Packard Enterprise Smart Array P420i
vmhba4  lpfc              link-up   fc.20000090fa561e40:10000090fa561e40    (0000:0a:00.0) Emulex Corporation LPe12000 8Gb Fibre Channel Host Adapter
vmhba5  lpfc              link-up   fc.20000090fa561e41:10000090fa561e41    (0000:0a:00.1) Emulex Corporation LPe12000 8Gb Fibre Channel Host Adapter
vmhba32 usb-storage       link-n/a  usb.vmhba32                             () USB
vmhba33 ata_piix          link-n/a  sata.vmhba33                            (0000:00:1f.2) Intel Corporation Patsburg 4 port SATA IDE Controller


Highlighted are the drivers in use and that confirmed scsi-lpfc820 is not in use. 

3) Remove the conflicting VIB
[root@esx01:~] esxcli software vib remove -n scsi-lpfc820

Removal Result
   Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.
   Reboot Required: true
   VIBs Installed:
   VIBs Removed: Emulex_bootbank_scsi-lpfc820_8.2.4.151.65-1OEM.500.0.0.472560
   VIBs Skipped:

4) Reboot ESXi host

5) Scan again and check status on VUM status
This time it shows Non-Compliant! 

So I decided to try removing Mellenox driver, which used to give issues with ESX5x to 6 upgrade! 

[root@esx01:~] esxcli software vib list |grep Mellanox
net-mlx4-core                  1.9.9.4-1OEM.550.0.0.1331820           Mellanox         VMwareCertified   2017-09-25
net-mlx4-en                    1.9.9.4-1OEM.550.0.0.1331820           Mellanox         VMwareCertified   2017-09-25

[root@esx01:~] esxcli software vib remove -n net-mlx4-en
Removal Result
   Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.
   Reboot Required: true
   VIBs Installed:
   VIBs Removed: Mellanox_bootbank_net-mlx4-en_1.9.9.4-1OEM.550.0.0.1331820
   VIBs Skipped:

[root@esx01:~] esxcli software vib remove -n net-mlx4-core
Removal Result
   Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.
   Reboot Required: true
   VIBs Installed:
   VIBs Removed: Mellanox_bootbank_net-mlx4-core_1.9.9.4-1OEM.550.0.0.1331820
   VIBs Skipped:

Rebooted ESXi host again. 
Once it came back, scanned again with VUM and checked status. It was happy this time and I could update it without issues.

Thank you! 













Comments

Post a Comment

Popular posts from this blog

vCenter Maintenance - Issue Non-ephemeral Portgroup

Image
Hi Friends, We had a issue last day due a miss configuration. We used to keep our vCenters on ephemeral port groups for troubleshooting purposes in case of any issue. We have a new vCenter now and as per standards our project team put that on a portgroup which was named as "ephemeral", but it was quiet late we found it was not actually setup as an ephemeral port group, but static instead :(. So issue was a config issue, but I wanted to share how we solved it hopping it might help someone in other situations too. The story is like this.  We planned to test an outage situation, by bringing down vCenter, to test if our VRA pre-build check can identify it. One of our lazy engineers went to Web Client of the ESXi server hosting vCenter and decided to turn the NIC off for the test. He received below error while turning it back on Description :- Reconfigure this virtual machine Virtual machine :- Non-PROD_vCenter State -: Failed - Invalid configuration for device '3
Read more

vMotion Failing at 21% with error ""The vMotion failed because the destination host did not receive data from the source host on the vMotion network. Please check your vMotion network settings and physical network configuration and ensure they are correct."

Image
vMotion Failing at 21% with error ""The vMotion failed because the destination host did not receive data from the source host on the vMotion network. Please check your vMotion network settings and physical network configuration and ensure they are correct." Scenario We built a new ESXi 6.7 Cluster and we couldn't make vMotions work there Troubleshooting steps 1) Make sure there is no IP address conflict. 2) SSH to ESXi and do a VMK Ping check For Default TCP/IP Stack vmkping 10.11.7.188 Or If you are using Multi NIC vMotion, you might want to specify which VMK interface to use vmkping -I vmk<vmkinterfacenumber> <Destination VMK IP to Ping> Eg -:  vmkping -I vmk3 192.168.1.1 For vMotion Stack I f you try above vmkping command on a ESXi host with VMK interfaces on VMK stack, they will fail with an error  Unknown interface 'vmk': Invalid argument Because the command is looking for TCP/IP stack by default and this VMK wont be listed there. So you need
Read more

applmgmt service wont start on PSC Appliace post converge operation

Scenario We had a vCenter with External PSC. We converged them and converge job was successful execpt a cert warning. After a week we tried to decommission the old PSC appliance and found that the status is shown in WebClient as "Unknown" Up on checking we found  applmgmt in stopped state. Tried to start it but it failed with below error [ ~ ]# service-control --status Running:  lwsmd pschealth vmafdd vmcad vmdird vmdnsd vmonapi vmware-analytics vmware-certificatemanagement vmware-cis-license vmware-cm vmware-rhttpproxy vmware-sca vmware-sts-idmd vmware-stsd vmware-vapi-endpoint vmware-vmon Stopped:  applmgmt vmware-statsmonitor [ ~ ]# service-control --start applmgmt Operation not cancellable. Please wait for it to finish... Performing start operation on service applmgmt... Error executing start on service applmgmt. Details {     "detail": [         {             "translatable": "An error occurred while starting service '%(0)s'",        
Read more