Chapter 1. Overview

New and Changed Information

Chapter 2. Cisco UCS VIC Drivers

Overview of Cisco UCS Virtual Interface Card Drivers

Supported Hardware and Software

Obtaining the ISO Image Bundle

Installation Methods

Cisco UCS Manager User Documentation

Chapter 3. Installing Cisco UCS VIC Drivers for Windows

Installing Windows Drivers During OS Install (Windows 2012 and 2012 R2)

Installing Windows Drivers During OS Install (Windows 2008 SP2 and R2)

Installing Windows Drivers After OS Installation (Windows 2008-R2)

Installing Windows Drivers After OS Installation (Windows 2008 SP2)

Updating Existing Windows Drivers (Windows 2012 and 2012 R2)

Updating Existing Windows Drivers (Windows 2008 SP2 and R2)

Upgrading Cisco UCS VIC Drivers on Windows

Installing the iSCSI Crash Dump Driver

About the Cisco NIC Teaming Driver for Windows

Obtaining the NIC Teaming Driver for Windows

Installing the NIC Teaming Driver from the Control Panel

Installing the NIC Teaming Driver from the Command Prompt

Configuring the NIC Teaming Driver Using enictool.exe

Chapter 4. Uninstalling Cisco UCS VIC Drivers for Windows

Uninstalling Windows Drivers

Uninstalling the NIC Teaming Driver

Uninstalling the iSCSI Crash Dump Driver

Chapter 5. Install Cisco UCS VIC Drivers for ESXi

Installing ESXi Drivers During OS Installation

Installing Existing ESXi Drivers

Updating Existing ESXi Drivers

Chapter 6. Uninstall Cisco UCS VIC Drivers for ESXi

Uninstalling ESXi Drivers

Chapter 7. Install Cisco UCS VIC Drivers for Linux

Installing Linux Drivers to the Local Drive Using a Driver Disk

Installing Linux to SAN Storage Using the fNIC Driver and OS Driver Disk

Installing Linux Drivers using RPM

Installing Linux Drivers Using the Source Tarball

Displaying sNIC Status Using the sNIC Admin Utility

Displaying sNIC Statistics Using the sNIC Admin Utility

Installing Linux to DAS Storage Using the sNIC Driver Disk

Installing sNIC Linux Drivers using RPM

Installing sNIC Linux Drivers Using the Source Tarball

Upgrading Ubuntu with sNIC Driver Disk Image

Installing Ubuntu with sNIC Driver Disk Image

Chapter 8. Uninstall Cisco UCS VIC Drivers for Linux

Unloading sNIC Drivers

Uninstalling Linux Drivers

Preface

Audience

Conventions

Related Cisco UCS Documentation

Documentation Feedback

Copyright Page

Chapter 1. Overview

This chapter includes the following sections:

- New and Changed Information

New and Changed Information

The following table provides an overview of the significant changes to this guide for this current release. The table does not provide an exhaustive list of all changes made to this guide or of all new features in this release.

New Features and Changed Behavior in Cisco UCS Manager, Release 3.1(2)

Feature

Description

Where Documented

Consistent Device Naming

Consistent Device Naming (CDN) support has been expanded to include Red Hat Enterprise Linux 6.X and Red Hat Enterprise Linux 7.X.

Installing Linux Drivers to the Local Drive Using a Driver Disk

Chapter 2. Cisco UCS VIC Drivers

- Overview of Cisco UCS Virtual Interface Card Drivers

- Supported Hardware and Software

- Obtaining the ISO Image Bundle

- Installation Methods

- Cisco UCS Manager User Documentation

Overview of Cisco UCS Virtual Interface Card Drivers

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 driver and an fNIC driver. The eNIC is the driver for the Cisco UCS VIC Ethernet NIC. The fNIC is the driver for the Cisco UCS VIC Fibre Channel over Ethernet HBA. fNIC is not supported in UCS Manager Release 2.5.

For Windows, the ISO bundle also includes the iSCSI Crash Dump driver, which supports Windows crash dumps when the server is booted from the Cisco VIC Ethernet interface using the Microsoft iSCSI initiator.

Important:
Cisco UCS Manager Release 3.1(2) and later releases do not support Cisco UCS M-Series Servers.

Cisco UCS Manager Release 2.5 that introduced Cisco UCS M-Series Modular servers, continues to provide vNIC capabilities. Additionally, it provides for a new capability with its virtualized shared local storage. This virtual storage controller provides access to a virtual drive that is provided to the server through the shared storage controller and hard drives in the chassis. The virtual storage controller introduces a new PCIe device known as a SCSI NIC (sNIC), which is presented to the OS. The OS views these items as locally-attached SCSI devices.

The sNIC provides the pathway for SCSI commands from the server to the virtual drive. This controller is a new device to the OS and uses an sNIC driver that is loaded into the OS. Because the sNIC is a new PCIe device, the sNIC driver may not be part of some OS distributions. When that is the case, the sNIC driver must be loaded at the time of OS installation to see the storage device on the server. The sNIC driver, like the eNIC and fNIC drivers, is certified by the OS vendor and eventually included as part of the core OS install package. When the driver is present, the virtual drive is visible to the OS, and is presented as a standard hard drive connected through a RAID controller.

Supported Hardware and Software

For a complete list of supported hardware and software, see the Hardware and Software Interoperability Matrix for this release.

Obtaining the ISO Image Bundle

You can download the UCS Drivers ISO bundle, which contains most of the Cisco UCS Virtual Interface Card drivers. In some cases, a driver might be in a different bundle, which is noted in the installation procedure for that driver.

Important:
Cisco UCS Manager Release 3.1(2) and later releases do not support Cisco UCS M-Series Servers.

Procedure

Step 1

In a web browser, navigate to Cisco.com.

Step 2

Under Support> Downloads, click All Downloads.

Step 3

In the product selector, click Products, then click Servers - Unified Computing.

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 Cisco UCS B-Series Blade Server Software, Cisco UCS C-Series Rack-Mount UCS-Managed Server Software, and Cisco UCS M-Series Modular Server Software.

Step 6

Click Unified Computing System (UCS) Drivers.

Step 7

Click the Release Notes link to view the latest version of the Release Notes.

Step 8

For each driver ISO that you want to download, do the following:

1. Click the link for the release that you want to download.
The latest release version is selected by default.

2. Choose your download method and follow the prompts to complete your driver download.
Download

Downloads the software immediately.

Add to Cart

Adds the software driver ISO to your cart to download at a later time.

What to Do Next

Read the Release Notes before installing the Cisco UCS Virtual Interface Card drivers.

Installation Methods

Installing and updating the Cisco UCS Virtual Interface Card drivers requires administrative privileges.

VIC Drivers for ESXi

You can install the Cisco UCS Virtual Interface Card drivers for ESXi in the following ways:

- During a new ESXi OS installation.

- After OS installation using the service console or through a command prompt.

VIC Drivers for Linux

You can install the Cisco UCS Virtual Interface Card drivers for Linux in the following ways:

- OS driver disks

- To SAN Storage using the fNIC driver and OS driver disk. (only fNIC):

- RPM

- Source tarball

VIC Drivers for Linux on M-Series

Important:
Cisco UCS Manager Release 3.1(2) and later releases do not support Cisco UCS M-Series Servers.

In Cisco UCS Manager Release 2.5, sNIC drivers support the following Linux OS:

- RHEL

- Centos

- Ubuntu

You can install the sNIC drivers for Linux in the following ways:

- To DAS Storage using the sNIC driver disk.

- RPM (for RHEL and CentOS only).

- Ubuntu with the sNIC driver disk image.

VIC Drivers for Windows

You can install the Cisco UCS Virtual Interface Card drivers for Windows in the following ways:

- During a new Windows OS installation.

- After OS installation using the Device Manager.

Note

To avoid a system crash, ensure that you adhere to the following best practice for installing the VIC drivers during the OS installation.

