Cisco UCS C-Series Servers

Cisco UCS C-Series Servers deliver unified computing in an industry-standard form factor to reduce total cost of ownership and increase agility. Each product addresses varying workload challenges through a balance of processing, memory, I/O, and internal storage resources.

About the Release Notes

This document describes the new features, system requirements, open caveats and known behaviors for C-Series software release 4.0(4) including Cisco Integrated Management Controller software and any related BIOS, firmware, or drivers. Use this document in conjunction with the documents listed in the Related Documentation section.


Note

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


Revision History

Revision

Date

Description

F0

September 27, 2019

Following changes were made:

  • Updated the Supported Features section.

  • Updated the Resolved Caveats section.

  • Updated the HUU version to 4.0(4h).

The firmware files in Cisco Host Upgrade Utility for individual releases are available at: Cisco UCS C-Series Integrated Management Controller Firmware Files, Release 4.0

E0

August 26, 2019

Following changes were made:

  • Updated the Resolved Caveats section.

  • Updated the Open Caveats section.

  • Updated the HUU version to 4.0(4f).

The firmware files in Cisco Host Upgrade Utility for individual releases are available at: Cisco UCS C-Series Integrated Management Controller Firmware Files, Release 4.0

D0

August 01, 2019

Following changes were made:

  • Updated the Supported Features section.

  • Updated the Open Caveats section.

  • Updated the Resolved Caveats section.

  • Updated the Known Behaviors section.

  • Updated the HUU version to 4.0(4e).

The firmware files in Cisco Host Upgrade Utility for individual releases are available at: Cisco UCS C-Series Integrated Management Controller Firmware Files, Release 4.0

C0

July 15, 2019

Following changes were made:

  • In this release, software images of the M5 servers are updated to enable the server manufacturing team.

  • Updated the HUU version to 4.0(4d).

The firmware files in Cisco Host Upgrade Utility for individual releases are available at: Cisco UCS C-Series Integrated Management Controller Firmware Files, Release 4.0

B0

May 17, 2019

Following changes were made:

  • Updated the Supported Features section.

  • Updated the Open Caveats section.

  • Added the Security Fixes section.

  • Updated the HUU version to 4.0(4c).

The firmware files in Cisco Host Upgrade Utility for individual releases are available at: Cisco UCS C-Series Integrated Management Controller Firmware Files, Release 4.0

A0

April 26, 2019

Created release notes for 4.0(4b).

System Requirements

The management client must meet or exceed the following minimum system requirements:

  • Sun JRE 1.8.0_92 or later

  • HTML based interfaces are supported on:

    • Microsoft Internet Explorer 10.0 or 11

    • Mozilla Firefox 47.0 or higher

    • Google Chrome 38 or higher

    • Safari 7 or higher


    Note

    If the management client is launched using an unsupported browser, check the help information from the For best results use supported browsers option available in the login window for the supported browser versions.


  • Microsoft Windows 7, Microsoft Windows XP, Microsoft Windows Vista, Microsoft Windows 10, Apple Mac OS X v10.6, Red Hat Enterprise Linux 5.0 or higher operating systems

  • Transport Layer Security (TLS) version 1.2.

Overview of the Server Models

Supported Platforms

The following servers are supported in this release:

  • UCS C220 M5

  • UCS C240 M5

  • UCS C480 M5

  • UCS C480 ML M5

  • UCS S3260 M5

For information about these servers, see Overview of Servers

Hardware and Software Interoperability

For detailed information about storage switch, operating system, adapter, adapter utility, and storage array interoperability, see the Hardware and Software Interoperability Matrix for your release located at:

http://www.cisco.com/en/US/products/ps10477/prod_technical_reference_list.html

For details about transceivers and cables that are supported on VIC cards, see the Transceiver Modules Compatibility Matrix

You can also see the VIC data sheets for more compatibility information: Cisco UCS Virtual Interface Card Data Sheets

Cisco UCS C-Series and Cisco UCS Manager Release Compatibility Matrix for C-Series Rack-Mount Servers

Cisco UCS C-Series Rack-Mount Servers are managed by built-in standalone software — Cisco Integrated Management Controller (Cisco IMC). However, when a C-Series Rack-Mount Server is integrated with Cisco UCS Manager, the Cisco IMC does not manage the server anymore.

The following table lists the C-Series software standalone and Cisco UCS Manager releases for C-Series Rack-Mount Servers:

Table 1. Cisco C-Series and UCS Manager Software Releases for C-Series Servers

C-Series Standalone Release

Cisco UCS Manager Release

C-Series Servers

4.0(4h)

4.0(4e)

C220 M5, C240 M5, C480 M5 and S3260 M5.

4.0(4f)

4.0(4d)

C220 M5, C240 M5, C480 M5, S3260 M5 and C480 ML M5 servers.

4.0(4e)

4.0(4c)

C220 M5, C240 M5, C480 M5, S3260 M5 and C480 ML M5 servers.

4.0(4d)

No Support

C220 M5, C240 M5, C480 M5 and S3260 M5.

4.0(4b)

4.0(4a)

C220 M5, C240 M5, C480 M5, S3260 M5 and C480 ML M5 servers.

4.0(2h)

No Support

All M4, M5 servers, C125 M5 and C480 ML M5 servers.

4.0(2g)

4.0(2e)

All M4, M5 servers, C125 M5 and C480 ML M5 servers.

4.0(2f)

4.0(2d)

All M4, M5 servers, C125 M5 and C480 ML M5 servers.

4.0(2d)

4.0(2b)

C220 M5, C240 M5, C125 M5, S3260 M5 and C480 ML M5 servers.

4.0(2c)

4.0(2a)

All M4, M5 servers, C125 M5 and C480 ML M5 servers.

4.0(1d)

4.0(1d)

All M4, M5 servers and C125 M5

4.0(1c)

4.0(1c)

All M4, M5 servers and C125 M5

4.0(1b)

4.0(1b)

All M4, M5 servers and C125 M5

4.0(1a)

4.0(1a)

All M4, M5 servers and C125 M5

3.1(3f)

3.2(3f)

C480 M5, C220 M5, C240 M5, S3260 M5

3.1(3d)

3.2(3e)

C480 M5, C220 M5, C240 M5, S3260 M5

3.1(3c)

3.2(3d)

C480 M5, C220 M5, C240 M5, S3260 M5

3.1(3b)

3.2(3b)

C480 M5, C220 M5, C240 M5

3.1(3a)

3.2(3a)

C480 M5, C220 M5, C240 M5, S3260 M5

3.1(2d)

3.2(2d)

C480 M5, C220 M5, C240 M5

3.1(2c)

3.2(2c)

C480 M5, C220 M5, C240 M5

3.1(2b)

3.2(2b)

C480 M5, C220 M5, C240 M5

3.1(1d)

3.2(1d)

C220 M5, C240 M5

Upgrade Paths to Release 4.0

The section provides information on the upgrade paths to release 4.0(x). Refer to the table for upgrade paths for various Cisco UCS C-series IMC versions.

Table 2. Upgrade Paths to Release 4.0(x)

Upgrade From Release

Upgrade To Release

Recommended Upgrade Path

