The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter contains the following sections:
Step 1 | In a web browser, navigate to http://www.cisco.com. |
Step 2 | Under Support, click Download Software. |
Step 3 | Click Unified Computing and Servers. |
Step 4 |
If prompted, enter your Cisco.com username and password to log in. You must be signed in to download Unified Computing System (UCS) drivers. |
Step 5 |
Choose your server. Cisco UCS drivers are available for both Cisco UCS B-Series Blade servers and Cisco UCS C-Series Rack-Mount UCS-Managed Server Software. |
Step 6 | Click Unified Computing System (UCS) Drivers. |
Step 7 | Click the Release Notes button to download the latest version of the Release Notes. |
Step 8 |
For each driver ISO that you want to download, do the following:
|
Step 9 | Read the Release Notes before installing the Cisco UCS Virtual Interface Card drivers. |
Cisco UCS Virtual Interface Card drivers for ESX can be installed in the following ways:
During a new ESX OS installation.
After OS installation using the service console or through a command prompt.
Administrative privileges are required to install and update Cisco UCS Virtual Interface Card drivers.
A virtual media image may be used in the following procedure in place of physical media.
If the driver loads correctly, one of the following messages is displayed on the console screen after reboot:
Kernel module enic was loaded, but has no signature attached.
Kernel module fnic was loaded, but has no signature attached.
You can use this procedure to install offline bundles that have been copied from the driver ISO image to the ESX host.
If the driver loads correctly, one of the following messages appear on the console screen after reboot:
Kernel module enic was loaded, but has no signature attached.
Kernel module fnic was loaded, but has no signature attached.
The following example shows how to update an existing ESX driver with the latest version:
UCS-A# esxupdate update --nosigcheck --olderversion --maintenancemode --bundle fnic-1.4.0.195-esx400-release.zip