- Upgrade the infrastructure firmware, which includes the UCS Manager, the fabric interconnects, and the chassis I/O modules.

- Upgrade the server and adapter firmware.

- Upgrade the OS VIC drivers.

Caution

Failure to adhere to the proper upgrade sequence can cause the server to crash.

Cisco UCS Manager User Documentation

Cisco UCS Manager offers you a new set of smaller, use-case based documentation described in the following table:

Guide

Description

Cisco UCS Manager Getting Started Guide

Discusses Cisco UCS architecture and Day 0 operations, including Cisco UCS Manager initial configuration and configuration best practices.

Cisco UCS Manager Administration Guide

Discusses password management, role-based access configuration, remote authentication, communication services, CIMC session management, organizations, backup and restore, scheduling options, BIOS tokens, and deferred deployments.

Cisco UCS Manager Infrastructure Management Guide

Discusses physical and virtual infrastructure components used and managed by Cisco UCS Manager.

Cisco UCS Manager Firmware Management Guide

Discusses downloading and managing firmware, upgrading through Auto Install, upgrading through service profiles, directly upgrading at endpoints using firmware auto sync, managing the capability catalog, deployment scenarios, and troubleshooting.

Cisco UCS Manager Server Management Guide

Discusses the new licenses, registering Cisco UCS domain with Cisco UCS Central, power capping, server boot, server profiles, and server-related policies.

Cisco UCS Manager Storage Management Guide

Discusses all aspects of storage management, such as SAN and VSAN in Cisco UCS Manager.

Cisco UCS Manager Network Management Guide

Discusses all aspects of network management, such as LAN and VLAN connectivity in Cisco UCS Manager.

Cisco UCS Manager System Monitoring Guide

Discusses all aspects of system and health monitoring, including system statistics in Cisco UCS Manager.

Chapter 3. Installing Cisco UCS VIC Drivers for Windows

- Installing Windows Drivers During OS Install (Windows 2012 and 2012 R2)

- Installing Windows Drivers During OS Install (Windows 2008 SP2 and R2)

- Installing Windows Drivers After OS Installation (Windows 2008-R2)

- Installing Windows Drivers After OS Installation (Windows 2008 SP2)

- Updating Existing Windows Drivers (Windows 2012 and 2012 R2)

- Updating Existing Windows Drivers (Windows 2008 SP2 and R2)

- Upgrading Cisco UCS VIC Drivers on Windows

- Installing the iSCSI Crash Dump Driver

- About the Cisco NIC Teaming Driver for Windows

- Obtaining the NIC Teaming Driver for Windows

- Installing the NIC Teaming Driver from the Control Panel

- Installing the NIC Teaming Driver from the Command Prompt

- Configuring the NIC Teaming Driver Using enictool.exe

Installing Windows Drivers During OS Install (Windows 2012 and 2012 R2)

If you are installing Windows on a SAN LUN, you must install Cisco VIC drivers for Windows during the OS installation. If you do not provide the drivers during the OS installation, the system is not able to detect the SAN LUN.

Except in Cisco UCS M-Series, if installing Windows on the local hard disk, it is not required to install the drivers during the OS installation. You can install the drivers after completing the OS installation.

Important:
Cisco UCS Manager Release 3.1(2) and later releases do not support Cisco UCS M-Series Servers.

In Cisco UCS M-Series, to install Windows on the local hard disk, you must install the VIC drivers during OS installation.

Caution

The driver installation file modifies certain registry entries, such as the disk timeout value of the system disk driver. Removing the driver does not restore these values.

Ensure that you adhere to the following best practice for installing the Windows drivers during the OS installation of Windows 2012 and 2012 R2. You must upgrade the infrastructure in the following order before upgrading the drivers.

- Upgrade the infrastructure firmware which includes the UCS Manager, the fabric interconnects, and the chassis I/O modules.

- Upgrade the server and adapter firmware.

- Upgrade the OS VIC drivers.

Caution

Failure to adhere to the proper upgrade sequence can cause the server to crash.

Procedure

Step 1

Start the Windows installation using the installation DVD or virtual media.

Step 2

On the Where do you want to install Windows screen, click Load Driver.

Step 3

Browse to the driver and click OK.The driver appears in the Select the drive to be installed window.

Step 4

Confirm that the correct driver is displayed on the Select the drive to be installed screen and click Next.

Step 5

Continue with your Windows installation on the LUN or select the LUN on the Where do you want to install Windows? screen.

Installing Windows Drivers During OS Install (Windows 2008 SP2 and R2)

If you are installing Windows on a SAN LUN, you must install Cisco VIC drivers for Windows during the OS installation. If you do not provide the drivers during OS installation, the system cannot detect the SAN LUN.

If you are installing Windows on the local hard disk, it is not required to install the drivers during the OS installation. You can install the drivers after completing the OS installation.

Caution

The driver installation file modifies certain registry entries, such as the disk timeout value of the system disk driver. Removing the driver does not restore these values.

Ensure that you adhere to the following best practice for installing the Windows drivers during the OS installation of Windows 2008 and 2008 R2. You must upgrade the infrastructure in the following order before upgrading the drivers.

- Upgrade the infrastructure firmware which includes the UCS Manager, the fabric interconnects, and the chassis I/O modules.

Upgrade the server and adapter firmware.

Upgrade the OS VIC drivers.

Caution

Failure to adhere to the proper upgrade sequence can cause the server to crash.

Note

Do not reboot until all three hotfixes are installed.

If these hotfixes are not installed, the device drivers are not correctly registered as critical devices, and cause a crash when they are being upgraded.

Procedure

Step 1

Start the Windows installation using the installation DVD or virtual media.

Step 2

On the Where do you want to install Windows screen, click Load Driver.

Step 3

Browse to the driver and click OK.The driver appears in the Select the drive to be installed window.

Step 4

Confirm that the correct driver is displayed on the Select the drive to be installed screen and click Next.

Step 5

Continue with your Windows installation on the SAN LUN or select SAN LUN on the Where do you want to install Windows? screen.

Installing Windows Drivers After OS Installation (Windows 2008-R2)

Caution

The driver installation file modifies certain registry entries, such as the disk timeout value of the system disk driver. Removing the driver does not restore these values.

Note

Follow the same steps for Windows 2012 and Windows 2012 R2.

Procedure

Step 1

Windows detects the newly installed Fibre Channel or Ethernet device and displays a Device driver software was not successfully installed message.

Step 2

Right-click the Ethernet or Fibre Channel device and choose Update driver software.

Step 3

Click Browse my computer for driver software.

Step 4

Click Let me pick from a list of device drivers on my computer.

Step 5

On the Select your drivers type from the list below window, leave Show All Devices selected and click Next.

Step 6

On the Select the device driver you want to install for this hardware window, click Have Disk.

Step 7

On the Install from Disk window, Browse for the driver and click OK.

Step 8

Click Next on the Select the device driver you want to install for this hardware screen.

Step 9

Click Close to exit the wizard.

Step 10

If Windows displays the following message following SAN boot, click Yes to restart the computer immediately.
System Settings Change. Windows has finished installing a new device. The software that supports your device requires that you restart your computer. You must restart your computer before the new settings will take effect. Do you want to restart your computer now?

Installing Windows Drivers After OS Installation (Windows 2008 SP2)

Caution

The driver installation file modifies certain registry entries, such as the disk timeout value of the system disk driver. Removing the driver does not restore these values.

Procedure

Step 1

When Windows detects the newly installed Fibre Channel or Ethernet device and displays the Found New Hardware wizard, click Locate and install driver software (recommended).

Step 2

When asked to insert the disk, click I don't have the disc. Show me other options.

Step 3

Click Browse my computer for driver software (advanced).

Step 4

Browse for the drivers and click Next.

Step 5

On the Would you like to install this device software? window, click Install.

Step 6

Click Close twice to complete the driver software installation.

Step 7