All M5 Servers from 3.1(x)

4.0(x)

Follow below upgrade path:

  • You can use Interactive HUU or Non-Interactive HUU (NIHHU) script to update the server.

  • While updating the firmware using the Non-Interactive HUU (NIHUU) tool, use the Python scripts that are released with version 4.0(1a).

  • Use OpenSSL 1.0.1e-fips on the client side (where the NIHUU python scripts are running).

  • Download HUU iso from here.

  • Download NIHUU script from here.

For all M4 servers for releases greater than 2.0(4c)

For all M4 servers from 3.0(x)

4.0(x)

Follow below upgrade path:

  • You can use Interactive HUU or Non-Interactive HUU (NIHHU) script to update the server.

  • While updating the firmware using the Non-Interactive HUU (NIHUU) tool, use the Python scripts that are released with version 4.0(1a).

  • Use OpenSSL 1.0.1e-fips on the client side (where the NIHUU python scripts are running).

  • If you wish to secure Cimc Boot, set flag use_cimc_secure as yes in multiserver_config file present with python script.

  • Download HUU iso from here.

  • Download NIHUU script from here.

For all M4 servers for release lesser than 2.0(4c)

4.0(x)

Follow these steps to upgrade from releases less than 2.0(4c) to 4.0(x):

Upgrade from version less than 2.0(4c) to 2.0(4c)

  • You can use Interactive HUU or Non-Interactive HUU (NIHHU) script to update the server.

  • While updating the firmware using the Non-Interactive HUU (NIHUU) tool, use the Python scripts that are released with version 3.0(3a).

  • Use OpenSSL 1.0.0-fips on the client side (where the NIHUU python scripts are running).

  • Download HUU iso from here.

  • Download NIHUU script from here.

Upgrade from 2.0(4c) to 4.0(x)

  • You can use Interactive HUU or Non-Interactive HUU (NIHHU) script to update the server.

  • While updating the firmware using the Non-Interactive HUU (NIHUU) tool, use the Python scripts that are released with version 4.0(1a).

  • Use OpenSSL 1.0.1e-fips on the client side (where the NIHUU python scripts are running).

  • If you wish to secure Cimc Boot, set flag use_cimc_secure as yes in multiserver_config file present with python script.

  • Download HUU iso from here.

  • Download NIHUU script from here.

Firmware Upgrade Details

Firmware Files

The C-Series software release 4.0(4) includes the following software files:

CCO Software Type File name(s) Comment
Unified Computing System (UCS) Server Firmware

ucs-c240m5-huu-4.0.4.iso

ucs-c220m5-huu-4.0.4.iso

ucs-c480m5-huu-4.0.4.iso

ucs-s3260-huu-4.0.4.iso

For release specific ISO versions, see Cisco UCS C-Series Integrated Management Controller Firmware Files, Release 4.0

Host Upgrade Utility
Unified Computing System (UCS) Drivers ucs-cxxx-drivers.4.0.4.iso Drivers
Unified Computing System (UCS) Utilities

ucs-cxxx-utils-efi.4.0.4.iso

ucs-cxxx-utils-linux.4.0.4.iso

ucs-cxxx-utils-vmware.4.0.4.iso

ucs-cxxx-utils-windows.4.0.4.iso

Utilities

Note

Always upgrade the BIOS, the Cisco IMC and CMC from the HUU ISO. Do not upgrade individual components (only BIOS or only Cisco IMC), since this could lead to unexpected behavior. If you choose to upgrade BIOS, and the Cisco IMC individually and not from the HUU ISO, make sure to upgrade both Cisco IMC, and BIOS to the same container release. If the BIOS and the Cisco IMC versions are from different container releases, it could result in unexpected behavior. Cisco recommends that you use the Update All option from the Host Upgrade Utility to update the firmware versions of Cisco IMC, BIOS, and all other server components (VIC, RAID Controllers, PCI devices, and LOM) together.


Host Upgrade Utility

The Cisco Host Upgrade Utility (HUU) is a tool that upgrades the Cisco UCS C-Series firmware.

The image file for the firmware is embedded in the ISO. The utility displays a menu that allows you to choose which firmware components to upgrade. For more information on this utility see:

http://www.cisco.com/en/US/products/ps10493/products_user_guide_list.html

For details of firmware files in Cisco Host Upgrade Utility for individual releases, see Cisco UCS C-Series Integrated Management Controller Firmware Files, Release 4.0

Updating the Firmware

Use the Host Upgrade Utility to upgrade the C-Series firmware. Host Upgrade Utility can upgrade the following software components:

  • BIOS

  • Cisco IMC

  • CMC

  • Cisco VIC Adapters

  • LSI Adapters

  • LAN on Motherboard

  • PCIe adapter firmware

  • HDD firmware

  • SAS Expander firmware

For detailed information about the components available in a server for each release, see: Cisco UCS C-Series Integrated Management Controller Firmware Files

All firmware should be upgraded together to ensure proper operation of your server.


Note

We recommend that you use the Update All option from the Host Upgrade Utility to update the firmware versions of Cisco IMC, BIOS and all other server components (VIC, RAID Controllers, PCI devices, and LOM) together. Click Exit once you deploy the firmware.


For more information on how to upgrade the firmware using the utility, see:

Cisco Host Upgrade Utility User Guide

Supported Features

Supported Features

Release 4.0(4h)

The following new software feature is supported in Release 4.0(4h):

Fault ID is included in the Cisco IMC logs.

On the S3260 servers with Cisco UCS VIC 14xx series cards, added Physical NIC Mode to the Network Adapter Configuration on an experimental basis. When this option is enabled, up-link ports of the VIC are set to pass-through mode. This allows the host to transmit packets without any modifications. VIC ASIC does not rewrite the VLAN tag of the packets based on the VLAN and CoS settings for the vNIC. This option is disabled by default.


Note

This option cannot be enabled on an adapter that has:

  • Port Channel mode enabled

  • VNTAG mode enabled

  • Multiple user created vNICs


Release 4.0(4e)

The following new software features are supported in Release 4.0(4e):

  • Added support to enable Device Connector on the S3260 servers which allows access to Cisco Intersight.

  • Added the ADDDC Sparing option to the Select Memory RAS Configuration BIOS token for all M5 servers except C125 M5. This is now the new default value of this token.

    ADDDC RAS Changes - Adaptive Double Device Data Correction (ADDDC) is a memory RAS feature that enables dynamic mapping of failing DRAM by monitoring corrected errors and taking action before uncorrected errors can occur and cause an outage. It is now enabled by default.

    Once ADDDC sparing remaps a memory region the system could incur marginal memory latency and bandwidth penalties on memory bandwidth intense workloads that target the impacted region. Cisco recommends scheduling proactive maintenance to replace a failed DIMM once an ADDDC RAS fault is reported.

  • Intel ® VMD Enhancements to NVME

    Support for Volume Management Devices (VMD) in NVMe. Optional VMD drivers are available on the Cisco download site. VMD is supported on the following Operating Systems:

    • RHEL 7.3, 7.4, 7.5, 7.6

    • CENTOS 7.3, 7.4, 7.5, 7.6

    • SLES-15, SLES-15 v4

    • Windows 2016, Windows 2019

    • ESXi 6.5U2, 6.7U1, 6.7U2

    • Ubuntu 18.04.1

    Enhanced features provided by VMD provide support for hot-plugging of PCIe Solid State Drives (SSD), as well as the ability to use a command line interface to configure blinking patterns to indicate drive status.

  • Added the Disable User on Lockout feature: When you choose this option it disables the user account on lockout.

