Table of Contents

vicdrivers_22_rn.fm

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

First Published: December 12, 2013

Last Updated: June 14, 2017

Part Number: OL-31142-01

Introduction

Table 1 Online Revision History

Part Number

Revision

Revision Date

Description

OL-31142-01

A0

December 12, 2013

Created the release notes document.

B0

May 30, 2014

Updated release notes for Cisco UCS

Software Release 2.2(2c).

C0

September 8, 2014

Updated release notes for Cisco UCS

Software Release 2.2(3a).

D0

January 5, 2015

Updated release notes for Cisco UCS

Software Release 2.2(3d).

EO

September 11, 2015

Updated release notes for Cisco UCS

Software Release 2.2(4b)

FO

March 7, 2016

Updated release notes for Cisco UCS

Software Release 2.2(6g)

G0

July 13, 2016

Updated release notes for Cisco UCS Software Release 2.2(8a)

H0

February 10, 2017

Added CSCvc82843, CSCvb77959, and CSCvb59635 to Open Caveats section.

I0

June 14, 2017

Added CSCvc82843 to 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/c/en/us/support/servers-unified-computing/unified-computing-system/products-technical-reference-list.html

New Software Features in Release 2.2

Release 2.2(8a) adds support for the following:

- All VIC cards are now supported in Red Hat Enterprise Linux 6.8

Release 2.2(7b) adds support for the following:

- RDMA over Converged Ethernet (RoCE) support for Microsoft SMB Direct

Expanded support for Cisco VIC 1385 and 1387 along with Cisco VIC 1340 and 1380.

- NVGRE Task Offload implementation

Cisco UCS Manager now expands support for stateless offloads with NVGRE with Cisco UCS VIC 1385 and 1387 adapters.

Release 2.2(4b) adds support for the following:

- Support NVGRE with IPv6 and VMQ

- Support usNIC with Intel ®MPI

- RoCE support for Microsoft SMB Direct (Supported only on Cisco VIC 1340 and 1380)

- Consistent Device Naming (CDN) support (CDN is supported only on Windows 2012R2.)

Release 2.2(3a) adds support for the following:

- ENIC - DPDK Integration

- Overlay Network Offload for Cisco UCS VIC 1340 and Cisco UCS VIC 1380 cards:

– VXLAN Task Offload implementation

Cisco UCS Manager supports stateless offloads with VXLAN only with Cisco UCS VIC 1340 and Cisco UCS VIC 1380 adapters that are installed on servers running VMWare ESXi Release 5.5 and later releases of the operating system. Stateless offloads with VXLAN cannot be used with NetFlow, usNIC, VM-FEX, or VMQ.

– NVGRE Task Offload implementation

Cisco UCS Manager supports stateless offloads with NVGRE only with Cisco UCS VIC 1340 and/or Cisco UCS VIC 1380 adapters that are installed on servers running Windows Server 2012 R2 and later operating systems. Stateless offloads with NVGRE cannot be used with NetFlow, usNIC, VM-FEX, or VMQ.

Note For documentation, see the Cisco UCS Manager Configuration Guides.

Release 2.2(2c) adds support for the following:

- Accelerated Receive Flow Steering (ARFS) support for Linux. ARFS is supported on the following Operating Systems:

– Red Hat Enterprise Linux 6.5, and 6.6

– Red Hat Enterprise Linux 7.0 and higher versions

– SUSE Linux Enterprise Server 11 SP2 and SP3

– SUSE Linux Enterprise Server 12 and higher versions

– Ubuntu 14.04.2

- Adaptive Interrupt Coalescing (AIC) support for Linux. AIC is supported on the following Operating Systems:

– Red Hat Enterprise Linux 6.4 and higher versions

– Red Hat Enterprise Linux 7.0 and higher versions

– SUSE Linux Enterprise Server 11 SP2 and SP3

– SUSE Linux Enterprise Server 12

– XenServer 6.5

– Ubuntu 14.04.2

- 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.

Release 2.2(1a) adds support for the following:

- VMQ Support for Windows 2012 and Windows 2012 R2

- SCVMM-VMFEX Support for Windows 2012 HyperV

- LACP Support for Windows 2008 R2 SP1 (Cisco VIC TEAM Driver), Windows 2012 and Windows 2012 R2 (LBFOADMIN) for standalone rack servers

- FC Control Path Tracing for Linux and ESX fNIC drivers

Operating System Support

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:

http://www.cisco.com/c/en/us/support/servers-unified-computing/unified-computing-system/products-technical-reference-list.html

Resolved Caveats

Table 2 lists the caveats that have been resolved since Release 2.2.

Table 2 Resolved Caveats

Bug ID

OS

Where defect was found

Description

Fixed Version

VIC Firmware Fixes

CSCuw02439