If Windows displays the following message following SAN boot, click Yes to restart the computer immediately.
System Settings Change. Windows has finished installing a new device. The software that supports your device requires that you restart your computer. You must restart your computer before the new settings will take effect. Do you want to restart your computer now?

Updating Existing Windows Drivers (Windows 2012 and 2012 R2)

Caution

The driver installation file modifies certain registry entries, such as the disk timeout value of the system disk driver. Removing the driver does not restore these values.

Follow the steps in this section to update existing Windows drivers. You can alternately upgrade the drivers using the Cisco VIO installer. Download the respective driver ISO for the required release, and use the MSI installer from that file location. For example, here are the paths to the specific releases:

- Windows/Installers/Cisco/MLOM/W2K12/x64/

- Windows/Installers/Cisco/MLOM/W2K12R2/x64/

Use the Cisco VIO installer to install and upgrade the VIC drivers across different versions and editions of Windows 2012 and 2012 R2. Refer to the readme file for additional information on the Cisco VIO installer.

Ensure that you adhere to the following best practice for installing the Windows drivers during the OS installation of Windows 2012 and 2012 R2.

Note

You must upgrade the infrastructure in the following order before upgrading the drivers.

- Upgrade the infrastructure firmware which includes the UCS Manager, the fabric interconnects, and the chassis I/O modules.

- Upgrade the server and adapter firmware.

- Upgrade the OS VIC drivers.

Caution

Failure to adhere to the proper upgrade sequence can cause the server to crash.

Procedure

Step 1

Start the Device Manager.

1. Right-click My Computer.

2. choose Manage.

3. choose Device Manager.

Step 2

Expand the adapter.

- For the eNIC driver, expand Network Adapters.

- For the fNIC driver, expand Storage Controllers.

Step 3

In the Devices list, right-click the adapter and choose Update Driver Software.
The Update Driver Software window opens.

Step 4

In the How do you want to search for driver software? area, choose Browse my computer for driver software.

Step 5

Choose your adapter and click Next.

Step 6

In the Install from Disk window, browse to the driver file and click OK.

Step 7

Click OK in the restart pop up to reboot the server.

Updating Existing Windows Drivers (Windows 2008 SP2 and R2)

Caution

The driver installation file modifies certain registry entries, such as the disk timeout value of the system disk driver. Removing the driver does not restore these values.

Follow the steps in this section to update existing Windows drivers. You can alternately upgrade the drivers using the Cisco VIO installer. Download the respective driver ISO for the required release, and use the MSI installer from that file location. For example, here is the path to the Windows 2008 R2 release:

- Windows/Installers/Cisco/MLOM/W2K8R2/x64/

Use the Cisco VIO installer to install and upgrade the VIC drivers across different versions and editions of Windows 2008 and 2008 R2. Refer to the readme file for additional information on the Cisco VIO installer.

Ensure that you adhere to the following best practice for installing the Windows drivers during the OS installation of Windows 2008 and 2008 R2.

Note

You must upgrade the infrastructure in the following order before upgrading the drivers.

- Upgrade the infrastructure firmware which includes the UCS Manager, the Fabric Interconnects, and the chassis I/O Modules.

- Upgrade the server and adapter firmware.

- Upgrade the OS VIC drivers.

Caution

Failure to adhere to the proper upgrade sequence can cause the server to crash.

Procedure

Step 1

Start the Device Manager.

1. Right-click My Computer.

2. choose Manage.

3. choose Device Manager.

Step 2

Expand the adapter.

- For the eNIC driver, expand Network Adapters.

- For the fNIC driver, expand Storage Controllers.

Step 3

In the Devices list, right-click the adapter and choose Update Driver Software.
The Update Driver Software window opens.

Step 4

In the How do you want to search for driver software? area, choose Browse my computer for driver software.

Step 5

Choose your adapter and click Next.

Step 6

In the Install from Disk window, browse to the driver file and click OK.

Step 7

Click OK in the restart pop up to reboot the server.

Upgrading Cisco UCS VIC Drivers on Windows

You can use the Cisco VIO installer to install and upgrade the VIC drivers across different versions and editions of Windows 2008, 2008 R2, 2012, and 2012 R2. The Cisco VIO installer is available as part of the Cisco UCS Drivers ISO bundle.

Installing the iSCSI Crash Dump Driver

Before You Begin

Ensure that the Microsoft iSCSI service is running.

Run edumputil from the Administrator account.

Ensure that the iSCSI vNIC is defined in the service profile.

Procedure

Step 1

Open a command prompt with administrator privileges.

Step 2

Enter the following command to install the iSCSI Crash Dump Driver using the iSCSI Crash Dump Driver utility:
edumputil -i "C:\sample\edumpw164.sys".

Step 3

Reboot the host.

About the Cisco NIC Teaming Driver for Windows

The Cisco NIC Teaming Driver for Windows is supported by Windows Server 2008 and Windows Server 2008 R2 64 bit. The driver can be installed through either the Windows Control Panel or the Windows command prompt.

Note

- Hyper-V guest operating systems are not supported with the Cisco NIC Teaming Driver for Windows.

- The NIC teaming driver supports up to four teams.

After installing the driver, you can configure NIC teaming using the enictool.exe command line utility provided with the driver files. The driver supports the following teaming modes:

- Active-Backup (with or without failback)

- Active-Active (transmit load balancing)

- 802.3ad LACP

The driver supports the following transmit load balancing methods:

- TCP connection

- Source and destination MAC address

- MAC address and IP address

The driver supports the following hashing options for load balancing:

- XOR hash

- CRC hash

Obtaining the NIC Teaming Driver for Windows

The Cisco NIC Teaming Driver is contained in the UCS-related Windows Utilities ISO.

Procedure

Step 1

In a web browser, navigate to Click Here .

Step 2

Under Support, click All Downloads.

Step 3

In the product selector, click Products, then 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 UCS drivers.

Step 5

Depending on your platform, choose Cisco UCS B-Series Blade Server Software, Cisco UCS C-Series Rack-Mount UCS-Managed Server Software.

Step 6

Click Unified Computing System (UCS) Utilities and select the Windows platform.

Step 7

Click the link for the release that you want to download.
The latest release version is selected by default.

Step 8

Click the Release Notes link to view the latest version of the Release Notes.

Step 9

Choose your download method and follow the prompts to complete your driver download.
Download

Downloads the software immediately.

Add to Cart

Adds the utilities ISO to your cart to be downloaded at a later time.

What to Do Next

Read the Release Notes for Cisco UCS Virtual Interface Card Drivers before installing the driver.

Installing the NIC Teaming Driver from the Control Panel

Procedure

Step 1

In Windows, click Start > Control Panel.

Step 2

Navigate to and click the Network and Sharing Center.
For the specific location see the Windows server documentation.

Step 3

In the Network and Sharing Center, click Manage Network Connections.

Step 4

In the Network Connections folder, right-click on an Ethernet interface and choose Properties.

Step 5

Click Install and choose Protocol > Add.

Step 6

Browse to the drivers directory and click OK.
The Cisco NIC Teaming Driver is installed and listed in the Ethernet interface properties.

What to Do Next

In the command prompt, run the enictool.exe utility to create and delete teams.

Installing the NIC Teaming Driver from the Command Prompt

Procedure

Step 1

In Windows, open a command prompt with administrator privileges.

Step 2

At the command prompt, enter enictool -p "drivers_directory"
The Cisco NIC Teaming Driver is installed using the .inf files located in the specified directory.

Example:
This example installs the teaming driver using the .inf files located in the temp directory:

C:\> enictool -p "c:\temp"

What to Do Next

Use the enictool.exe utility to create and delete teams.

Configuring the NIC Teaming Driver Using enictool.exe

Procedure

Step 1

In Windows, open a command prompt with administrator privileges.

Step 2

To create a team, enter enictool -c "list of connections" -m mode
The mode options are as follows:

- 1—Active Backup

- 2—Active Backup with failback to active mode

- 3—Active Active (transmit load balancing)

- 4—802.3ad LACP

