VMware ESX 6.5 – How to Resolve Driver Incompatibility Issues in vSphere Update Manager (VUM) When Updating Host Drives

Blog Written by Jason White
Champion Solutions Group Professional Services Engineer

After you assign a driver baseline to a host and scan for updates you will get a Compliance status of Incompatible. This is due to older drivers that are still on the host. You will need to remove the older drivers in order to install the new driver.

This is an example of an incompatible QLogic driver.

To get a list of the incompatible drivers highlight the baseline you are working with.

In the bottom pane you will see driver info with a status of conflict

Click on Show Details

This will open a second window with the info needed.

Under Compliance Status you will see the existing drivers that are conflicting with the new driver you are trying to install.

Document the drivers with the conflict.
You will need this information later to remove the conflicted drivers.


To remove the old driver, you will need to do this through CLI using SSH

You will need to ensure that SSH is enabled on the host

Using your choice of SSH client login to the host using root

You will need to verify that the device you are trying to upgrade the driver for is not using the driver that is listed as the conflict. In our example we are updating the Qlogic 25G NIC’s.

Run this command to get the list of NIC’s on the host.

# esxcli network nic list

Output:

In our example we are going to look at vmnic2 since it is one of the Qlogic 25G NIC’s.
Run this command to get detailed info on vmnic2
# esxcli network nic get -n vmnic2

Output:
Advertised Auto Negotiation: true
Advertised Link Modes: 10000None/Full, 25000None/Full, 40000None/Full, 50000None/Full, 100000None/Full, Auto
Auto Negotiation: false
Cable Type: DA
Current Message Level:
Driver Info:
Bus Info: 0000:0d:00:0
Driver: qedentv
Firmware Version: mfw 8.30.18.0 storm 8.22.2.0
 Version: 3.0.7.5
Link Detected: false
Link Status: Down
Name: vmnic2
PHYAddress: 0
Pause Autonegotiate: true
Pause RX: true
Pause TX: true
Supported Ports: DA
Supports Auto Negotiation: true
Supports Pause: true
Supports Wakeon: false
Transceiver: external
Virtual Address: 00:50:56:53:79:d8
Wakeon: None

In the output above you see the NIC is loaded with version 3.0.7.5

Now you need to look for the QLogic drivers that are loaded on this host.

Run the following command to get this info.
# esxcli software vib list |grep qe

qedentv      3.0.7.5-1OEM.650.0.0.4598673      QLC      VMwareCertified 2019-02-08
qedrntv      3.0.7.5.1-1OEM.650.0.0.4598673   QLC       VMwareCertified 2019-02-08
scsi-qedil   1.0.19.0-1OEM.600.0.0.2494585    QLC       VMwareCertified 2019-02-08

In this instance you will see there are similar Qlogic drivers and the scsi driver listed as one of the conflicts. The one with the conflict is 3.0.7.5.1 and the driver that is loaded is 3.0.7.5.
Now we need remove the conflicted qedrntv and scsi-qedil drivers.

Run the following command to get the driver info for the conflicted driver.
# esxcli software vib remove –vibname qedrntv

Once the driver is removed you will get the following results.

Removal Result
Message: Operation finished successfully.
Reboot Required: false
VIBs Installed:
VIBs Removed: QLC_bootbank_qedrntv_3.0.7.5.1-1OEM.650.0.0.4598673
VIBs Skipped:

Since there is no reboot required you can continue to remove the second conflicted driver.

# esxcli software vib remove –vibname scsi-qedil

Once the driver is removed you will get the following results.
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: QLC_bootbank_scsi-qedil_1.0.19.0-1OEM.600.0.0.2494585
VIBs Skipped:

In this instance a reboot is required.
Issue the reboot command
Once the host has rebooted you can run the software list command to verify that both the drivers have been removed.
Log back into the host once it has rebooted.
Run the following command to verify the drivers have been removed
# esxcli software vib list |grep qe
qedentv       3.0.7.5-1OEM.650.0.0.4598673       QLC       VMwareCertified 2019-02-08

You can see that only the running version of the driver is installed.
Go back to vCenter VUM and run another scan
You will now see that the baseline went from incompatible to Non-Compliant

 

From this point you can do a Remediate on the baseline and install the new driver.
Once the driver has been installed and the server reboots you can run another scan on the host and your driver should now be in a compliant state.

PREV

Data Protection and Disaster Recovery Combine to Meet Banking Needs

NEXT

Upgrade to POWER9 Planning Checklist

WRITTEN BY:

Erick Bacallao joined Champion Solutions Group in 2015 after a career of Software Development in Cuba at the National Cancer Care Institute of Cuba, followed by moving to the States with allAware.

 

Champion acquired allAware and its properties and Erick has utilized his extensive background and expertise in IT and Software Development to rise to VP of Product Development in less than 5 years. During this time, Erick has been involved with key projects that led to the launch of numerous products including CSP Boss, Inscape platform and 365 Productivity Insights.

 

Erick has a Bachelor of Science in Computer Science from the University of Havana. He won Gold Medals for Programming from the Ministry of Education in Cuba, and he is certainly still a Gold Medalist for Champion!

 

As President and CEO, Chris is responsible for the development of key strategic alliances and solution portfolio. He leads Champion’s go-to market and execution strategies for integrated offerings in the cloud, in security, and in digital infrastructure, always focusing on improving the customer experience and driving transformative business outcomes.

 

He also aligns key partner initiatives with company strategy and oversees corporate marketing and messaging to gain mindshare with customers and partners. It’s his vision and innovativeness that have catapulted Champion up the ranks to become a $100M+ organization—and one of the most respected solution providers in the industry.

 

Over the past two decades, Chris has also focused on mergers and acquisitions, as well as innovative product development. He is the original founder and an active member on the Board of Managed Maintenance, Inc., a SAAS provider and consulting firm that utilizes their award-winning One-View Portal to help the IT Channel and its customers manage their IT Maintenance.

 

Chris is also the original founder and chief strategist behind one of the original storage cloud providers, Storage Access / BluePoint. During the course of a few short years, he had raised $20M and took that company public on the Toronto Stock Exchange. It has since been acquired by Pomeroy.

 

In 2012, Chris led the acquisition of MessageOps and continued the product development and worldwide launch of its premier SAAS, 365 Command. Built on Microsoft Azure, 365 Command is currently managing over 1 million seats of Microsoft’s Office 365. After achieving this phenomenal milestone, 365 Command and other MessageOps O365 utilities were sold to Kaseya.

 

Over the past 35 years, Chris as worked tirelessly to not only advance his own career, but those of his employees. In addition to leading a $100M organization, Chris can also be found sitting with sales teams, cold calling and coaching, and validating why Champion has been listed on Best Places to Work by both South Florida Business Journal and Computerworld.

Ultimately, the success garnered by Champion Solutions Group, its associated companies, and their employees is due in large part to the leadership of its President and CEO. Perhaps the most fitting award Chris has earned is South Florida Business Journal’s 2013 Ultimate CEO Award.