Introduction

Welcome to the MSI USA website. MSI designs and creates Mainboard, AIO, Graphics card, Notebook, Netbook, Tablet PC, Consumer electronics, Communication, Barebone. Software Download. Login to view your download history LOG IN NOW. 4000 Series Integrated Services Routers Login and Valid Contract Required. AnyConnect Secure Mobility Client v4.x Login and Valid Contract Required. Jabber for Windows Login and Valid Contract Required. Link to drivers on Logitech Website: camera if you can't find.

This document describes how to install device drivers on the Cisco Unified Computing System (UCS) for common operating systems.

Prerequisites

Requirements

Cisco recommends that you have knowledge of these topics:

• Cisco UCS Manager
• Cisco Integrated Management Controller (CIMC)
• Virtual Machine-ware (VMware), Windows Server, or Linux Operating Systems (OS)

Components Used

The information in this document is based on these hardware platforms:

• UCS B Series
• UCS C Series
  

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.

Background Information

Driver Definition

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.

Devices that Require a Driver

Here is a list of hardware devices that require device drivers:

• Ethernet Network Interface Card (ENIC)
• Fibre Channel Network Interface Card (FNIC)
• Redundant Array of Indepent Disks (RAID) Controller
• Motherboard Chipset
• Video Card
• Trusted Platform Module (TPM)

Drivers Versus Firmware

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.

Driver Dependence on Firmware

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.

When Drivers Must be Installed and Updated

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:

• UCS firmware upgrades
• Major OS upgrades/patches

Driver Versions Required

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.

Download the Driver Bundle

Complete these steps in order to download the driver bundle:

1. In a web browser, navigate to http://www.cisco.com.
2. Under Support, click Download Software.
3. Click Unified Computing and Servers.
4. Choose your server. Cisco UCS drivers are available for both Cisco UCS B-Series Blade servers and Cisco UCS C-Series Rack-Mount.
5. Click Unified Computing System (UCS) Drivers.
6. Select the bundle you want to download, and click Download Now.
   

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.

Identify Server Hardware

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.

Intel Motherboard Drivers Download

UCS B Series

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.

UCS C Series

This example shows how to find the server hardware devices in the CIMC. The server has a LSI 9266-8i RAID controller installed.

Identify the UCS Firmware Release

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.

UCS B Series

In this example, the UCS B Series runs UCS Release 2.1(1a).

UCS C Series

VMware KB: Installing Async Drivers On ESXi 4.x (1032936)

In this example, the UCS C Series runs UCS Release 1.4(6d).

OS Specifics

This section describes how to check driver versions and how to install drivers on common OSs.

VMware ESXi

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.

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.

Install the Driver

Complete these steps in order to install the driver:

1. Extract the contents of the driver zip file, and identify the *.vib file.
2. Use the Datastore Browser in order to upload the *.vib file to an ESXi host datastore.
   
3. Enter the host into Maintenance mode.
4. Install the driver.

ESXi 5.x/6.x

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.

ESXi 4.x

Use this command in order to install the driver on ESXi Release 4.x:

Finish the Installation

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.

Useful VMware CLI Commands

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

Microsoft Windows Server

This section describes how to install a driver on a Microsoft Windows server.

Check Current Driver Version

In order to check the device drivers in Microsoft Windows, use the Device Manager located in the Control Panel.

Check Current Driver Version CLI

For Windows Server Core the Plug-and-Play (PnP) Utility (PNPUtil.exe) is used to check driver versions.

Missing Drivers

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.

Install the Driver

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.

Install the Driver from CLI

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.

Useful Windows CLI Commands

Red Hat and SUSE Linux

This section describes how to install and validate a driver on Red Hat Enterprise Linux (RHEL) and SUSE Linux Enterprise Server (SLES).

SUSE Background Information

Starting with SLES 12 SP1, the Cisco eNIC and usNIC drivers are bundled together into a single RPM (vs. being packaged in separate RPMs, as they are for other Linux distributions). Bundling both drivers into a single RPM is required because of how kernel module dependencies are managed in SLES 12 SP1 and later. If you are not using Cisco usNIC functionality (i.e., if you have not provisioned any usNIC devices in UCSM / CIMC), the usNIC driver will effectively be ignored.

The eNIC and usNIC drivers have their own distinct version numbers. If you install the cisco-enic-usnic RPM on SLES 12 SP 1 or later, once those drivers are loaded into the running kernel (e.g., via rebooting), use cat /sys/module/enic/version and cat /sys/module/usnic_verbs/version to view their respective version numbers. The cisco-enic-usnic RPM has its own distinct version number as well. Because it represents the packaging of the eNIC and usNIC drivers, the RPM version number may look similar, but does not reflect the specific version of either driver.