Example:
This example creates a team of two NICs in Active Backup mode:

C:\> enictool -c "Local Area Connection" "Local Area Connection 2" -m 1

Step 3

To delete a team, enter enictool -d "name of the NIC team"

Example:
This example deletes a team called "Local Area Connection 3":

C:\> enictool -d "Local Area Connection 3"
Note:
Local Area Connection 3 is the name of the NIC team and not the name of the individual adapters.

Step 4

To view additional options and usage information, enter enictool /?
Use the displayed command option information to configure load balancing method, load balancing hash method, and other options.

Chapter 4. Uninstalling Cisco UCS VIC Drivers for Windows

- Uninstalling Windows Drivers

- Uninstalling the NIC Teaming Driver

- Uninstalling the iSCSI Crash Dump Driver

Uninstalling Windows Drivers

Procedure

Step 1

Start the Device Manager.

1. Right-click My Computer.

2. Choose Manage.

3. Choose Device Manager.

Step 2

Expand the adapter.

- For the eNIC driver, expand Network Adapters.

- For the fNIC driver, expand Storage Controllers.

Step 3

In the Devices list, right-click the adapter and select Uninstall.

- For the eNIC driver, right-click Cisco VIC Ethernet Interface.

- For the fNIC driver, right-click Cisco VIC FCoE Storport Miniport.

Step 4

In the Confirm Device Removal dialog box, click OK.

Uninstalling the NIC Teaming Driver

Procedure

Step 1

In Windows, open a command prompt with administrator privileges.

Step 2

At the command prompt, enter enictool -u
The Cisco NIC Teaming Driver is uninstalled.

Uninstalling the iSCSI Crash Dump Driver

Procedure

Step 1

Open a command prompt with administrator privileges.

Step 2

Enter the following command to uninstall the iSCSI Crash Dump Driver using the iSCSI Crash Dump Driver utility:
edumputil -u.

Step 3

Reboot the host.

Chapter 5. Install Cisco UCS VIC Drivers for ESXi

- Installing ESXi Drivers During OS Installation

- Installing Existing ESXi Drivers

- Updating Existing ESXi Drivers

Installing ESXi Drivers During OS Installation

You can use a virtual media image in place of the physical media.

Before You Begin

Ensure that you adhere to the following best practice for installing the ESXi drivers during the OS installation of ESXi. You must upgrade the infrastructure in the following order before upgrading the drivers.

- Upgrade the infrastructure firmware which includes the UCS Manager, the fabric interconnects, and the chassis I/O modules.

- Upgrade the server and adapter firmware.

- Upgrade the OS VIC drivers

Caution

Failure to adhere to the proper upgrade sequence can cause the server to crash.

Procedure

Step 1

Insert the ESXi installation DVD in the host machine's DVD drive.

Step 2

Restart the ESXi host.

Step 3

Accept the terms of the license agreement.

Step 4

Choose a keyboard type.

Step 5

When prompted for custom drivers, click Yes to install custom drivers.

Step 6

Click Add to eject the ESXi installation DVD.

Step 7

Place the supplemental eNIC or fNIC driver CD in the DVD driver of the ESXi host and click Next.

Step 8

Click Yes to load the system drivers.

Step 9

Complete the ESXi installation.
After the drivers are installed, you are prompted to remove the driver CD and reinsert the ESXi installation DVD.

What to Do Next

You can run the following command to check if the VMware vSphere Installation Bundle(VIB) installed successfully:

esxcli software vib list |grep -i vib_name

Installing Existing ESXi Drivers

You can use this procedure to install offline bundles that are copied from the driver ISO image to the ESXi host.

Before You Begin

Ensure that you adhere to the following best practice for installing the ESXi drivers during the OS installation of ESXi. You must upgrade the infrastructure in the following order before upgrading the drivers.

- Upgrade the infrastructure firmware which includes the UCS Manager, the fabric interconnects, and the chassis I/O modules.

- Upgrade the server and adapter firmware.

- Upgrade the OS VIC drivers

Procedure

Step 1

Extract the contents of the ISO image to the ESXi host.

Step 2

Identify the offline-bundle.zip file containing the eNIC or fNIC driver being installed.

Step 3

Log into the ESXi host using the vSphere Client with administrator privileges, such as root.

Step 4

Using DataStore Browser, upload the offline-bundle.zip file to the ESXi host's datastore.

Step 5

Enter the host into maintenance mode.

Step 6

Log into the ESXi console as root through SSH or iLO/DRAC.

Step 7

Copy the offline-bundle.zip file to a datastore accessible by the ESXi host by running this command:
cp offline-bundle.zip /vmfs/volumes/datastore_name

Step 8

Run the following command to install drivers using the offline bundle. An absolute path is required to run this command.
cp offline-bundle.zip /vmfs/volumes/datastore_name

For example:esxcli software vib install -d /vmfs/volumes/datastore_name/offline_bundle.zip

Step 9

You can run the following command to check that the VMware vSphere Installation Bundle(VIB) is installed successfully: esxcli software vib list | grep -i vib_name

Step 10

Restart the host.

Step 11

Exit maintenance mode.

Updating Existing ESXi Drivers

You can use this procedure to install offline bundles that were copied from the driver ISO image to the ESXi host.

Procedure

Step 1

Extract the contents of the ISO image to the ESXi host.

Step 2

Identify the offline-bundle.zip file containing the eNIC or fNIC driver being installed.

Step 3

Log into the ESXi host using the vSphere Client with administrator privileges, such as root.

Step 4

Using DataStore Browser, upload the offline-bundle.zip file to the ESXi host's datastore.

Step 5

Enter the host into maintenance mode.

Step 6

Log into the ESXi console as root through SSH or iLO/DRAC.

Step 7

Copy the offline-bundle.zip file to a datastore accessible by the ESXi host using the following command: cp offline-bundle.zip /vmfs/volumes/datastore_name

Step 8

Run the following command to install drivers using the offline bundle. An absolute path is required to run this command.
esxcli software vib update -d /path/offline-bundle.zip

For example:esxcli software vib update -d /vmfs/volumes/datastore_name/offline-bundle.zip

Step 9

You can run the following command to check that the VMware vSphere Installation Bundle(VIB) is installed successfully: esxcli software vib list | grep -i vib_name

Step 10

Exit maintenance mode.

Chapter 6. Uninstall Cisco UCS VIC Drivers for ESXi

- Uninstalling ESXi Drivers

Uninstalling ESXi Drivers

For information about uninstalling Cisco UCS VIC drivers for ESXi, see the VMware documentation.

Chapter 7. Install Cisco UCS VIC Drivers for Linux

- Installing Linux Drivers to the Local Drive Using a Driver Disk

- Installing Linux to SAN Storage Using the fNIC Driver and OS Driver Disk

- Installing Linux Drivers using RPM

- Installing Linux Drivers Using the Source Tarball

- Displaying sNIC Status Using the sNIC Admin Utility

- Displaying sNIC Statistics Using the sNIC Admin Utility

- Installing Linux to DAS Storage Using the sNIC Driver Disk

- Installing sNIC Linux Drivers using RPM

- Installing sNIC Linux Drivers Using the Source Tarball

- Upgrading Ubuntu with sNIC Driver Disk Image

- Installing Ubuntu with sNIC Driver Disk Image

Installing Linux Drivers to the Local Drive Using a Driver Disk

Before You Begin

Ensure that you adhere to the following best practice for installing the Linux drivers during the OS installation of Linux. Upgrade the infrastructure in the following order before upgrading the drivers.

- Upgrade the infrastructure firmware which includes the UCS Manager, the Fabric Interconnects, and the chassis I/O Modules.

- Upgrade the server and adapter firmware.

- Upgrade the OS VIC drivers.

Caution

Failure to adhere to the proper upgrade sequence can cause the server to crash.

Procedure

Step 1

Enable CDN from the BIOS settings.

Step 2

