PDF(266.9 KB) View with Adobe Reader on a variety of devices
ePub(72.6 KB) View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle)(77.7 KB) View on Kindle device or Kindle app on multiple devices
Updated:September 17, 2014
Bias-Free Language
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.
First Published: November 16, 2012 Last Updated: May 13, 2016
Part Number: OL-29921-01 C0
Introduction
This release note discusses new features, resolved caveats, open caveats, and behavior changes for Cisco UCS Virtual Interface Card (VIC) Drivers, Release 2.1. This document also includes current information that became available after the technical documentation was published. Use this document with the document listed in the Related Documentation section. Table 1 shows the change history for this document.
Revision History
Table 1 Online Revision History
Part Number
Revision
Revision Date
Description
OL-29921-01
A0
November 16, 2012
Created release notes.
B0
July 12, 2013
Updated release notes for Release 2.1(2a).
C0
July 22, 2013
Updated the New Software Features in Release 2.1(2a) section.
Table 2 lists the caveats that have been resolved since Release 2.0(5).
Table 2 Resolved Caveats
Bug ID
OS
Drivers/Firmware
Description
Fixed Version
VIC Firmware Fixes
CSCus64439
—
—
Cisco UCS Manager Mezz logs and VMware vmkernel logs no longer indicate storage latency and FNIC aborts.
2.1(3i)A
CSCuh78503
—
—
iSCSI reboot loop fails sometimes with oprom Initialize error 1.
2.1(3h)B, 2.1(3g)B
CSCus96016
—
—
During iSCSI boot, even when the boot goes through and target is discovered, the command iscsi_get_config still shows initiator_state: ISCSI_INITIATOR_FAILED.
2.1(3h)B
CSCuj99958
—
—
During heavy FC traffic the following error appeared: ASSERT FAILED (Exception 2 triggered!) @ mips/ecpu_panic.c:138.
2.1(3a)A
CSCtu17983
—
—
Boot up time was optimized on VIC cards.
2.1(2a), 2.1(3a)
CSCud62727
—
—
Improper queue sizing on VIC adapters from excessive IO timeouts, aborts, intermittent performance issues, and host hangs has been resolved.
2.1(1b)
VMware ESXi
CSCuf78224
ESXi 5.1
—
VMware Auto Deploy 5.1 with UCS B440 M2 / M72KR-Q hangs at boot.
2.1(2a), 2.1(3a)
CSCut43948
ESXi 5.5, 5.5 U2
—
In an Auto Deploy boot deployment, after upgrading the adapter firmware from Release 2.1(1a) to later versions for Cisco UCS VIC adapter M81KR on Cisco servers B230 M1 or C260, ESXi will no longer show a Purple Screen of Death (PSOD) while PXE booting.
2.1(3j)A
Red Hat Enterprise Linux
CSCuj61839
RHEL 6.3
VIC FW 2.2(0.336)B
P81E and M81KR adapter encountered an ASSERT FAILED error on a corrupt frame.
2.1(3a)B
CSCug54756
RHEL 6.3
eNIC 2.1(1.38)
ENIC driver for the VIC 1225 doesn't install for RHEL 6.3.
2.1(1.38)
Windows Server
CSCts85190
Windows Server 2008 R2
fNIC 2.1(0.18)
Computer intermittently performs poorly or stops responding when the Storport driver is used. To resolve this bug, you will need to apply a storport hotfix (http://support.microsoft.com/kb/2468345).
2.1(0.18)
CSCub19987
Windows Server 2008 R2
fNIC 2.1(0.18)
Storport.sys blue screens on multiple blades in UCS domains.
2.1(0.18)
CSCug93216
Windows 2012
fNIC 2.1(0.9)
FNIC Crashdump test failed - Can't generate MEMORY.DMP.
2.1(0.9)
CSCuj92809
Windows Server 2008 R2
fNIC 2.1(0.27)
Host OS reboot takes 17 minutes with multiple paths.
2.1(0.27)
CSCuu20647
Windows Server 2008 R2
fNIC 2.1(0.27)
2.1.0.25 FNIC driver causes BSOD on Windows 2008 R2 B200 M3.
2.1(0.27)
CSCuc91844
Windows Server 2003, 2008 R2, 2012
VIC FW 2.0(4.47)B
Multiple IBFT prevent redundant iSCSI paths in Windows.
2.1(1a)B, 2.1(1.223)B
Open Caveats
The following caveats are open in Release 2.1(1a).
Table 3 Open Caveats in Release 2.1(1a)
Defect ID
Symptom
Workaround
First Bundle Affected
CSCus64439
Servers experiencing poor storage performance and seeing an increasing number of aborts in the UCS Mezz logs for Cisco VIC 1240/1280/1340/1380 and within OS logs.
An immediate workaround for this issue is to reboot the blade that is flooding traffic to the IOM. This will result in the pause configuration being re-programmed.
2.1(1a)A
Resolved in 2.1(3i)
CSCuh61202
When performing a IOM reset test from the CLI under heavy FC traffic load conditions, all the FC traffic stops on the UCS VIC 1240 and UCS M82-8P VIC adapters.
An immediate workaround for this issue is to reboot the blade that is flooding traffic to the IOM. This will result in the pause configuration being re-programmed.
2.1(1a)A
Resolved in 2.1(3)B
CSCug17063
When a C240 M3 server is decommissioned then recommissioned, the following error appears: Lexington: vNIC device open failed, err -110.
An immediate workaround for this issue is to remove power from the server and then powering the server back up.
2.1(1a)C
Resolved in 1.5(2), 2.2(1b)
Customers using Red Hat Enterprise Linux version 5.8 or an earlier version should be aware that an libfc bug exists in distributions. The details of this bug are available in the Red Hat Bugzilla 884740.
Behavior Changes and Known Limitations
The following are known limitations:
Rx CRC errors might occur on interfaces that are experiencing a heavy amount of incoming traffic. Disabling the following BIOS settings reduces the number of errors:
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
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.
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.