Release 4.0(4c)

The following new software feature is supported in Release 4.0(4c):

Account Lockout—Added support to configure the maximum number of failed login attempts (due to incorrect password) for local users. You can also set the time period for which the user will be locked out.

Release 4.0(4b)

The following new software features are supported in Release 4.0(4b):

Intel ® Optane Data Center Persistent Memory Modules

Cisco UCS C-Series Release 4.0(4) introduces support for the Intel® Optane Data Center persistent memory modules on the UCS M5 servers that are based on the Second Generation Intel® Xeon® Scalable processors. Intel® Optane DC persistent memory modules can be used only with the Second Generation Intel® Xeon® Scalable processors.

This release provides the ability to configure and manage Intel® Optane DC persistent memory modules through Cisco IMC and the host Operating System tools. Persistent memory modules are non-volatile memory modules that bring together the low latency of memory and the persistence of storage. Data stored in persistent memory modules can be accessed quickly compared to other storage devices, and is retained across power cycles.

Cisco Boot Optimized M.2 RAID Controller Support—Cisco C-Series Release 4.0(4) introduces support for Cisco Boot Optimized M.2 RAID Controller (UCS-M2-HWRAID). Cisco IMC interfaces allow you to view controller and physical drive details, and perform related configuration tasks.

PCIe Switch Updates—Added option to recover a PCIe Switch. Yo can use this feature to re-flash the firmware on the PCIe switches.

BIOS Token Updates—On servers with NVMe controllers, added the Intel ® Speed Select BIOS token.

Redfish—Redfish schema was updated.

Unified Driver Support —Added unified driver support for Fibre Channel and NVMe over Fibre Channel on SLES 12 SP4, SLES 15, and RHEL 7.6. This is in addition to being previously supported on SLES 12 SP3.

Support for Signed Drivers —Added support for signed drivers in all supported Linux platforms. All Cisco Linux drivers are now cryptographically signed, which means that they can be used with UEFI Secure Boot on all supported Linux platforms. UEFI Secure Boot ensures that only trusted firmware and drivers are allowed to run at system boot, decreasing vulnerability to malware at boot time.

New Hardware in Release 4.0(4)

New Hardware in Release 4.0(4e)

Intel ® NVMe P4510/4511 and P4610 Drive Support

Firmware support for the following NVMe drives was introduced in Release 4.0(4e):

NMVe Drive

PID

Intel ® P4510 1TB (SSDPE2KX010T8K)

UCSC-NVME2H-I1000

Intel ® P4510 2TB (SSDPE2KX020T8K)

UCSC-NVME2H-I2TBV

Intel ® P4510 4TB (SSDPE2KX040T8K)

UCSC-NVME2H-I4000

Intel ® P4510 8TB (SSDPE2KX080T8K)

UCSC-NVMEHW-I8000

Intel ® P4610 1.6TB (SSDPE2KE016T8K)

UCSC-NVME2H-I1600

Intel ® P4610 3.2TB (SSDPE2KE032T8K)

UCSC-NVME2H-I3200

Second Generation Intel® Xeon® Scalable Processors

Cisco UCS C-Series Release 4.0(4b) introduces support for Second Generation Intel® Xeon® Scalable processors on the following servers:

  • Cisco UCS C220 M5 Server

  • Cisco UCS C240 M5 Server

  • Cisco UCS C480 M5 Server

  • Cisco UCS S3260 M5 Server

Intel® Optane Data Center Persistent Memory Modules

Intel® Optane Data Center persistent memory modules can be used only with the Second Generation Intel® Xeon® Scalable processors.

Cisco UCS C-Series Release 4.0(4b) introduces support for the Intel® Optane DC persistent memory modules on the following servers that are based on the Second Generation Intel® Xeon® Scalable processors:

  • Cisco UCS C220 M5 Server

  • Cisco UCS C240 M5 Server

  • Cisco UCS C480 M5 Server

  • Cisco UCS S3260 M5 Server

Intel® Optane DC persistent memory modules support 128GB, 256GB and 512GB of persistent memory. This can be configured through Cisco IMC or the host Operating System tools.

Cisco Boot Optimized M.2 RAID Controller

Cisco UCS C-Series Release 4.0(4b) introduces support for Cisco Boot Optimized M.2 RAID Controller (UCS-M2-HWRAID) on the following servers:

  • Cisco UCS C220 M5 Server

  • Cisco UCS C240 M5 Server

  • Cisco UCS C480 M5 Server

Peripherals

Support for NVIDIA T4 16GB GPU cards (UCSC-GPU-T4-16) on the following servers:

  • UCS C240 M5

  • UCS C220 M5

  • UCS C480 M5

Support for Support for the QLogic QL45611HLCU single port 100GbE PCIe NIC (UCSC-PCIE-QS100GF) on all UCS M5 servers supported in this release.

Software Utilities

The following standard utilities are available:

  • Host Update Utility (HUU)

  • BIOS and Cisco IMC Firmware Update utilities

  • Server Configuration Utility (SCU)

  • Server Diagnostic Utility (SDU)

The utilities features are as follows:

  • Availability of HUU, SCU on the USB as bootable images. The USB also contains driver ISO, and can be accessed from the host operating system.

Security Fixes

Security Fixes in Release 4.0(4c)

The following Security Fixes were added in Release 4.0(4c):

Release

Defect ID

CVE

Symptom

4.0(4c)

CSCvp34806

  • CVE-2018-12126

  • CVE-2018-12127

  • CVE-2018-12130

  • CVE-2019-11091

Cisco UCS M5 servers are based on Intel® Xeon® Scalable processors that are vulnerable to variants of exploits that use Microarchitectural Data Sampling (MDS) to gain access to data being processed in the CPU by other applications.

  • CVE-2018-12126 (Microarchitectural Store Buffer Data Sampling) affects store buffers in the CPU, and is addressed by applying the updated microcode included in the UCS Cisco IMC release as well as the relevant Operating System and Hypervisor patches from the appropriate vendors.

  • CVE-2018-12127 (Microarchitectural Load Port Data Sampling) affects load buffers in the CPU, and is addressed by applying the updated microcode included in the UCS Cisco IMC release as well as the relevant Operating System and Hypervisor patches from the appropriate vendors.

  • CVE-2018-12130 (Microarchitectural Fill Buffer Data Sampling) affects line fill buffers in the CPU, and is addressed by applying the updated microcode included in the UCS Cisco IMC release as well as the relevant Operating System and Hypervisor patches from the appropriate vendors.

  • CVE-2019-11091 (Microarchitectural Uncacheable Data Sampling) affects the uncacheable memory buffers in the CPU, and is addressed by applying the updated microcode included in the UCS Cisco IMC release as well as the relevant Operating System and Hypervisor patches from the appropriate vendors.