Insert the RHEL installation DVD and at the installation menu, enter Linux dd.
A prompt displays requesting the driver disk.
Note:
While performing an RHEL installation of drivers with dd.iso, press Tab at the initial launch of the DVD, edit the line and enter dd.

Step 3

Remove the RHEL installation DVD and insert the DVD generated from the dd.iso image. The RHEL installer reads the new drivers and overrides the default drivers.

Step 4

Reinsert the RHEL DVD to start the installation.
Note:
To configure Consistent Device Name (CDN) on RHEL, enter the biosdevname=1 option to the bootloader during the installation.

Step 5

To install RHEL 6.X, choose the package at the time of install. For further details, refer to the RHEL 6.X Deployment Guide.
Minimal install option does not include RHEL 6.X.

Step 6

RHEL 7.X is installed by default. For further details, refer to the RHEL 7.X Deployment Guide.

Step 7

Complete the RHEL installation.

Note:   During installation using RHEL 7.X, unmap the OS ISO image and map the driver ISO image. Run the refresh command, and then select the driver with a numerical option. Run the continue command, and then after extraction, remap the dvd.iso.

Step 8

Verify that the default RHEL driver was replaced by the driver in the dd.iso image.
For the eNIC driver, cat /sys/module/enic/version.

For the fNIC driver, cat /sys/module/enic/version.

To read the CDN label assigned to a given VNIC, use the command biosdevname -d in the host terminal.

Installing Linux to SAN Storage Using the fNIC Driver and OS Driver Disk

Procedure

Step 1

Create a vHBA on the Cisco UCS M81KR Virtual Interface Card.

Step 2

In Cisco UCS Manager, mark the vHBA bootable and add the WWPN of the SAN storage.
For more information on how to do this step, see the Cisco UCS Manager Configuration Guide.

Step 3

Boot the server using the RHEL installation DVD through vMedia.

Step 4

At the installation menu, enter linux dd.
The installer displays the available installation disks, including the local disk and the SAN disk discovered by the Cisco UCS M81KR Virtual Interface Card.

Step 5

For the installation target, choose the SAN storage device.
The RHEL installer reads the new drivers and overrides the default drivers to install RHEL on the SAN disk.

Step 6

Complete the RHEL installation and reboot the host, choosing SAN storage as the first boot option.

Installing Linux Drivers using RPM

If the management connection is over the eNIC, Cisco recommends using the serial or KVM console to complete the driver installation. Completing an rmmod of the current driver results in a loss of eNIC network connectivity.

Before You Begin

Remove existing drivers by entering one of the following commands:

- rmmod {enic | fnic}

- modprobe {-r enic | -r fnic}

Note

If you are booting from SAN storage, you cannot remove the existing driver using the rmmod fNIC command because this driver is required to use the SAN LUNs. Instead, enter the rpm --erase old-kmod-fnic-rpm-name command to erase the old RPM. Then, enter the rpm -ivh --nodeps new-kmod-fnic-rpm-name command to update the driver and reboot the node. The rpm -ivh --nodeps new-kmod-fnic-rpm-name command replaces the older driver with the new driver in the system memory.

If an fNIC RPM is not installed, and the fNIC driver that is available with the OS kernel is used, do not remove any existing drivers.

To determine the package that the fNIC belongs to, perform the following steps:

1. Find the installed fNIC modules

$ find /lib/modules -name *fnic*
/lib/modules/2.6.18-194.el5/kernel/drivers/scsi/fnic/fnic.ko

2. Determine which package the fNIC modules belong to.

cd /lib/modules/2.6.18-194.el5/kernel/drivers/scsi/fnic/fnic.ko
rpm -qf ./fnic.ko

If this command displays the fNIC package name, uninstall the fNIC RPM. You do not need to remove the fNIC RPM if it belongs to the Linux kernel package.

If drivers were previously installed using the driver disk installation process, the driver disk's enic/fnic.ko file is in the /lib/modules/'uname -r'/updates/ directory. The default search order of depmod (as specified in the /etc/depmod.d/depmod.conf.dist file) places a higher priority on the updates/ directory. Because new RPM installations place the enic/fnic.ko file under /lib/modules/'uname -r'/extra/, you can rename, delete or move the driver in the /lib/modules/'uname -r'/updates/ directory. Alternatively, you can modify the /etc/depmod.d/depmod.conf.dist to change the search order by placing extra/ before updates/. To ensure that the depmod picks up the RPM installation's driver and not the existing driver installed using the driver disk method.

Procedure

Step 1

Install the binary RPM by entering the corresponding command for your driver:

Driver

Command

eNIC driver on RHEL

rpm -ivh kmod-enic-version-0.x86_86.rpm

eNIC driver on RHEL with XEN support

rpm -ivh kmod-enic-version-0.x86_86.rpm

eNIC driver on SuSE

rpm -ivh cisco-enic-kmp-default-version-0.x86_64.rpm

eNIC driver on SuSE with XEN support

rpm -ivh cisco-enic-kmp-default-version-0.x86_64.rpm

fNIC driver on RHEL

rpm -ivh --nodeps kmod-fnic-

The driver is installed but not loaded.

Step 2

Load the driver in one of the following ways:

- Reboot the host.

- Load the driver manually while the host is running by entering the modprobe{enic | fnic} command.

Note:
If an error message displays that the module is in use, remove any modules that are using the driver, then remove the driver. Issuing the lsmod | grep {enic | fnic} command can help determine which modules are in use.

If there are many references to the eNIC or fNIC module and it is not possible to remove all of the dependencies, reboot the system.

Step 3

Verify the driver installation by entering the sbin/lsmod | grep {enic | fnic} command.

Installing Linux Drivers Using the Source Tarball

To install the Linux driver for eNIC or fNIC for the first time, complete the entire procedure. To upgrade an existing driver, remove the currently running eNIC or fNIC module, then complete steps 3-10.

Note

You can use the source tarball for any Linux distribution.

Before You Begin

Remove existing drivers by entering one of the following commands:

- /sbin/rmmod {enic | fnic}

- modprobe {-r enic | -r fnic}

Note

If you are booting from SAN storage, you cannot remove the existing driver using the rmmod fNIC command because this driver is required to use the SAN LUNs. Instead, enter the rpm --erase old-kmod-fnic-rpm-name command to erase the old RPM. Then, enter the rpm -ivh --nodeps new-kmod-fnic-rpm-name command to update the driver and reboot the node. Entering the rpm -ivh --nodeps new-kmod-fnic-rpm-name command replaces the older driver with the new driver in the system memory.

If drivers were previously installed using the driver disk installation process, the driver disk's enic/fnic.ko file is in the /lib/modules/'uname -r'/updates/ directory. The default search order of depmod (as specified in the /etc/depmod.d/depmod.conf.dist file) places a higher priority on the updates/ directory. Because new RPM installations place the enic/fnic.ko file under /lib/modules/'uname -r'/extra/, you can rename, delete or move the driver in the /lib/modules/'uname -r'/updates/ directory. Alternatively, you can also modify the /etc/depmod.d/depmod.conf.dist to change the search order by placing extra/ before updates/. To ensure that the depmod picks up the RPM installation's driver and not the existing driver installed using the driver disk method.

Procedure

Step 1

Copy the source tarball to the specified folder.
cp {enic- | fnic}version-num.tar.gz folder-name

Step 2

Change directories to the specified folder.
cd folder-name

Step 3

Extract the source tarball.
tar xvfz {enic- | fnic}version-num.tar.gz

Step 4

Change directories to the eNIC or fNIC version folder.
cd {enic- | fnic}version-num

Step 5

Create the driver by entering one of the following commands:

Driver

Command

eNIC

make CONFIG_ENIC=m

fNIC

make CONFIG_FNIC=m

Creating the driver builds the new .ko file and removes the existing driver. The new driver is copied to /lib/modules/'uname -r'/kernel/drivers/scsi/fnic/.

Step 6

Install the driver by entering one of the following commands:

Driver

Command

eNIC

make CONFIG_ENIC=m install