—

—

Cisco VIC crashed with an fcpu core (core named as MEZZxxxx_palo_dfw) has been resolved.

2.2(3k), 2.2(6i)

CSCux59298

—

—

The error “Assert failed - Exception 11” for the 1240 VIC card has been resolved.

2.2(6i), 2.2(3k)

CSCuy62783

—

—

When a server encountered manageability loss during a TCP bulk transfer workload for 13XX VIC cards has been resolved.

2.2(7c), 2.2(6i), 2.2(3k)

CSCuw02439

—

—

The defect when the Cisco VIC crashed with a fcpu core has been resolved.

2.2(6i), 2.2(3k)

CSCuv20324

—

—

The defect when a VIC lost the PFC PGS state during a switch from CE to NIV after DCBX config timeout has been fixed.

2.2(6g), 2.2(3k)

CSCus64439

—

—

The defect when a "PFC feature operational" error appears which caused storage latency and aborts has been fixed.

2.2(6c), 2.2(5b), 2.2(3h)

CSCuv72975

—

—

The defect when a backplane port of IOM goes down has been fixed.

2.2(7b), 2.2(6c), 2.2(3j)

CSCus96016

—

—

The defect with the following error: iSCSI initiator_state: ISCSI_INITIATOR_FAILED

has been fixed.

2.2(5a), 2.2(4b), 2.2(3f)

CSCuh78503

—

—

The defect when an iSCSI reboot loop failed with the oprom Initialize error 1 has been fixed.

2.0(4c)

CSCuq17289

—

—

The defect when VNIC transmission errors appeared with different input cos values has been fixed.

2.2(4b), 2.2(3c)

CSCun25692

—

—

The defect when no SAN boots after upgrade from 2.1(3a) to 2.2(1b) has been fixed.

2.2(3a), 2.2(2d), 2.2(1e)

CSCum43435

—

—

The defect when a VIC option ROM intermittently hangs during PXE boot has been fixed.

2.2(3a)T,2.2(3a), 2.2(2c), 2.2(1c)

ESXi Resolved Caveats

CSCut64613

ESXi 5.1

—

When running ESXi 5.1 with fNIC driver version 1.6.0.12b, 1.5.0.49 or 1.6.0.16 is no longer terminating with stacktraces.

fnic 1.6.0.17

CSCux68195

ESXi

ENIC 2.3.0.7

The ESXi operating system kernel is no longer crashing during firmware upgrades or HIF port flap while running VM-FEX.

enic 2.3.0.7

CSCux75488

ESXi

FNIC 1.6.0.12b

The data corruption issue seen with controller resets, controller panic, and target port blocks is resolved on ESXi hosts running 3GFI and 2GFI setups with NetApp.

fnic 1.6.0.16

RHEL Resolved Caveats

CSCuw30291

RHEL

FNIC 1.6.0.12b

Connection to a storage target is no longer lost when a FC link is removed from the SAN port-channel.

fnic 1.6.0.23

CSCur05484

RHEL 6.4

FNIC 1.5.0.45

The fNIC drivers are no longer crashing with a null pointer value.

fnic 1.6.0.16

CSCuu29425

RHEL

7.0 / 7.1

ENIC 2.3.0.20

Packets that should be untagged coming across RHEL 7 as being tagged with VLAN ID 0 is resolved.

enic 2.3.0.20

2.2(7b)B

CSCuf73395

RHEL

FNIC 1.5.0.41

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.

fnic 1.5.0.41

CSCur34669

RHEL

FNIC 1.6.0.18

The fNIC driver name and meta data must be different across RHEL versions.

fnic 1.6.0.17

CSCuj67510

RHEL

FNIC 1.6.0.6

The fNIC driver no longer fails to update in Linux.

fnic 1.6.0.6

CSCuw74425

RHEL

FNIC 1.6.0.17

The fNIC drivers are no longer crashing when the multi-queue block IO queueing mechanism (blk-mq) is enabled in the Unbreakable Enterprise Kernel Release 4 (UEK4).

fnic 1.6.0.17

CSCus25300

RHEL

FNIC 1.6.0.18

The XEN server panic issue when installing the XEN6.5 RC2 through SAN boot is resolved.

fnic 1.6.0.18

Windows Resolved Caveats

CSCva02566

Windows

FNIC 2.4.0.19

Windows FNIC crashed on HBA API SCSI inquiry.

fnic 2.4.0.19

CSCui27355

Windows

Windows Driver 2.4.0.15

Windows iSCSI crash dump driver installation no longer fails on a non-English locale.

2.2(1a)A

CSCui63048

Windows

WinDDK2.1.0.9

A VIC management driver no longer causes a Windows OS 2008 R2 install failure.

2.1(0.9)

CSCuj92809

Windows