This release includes BIOS revisions for Cisco UCS M5 generation servers. These BIOS revisions include the updated microcode that is a required part of the mitigation for these vulnerabilities.

Resolved Caveats

The following section lists resolved caveats.

Resolved Caveats in Release 4.0(4)

Release 4.0(4h)

The following caveat was resolved in Release 4.0(4h):

Table 3. Cisco VIC

Defect ID

Symptom

First Affected Release

Resolved in Release

CSCvr04369

Under rare and specific conditions, the link status of the Ethernet port of a Cisco UCS 14xx adapter card, and of the attached switch port, failed to come up multiple times. This was due to due to poor quality of the analog electrical signal received by Ethernet SERDES component of the VIC adapter, in the configurations which do not use the Ethernet Link-Training protocol. This issue occurred when the following conditions were present:

  • Cisco VIC 14xx adapter card instance and port instance:

    • Cisco UCS VIC 1455

    • Cisco UCS VIC 1457

    • Cisco UCS VIC 1495

    • Cisco UCS VIC 1497

  • Transceiver module instances that do not use the Ethernet Auto-Negotiation protocol:

    • 10G CU

    • 10G Optical

    • 25G CU

    • 25G Optical

    • 40G Optical

    • 100G Optical

  • Other possible environmental conditions.

4.0(4e)

4.0(4h)

Release 4.0(4f)

The following caveats were resolved in Release 4.0(4f):

Table 4. Server

Defect ID

Symptom

First Affected Release

Resolved in Release

CSCvq95077

S3260 M5 servers keep rebooting and fail to power on and do not complete BIOS POST.

4.0(4e)

4.0(4f)

Table 5. BMC

Defect ID

Symptom

First Affected Release

Resolved in Release

CSCvq26149

M5 server fans run at MAX speed after PECI temperature read failure. The fan speed continues to remain at MAX speed until you perform a power cycle of the server.

4.0(4c)

4.0(4f)

CSCvq93258

The Product IDs (PID) of the new Intel® Optane Data Center Persistent Memory Modules parts are displayed as UNKNOWN in version 4.0(4d).

Upgrading the PID catalog to 4.0(4e) displays the correct PID numbers.

4.0(4d)

4.0(4f)

CSCvq86332

PIDs of SED drives present in the system are displayed as non-SED drives.

4.0(4e)

4.0(4f)

Table 6. Host Firmware Upgrade

Defect ID

Symptom

First Affected Release

Resolved in Release

CSCvq58364

Non-Interactive HUU (NIHUU) drive updates fail with a timeout error. This happens while upgrading the HDD firmware of one or more drives using the NIHUU.

4.0(4d)

4.0(4f)

Table 7. External Controllers

Defect ID

Symptom

First Affected Release

Resolved in Release

CSCvq81930

Firmware update of the following Intel drives fail while upgrading from 4.0(2c) to 4.0(4b) or 4.0(4e):

  • SSDSC2KB038T7K : 3.8TB 2.5 inch Enterprise Value 6G SATA SSD

  • SSDSC2KB960G7K - 960GB 2.5-inch Enterprise Value 6G SATA SSD

  • SSDSC2KG019T7K - 1.9TB 2.5-inch Enterprise performance 6G SATA SSD

    SSDSC2KG480G7K - 480GB 2.5-inch Enterprise performance 6GSATA SSD

  • SSDSC2KG960G7K - 960GB 2.5-inch Enterprise performance 6G SATA SSD

4.0(4b)

4.0(4f)

Release 4.0(4e)

The following caveats were resolved in Release 4.0(4e):

Table 8. BIOS

Defect ID

Symptom

First Affected Release

Resolved in Release

CSCvp39108

On the Cisco UCS M5 servers with Intel X710 adapters in UEFI mode, unable to complete the UEFI boot process (unable to perform OS boot and PXE boot) when iSCSI is configured with Intel X710-DA4 Quad Port 10Gb SFP+ converged NIC.

4.0(4b)

4.0(4e)

Table 9. BMC

Defect ID

Symptom

First Affected Release

Resolved in Release

CSCvo55902

Network link activity LED does not display the correct LOM port and LED status.

4.0(4b)

4.0(4e)

Table 10. External Controllers

Defect ID

Symptom

First Affected Release

Resolved in Release

CSCvp43280

When two or more Intel PCI Adapters are populated in the UCS C-Series and S-Series M5 servers, upgrading the firmware using HUU may fail for the PCI cards.

4.0(2c)

4.0(4e)

CSCvo93353

The StorCLI command storcli /cX show all does not display the World Wide Number (WWN) of the drives. This happens when you use StorCLI version 7.0813 or earlier.

4.0(2f)

4.0(4e)

CSCvp08512

The MegaRAID controller firmware does not check Hot Spare physical drive size and allows you to create and assign a Dedicated Hot Spare of small size.

4.0(4b)

4.0(4e)

Table 11. Intel® Optane Data Center Persistent Memory Modules - Intel Resolved Caveats

Defect ID

Symptom

First Affected Release

Resolved in Release

CSCvo78920

When a system with Intel® Optane Data Center persistent memory modules installed boots, in some instances, a persistent memory module health state may enter a "Non-Functional" state. In some instances, the persistent memory module will recover ("Healthy" health state) after an AC power cycle. If a persistent memory module becomes "Non-Functional" and does not recover, it should be replaced.

Intel IPS case filed.

4.0(4b)

4.0(4e)

CSCvp38545

Intel® Optane Data Center persistent memory module goes into a "Non-Functional" health state when tested in a chamber with HiBit DIMMs. AC power cycle causes the failed persistent memory module to go into a "Fatal Failure" state.

Intel IPS case filed.

4.0(4b)

4.0(4e)

CSCvp38555

Intel® Optane Data Center persistent memory modules go into a "Non-Functional" health state when it is first powered up.

Intel IPS case filed.

4.0(4b)

4.0(4e)

Release 4.0(4b)

The following caveat was resolved in Release 4.0(4b):

Table 12. BMC

Defect ID

Symptom

First Affected Release

Resolved in Release

CSCvo97900

On the C480 M5 servers that do not have HDD or NVMe cage (front as well as auxiliary) with the OS boot is configured over FlexFlash and storage provisioning is over SAN, faulty entries display the following error: SAS_EEPROM_PRSNT: Add-in Card 9 missing: reseat or replace Add-in Card 9.

4.0(2c)

4.0(4b)

CSCvo18799

While updating the firmware using Cisco IMC, Power Sequencer (PWR_SEQ) update fails with the following message: Firmware update failed, AC Cycle system and retry. PWRSEQ

3.0(3e)

4.0(4b)

CSCvo15978

On servers with M393A4K40BB2-CTD DIMMs, IPMI may stop working. Errors related to temperature, CPU and/or DIMM mismatch in the management console, fan speed 100%, and chassis notifications are reported.

4.0(1a)

4.0(4b)

CSCvo02861

Syslog Minimum Severity to report severity is not functional.

3.1(3a)

4.0(4b)

CSCvo85413

Unable to launch KVM console using Cisco IMC on the S3260 servers running on firmware version 4.0(2c).

4.0(2c)

4.0(4b)

