Table of Contents
This release note discusses the new features, known limitations, and open caveats for Cisco UCS Virtual Interface Card (VIC) Drivers, Release 2.2. It does not cover new features, resolved and open caveats for third-party drivers, and known limitations.
Table 1 shows the online change history for this document.
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/c/en/us/support/servers-unified-computing/unified-computing-system/products-technical-reference-list.html .
- ENIC - DPDK Integration
- Overlay Network Offload for Cisco UCS VIC 1340 and Cisco UCS VIC 1380 cards:
Note For documentation, see the Cisco UCS Manager Configuration Guides.
- Accelerated Receive Flow Steering (ARFS) support for Linux
- Adaptive Interrupt Coalescing (AIC) support for Linux
- Netflow monitoring support with the Cisco UCS VIC 1240, Cisco UCS VIC 1280, and Cisco UCS VIC 1225. For documentation, see the Cisco UCS Manager Configuration Guides .
- VMware NetQueue support through VMQ.
For complete information about the operating systems that Release 2.2 supports, see the Hardware and Software Interoperability for UCSM Managed Servers document for each Release 2.2 release located here:
Table 2 lists the caveats that have been resolved since Release 2.1(2).
A Cisco UCS B420 M3 blade server configured with more than 1.1 TB of memory and using a Cisco VIC adapter fails to render the multipath file system (FS) in read-only mode after performing a read or write operation.
Table 3 lists the open caveats in Release 2.2.
Customers using Red Hat Enterprise Linux version 5.8 or an earlier version should be aware that a libfc bug exists in distributions. The details of this bug are available in the Red Hat Bugzilla 884740.
- Supported only on UCS-VIC-M82-8P and UCSB-MLOM-40G-01.
- Supports 64 flow classifier entries per vNIC.
- Supports approximately 992 flow classifier entries per adaptor (approximately 15 vNICs with ARFS enabled).
- Does not provide any advantage when the link utilization is greater than 80%.
- When enabled, this feature disables static coalescing.
- VMware recommends no more than 8 NetQueues per port for standard or jumbo (9000) frame configurations.
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
An ISO file containing all B and C-Series documents is available at the following URL: http://software.cisco.com/download/type.html?mdfid=283853163&flowid=25821. From this page, click Unified Computing System (UCS) Documentation Roadmap Bundle .
Follow Cisco UCS Docs on Twitter to receive document update notifications.
For information on obtaining documentation, using the Cisco Bug Search Tool (BST), submitting a service request, and gathering additional information, see What’s New in Cisco Product Documentation at: http://www.cisco.com/c/en/us/td/docs/general/whatsnew/whatsnew.html .
Subscribe to What’s New in Cisco Product Documentation , which lists all new and revised Cisco technical documentation, as an RSS feed and deliver content directly to your desktop using a reader application. The RSS feeds are a free service.This document is to be used in conjunction with the documents listed in the “Related Cisco UCS Documentation” section.
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: 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 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.