Release Notes for Cisco UCS Virtual Interface Card Drivers, Release 2.5
Available Languages
Table of Contents
Release Notes for Cisco UCS Virtual Interface Card Drivers, Release 2.5
New Software Features in Release 2.5
Known Limitations and Behaviors
Related Cisco UCS Documentation
Obtaining Documentation and Submitting a Service Request
Introduction
This release note discusses the new features, known limitations, and open caveats for Cisco UCS Virtual Interface Card (VIC) Drivers, Release 2.5. It does not cover new features, resolved and open caveats for third-party drivers, and known limitations.
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 document listed in the Related Documentation section.
Table 1 shows the online change history for this document.
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/c/en/us/support/servers-unified-computing/unified-computing-system/products-technical-reference-list.html.
Operating System Support
For complete information about the operating systems that Release 2.5 supports, see the Hardware and Software Interoperability for UCSM Managed Servers document for each Release 2.5 release located here:
http://www.cisco.com/c/en/us/support/servers-unified-computing/unified-computing-system/products-technical-reference-list.htmlOpen Caveats
Table 2 lists the open caveats in Release 2.5(1a).
sNIC is always the first vNIC on each host. If it was not previously there and was added later, it will shift the BDF of all other vNICs, including the iSCSI overlay vNIC.
According to Microsoft, if the BDF location changes then the Windows PNP Manager for iSCSI does not know how to load the driver on the new vNIC, and will not work. The only alternative is to reinstall the OS.
http://support.microsoft.com/en-us/kb/976042/en-us provides more information about this issue.
Related Cisco UCS Documentation
For a complete list of all M-Series documentation, see the Cisco UCS M-Series Servers Documentation Roadmap available at the following URL: http://www.cisco.com/go/unifiedcomputing/m-series-doc.
Follow Cisco UCS Docs on Twitter to receive document update notifications.
Obtaining Documentation and Submitting a Service Request
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 delivers 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.
FeedbackContact Cisco
- Open a Support Case
- (Requires a Cisco Service Contract)