Table 13. BMC Storage

Defect ID

Symptom

First Affected Release

Resolved in Release

CSCvn29592

Following drives:

  • KPM51RUG480G

  • KPM51RUG960G

  • KPM51RUG1T92

  • KPM51RUG3T84

  • KPM51VUG400G

  • KPM51VUG800G

  • KPM51VUG1T60

  • KPM51VUG3T20

  • MZ6ER400HAGL/003

incorrectly display the Wear Status in Days and Percentage Life Left as zero in Cisco IMC.

4.0(2c)

4.0(4b)

Table 14. BIOS

Defect ID

Symptom

First Affected Release

Resolved in Release

CSCvn77825

On servers with Windows Hyper-V 2019 Guarded Host feature and TPM, running Shielded Virtual Machines in our environment results in Host Guardian Shielded VM attestation failure and returns incorrect UEFI variable data structure.

4.0(1c)

4.0(4b)

Table 15. CMC

Defect ID

Symptom

First Affected Release

Resolved in Release

CSCvo25387

On S3260 servers running on 4.0(1b) version, chassis may enter a SAFE state and have the fans spin at 100% RPM due to missing MEZZ temperature sensor readings.

4.0(1b)

4.0(4b)

Table 16. CMC Storage

Defect ID

Symptom

First Affected Release

Resolved in Release

CSCvo03830

SAS Expander link address is set to 0 on HGST drives after the expander is disconnected.

4.0(1a)

4.0(4b)

Table 17. External Controllers

Defect ID

Symptom

First Affected Release

Resolved in Release

CSCvn34219

UCSC-RAID-M5HD controller fails to boot as it encounters unrecoverable fault during boot. Cisco IMC web UI reports the following error: Storage Controller Inoperable. All boot and data volumes hosted by the UCSC-RAID-M5HD controller will not be available. This happens when online RAID level migration is in progress and system encounters a power cycle or shutdown.

4.0(2c)

4.0(4b)

CSCvm94424

After upgrading the S3260 servers to 4.0(1a), F1256 equipment-missing informational fault is logged for empty drive slots .

4.0(1a)

4.0(4b)

Resolved Caveats in Release 4.0(2)

Release 4.0(2i)

The following defects were resolved in release 4.0(2i):

Table 18. BIOS

Defect ID

Symptom

First Affected Release

Resolved in Release

CSCvo77732

After upgrading the UCS C460 M4 with Intel Xeon v2 CPUs to 4.0 firmware versions, the server crashes (PSOD), becomes unresponsive, or encounters a CATERR.

4.0(1c)

4.0(2i)

Table 19. Utilities

Defect ID

Symptom

First Affected Release

Resolved in Release

CSCvr07491

After upgrading the firmware of multiple S3260 servers using the Non-Interactive HUU, firmware activation fails for a few server components such as BMC, BIOS, CMC and SAS Expander.

4.0(1a)

4.0(2i)

Release 4.0(2h)

The following defect was resolved in release 4.0(2h):

Table 20. BIOS

Defect ID

Symptom

First Affected Release

Resolved in Release

CSCvo48006

On the M4 servers, uncorrectable ECC error detected during Patrol Scrub. When the CPU IMC (Integrated Memory Controller) Patrol Scrubber detects an uncorrectable ECC error, it logs a truncated DIMM address (4KB page boundary) to the Machine Check Banks.

4.0(2c)

4.0(2h)

Release 4.0(2g)

The following defects were resolved in release 4.0(2g):

Table 21. BMC

Defect ID

Symptom

First Affected Release

Resolved in Release

CSCvo15978

On servers with M393A4K40BB2-CTD DIMMs, IPMI may stop working. Errors related to temperature, CPU and/or DIMM mismatch in the management console, fan speed 100%, and chassis notifications are reported.

4.0(1a)

4.0(2g)

CSCvp41543

SSH clients fail to establish a connection to Cisco IMC. This happens when the SSH clients use diffie-hellman-group14-sha1 as default KEX algorithm as support for this KEX algorithm has been removed from Cisco IMC.

Update the SSH clients to the latest version that uses stricter KEX algorithms to establish SSH sessions.

3.0(4j)

4.0(2g)

Release 4.0(2f)

The following defects were resolved in release 4.0(2f):

Table 22. BMC

Defect ID

Symptom

First Affected Release

Resolved in Release

CSCvn81570

Modifying the LUN ID for Flex Flash SD card VD fails with the following error: error in configuring device

4.0(1c)

4.0(2f)

CSCvn80088

Unable to initiate non-interactive HUU update when the remote share password provided in the NI HUU contains any of the following special characters ; | ? $ ! @ # % ^ * - _ +

4.0(1a)

4.0(2f)

Release 4.0(2d)

The following defects were resolved in release 4.0(2d):

Table 23. Utilities

Defect ID

Symptom

First Affected Release

Resolved in Release

CSCvn92435

Host Update Utility not booting on the following platform: BE7M-M5-K9. HUU fails with the following error message: “Host Update Utility is unable to detect Cisco IMC firmware

4.0(2c)

4.0(2d)

Release 4.0(2c)

The following defects were resolved in release 4.0(2c):

Table 24. BMC

Defect ID

Symptom

First Affected Release

Resolved in Release

CSCvm12144

PSU input voltage lost assert issue seen though there is no physical power loss.

3.1(3b)

4.0(2c)

CSCvm27310

C-Series servers with NVIDIA P40 Card installed has fans running at 100% at all times. BMC sets the server to Max Power policy instead of High Power policy on the servers that have NVIDIA GPU P40 cards installed.

3.1(1d)

4.0(2c)

CSCvn04038

RAID cannot be set up between the two SD cards, resulting in the following error:

Controller State: Disconnected Partition From Host

3.1(1d)

4.0(2c)

Table 25. CMC Storage

Defect ID

Symptom

First Affected Release

Resolved in Release

CSCvj95793

The "show fault-entries" list does not display the faults reported from the subordinate CMC when logged in using the management IP. It only reports the primary CMC faults.

4.0(1a)

4.0(2c)

Table 26. External Controllers

Defect ID

Symptom

First Affected Release

Resolved in Release

CSCvj74706

On the M4 servers, physical drives managed by UCSC-SAS12GHBA displays the physical drive state as Unconfigured Good instead of JBOD.

3.(3a)

4.0(2c)

CSCvm83587

On the C220 and 240 M5 servers with 3.1(3a) firmware versions, file transfer on VMware host results in Rx packet drops and CRC errors with Qlogic 25G card (QL41212H) running on driver version 8.21.x.

3.1(3a)

4.0(2c)

Table 27. Utilities

Defect ID

Symptom

First Affected Release

Resolved in Release

CSCvi65660

Cisco VIC adapter firmware may not automatically activate when you upgrade the firmware of the server components using the HUU. This happens when single server dual SIOC is enabled.

4.0(1a)

4.0(2c)

Open Caveats

The following section lists open caveats.

Open Caveats in Release 4.0(4)

Release 4.0(4f)

The following defect is open in release 4.0(4f):

Table 28. External Controllers

Defect ID

Symptom

Workaround

First Affected Release

CSCvq50290

