How to make your unsupported NIC work with ESXi 5.x or 6.0. Because in 6.0 VMware 'blacklisted' the drivers of ESXi 5.1. Its form VMware Download Center. IntelĀ® Ethernet Adapters that work with VMware* and links to VMware* Hardware Compatibility. Network Adapters and drivers in the VMware. Driver download.
This document describes how to install device drivers on the Cisco Unified Computing System (UCS) for common operating systems.
Cisco recommends that you have knowledge of these topics:
The information in this document is based on these hardware platforms:
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.
A device driver is software that is the interface between the OS and the hardware. The device driver translates general OS commands into specialized commands for a particular device, which allows the OS to communicate with hardware devices.
Here is a list of hardware devices that require device drivers:
Device drivers are different from firmware. Device driver software is installed on the OS, whereas firmware is lower-level code that is installed on hardware devices. Firmware is stored in non-volatile memory, such as ROM, Erasable Programmable ROM (EPROM), or flash memory.
Device drivers have a strong dependence on the device firmware. Device drivers must be compatible with the firmware level of a hardware device, so that they properly communicate with each other; driver and firmware functionality must match for correct operation to take place.
Device drivers come pre-installed with operating systems (such as Cisco OEM VMware ESXi images), or they can be manually installed post-OS setup.
Device drivers generally need to be updated after these procedures:
The UCS Hardware and Software Interoperability matrix outlines the driver versions that are required for a particular OS, device, and firmware combination.
Warning: The driver versions listed on the matrix have been tested and verified by the Cisco Engineering Quality Assurance team, and it is crucial to install the correct driver; otherwise, you might run into unexpected behavior which could lead to network outages.
This example shows that an FNIC driver version of 1.6.0.36 is required for a B200 M4 with a Virtual Interface Card (VIC) 1240 that runs ESXi 6.0 U3, on UCS Release 3.2.2.
Complete these steps in order to download the driver bundle:
Tip: When you choose which driver bundle to download, it is important to select the driver bundle version that is most similar to the server firmware release. For example, if you run a UCS-B Release 3.2(2b), then VMware driver bundle ucs-bxxx-drivers-vmware.3.2.2.iso is required.
Tip: Most VMware ESXi drivers are downloaded directly from www.vmware.com/download, with a search for the driver version. This is often quicker than if you were to download the entire driver bundle.
Before you select the correct driver, you must identify what hardware devices are installed on the server. This section describes how to find the devices located on the UCS Manager and in the CIMC.
This example shows how to find the server inventory in UCS Manager. Server 1/1 has two adapter models installed: the VIC 1240 and 1280.
This example shows how to find the server hardware devices in the CIMC. The server has a LSI 9266-8i RAID controller installed.
Before the correct driver version is selected, the UCS release must be identifed. This section describes how to identify the current UCS release installed on the servers.
In this example, the UCS B Series runs UCS Release 2.1(1a).
In this example, the UCS C Series runs UCS Release 1.4(6d).
This section describes how to check driver versions and how to install drivers on common OSs.
Use these commands in order to check the current driver versions and VMware build:
Tip: These commands are executed from the ESXi CLI. Secure Shell (SSH) must be enabled before an SSH session is initated.
Command | Description | ||||
vmware -vl | Displays the VMware build and patch level | ||||
esxcli software profile get | Displays flavor of install ISO | ||||
esxcfg-scsidevs -a | Lists the hosts HBAs and the associated driver name | ||||
esxcfg-nics -l | Lists the host vmnics and network interface card (NIC) models | ||||
ethtool -i vmnicX | Displays the Ethernet driver used by the specified vmnic | ||||
esxcli network nic get -n vmnicX | Displays the Ethernet driver used by the specified vmnic on ESXi 6.5 | ||||
vmkload_mod -s fnic | Displays the host bus adapter (HBA) driver version for the Cisco VIC | ||||
vmkload_mod -s enic | Displays the Ethernet driver version for the Cisco VIC | ||||
vmkload_mod -s nenic | Displays the Ethernet driver version for the Cisco VIC for ESXi 6.5 and later releases | ||||
vmkload_mod -s megaraid_sas | Displays the LSI MegaRAID driver version | ||||
vmkload_mod -s lsi_mr3 | Displays the LSI lsi_mr3 driver version(Native driver on ESXi 6.7) | ||||
vmkload_mod -s driver_name | Displays the driver version for a specified driver |
These examples show that vmnic2 uses a Cisco VIC and a driver version of 1.4.2.15a.
These examples show that the Qlogic Host Bus Adapter (HBA) uses driver qla2xxx Version 901.1k.1-14vmw.
Complete these steps in order to install the driver:
Use this command in order to install the driver on ESXi Release 5.x/6.x:
Note: If the drivers require a signature verification, run this command with the --no-sig-check switch. Ensure that you use the full path to the file.
Use this command in order to install the driver on ESXi Release 4.x:
After you install the driver with one of the previously mentioned commands, exit Maintenance mode and reboot the host. For more information on how to install drivers, reference the Related Information section at the end of this document.
Here are some other useful VMware commands that you can use when you install a driver:
Check Maintenance Mode Status
Check for Powered-On VMs
Power-Off VMs
Enter Maintenance Mode
Exit Maintenance Mode
This section describes how to install a driver on a Microsoft Windows server.
In order to check the device drivers in Microsoft Windows, use the Device Manager located in the Control Panel.
For Windows Server Core the Plug-and-Play (PnP) Utility (PNPUtil.exe) is used to check driver versions.
Hardware devices with missing drivers are displayed in the Device Manager with a yellow question mark. These devices should be updated with the correct driver in order to prevent unexpected behavior.
In order to install or update a driver in Microsoft Windows, right-click on the device, and choose Install/Update Driver in order to start the Installation Wizard.
The PNPUtil tool can also be used to install drivers from the CLI. The driver ISO bundle can be mounted via the UCS KVM Console Virtual Media.
Command | Description |
pnputil.exe -e | List all installed 3rd party drivers |
pnputil.exe -a <INF name> | Install driver |
pnputil.exe -d <INF name> | Delete driver |
pnputil.exe -f -d <INF name> | Force delete driver |
This section describes how to install a driver on Redhat and SuSE Linux systems.
Here is a list of commands used in order to check the current driver version and OS release:
Command | Description |
modinfo driver_name | Displays driver version for the specified driver |
modinfo enic | Displays the Ethernet driver for the Cisco VIC adapter |
modinfo fnic | Displays the FC NIC driver for the Cisco VIC adapter |
modinfo megaraid_sas | Displays the LSI MegaRAID driver version |
lsmod -l | Lists currently-loaded drivers in the kernel |
cat /etc/redhat-release | Shows the Redhat release |
cat /etc/SuSE-release | Shows the SUSE release |
uname -a | Shows kernel related information |
Tip: Refer to the Driver Name Reference Table located in the Appendix for examples of other common driver names.
This example shows that an ENIC driver version of 2.1.2.41 is installed on Redhat Enterprise Linux Release 6.2.
Drivers in Redhat and SuSE Linux are installed with the Redhat Package Manager (RPM). Use this command in order to install the driver:
Tip: When you install drivers in Linux, ensure that you review the README files associated with the driver. These are located in the same directory as the driver file. Some RPM driver packages have dependencies on other modules, and require installation of additional RPM packages. The README files contain full instructions on how to install the driver file.
This table shows the driver names or prefixes for common drivers.
Command | Description |
enic | Cisco VIC Ethernet NIC |
fnic | Cisco VIC FC NIC |
qle or qla | Qlogic adapter |
lpfc | Emulex HBA (light pulse) |
be2net | Emulex Ethernet NIC |
igb or ixgbe | Intel NICs |
bnx | Broadcom adapter |
megaraid | LSI MegaRAID |
megasr | Embedded SW RAID |
nenic | Cisco VIC Ethernet NIC for ESXi 6.5 |