Recently I ran into a problem, where I was unable to update the Qlogic Native Driver Module qedentv

I was working on a Network Performance issue & as always, Driver/Firmware Update struck first in the list of Troubleshooting Steps.

ESXi Version: VMware ESXi 6.5.0 Update 1 build-5969303

+ Ran the command “esxcfg-nics -l” to list the NIC Details
Name PCI Driver Link Speed Duplex MAC Address MTU Description
vmnic4 0000:65:00.0 qedentv Up 10000Mbps Full f4:e9:d4:f0:39:a2 1500 QLogic Corp. QLogic FastLinQ QL41xxx 1/10/25 GbE Ethernet Adapter

As per the VMware HCL, Driver update was required as the driver currently installed is

I feel VMware HCL for the Driver Download for “qedentv version” should be updated as it points to a generic link

The correct link for the Driver download is Here
Please note, it would require MyVMware Login Credentials.

+ Downloaded the driver and then uploaded the offline_bundle to the /tmp folder within the ESXi Host.

My understanding says if a module/vib is already installed within the ESXi Host, we should be using the command below
esxcli software vib update -d /tmp/

However, it gave below error

[root@host01] esxcli software vib update -d /tmp/
VIB QLC_bootbank_qedentv_3.9.31.0-1OEM.670.0.0.8169922 requires vmkapi_2_5_0_0, but the requirement cannot be satisfied within the ImageProfile.
Please refer to the log file for more details.

As per the above error, it needs vmkapi_2_5_0_0 which doesn’t exist within the image profile.

Resolution: To my surprise, it worked using “install” command with -f switch option as below

[root@host01] esxcli software vib install -d /tmp/ -f
Installation Result
Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.
Reboot Required: true
VIBs Installed: QLC_bootbank_qedentv_3.9.31.0-1OEM.670.0.0.8169922, QLC_bootbank_qedrntv_3.9.31.1-1OEM.670.0.0.8169922
VIBs Removed: QLC_bootbank_qedentv_3.0.7.5-1OEM.650.0.0.4598673
VIBs Skipped:

Bounced the Server & would check the Network Performance problem.

I wrote this article to save your time if you encounter a similar Driver Update problem.