fNIC

make CONFIG_FNIC=m install

If an enic or fnic.ko file already exists in that directory, it is renamed as enic or fnic.ko.orig during the make installation. The make file backs up the currently installed enic or fnic.ko module and replaces it with the newly build module. For the fNIC, if libfc.ko, fcoe.ko, and libfcoe.ko exist on the system, they are left unmodified.

Step 7

(Optional)If you installed and are booting from SAN storage, rebuild the initrd file with the updated fNIC drivers.

Example:

# cp /boot/initrd-'uname -r'.img /boot/initrd-'uname -r'.img.orig
# mkinitrd /boot/initrd-'uname -r'.img 'uname -r'

Step 8

Load the driver in one of the following ways:

- Reboot the host

- Load the driver manually while the host is running by entering the modprobe{enic | fnic} command.

- Load the installed module manually by entering the /sbin/insmod /lib/modules/uname-r/extra/{enic | fnic}/{enic | fnic}.ko command.

Note:
If an error message displays that the module is in use, remove any modules that are using the driver, then remove the driver. Entering the lsmod | grep {enic | fnic} command can determine which modules are in use.

If there are many references to the eNIC or fNIC module and it is not possible to remove all of the dependencies, reboot the system.

Step 9

Verify the new driver is loaded.
/sbin/lsmod | grep {enic| fnic}

Step 10

(Optional)Enter the fcc command with any of the following arguments to run the FCC tool.

Argument

Description

No arguments specified

Lists all FC hosts, remote ports, and LUNs.

fcc --help

Lists all of the FC commands.
Note:
Only the list, luns, stats, info, and reset commands work at this time. The other options are supported in the software FCoE stack only.

fcc list hosthost-num

Lists only the hosts, ports, and LUNs associated with a single host.

fcc reset hosthost-num

Resets the specified host.

The FCC tool that is packaged with the driver and can be used to list all of the associated Fibre Channel HBAs, remote ports, and LUNs. Entering the make install command copies the FCC to the /root/bin/ directory and creates a link to this file in the /bin/ directory.

The following example extracts version 11 of the tarball to a folder called tmp and installs the driver. The driver is loaded using the reboot method.

$ cp enic-11.tar.gz /tmp
$ cd /tmp
$ tar xvfz enic-11.tar.gz
$ cd enic-11
$ make CONFIG_ENIC=m
# make CONFIG_ENIC=m install

What to Do Next

After the reboot, you can run the following commands to ensure that the correct driver is loaded:

$ ([root@linux-host]# dmesg | grep -i fnic
$ fnic: Cisco FCoE HBA Driver, ver 1.5.0.1
$ scsi0 : fnic
$ scsi1 : fnic

Displaying sNIC Status Using the sNIC Admin Utility

Procedure

# snic_admin
Displays the status of the sNIC device.

This example shows how to display the status of the sNIC device:

# snic_admin
SNIC HBAs:
host2
SCSI States:
HBA       Device      Mode             State           Busy [ DrVer ]
host2     snic2       Initiator        running            0      [ 0.0.1.2 ]

host2 Targets
snic_sas_tgt:2:0-0                       SNIC Target

host2 LUNs:
Path       Device     Size   Vendor          Model                State
2:0:0:0    sdb       32 GB   LSI             MR9271-8i            running
2:0:0:1    sdc       32 GB   LSI             MR9271-8i            running

Displaying sNIC Statistics Using the sNIC Admin Utility

Procedure

Command or Action

Purpose

Step 1

# snic_admin stats

Displays the statistics of the sNIC device.

This example shows how to display the statistics of the sNIC device:

# snic_admin stats
host0 Statistics:
------------------------------------------
IO Statistics
------------------------------------------
Active IOs                  : 28
Max Active IOs              : 50
Total IOs                   : 37751401
IOs Completed               : 37751373
IOs Failed                  : 0
IOs Not Found               : 0
Memory Alloc Failures       : 0
REQs Null                   : 0
SCSI Cmd Pointers Null      : 0
Max SGL for any IO          : 60
Max IO Size                 : 1024 Sectors
Max Queuing Time            : 1
Max Completion Time         : 1
Max IO Process Time(FW)     : 363 (363 msec)

SGL Counters
117396       4038       5428     623191     590080       1787       1542   30045078
6356933        578       2157        253        158         99         67       1918
86         99         46         26         31         27         36         30
19         29         27         45         20         25         31         56
13          1          1          1          1          1          3          4
2          1          2          0          1          0          2          1
0          0          2          3          2          2          0          1
1          1          2         12
-------------------------------------------
Abort Statistics
---------------------------------------------
Aborts                      : 0
Aborts Fail                 : 0
Aborts Driver Timeout       : 0
Abort FW Timeout            : 0
Abort IO NOT Found          : 0

-------------------------------------------
Reset Statistics
---------------------------------------------
HBA Resets                  : 0
HBA Reset Cmpls             : 0
HBA Reset Fail              : 0

-------------------------------------------
Firmware Statistics
---------------------------------------------
Active FW Requests             : 28
Max FW Requests                : 50
FW Out Of Resource Errs        : 0
FW IO Errors                   : 0
FW SCSI Errors                 : 0

---------------------------------------------
Other Statistics

---------------------------------------------
Last ISR Time               : 4367682369 ( 4367018.481279912)
Last Ack Time               : 4367682355 ( 4367018.467282040)
ISRs                        : 64909272
Max CQ Entries              : 9
Data Count Mismatch         : 0
IOs w/ Timeout Status       : 0
IOs w/ Aborted Status       : 0
IOs w/ SGL Invalid Stat     : 0
WQ Desc Alloc Fail          : 0
Queue Full                  : 0
Queue Ramp Up               : 0
Queue Ramp Down             : 0
Queue Last Queue Depth      : 0
Target Not Ready            : 0
IOs fw processing (<= 10ms) : 1042938
IOs fw processing (>10 && <= 100ms)    : 34946117
IOs fw processing (>100 && <= 500ms): 1762320
IOs fw processing (>500ms)  : 0

-------------------------------------------
IO Compl CQ Info
---------------------------------------------
CQ ring base        : 0x413854000
CQ ring size        : 192
CQ head             : 0
CQ tail             : 143
CQ tail color       : 0
CQ to clean idx     : 143
CQ last color       : 1

Installing Linux to DAS Storage Using the sNIC Driver Disk

Procedure

Step 1

In the Navigation pane of Cisco UCS Manager, click the Servers tab.

Step 2

On the Servers tab, expand Servers > Service Profiles.

Step 3

Create a service profile with two LUNs and associate it with a server.
Detailed information about creating a service profile and associating it with a server is available in Cisco UCS Server Manager CLI Configuration Guide.

Step 4

For the service profile that you created, configure a local disk as the first boot device.
Detailed information about configuring a local disk as the first boot device is available in Cisco UCS Server Manager CLI Configuration Guide. .

Step 5

Boot the server using the OS installation DVD through vMedia.

Step 6

At the installation menu, enter linux dd.
A message appears that asks you whether you have a driver disk.

Step 7

If you have a driver disk, select Yes, and map the driver disk dd-snic-version to the vMedia.

Step 8

Select the relevant vMedia.
The OS installer reads the new drivers and overrides the default drivers to install the OS on the DAS disk.

Step 9

Ensure that the DAS storage is discovered.

Step 10

Complete the OS installation, and reboot the host.

Installing sNIC Linux Drivers using RPM

You can use RPM to install sNIC drivers only on RHEL and CentOS.

Important:
Use this procedure only to upgrade driver versions

Procedure

Step 1

Install the binary RPM on RHEL and CentOS by using the rpm -ivh snic-rpm-package command for the sNIC driver.
The driver is installed, but not loaded.

If the OS is already installed by using DD, then using this command displays an error message. You can use the RPM package only for upgrading the driver version by using the rpm -Uvh snic-rpm-package command. After this is done, you cannot unload the sNIC driver.

Step 2

List the module information for the sNIC driver by entering the modinfo snic command.
The driver version in the kernel may not be upgraded before rebooting the host.

Step 3

Reboot the host.
After reboot, the host boots successfully with the latest driver.

Step 4

Verify that the driver version is the same when you run the modinfo snic command and the cat /sys/module/snic/version command.

Installing sNIC Linux Drivers Using the Source Tarball

Procedure

Step 1

Copy the source tarball to the specified folder.
cp {snic}version-num.tar.gz folder-name

Example:

cp snic-0.0.19.tar.gz

Step 2

Change directories to the specified folder.
cd folder-name

Example:

cd /tmp

Step 3

Extract the source tarball.
tar xvfz {snic}version-num.tar.gz

Example:

# tar xvf snic-0.0.19.tar

Step 4

Change directories to the sNIC version folder.
cd {snic}version-num

Example:

# cd snic-0.0.19

Step 5

Make the driver by entering the following command:
make CONFIG_SCSI_SNIC=m

Making the driver builds the new .ko file and removes the existing driver. The new driver is copied to /lib/modules/'uname -r'/kernel/drivers/scsi/snic/.

Example:

]# make CONFIG_SCSI_SNIC=m
make -C /lib/modules/2.6.32-431.el6.x86_64/build M=/root/snic-0.0.1.19/drivers/scsi modules
make[1]: Entering directory `/usr/src/kernels/2.6.32-431.el6.x86_64'
CC [M]  /root/snic-0.0.1.19/drivers/scsi/snic/snic_attrs.o
CC [M]  /root/snic-0.0.1.19/drivers/scsi/snic/snic_main.o
CC [M]  /root/snic-0.0.1.19/drivers/scsi/snic/snic_res.o
CC [M]  /root/snic-0.0.1.19/drivers/scsi/snic/snic_isr.o
CC [M]  /root/snic-0.0.1.19/drivers/scsi/snic/snic_ctl.o
CC [M]  /root/snic-0.0.1.19/drivers/scsi/snic/snic_io.o
CC [M]  /root/snic-0.0.1.19/drivers/scsi/snic/snic_scsi.o
CC [M]  /root/snic-0.0.1.19/drivers/scsi/snic/snic_disc.o
CC [M]  /root/snic-0.0.1.19/drivers/scsi/snic/snic_debugfs.o
CC [M]  /root/snic-0.0.1.19/drivers/scsi/snic/snic_trc.o
CC [M]  /root/snic-0.0.1.19/drivers/scsi/snic/snic_dbg.o
CC [M]  /root/snic-0.0.1.19/drivers/scsi/snic/vnic_cq.o
CC [M]  /root/snic-0.0.1.19/drivers/scsi/snic/vnic_intr.o
CC [M]  /root/snic-0.0.1.19/drivers/scsi/snic/vnic_dev.o
CC [M]  /root/snic-0.0.1.19/drivers/scsi/snic/vnic_wq.o
LD [M]  /root/snic-0.0.1.19/drivers/scsi/snic/snic.o
Building modules, stage 2.
MODPOST 1 modules
CC      /root/snic-0.0.1.19/drivers/scsi/snic/snic.mod.o
LD [M]  /root/snic-0.0.1.19/drivers/scsi/snic/snic.ko.unsigned
NO SIGN [M] /root/snic-0.0.1.19/drivers/scsi/snic/snic.ko
make[1]: Leaving directory `/usr/src/kernels/2.6.32-431.el6.x86_64'