Cisco IMC fails to recognize SATA disk UCS-SD960G63X-EP. This happens when you upgrade to 4.0(4) version from 4.0(2c) or below versions.

If this issue occurs, do the following:

  1. Boot to 4.0.(2d) HUU

  2. Downgrade the storage controller version to 00.00.00.58.

  3. Reboot and discover the drive and upgrade to version SCV1CS07.

  4. Boot to 4.0(4) release.

  5. Upgrade storage controller to the latest version available in the 4.0(4) release.

4.0(4b)

CSCvr03037

Intel drives and few of the other SATA drives are displayed as Unconfigured bad in Cisco IMC Storage section after upgrading the firmware from version CS05 to version CS07.

This issue is seen only when Cisco 12G Modular SAS HBA controller is connected with Intel drives and SAS drives. This is observed only in Cisco IMC Out of Band Interface, wherein the drives are shown as healthy in HII/Host interface of the storage controller.

Note 

Sometimes it may take around 15 minutes to reflect the right status of controller and drives from Cisco IMC.

Perform Cisco IMC reboot.

4.0(4e)

CSCvr03044

While upgrading Cisco IMC from 4.0(2c) to 4.0(4f), SAS drive firmware update may fail when the drives are connected to Cisco 12G Modular SAS HBA controller.

Update the failed drives or all the drives again for a successful update.

4.0(4e)

CSCvr03041

Slot numbers of the connected drives are displayed as NA in Host Update Utility even after updates are completed successfully.

This issue is seen only in Software RAID configurations.

There is no functional impact as the drives are updated successfully.

4.0(4c)

Release 4.0(4e)

The following defects are open in release 4.0(4e):

Table 29. Server

Defect ID

Symptom

Workaround

First Affected Release

CSCvq95077

S3260 M5 servers keep rebooting and fail to power on and does not complete BIOS POST.

Power cycle the server to recover the setup.

4.0(4e)

Table 30. External Controllers

Defect ID

Symptom

Workaround

First Affected Release

CSCvq74492

System becomes unresponsive during BIOS post when the Intel X520 PCIe adapter is present on the system and iSCSI mode is enabled for Intel X550 LOMs. This happens only when boot mode is set to legacy.

If this issue occurs, do one of the following:

  • Switch to UEFI boot mode.

Or

  1. When system is hung, set the LOM Option to disable using the CIMC feature to set the BIOS tokens.

  2. Reboot the server to the UEFI shell.

  3. Use the Intel bootutil and enable iSCSI for X520 adapter and reboot the server (Intel bootutil along with its userguide is part of the driver iso).

  4. On next boot, during BIOS post enter into Intel OPROM Utility(Ctrl +D), enable the ISCSI mode for X550 LOM. Save and restart.

  5. LOM ISCSI LUN will boot without any issue.

4.0(4e)

CSCvq26156

Upgrade of UCS C-Series Server firmware to 4.0(4a) or later releases causes Cisco 12G Modular SAS HBA to stop discovering the following drive models:

  • SSDSC2KB480G7K - 480GB 2.5-inch Enterprise Value 6G SATA SSD

  • SDSC2KB960G7K - 960GB 2.5-inch Enterprise Value 6G SATA SSD

  • SSDSC2KG019T7K - 1.9TB 2.5-inch Enterprise performance 6G SATA SSD

  • SSDSC2KG480G7K - 480GB 2.5-inch Enterprise performance 6GSATA SSD

  • SSDSC2KG960G7K - 960GB 2.5-inch Enterprise performance 6G SATA SSD

  • SSDSC2KB038T7K - 3.8TB 2.5-inch Enterprise Value 6G SATA SSD

This issue occurs only when the drive firmware version before the upgrade is SCV1CS05. Other drive firmware versions are not affected.

  1. Before upgrading to 4.0(4a) release, upgrade only the firmware of the drives to SCV1CS07, which is part of Release 4.0(4a) or later release packages.

  2. Now proceed with full upgrade of 4.0(4a) or later release package.

If already impacted by this issue, do the following to recover:

  1. Downgrade Cisco 12G Modular SAS HBA to a previous working version (00.00.00.50 or 00.00.00.58 available in 4.0(1) and 4.0(2) release packages respectively).

  2. Upgrade the firmware of the impacted drives to SCV1CS07, which is part of Release 4.0(4a) or later release packages.

  3. After drive firmware is updated, proceed with upgrade of Cisco 12G Modular SAS HBA firmware to 09.00.00.06, which is part of Release 4.0(4a) or later release packages.

4.0(4e)

Release 4.0(4b)

The following defects are open in release 4.0(4b):

Table 31. Intel® Optane Data Center Persistent Memory Modules - Intel Open Caveats

Defect ID

Symptom

Workaround

First Bundle Affected

CSCvn77341

Namespaces created under Red Hat Enterprise Linux 7.6 by using the in-box ndctl tool, may be seen in "Critical" health state when examined in the BIOS Setup or the UEFI IPMCTL tool. However, the namespaces are healthy, and their functionality is not affected.

This is an issue with the Intel® Optane Data Center persistent memory module HII and UEFI IPMCTL tool.

Intel IPS case filed.

No known workaround. The namespaces are healthy, and their functionality is not affected.

4.0(4b)

CSCvn81521

On systems with Intel® Optane Data Center persistent memory modules in 2LM (memory mode), uncorrectable errors get logged on the persistent memory modules when errors occur on DDR4 DIMMs (configured as near memory) on the same channel.

Intel IPS case filed.

Examine the MCAOut files to identify the actual failed DIMM location.

4.0(4b)

CSCvp08356, CSCvo72182

When Intel® Optane Data Center persistent memory modules are populated in the system, and the system is operational, occasionally false uncorrectable errors are reported on DIMM A1. This has no functional impact.

Intel IPS case filed.

Clear errors by using Reset all Memory errors in Cisco UCS Manager.

4.0(4b)

CSCvp38564

Intel® Intelligent Power Technology Node Manager (NM) PTU does not work with Intel® Optane DC persistent memory modules in App Direct mode. Hence, the power characterization accuracy is reduced.

Intel IPS case filed.

If persistent memory modules are detected in a system, the BIOS will not load NMPTU to prevent unresponsiveness or an infinite loop.

4.0(4b)

CSCvp37389

In some specific situations, in-flight write traffic can hit a small probability of a DDRT surprise clock stop, which may cause the Intel® Optane Data Center persistent memory module to go into a "Fatal Failure" state and result in a persistent memory module Media Disable.

No known workaround.

4.0(4b)

Table 32. Intel® Optane Data Center Persistent Memory Modules - Cisco Open Caveats

Defect ID

Symptom

Workaround

First Affected Release

CSCvo17390

On the S3260 M5 servers with Intel® Optane Data Center persistent memory module, fault engine displays a warning message that indicates RDIMM size from SPD is 0.

None.

4.0(4b)

CSCvp03376

Fault engine displays "mismatch FW revision" warning for persistent memory DIMMs though the firmware version is the same on the DIMMs.

None.

4.0(4b)

CSCvn93216

On systems with Intel® Optane Data Center persistent memory module, fault engine warning summary for persistent memory module may not be complete. In case of faults on both CPU1, CPU2, fault summary displays only CPU2's faults.

