PDF(12.5 KB) View with Adobe Reader on a variety of devices
ePub(72.4 KB) View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle)(74.8 KB) View on Kindle device or Kindle app on multiple devices
Updated:October 24, 2017
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 document describes how to troubleshoot a problem when the Cisco Unified Computing Solutions (UCS) Virtual Interface Card (VIC) drivers not recognized by SUSE Linux Enterprise 12 after installation or an upgrade.
Cisco recommends that you have knowledge of these topics:
SUSE Linux Enterprise Administration
This document is restricted to Cisco UCS VIC drivers and SUSE Linux Enterprise (SLES) 12 SP1.
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, ensure that you understand the potential impact of any command.
Cisco UCS Virtual Interface Card (VIC) drivers facilitate communication between supported operating systems and Cisco UCS Virtual Interface Cards. Cisco UCS VIC driver ISO bundles include an eNIC and fNIC driver.
The eNIC driver is used for the Cisco UCS VIC Ethernet NIC. The fNIC driver is used for the Cisco UCS VIC Fibre Channel over Ethernet Host Bus Adapter (HBA).
In certain situations, the Redhat Package Manager (RPM) eNIC and fNIC driver installation finishes successfully, but the driver is not loaded by the SLES 12 SP1 Linux kernel. The driver version could be different in your environment and do have a dependency to the installed UCS release.
Note: Refer to the defect CSCvd50252 for additional information.
Check the Driver Version
Confirm the driver version installed by RPM.
(root) # rpm -qa -last |grep cisco
cisco-fnic-kmp-default-184.108.40.206_k3.12.49_11-1.x86_64 Tue 03 Oct 2017 10:32:32 AM EDT cisco-enic-usnic-kmp-default-220.127.116.114.534.0_k3.12.49_11-1.x86_64 Fri 04 Aug 2017 06:06:39 PM EDT
Next confirm the Linux Kernel driver module version.
From this example, you recognize a driver version mismatch between the version installed by RPM and loaded by the kernel.
UCS Release 3.1(3a) or Newer
Starting with Cisco UCS release 3.1(3a) new drivers are built and released as combo drivers. The drivers are available in the UCS Drivers ISO bundle folder /Drivers/Linux/Network/Cisco/VIC/SLES/SLES12.X/usNIC.