For additional information on the exact driver versions query and review the RPM description section. The query looks similar to the example below:

Verify current driver versions and OS Release

Here is a list of commands used in order to check the current driver version and OS release:

Note: Be aware of the command modinfo [ driver name ]shows the module information about the driver that will be loaded upon next reboot. This is not necessarily the same driver version currently loaded in the running kernel. Review cat/sys/module/DRIVER_NAME/version to validate the driver version loaded in the currently running kernel, and/or use the command modinfo [ /path/to/driver.ko ] to validate the module info for a specific driver kernel object file.

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 3.2.210.18-738.12 bundled in the cisco-enic-usnic RPM package 3.2.272.23 is installed on SLES 15 GA.

Cisco Motherboards Driver Downloads

Install the Driver

Drivers in RHEL and SLES are installed using the Redhat Package Manager (RPM). Use this command in order to install the driver:

Cisco Motherboards Driver Download Windows 7

Tip: When you install drivers in Linux, ensure that you review the README files associated with the driver if available. You can look at the contents of the RPM to see where its associated README file was installed (e.g., rpm -qp kmod-enic). 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.

Msi Motherboard Driver Download

Appendix

Driver Name Reference Table

This table shows the driver names or prefixes for common drivers.

Related Information

0-9

• 3

  3G Small Cell

• 100

  Business 100 Series Access PointsBusiness 100 Series Mesh ExtendersSmall Business 100 Series Wireless Access Points

• 200

  Business 200 Series Access Points

• 300

  Small Business 300 Series Wireless Access Points

• 500

  Small Business 500 Series Wireless Access Points

• 600

  Aironet 600 Series OfficeExtend Access Point

• 700

  Aironet 700 Series Access PointsAironet 700W Series Access Points

• 800

  800 and 1900 Series ISR Integrated Access Points

• 1530

  Aironet 1530 Series

• 1540

  Aironet 1540 Series

• 1550

  Aironet 1550 Series

• 1560

  Aironet 1560 Series

• 1570

  Aironet 1570 Series

• 1600

  Aironet 1600 Series

• 1700

  Aironet 1700 Series Access Points

• 1800

  Aironet 1800 Access PointsAironet 1800 Series

• 1810

  Aironet 1810 Series OfficeExtend Access PointsAironet 1810w Series Access Points

• 1815

  Aironet 1815 Series Access Points

• 1830

  Aironet 1830 Series Access Points

• 1840

  Aironet 1840 Series Access Points

• 1850

  Aironet 1850 Series Access Points

• 2500

  2500 Series Wireless Controllers

• 2600

  Aironet 2600 Series

• 2700

  Aironet 2700 Series Access Points

• 2800

  Aironet 2800 Series Access Points

• 3000

  Universal Small Cell 3000 Series

• 3500

  3500 Series Wireless ControllersAironet 3500 Series

• 3600

  Aironet 3600 Series

• 3700

  Aironet 3700 Series Access PointsIndustrial Wireless 3700 Series

• 3800

  Aironet 3800 Series Access Points

• 4800

  Aironet 4800 Access Points

• 5000

  ASR 5000 Element Management SystemASR 5000 SeriesASR 5000 Session Control ManagerASR 5000 Small Cell GatewayUniversal Small Cell 5000 Series

• 5500

  5500 Series Wireless Controllers

• 5700

  5700 Series Wireless LAN Controllers

• 6300

  6300 Series Embedded Services Access PointsCatalyst IW6300 Heavy Duty Series Access Points

• 7000

  Universal Small Cell 7000 Series

• 7500

  Flex 7500 Series Wireless Controllers

• 7600

  7600 Wireless Security Gateway

• 8000

  Universal Small Cell 8000 Series

• 8500

  8500 Series Wireless Controllers

• 9000

  Universal Small Cell 9000 Series

• 9100

  Catalyst 9100 Access Points

• 9105

  Catalyst 9105AX Series Access Points

• 9115

  Catalyst 9115AX Series Access Points

• 9117

  Catalyst 9117AX Series Access Points

• 9120

  Catalyst 9120AX Series Access Points

• 9130

  Catalyst 9130AX Series Access Points

• 9800

  Catalyst 9800 Series Wireless ControllersCatalyst 9800 Wireless Controllers for Cloud

A-Z

The above products will no longer be supported by Cisco upon reaching the end-of-support date. They will be removed from the Cisco Support site two years after the end-of-support date.