FNIC 2.1.0.20

HDS: HDLM-7.5 WS2008R2SP1 host reboot takes 17 minutes with multiple paths.

2.1(0.27)

Open Caveats

Table 3 Lists the open caveats in release 2.2.

Defect ID

OS

Driver

Symptom

Workaround

First Bundle Affected

CSCvc71862

RHEL 7.3

ENIC 2.3.0.30

With RHEL 7.3 ISCSI boot and ISCSI initiator configured for static IP address, the second path does not come up after a reboot if the asynchronous ENIC driver is supplied during the RHEL 7.3 ISCSI installation.

Use the RHEL 7.3 Inbox Driver during an OS installation. Both ISCSI paths will come up after reboot. Install the latest enic driver and reboot the server. Use the command multipath -ll to display both paths.

2.2(8g)

CSCvb15143

ESXi 6.0 U2

VMFEX Driver: v171-6.0-1.2.10.1

Jumbo frames is not supported on ESXi 6.0 U2 with VMFEX and driver version v171-6.0-1.2.10.1. Impacted B-series UCS Releases include 2.2(7), 2.2(8), 3.1(1), and 3.1(2).

There is no available workaround.

2.2(7c)

CSCvc82843

Windows 2012 R2

Windows 2012 ENIC: 3.5.0.13

Cisco VMFEX "Register filter driver OK" message may be seen upon booting up in the Windows Event Log.

There is no available workaround. This issue does not cause any disruption in functionality or performance.

2.2(7c)B

CSCvb77959, CSCvb59635

Windows 2012 R2, Windows 2016

Windows 2012 R2 ENIC: 3.5.0.13

Windows 2016 ENIC: 4.0.02

Error with event ID 5005 from the ENIC in the event logs may occur on Windows 2012 R2 and Windows 2016.

There is no available workaround. It has been determined that this issue does not cause any disruption in functionality or performance. This issue will not be fixed for the current drivers.

A fix for this issue will be made available with the new re-architected driver in a future release.

—

FNIC Driver: 1.6.0.25

ENIC Driver: 2.3.0.7

The ESX host reboot hangs while loading the ENIC module with NetFlow enabled.

If this issue occurs, do the following:

1. Disable Netflow

2. Reboot the system

3. Enable NetFlow

2.2(8a)B, 2.2(8a)C

CSCuz79138

—

FNIC Driver: 1.6.0.25

ENIC Driver: 2.3.0.7

The host becomes unresponsive when using second generation VIC adapters while running FCOE traffic and Ethernet traffic on the same side of the fabric with NetFlow enabled.

No known workaround for second generation VIC adapters. You can enable NetFlow with third generation VIC adapters or later generation adapters.

2.2(8a)B, 2.2(8a)C

CSCuy65407

—

VIC FW 4.1(1d)

ENIC Driver: 3.5.0.13

The VIC adapter may go into an inaccessible state while flapping RNICs that run high block size read/write workloads.

When this issue occurs, power cycle the server to reboot the VIC.

2.2(7b), 2.2(8a)B, 2.2(8a)C

CSCuw57834

ESXi 5.1 U3

FNIC Driver: 1.6.0.16

The system could crash when using ESXi 5.1 U3 host with FNIC 1.6.0.16.

There is no available workaround.

2.2(3f)A

Behavior Changes and Known Limitations

The Cisco UCS Manager release 2.2(2c) supports ARFS with the following features:

- Supports only on UCS-VIC-M82-8P and UCSB-MLOM-40G-01.

- Supports only 64 flow classifier entries per vNIC.

- Supports approximately 992 flow classifier entries per adaptor (approximately 15 vNICs with ARFS enabled).

The Cisco UCS Manager release 2.2(2c) supports AIC in Linux ENIC driver with the following features:

- Provides faster performance up to 80% link utilization.

- When enabled, this feature disables static coalescing.

The following limitations were introduced with support of NetQueue in Cisco UCS Manager release 2.2(2c):

- VMware recommends no more than 8 NetQueues per port for standard or jumbo (9000) frame configurations.

– When enabling NetQueue on vNICs, Cisco recommends using the default VMware adapter policy.

– Enabling too many NetQueues on too many vNICs can result in the host exceeding limits for netPKtheap and msix interrupts.

- NetQueue should be enabled only for vNICs configured to use MSI-X interrupts.

- VMware recommends disabling NetQueue for 1G NICs.

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://software.cisco.com/download/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, using the Cisco Bug Search Tool (BST), submitting a service request, and gathering additional information, see What’s New in Cisco Product Documentation.

To receive new and revised Cisco technical content directly to your desktop, you can subscribe to the What’s New in Cisco Product Documentation RSS feed. 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.

© 2011–2016 Cisco Systems, Inc. All rights reserved.