None.

4.0(4b)

CSCvp11872

Duplicate faults are reported for Intel® Optane Data Center persistent memory module. Existing persistent memory module faults are reported again (duplicates) after every host reboot.

None.

4.0(4b)

CSCvp13906

Memory is not accessible when Intel® Optane Data Center persistent memory module is configured as volatile memory with NUMA in disabled state.

None.

4.0(4b)

CSCvo99814

When security is disabled on Intel® Optane Data Center persistent memory module, security state is displayed as Disabled, Unlocked, Frozen, Count not expired on Cisco IMC. But the host tools display the security state as Disabled, Frozen.

None.

4.0(4b)

CSCvp15031

Intel® Optane Data Center persistent memory module health state changes to Non-functional after upgrading its firmware from 2019_WW10 to 2019_WW12BKC.

None.

4.0(4b)

CSCvo20670

Intel® Optane Data Center persistent memory module displays a Fatal Failure message after performing goal configuration changes.

None

4.0(4b)

CSCvo80193

Media errors reported for Intel® Optane Data Center persistent memory module while performing configuration changes. These errors are seen on both EFI and OS.

None.

4.0(4b)

CSCvo85065

For Intel® Optane Data Center persistent memory module Failure Conditions, no SEL event is logged to indicate failure.

You can view the errors in the BMC fault logs and Windows or Linux SEL through ACPI.

4.0(4b)

Table 33. BIOS

Defect ID

Symptom

Workaround

First Affected Release

CSCvo46953

Unable to initiate iPXE boot from LOM port 1.

Use LOM port 2.

4.0(4b)

CSCvp21118

Precision boot order (L2 boot order) feature of Cisco UCS C480 M5 servers may not list the external physical USB drives in the boot order.

You can use BIOS F6 to boot from the required device.

4.0(4b)

CSCvp43349

After upgrading the BIOS firmware to 4.0(4b), Cisco UCS M5 servers may lose the previously configured (before the upgrade) iSCSI attempts.

You can add the iSCSI attempt from the BIOS setup for third party Adapters and using the Cisco IMC GUI for VIC cards.

4.0(4b)

CSCvp36893

When you run the PTU TDP test on the Cisco UCS M5 servers with some CPU SKUs, CPU domain max power limit reaches only half the actual CPU TDP.

None.

4.0(4b)

Table 34. External Controllers

Defect ID

Symptom

Workaround

First Affected Release

CSCvp11474

While updating firmware on multiple drives using HUU, an error indicating that the drive update for a particular drive has "Failed" is displayed even though the firmware is updated.

Manually update the firmware of the drive reported by HUU or ignore the error and continue with the reboot step as firmware is already updated.

4.0(4b)

CSCvo3964,

CSCvo89921

CATERR/IERR occurs on multiple reboots and the system becomes unresponsive during POST. This issue occurs on servers with NVMe drives on mSwitch connected configuration.

Perform warm reboot.

4.0(4b)

CSCvm15304

On the C480 M5 servers with two Intel ColdStream drives on PCI Switch1 and PCI Switch Rear, Intel ColdStream Next 750GB drive link goes to degraded state after a few reboots.

None.

4.0(4b)

CSCvp30283

On servers with QL45412H card, iSCSI configuration restores to default settings after updating the adapter firmware. This happens when you configure iSCSI using the Qlogic HII configuration utility from the BIOS menu.

  1. Enter the F2 BIOS setup menu and access the Advanced tab of iSCSI configuration.

  2. Enter the iSCSI Initiator Name and Target Name.

  3. Save and Exit.

4.0(4b)

CSCvq81930

Firmware update of the following Intel drives fail while upgrading from 4.0(2c) to 4.0(4b) OR 4.0(4e):

  • SSDSC2KB038T7K : 3.8TB 2.5 inch Enterprise Value 6G SATA SSD

  • SSDSC2KB960G7K - 960GB 2.5-inch Enterprise Value 6G SATA SSD

  • SSDSC2KG019T7K - 1.9TB 2.5-inch Enterprise performance 6G SATA SSD

    SSDSC2KG480G7K - 480GB 2.5-inch Enterprise performance 6GSATA SSD

  • SSDSC2KG960G7K - 960GB 2.5-inch Enterprise performance 6G SATA SSD

Use HUU 4.0(2f) to update the drives.

4.0(4b)

Open Caveats in Release 4.0(2)

Release 4.0(2c)

The following defects are open in release 4.0(2c):

Table 35. BIOS

Defect ID

Symptom

Workaround

First Affected Release

CSCvn09309

While trying to boot to PXE by pressing the F12 key during POST, F12 network boot will not work for Cisco FastlinQ QL45611HLCU 100GBE adapter.

Press the F6 or F2 key and select Cisco FastlinQ QL45611HLCU 100GBE adapter for PXE boot.

4.0(2c)

Table 36. External Controllers

Defect ID

Symptom

Workaround

First Affected Release

CSCvm78123

ISCSI Boot protocol for Intel® XXV710-DA2 and X710-T4 cards is not displayed in the Boot Utility (bootutil) for the servers with firmware version 4.0(1a).

None

4.0(2c)

CSCvm78419

ISCSI lun may not be able establish TCP/IP connection with the Cisco Etherent Converged NIC X710-DA2, Intel X710-DA4 , and Intel XL710QDA2 PCIe cards after the firmware is updated to version 4.0(1a ).

Use the following command on switch:

conf t
    no lldp tlv-select dcbxp

4.0(2c)

Open Caveats in Release 4.0(1)

Release 4.0(1a)

The following defect is open in Release 4.0(1a):

Table 37. BIOS

Defect ID

Symptom

Workaround

First Affected Release

CSCvk58997

On the M4 servers, booting IPv6 based UEFI PXE using Windows WDS application fails with a server time out error. This happens with all M4 servers in UEFI mode.

Use IPv4 UEFI PXE.

4.0(1a)

CSCvo77732

After upgrading the C460 M4 servers with Intel® Xeon® Processor v2 to 4.0(1a) version, server encounters a CATERR fault and the server becomes unresponsive.

Downgrade to 3.0(x) version.

4.0(1a)

Table 38. VIC

Defect ID

Symptom

Workaround

First Affected Release

CSCvq64055

Cisco VIC1455 and VIC 1457 interfaces take more than four minutes to recover to Link-Up state after the far end Switch configuration is changed to no shut. This happens when a 25G 5M copper passive cable (SFP-H25G-CU5M) cable is connecting the VIC1455 or VIC 1457 and the N9K-C93180YC-EX switch.

Use shorter copper passive cables (SFP-25G-CU1M. SFP-25G-CU2M, SFP-25G-CU3M).

Or

Use optical cables.

4.0(1a)

Open Caveats in the Previous Releases

Refer to the following release notes for Open Caveats in the previous releases:

Release Notes for Cisco UCS C-Series Software

Known Behaviors

The following section lists known behaviors.

Known Behaviors in Release 4.0(4)

Release 4.0(4e)

The following caveats are the known limitations in Release 4.0(4e):

Table 39. BMC

Defect ID

Symptom

Workaround

First Affected Release