Step 6

Install the driver by entering the following command:
make CONFIG_SCSI_sNIC=m install

If the snic.ko file already exists in that directory, it is renamed as snic.ko.orig during the make installation. The make file backs up the currently installed snic.ko module and replaces it with the newly built module.

Example:

]# make CONFIG_SCSI_SNIC=m install
install: backing up old versions of modules
#
# Just find all .ko files in /lib/modules/2.6.32-431.el6.x86_64/kernel/drivers/scsi/ directory,
# and backup the file if it isn't a soft link.
#
find /lib/modules/2.6.32-431.el6.x86_64/kernel/drivers/scsi/ \
\( -name snic.ko -o -false \) | \
xargs -t -r -I {} -i sh -c '[ -h {} ] || cp {} {}.orig'
install: completed backing up original OS .ko files
install: backing up last built .ko files
find /lib/modules/2.6.32-431.el6.x86_64/extra/ \
\( -name snic.ko -o -false \) | \
xargs -t -r -I {} -i sh -c ' mv {} {}.prev '
sh -c  mv /lib/modules/2.6.32-431.el6.x86_64/extra/snic/snic.ko /lib/modules/2.6.32-431.el6.x86_64/extra/snic/snic.ko.prev
make -C /lib/modules/2.6.32-431.el6.x86_64/build M=/root/snic-0.0.1.19/drivers/scsi modules_install
make[1]: Entering directory `/usr/src/kernels/2.6.32-431.el6.x86_64'
INSTALL /root/snic-0.0.1.19/drivers/scsi/snic/snic.ko
DEPMOD  2.6.32-431.el6.x86_64
make[1]: Leaving directory `/usr/src/kernels/2.6.32-431.el6.x86_64'
if [ -d /lib/modules/2.6.32-431.el6.x86_64/kernel/drivers/scsi//snic ]; then \
find /lib/modules/2.6.32-431.el6.x86_64/extra/ \
\( -name snic.ko -o -false \) | \
xargs -t -r -I {} -i sh -c 'rm -f `echo {} | sed -e \
"s!extra!kernel/drivers/scsi!g"`; ln -s {} `echo {} | \
sed -e "s!extra!kernel/drivers/scsi!g"`' ; \
fi
#
# Finally, copy the snic_admin script to /bin/
#
rm -f /bin/snic_admin
cp /root/snic-0.0.1.19/tools/bin/snic_admin /bin/
/sbin/depmod -a > /dev/null

Step 7

(Optional)If you installed and are booting from DAS storage, rebuild the initrd file with the updated sNIC drivers.

Example:

# cp /boot/initrd-'uname -r'.img /boot/initrd-'uname -r'.img.orig
# mkinitrd /boot/initrd-'uname -r'.img 'uname -r'

Step 8

Verify that the new driver is loaded.
/sbin/lsmod | grep {snic}

Example:

# lsmod | grep snic

snic                  108564  2

What to Do Next

After the reboot, you can run the following command to ensure that the correct driver is loaded:

$ ([root@linux-host]# dmesg | grep -i snic
snic:Cisco SCSI NIC Driver, ver 0.0.1.19
snic:Trace Facility Enabled.
snic:snic device 1137:  46:1137: 12a:
snic:snic device bus 5: slot 0: fn 0
scsi host0: snic0 = ffff880414a9a5e0 shost = ffff880414a9a000 device bus 5: slot 0: fn 0
snic 0000:05:00.0: PCI INT B -> GSI 17 (level, low) -> IRQ 17
snic 0000:05:00.0: setting latency timer to 64
snic:vNIC resources wq 64
snic:vNIC mtu 2048 intr timer 0
snic:vNIC flags 0x0 luns per tgt 256
snic:vNIC io throttle count 64
snic:vNIC port down timeout 0 port down io retries 30
snic:vNIC back end type = 1
snic:vNIC hid = 4
snic 0000:05:00.0: irq 33 for MSI/MSI-X
snic 0000:05:00.0: irq 34 for MSI/MSI-X
snic 0000:05:00.0: irq 35 for MSI/MSI-X
snic:vNIC interrupt mode: MSI-X
snic:wq 1 cq 2 intr 3
scsi0 : snic
scsi host0: snic state change from SNIC_INIT to SNIC_ONLINE
scsi host0: Retrieving snic params.
scsi host0: SNIC Device Probe Successful.
scsi host0: Scanning snic_das_tgt:0:0-5.
scsi host0: Scanning snic_das_tgt:0:0-4.

Upgrading Ubuntu with sNIC Driver Disk Image

Upgrading Ubuntu drivers includes upgrading three packages in the following order:

1. snic-image-generic_version_-0ubuntu1_amd64.deb

2. snic_version_-0ubuntu1_amd64.deb

3. snic-common_version-0ubuntu1_amd64.deb

Procedure

Step 1

Upgrade the three packages.

Example:

# sudo dpkg -i snic-3.13.0-32-generic_0.0.1.14-0ubuntu1_amd64.deb
(Reading database ... 55192 files and directories currently installed.)
Preparing to unpack snic-3.13.0-32-generic_0.0.1.14-0ubuntu1_amd64.deb ...
Unpacking snic-3.13.0-32-generic (0.0.1.14-0ubuntu1) over (0.0.1.12-0ubuntu1) ...
Setting up snic-3.13.0-32-generic (0.0.1.14-0ubuntu1) ...

# sudo dpkg -i snic_0.0.1.14-0ubuntu1_amd64.deb
(Reading database ... 55192 files and directories currently installed.)
Preparing to unpack snic_0.0.1.14-0ubuntu1_amd64.deb ...
Unpacking snic (0.0.1.14-0ubuntu1) over (0.0.1.14-0ubuntu1) ...
Setting up snic (0.0.1.14-0ubuntu1) ...
Building module database ...
filename:       /lib/modules/3.13.0-32-generic/extra/snic/snic.ko
author:         abc <abc@email.com>
version:        0.0.1.14
description:    Cisco SCSI NIC Driver
license:        GPL v2
srcversion:     FE26EB9752C9F8C25FBCD95
alias:          pci:v00001137d00000046sv*sd*bc*sc*i*
depends:
vermagic:       3.13.0-32-generic SMP mod_unload modversions
parm:           snic_log_level:bitmask for snic logging levels (int)
parm:           snic_trace_max_pages:Total allocated memory pages for snic trace buffer (uint)
parm:           snic_max_qdepth:Queue depth to report for each LUN (uint)
Updating initramfs ...
update-initramfs: Generating /boot/initrd.img-3.13.0-32-generic

# sudo dpkg -i snic-common_0.0.1.14-0ubuntu1_amd64.deb
(Reading database ... 55192 files and directories currently installed.)
Preparing to unpack snic-common_0.0.1.14-0ubuntu1_amd64.deb ...
Unpacking snic-common (0.0.1.14-0ubuntu1) over (0.0.1.12-0ubuntu1) ...
Setting up snic-common (0.0.1.14-0ubuntu1) ...

Step 2

Verify that the upgrade has completed successfully.

Example:

$ sudo dpkg -s snic
Package: snic
Status: install ok installed
Priority: standard
Section: kernel
Installed-Size: 26
Maintainer: abc <abc@email.com>
Architecture: amd64
Version: 0.0.1.14-0ubuntu1
Provides: snic
Depends: snic-3.13.0-32-generic (= 0.0.1.14-0ubuntu1)
Description: Meta-package for installing the latest snic drivers.
This is meta-package for Cisco SNIC driver (meta).

Installing Ubuntu with sNIC Driver Disk Image

Procedure

Step 1

Download the disk image from the build server.

Step 2

Map the driver disk image and OS ISO images to vMedia.

Note:   The driver disk image must be mapped as a removable disk under vMedia.

Step 3

Boot from the BIOS boot menu, by using the mapped DVD.
The Ubuntu OS detects the virtual driver disk.

Step 4

Select Yes to load drivers from the internal virtual driver disk.

Chapter 8. Uninstall Cisco UCS VIC Drivers for Linux

- Unloading sNIC Drivers

- Uninstalling Linux Drivers

Unloading sNIC Drivers

You can unload the sNIC driver, but uninstalling the sNIC drivers requires uninstalling the OS.

Important:
To unload an sNIC driver that is in use, reboot the host.

Procedure

Command or Action

Purpose

Step 1

# modprobe -r snic

Unloads the sNIC driver when the driver is not in use.

Note:
You cannot use this command to unload an sNIC driver that is in use.

This example shows how to unload sNIC drivers:

# modprobe -r snic

Uninstalling Linux Drivers

If the management connection is over the eNIC, Cisco recommends using the serial or KVM console to complete the driver installation. Completing an rmmod of the current driver results in a loss of eNIC network connectivity.

If you are booting from SAN storage, you cannot remove the existing fNIC driver using the rmmod fNIC command because this driver is required to use the SAN LUNs. Instead, enter the rpm --erase old-kmod-fnic-rpm-name command to erase the old RPM.

Procedure

Step 1

Remove existing drivers by entering one of the following commands:

Driver

Command

eNIC driver for RHEL

rpm -e kmod-enic

eNIC driver for SuSE

rpm -e cisco-enic-kmp-default

fNIC driver for RHEL

/sbin/rmmod fnic

fNIC driver for SuSE

rpm -e cisco-fnic-kmp-default

Step 2

Reboot the host.
If it is not possible to reboot the host, manually unload the running driver and reload the previously installed driver by entering the following commands:

rmmod enic

modprobe enic

Step 3

Verify that the driver is deleted from the host.
sbin/lsmod | grep {enic | fnic}

Preface

- Audience

- Conventions

- Related Cisco UCS Documentation

- Documentation Feedback

Audience

This guide is intended primarily for data center administrators with responsibilities and expertise in one or more of the following:

- Server administration

- Storage administration

- Network administration

- Network security

Conventions

Text Type

Indication

GUI elements

GUI elements such as tab titles, area names, and field labels appear in this font.

Main titles such as window, dialog box, and wizard titles appear in this font.

Document titles

Document titles appear in this font.

TUI elements

In a Text-based User Interface, text the system displays appears in this font.

System output

Terminal sessions and information that the system displays appear in this font.

CLI commands

CLI command keywords appear in this font.

Variables in a CLI command appear in this font.

[ ]

Elements in square brackets are optional.

{x | y | z}

Required alternative keywords are grouped in braces and separated by vertical bars.

[x | y | z]

Optional alternative keywords are grouped in brackets and separated by vertical bars.

string

A nonquoted set of characters. Do not use quotation marks around the string or the string will include the quotation marks.

< >

Nonprinting characters such as passwords are in angle brackets.

[ ]

Default responses to system prompts are in square brackets.

!, #

An exclamation point (!) or a pound sign (#) at the beginning of a line of code indicates a comment line.

Note

Means reader take note. Notes contain helpful suggestions or references to material not covered in the document.

Tip

Means the following information will help you solve a problem. The tips information might not be troubleshooting or even an action, but could be useful information, similar to a Timesaver.

Timesaver

Means the described action saves time. You can save time by performing the action described in the paragraph.

Caution

Means reader be careful. In this situation, you might perform an action that could result in equipment damage or loss of data.

Warning

IMPORTANT SAFETY INSTRUCTIONS

This warning symbol means danger. You are in a situation that could cause bodily injury. Before you work on any equipment, be aware of the hazards involved with electrical circuitry and be familiar with standard practices for preventing accidents. Use the statement number provided at the end of each warning to locate its translation in the translated safety warnings that accompanied this device.

SAVE THESE INSTRUCTIONS

Related Cisco UCS Documentation

Documentation Roadmaps

For a complete list of all B-Series documentation, see the Cisco UCS B-Series Servers Documentation Roadmap available at the following URL: Click Here .

For a complete list of all C-Series documentation, see the Cisco UCS C-Series Servers Documentation Roadmap available at the following URL: Click Here .

For information on supported firmware versions and supported UCS Manager versions for the rack servers that are integrated with the UCS Manager for management, refer to Release Bundle Contents for Cisco UCS Software.

Other Documentation Resources

Follow Cisco UCS Docs on Twitter to receive document update notifications.

Documentation Feedback

To provide technical feedback on this document, or to report an error or omission, please send your comments to ucs-docfeedback@cisco.com. We appreciate your feedback.

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.

THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.

The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB's public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.

NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS" WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: Click Here . Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)