Guest

Cisco UCS Manager

Release Notes for Cisco UCS Virtual Interface Card Drivers, Release 2.0

 Feedback

Introduction

This release note discusses the new features, known limitations, and open caveats for Cisco UCS Virtual Interface Card Drivers, Release 2.0. It does not cover new features, known limitations, and open caveats for third party drivers.


Note


We sometimes update the documentation after original publication. Therefore, you should also review the documentation on Cisco.com for any updates.


Use this document in conjunction with the documents listed in the Related Documentation section.

The following table shows the online change history for this document.

Part Number Revision Date Description

OL-25372-01

September 19, 2011

Created release notes.

March 2, 2012

Updated to add NIC Teaming drivers for Windows.

July 19, 2012

Updated to indicate eNIC for Linux support for Multiple Receive Queues feature.

November 16, 2012

Updated Open Caveats section.

System Requirements

For a complete list of supported hardware and software, see the Hardware and Software Interoperability Matrix for this release located at: http:/​/​www.cisco.com/​en/​US/​products/​ps10477/​prod_​technical_​reference_​list.html

Known Limitations and Behaviors

The following known limitations are not otherwise documented:

  • FcoE driver for Windows fails to perform VLAN discovery. Since there is no VLAN discovery support, we recommend that you manually configure FCoE VLANs for all adapters that support FIP,
  • During iSCSI boot, only one initiator posts the iSCSI LUN to the BIOS boot menu, even if there are two iSCSI vNICs configured. For adapters configured with two iSCSI vNICs, only the iSCSI vNIC designated as Primary in the boot order will post the discovered iSCSI LUN to the BIOS boot menu and write the iBFT entry to host memory.
  • Rx CRC errors might happen on interfaces that are experiencing a heavy amount of incoming traffic. Disabling the following BIOS settings reduces the number of errors:
    • C6
    • Speedstep
    • executeDisable
    • Turbo Boost

Resolved Caveats

There are currently no resolved caveats.

Open Caveats

Bug ID Symptom Workaround

CSCuc20232

When the uplink FC port is flapped on the SAN path through a UCS Fabric Interconnect, the path from the vHBA to storage is occasionally lost.

Try one of the following:

  • Update the fnic driver to version 1.5.0.20 or later.
  • Configure the Fabric Interconnect FC uplinks in Port Channel mode. Path loss does not occur if the path is through an FC Port Channel.
  • If the server is not configured for SAN boot, unload and reload the fnic driver.
    Note   

    Unloading and reloading the fnic driver will cause a disruption to all SAN traffic from the server.

  • If the server is configured for SAN boot, reboot the server.

New Software Features in Release 2.0

July 19, 2012

The Release 2.0(3) update adds the following support:

Linux

eNIC support for the Multiple Receive Queues feature on Red Hat Enterprise Linux 6.x and SUSE Linux Enterprise Server 11.x operating systems.

To enable this support, complete the following steps while configuring a service profile in UCSM:

  1. Create and apply an adapter policy with the following parameters:
    • Transmit Queues = 1
    • Receive Queues = n (up to 8)
    • Completion Queues = # Transmit Queues + # Receive Queues
    • Interrupts = # Completion Queues + 2
    • Receive Side Scaling (RSS) = Enabled
    • Interrupt Mode = Msi X
    Do not modify the default setting for other parameters.
  2. Install eNIC driver 2.1.1.35 or later.
  3. Reboot the host.

March 2, 2012

The Release 2.0(1b) update adds the following support:

Windows

NIC Teaming driver support for the M81KR/P81E VIC (aka Palo) adaptor

September 19, 2011

The initial Release 2.0 adds the following support:

ESX

  • eNIC support for UCS Manager VM-FEX for VMware

Linux

  • eNIC support for UCS Manager VM-FEX for KVM

Windows

  • eNIC support for MSFT Software iSCSI initiator
  • eNIC and fNIC support for UCS 2180
  • fNIC support for FIP VLAN discovery protocol (P81E only)
  • First release of Cisco UCS Virtual Interface Card (VIC) iSCSI Crashdump driver.
  • First release of Cisco UCS Virtual Interface Card (VIC) iSCSI Crashdump driver installer utility

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: http:/​/​www.cisco.com/​go/​unifiedcomputing/​b-series-doc.

For a complete list of all C-Series documentation, see the Cisco UCS C-Series Servers Documentation Roadmap available at the following URL: http:/​/​www.cisco.com/​go/​unifiedcomputing/​c-series-doc .

Other Documentation Resources

An ISO file containing all B and C-Series documents is available at the following URL: http:/​/​www.cisco.com/​cisco/​software/​type.html?mdfid=283853163&flowid=25821. From this page, click Unified Computing System (UCS) Documentation Roadmap Bundle.

The ISO file is updated after every major documentation release.

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

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation.

Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.

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

 

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.

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: http:/​/​www.cisco.com/​go/​trademarks. 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)

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