CSCvp65147

Despite user account being locked due to multiple incorrect login attempts, user can execute IPMI commands after successful user authentication through IPMI during the account lockout period.

Enable the Disable user on Lockout feature using the CLI or XML API or WebUI interface. This will disable the locked user and IPMI commands will not work for the user.

4.0(4c)

Table 40. External Controllers

Defect ID

Symptom

Workaround

First Affected Release

CSCvq20893

All the supported SN200 series drives are displayed as SN200 in device manager page or Hardware info page of ESXi. Specific version of the drive is not displayed.

None.

4.0(4e)

CSCvq20302

HGST SN200 NVMe drives connected to rear-end (direct connect) do not go offline when an informed drive removal is done on Windows OS. LEDs of the drives blink for a couple of seconds and display steady green status.

None.

4.0(4e)

Release 4.0(4b)

The following caveats are the known limitations in Release 4.0(4b):

Table 41. Intel® Optane Data Center Persistent Memory Modules

Defect ID

Symptom

Workaround

First Affected Release

CSCvo21859

You cannot scope into CLI when a namespace is configured with an empty name using the host tools (F2).

Do not create namespaces with empty name from host tools.

4.0(4b)

CSCvo59901

You cannot scope into CLI or delete a namespace using CLI when you create a namespace (using the host tools (F2)) that has special characters in the name.

Do not use special characters for namespace names other than the following supported ones: #, - and _

4.0(4b)

CSCvo21881

When a Goal is created in mixed mode, the actual capacity allocated for volatile and persistent memories does not match with the calculation done using the % of memory mode configured.

None.

4.0(4b)

Table 42. BMC

Defect ID

Symptom

Workaround

First Affected Release

CSCvo13512

Power consumption does not reduce to minimum limit set. This happens on servers with Intel® 8260C, 6254 CPU SKUs.

None.

4.0(4b)

Table 43. External Controllers

Defect ID

Symptom

Workaround

First Affected Release

CSCvn72355

Unable to create a virtual drive (VD) with Cached I/O Policy enabled on systems. While creating a VD, Cached I/O Policy is disabled on Cisco IMC and LSI Storage Authority (LSA).

None.

4.0(4b)

Known Behaviors in the Previous Releases

Refer to the following release notes for Known Behaviors in the previous releases:

Release Notes for Cisco UCS C-Series Software

Known Behaviors in Release 4.0(2)

Release 4.0(2c)

The following caveats are known limitations in Release 4.0(2c):

Table 44. BMC

Defect ID

Symptom

Workaround

First Affected Release

CSCvm08504

During a server firmware downgrade using the HUU, LLF (1050W PSUs) update fails when downgrading the firmware version from 4.0(1) to any previous releases.

None.

4.0(2c)

Table 45. External GPU Expander

Defect ID

Symptom

Workaround

First Affected Release

CSCvm92237

The nvidia-smi tool GPU slot mapping does not match with the lspci output and the C480-M5ML Silkscreen slot numbering.

To map lspci GPU slot nr/BusID to nvidia-smi GPU slot nr/BusID, run the following command (see the example below):

4.0(2c)

Mapping lspci GPU slot nr/BusID to nvidia-smi GPU slot nr/BusID:

[root@localhost ~]# lspci -tv

Search for Nvidia Devices with BusID 1b and 1c, for example; 
the tree will display GPU PCI bridge BusID mapped to nvidia-smi GPU BusID:

lspci GPU PCI bridge BusID: 19:08.0 mapped with nvidia-smi GPU BusID: [1b]  
(1B:00.0)
lspci GPU PCI bridge BusID: 19:0c.0 mapped with nvidia-smi GPU BusID: [1c]  
(1C:00.0)

-[0000:17]-+-00.0-[18-1c]----00.0-[19-1c]--+-04.0-[1a]--
 |           |                               +-08.0-[1b]----00.0 
                                   NVIDIA Corporation Device 1db5
 |           |                               \-0c.0-[1c]----00.0 
                                  NVIDIA Corporation Device 1db5

To find a GPU slot nr, run the following command:

[root@localhost ~]# lspci -vvv -s 19:08.0 | grep -i slot
	Capabilities: [68] Express (v2) Downstream Port (Slot+), MSI 00
		LnkSta:	Speed 8GT/s, Width x16, TrErr- Train- 
              SlotClk- DLActive+ BWMgmt- ABWMgmt-
			Slot #3, PowerLimit 0.000W; Interlock- NoCompl-
		VC0:	Caps:	PATOffset=03 MaxTimeSlots=1 RejSnoopTrans-

[root@localhost ~]# lspci -vvv -s 19:0c.0 | grep -i slot
	Capabilities: [68] Express (v2) Downstream Port (Slot+), MSI 00
		LnkSta:	Speed 8GT/s, Width x16, TrErr- Train- SlotClk- 
             DLActive+ BWMgmt- ABWMgmt-
			Slot #4, PowerLimit 0.000W; Interlock- NoCompl-
		VC0:	Caps:	PATOffset=03 MaxTimeSlots=1 RejSnoopTrans- 

lspci GPU Slot #3 (19:08.0) corresponds to nvidia-smi GPU Slot # 0 (1B:00.0)
lspci GPU Slot #4 (19:0c.0) corresponds to nvidia-smi GPU Slot # 1 (1C:00.0)

Repeat same steps for the other GPUs

Table 46. External OS

Defect ID

Symptom

Workaround

First Affected Release

CSCvj48637

HDD activity and locate LEDs are not working for AHCI controller. This happens when the Red Hat Enterprise Linux OS is installed.

None.

4.0(2c)

CSCvk15263

During installation, iSCSI LUN is not visible on Cavium OCP 41232 adapters with XEN 7.2, 7.3 or 7.4 OS versions.

None.

4.0(2c)

Known Behaviors in Release 4.0(1)

Release 4.0(1a)

The following caveat is a known limitation in Release 4.0(1a):

Table 47. CMC

Defect ID

Symptom

Workaround

First Affected Release

CSCvi46521

On the 3260 servers, when you are using a dual VIC single server configuration, you cannot access the second VIC.

You must enable the single server dual VIC feature to use the second VIC.

4.0(1a)

Table 48. External Controllers

Defect ID

Symptom

Workaround

First Affected Release

CSCvk11921

On the C125 servers with QL41232H 25G OCP card, the link does not work. This happens when OCP card is connected to the switch using a 5M SFP cable. The network LED is not on and the network is not functional.

  1. Enter the BIOS setup.

  2. Navigate to Advanced > Qlogic QL41232 Option > Port Level configuration

  3. Change the link Speed to 25Gbps.

  4. Press F10.

  5. Save and exit.

4.0(1a)

Known Behaviors in the Previous Releases

Refer to the following release notes for Known Behaviors in the previous releases:

Release Notes for Cisco UCS C-Series Software

Related Documentation

Related Documentation

For configuration information for this release, refer to the following:

For information about installation of the C-Series servers, refer to the following:

The following related documentation is available for the Cisco Unified Computing System:

Refer to the release notes for Cisco UCS Manager software and the Cisco UCS C Series Server Integration with Cisco UCS Manager Guide at the following locations: