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. |
Deprecation Notice
Deprecated Release 4.0(4k)
Release 4.0(4k) is deprecated and firmware files are no longer available. For more information, refer Field Notice: FN - 70595.
Cisco recommends that you upgrade to release 4.0(4l) or later.
Revision History
Revision |
Date |
Description |
---|---|---|
L1 |
March 18, 2021 |
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 |
K1 |
December 17, 2020 |
Updated Known Behaviors in Release 4.0(4) section. |
K0 |
November 03, 2020 |
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 |
J0 |
July 06, 2020 |
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 |
A3 |
May 21, 2020 |
Updated the Open Caveats section in 4.0(4b). |
D2 |
April 9, 2020 |
Updated the Open Caveats section in 4.0(4e). |
I1 |
April 2, 2020 |
Updated the Resolved Caveats section in 4.0(4k). |
I0 |
March 23, 2020 |
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 |
A1 |
March 11, 2020 |
Updated Open Caveats section for release 4.0(4b). |
H0 |
December 20, 2019 |
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 |
G0 |
December 09, 2019 |
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 |
F0 |
September 27, 2019 |
Following changes were made:
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:
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:
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:
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:
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). |
Supported Platforms and Release Compatibility Matrix
Supported Platforms in this Release
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
Cisco IMC and Cisco UCS Manager Release Compatibility Matrix
Cisco UCS C-Series and S-Series Rack-Mount Servers are managed by built-in standalone software —Cisco IMC. However, when a Rack-Mount Server is integrated with Cisco UCS Manager, the Cisco IMC does not manage the server anymore.
The following table lists the supported platforms, Cisco IMC releases, and Cisco UCS Manager releases for Rack-Mount Servers:
Cisco IMC Release |
Cisco UCS Manager Release |
Rack Mount Servers |
---|---|---|
4.0(4n) |
4.0(4l) |
Cisco UCS C220 M5, C240 M5, C480 M5, and S3260 M5 servers |
4.0(4m) |
4.0(4j) |
Cisco UCS C220 M5, C240 M5, C480 M5, and S3260 M5 servers |
4.0(4l) |
4.0(4i) |
Cisco UCS C220 M5, C240 M5, C480 M5, and S3260 M5 servers |
4.0(4k) |
4.0(4h) |
Cisco UCS C220 M5, C240 M5, and S3260 M5 servers |
4.0(4j) |
No Support |
Cisco UCS S3260 M5 servers |
4.0(4i) |
4.0(4g) |
Cisco UCS C220 M5, C240 M5, C480 M5 and S3260 M5 servers |
4.0(4h) |
4.0(4e) |
Cisco UCS C220 M5, C240 M5, C480 M5 and S3260 M5 servers |
4.0(4f) |
4.0(4d) |
Cisco UCS C220 M5, C240 M5, C480 M5, S3260 M5 and C480 ML M5 servers |
4.0(4e) |
4.0(4c) |
Cisco UCS C220 M5, C240 M5, C480 M5, S3260 M5 and C480 ML M5 servers |
4.0(4d) |
No Support |
Cisco UCS C220 M5, C240 M5, C480 M5 and S3260 M5 servers |
4.0(4b) |
4.0(4a) |
Cisco UCS C220 M5, C240 M5, C480 M5, S3260 M5 and C480 ML M5 servers |
Cisco IMC Release |
Cisco UCS Manager Release |
Rack Mount Servers |
---|---|---|
4.0(3b) |
4.0(3a) |
Cisco UCS C220 M5 and C240 M5 servers |
Cisco IMC Release |
Cisco UCS Manager Release |
Rack Mount Servers |
---|---|---|
4.0(2q) |
4.0(4l) |
Cisco UCS C220 M4, C240 M4, C460 M4, and S3260 M4 servers |
4.0(2p) |
No support. |
Cisco UCS C125 M5 servers |
4.0(2o) |
4.0(4j) |
Cisco UCS C220 M4, C240 M4, C460 M4, and S3260 M4 servers |
4.0(2n) |
No support. |
Cisco UCS C220 M5, C240 M5, C480 M5, C480 ML M5, S3260 M5, C125 M5, C220 M4, C240 M4, C460 M4, and S3260 M4 servers |
4.0(2m) |
No support. |
Cisco UCS S3260 M4 and M5 servers |
4.0(2l) |
No support. |
Cisco UCS C220 M5, C240 M5, C480 M5, C480 ML M5, S3260 M5, C220 M4, C240 M4, C460 M4, and S3260 M4 servers |
4.0(2k) |
No support. |
Cisco UCS S3260 M4 and M5 servers |
4.0(2i) |
No support. |
Cisco UCS C460 M4, S3260 M4, and S3260 M5 servers |
4.0(2h) |
4.0(2e) |
Cisco UCS C220 M5, C240 M5, C480 M5, C480 ML M5, S3260 M5, C125 M5, C220 M4, C240 M4, C460 M4, and S3260 M4 servers |
4.0(2f) |
4.0(2d) |
Cisco UCS C220 M5, C240 M5, C480 M5, C480 ML M5, S3260 M5, C125 M5, C220 M4, C240 M4, C460 M4, and S3260 M4 servers |
4.0(2d) |
4.0(2b) |
Cisco UCS C220 M5, C240 M5, C480 M5, C480 ML M5, S3260 M5, C125 M5, C220 M4, C240 M4, C460 M4, and S3260 M4 servers |
4.0(2c) |
4.0(2a) |
Cisco UCS C220 M5, C240 M5, C480 M5, C480 ML M5, S3260 M5, C125 M5, C220 M4, C240 M4, C460 M4, and S3260 M4 servers |
Cisco IMC Release |
Cisco UCS Manager Release |
Rack Mount Servers |
---|---|---|
4.0(1e) |
No support. |
Cisco UCS M4, M5 servers and C125 M5 |
4.0(1d) |
4.0(1d) |
Cisco UCS M4, M5 servers and C125 M5 |
4.0(1c) |
4.0(1c) |
Cisco UCS M4, M5 servers and C125 M5 |
4.0(1b) |
4.0(1b) |
Cisco UCS M4, M5 servers and C125 M5 |
4.0(1a) |
4.0(1a) |
Cisco UCS M4, M5 servers and C125 M5 |
Cisco IMC Release |
Cisco UCS Manager Release |
Rack Mount Servers |
||
---|---|---|---|---|
3.1(3k) |
3.2(3p) |
Cisco UCS C480 M5, C220 M5, C240 M5, and S3260 M5 servers |
||
3.1(3j) |
No Support
|
Cisco UCS C480 M5, C220 M5, C240 M5, and S3260 M5 servers |
||
3.1(3i) |
3.2(3i) |
Cisco UCS C480 M5, C220 M5, C240 M5, and S3260 M5 servers |
||
3.1(3h) |
3.2(3h) |
Cisco UCS C480 M5, C220 M5, C240 M5, and S3260 M5 servers |
||
3.1(3g) |
3.2(3g) |
Cisco UCS C480 M5, C220 M5, C240 M5, and S3260 M5 servers |
||
3.1(3d) |
3.2(3e) |
Cisco UCS C480 M5, C220 M5, C240 M5, and S3260 M5 servers |
||
3.1(3c) |
3.2(3d) |
Cisco UCS C480 M5, C220 M5, C240 M5, and S3260 M5 servers |
||
3.1(3b) |
3.2(3b) |
Cisco UCS C480 M5, C220 M5, and C240 M5 servers |
||
3.1(3a) |
3.2(3a) |
Cisco UCS C480 M5, C220 M5, C240 M5, and S3260 M5 servers |
Cisco IMC Release |
Cisco UCS Manager Release |
Rack Mount Servers |
---|---|---|
3.1(2d) |
3.2(2d) |
Cisco UCS C480 M5, C220 M5, and C240 M5 |
3.1(2c) |
3.2(2c) |
Cisco UCS C480 M5, C220 M5, and C240 M5 |
3.1(2b) |
3.2(2b) |
Cisco UCS C480 M5, C220 M5, and C240 M5 |
C-Series Standalone Release |
Cisco UCS Manager Release |
C-Series Servers |
---|---|---|
3.1(1d) |
3.2(1d) |
Cisco UCS C220 M5/C2540 M5 |
Cisco IMC Release |
Cisco UCS Manager Release |
Rack-Mount Servers |
---|---|---|
3.0(4s) |
No support |
Cisco UCS C220 M3, C240 M3, C3160 M3, S3260 M4 |
3.0(4r) |
No support |
Cisco UCS C220 M4, C240 M4, C460 M4, S3260 M4, C22 M3, C24 M3, C220 M3, C240 M3, C3160 M3, S3260 M3 |
3.0(4q) |
No support |
Cisco UCS C220 M4, C240 M4, C460 M4, S3260 M4, C22 M3, C24 M3, C220 M3, C240 M3, C3160 M3, S3260 M3 |
3.0(4p) |
3.2(3o) |
Cisco UCS C220 M4, C240 M4, C460 M4, S3260 M4, C22 M3, C24 M3, C220 M3, C240 M3, C3160 M3, S3260 M3 |
3.0(4o) |
No support |
Cisco UCS C220 M4, C240 M4, C460 M4, S3260 M4, C22 M3, C24 M3, C220 M3, C240 M3, C3160 M3, S3260 M3 |
3.0(4n) |
No support. |
Cisco UCS C220 M4, C240 M4, C460 M4, S3260 M4, C22 M3, C24 M3, C220 M3, C240 M3, C3160 M3, S3260 M3 |
3.0(4m) |
No support. |
Cisco UCS C220 M4, C240 M4, C460 M4, S3260 M4, C22 M3, C24 M3, C220 M3, C240 M3, C3160 M3, S3260 M3 |
3.0(4l) |
No support. |
Cisco UCS C220 M4, C240 M4, C460 M4, S3260 M4, C22 M3, C24 M3, C220 M3, C240 M3, C3160 M3, S3260 M3 |
3.0(4k) |
No support. |
Cisco UCS C220 M4, C240 M4, C460 M4, S3260 M4, C22 M3, C24 M3, C220 M3, C240 M3, C3160 M3, S3260 M3 |
3.0(4j) |
3.1(3k) |
Cisco UCS C220 M4, C240 M4, C460 M4, S3260 M4, C22 M3, C24 M3, C220 M3, C240 M3, C3160 M3, S3260 M3 |
3.0(4i) |
3.1(3j) |
Cisco UCS C220 M4, C240 M4, C460 M4, S3260 M4, C22 M3, C24 M3, C220 M3, C240 M3, C3160 M3, S3260 M3 |
3.0(4e) |
No support |
Cisco UCS C220 M4, C240 M4, C460 M4, S3260 M4, C22 M3, C24 M3, C220 M3, C240 M3, C3160 M3, S3260 M3 |
3.0(4d) |
3.1(3h) |
Cisco UCS C220 M4, C240 M4, C460 M4, S3260 M4, C22 M3, C24 M3, C220 M3, C240 M3, C3160 M3, S3260 M3 |
3.0(4a) |
3.1(3f) |
Cisco UCS C220 M4, C240 M4, C460 M4, S3260 M4, C22 M3, C24 M3, C220 M3, C240 M3, C3160 M3, S3260 M3 |
Cisco IMC Release |
Cisco UCS Manager Release |
Rack-Mount Servers |
---|---|---|
3.0(3f) |
- |
Cisco UCS C240 M4, and C220 M4 |
3.0(3e) |
3.0(3e) |
Cisco UCS C22 M3, C24 M3, C220 M3, C240 M3, C220 M4, C240 M4, C460 M4, C3160 M3, S3260 M4 and S3260 M3 servers |
3.0(3c) |
3.0(3c) |
Cisco UCS C240 M4, and C220 M4 |
3.0(3b) |
3.0(3b) |
Cisco UCS S3260 M3, C3160 M3, C460 M4, C240 M4, and C220 M4 |
3.0(3a) |
3.1(3a) |
Cisco UCS C22 M3, C24 M3, C220 M3, C240 M3, C220 M4, C240 M4, C460 M4, C3160 M3, S3260 M4 and S3260 M3 servers |
Cisco IMC Release |
Cisco UCS Manager Release |
Rack-Mount Servers |
||
---|---|---|---|---|
3.0(2b) |
No Support
|
C220 M4/C240 M4 only |
Cisco IMC Release |
Cisco UCS Manager Release |
Rack-Mount Servers |
||
---|---|---|---|---|
3.0(1d) |
No Support
|
All M3/M4 except C420 M3 |
||
3.0(1c) |
No Support |
All M3/M4 except C420 M3 |
Cisco IMC Release |
UCS Manager Release |
Rack Mount Servers |
---|---|---|
2.0(13e) |
3.1(2b) |
All M3/M4 except C420 M3 |
2.0(10b) |
3.1(1g) |
C220 M4/C240 M4 only |
2.0(9c) |
3.1(1e) |
All other M3/M4 |
2.0(9f) |
2.2(7b) |
For all other M3/M4 |
2.0(10b) |
2.2(7b) |
C220 M4/C240 M4 only |
1.5(9d) |
2.2(7b) |
C420-M3, C260-M2, C460-M2 only |
1.5(9d) |
2.2(8f) |
C420-M3, C260-M2, C460-M2 only |
2.0(9c) |
2.2(8f) |
For all other M3/M4 |
2.0(10b) |
2.2(8f) |
C220 M4/C240 M4 only |
2.0(12b) |
2.2(8f) |
C460 M4 only |
1.5(8a) |
2.2(6g) |
C420 M3, C260 M2, C460 M2 only |
2.0(8d) |
2.2(6c) |
For all other M3/M4 |
1.5(7f) |
2.2(5b) |
C420 M3, C260 M2, C460 M2 only |
2.0(6d) |
2.2(5a) |
For all other M3/M4 |
1.5(7a)2 |
2.2(4b) |
C420 M3, C260 M2, C460 M2 only |
2.0(4c) |
2.2(4b) |
For all other M3/M4 |
1.5(7c)1 |
2.2(3b) |
C420 M3, C260 M2, C460 M2 only |
2.0(3d)1 |
2.2(3a) |
For all other M3/M4 |
Operating System and Browser Requirements
For detailed information about supported Operating System, see the interactive UCS Hardware and Software Compatibility matrix.
Cisco recommends the following browsers for Cisco UCS Rack Server Software, Release 4.0(2):
-
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.
-
-
Transport Layer Security (TLS) version 1.2.
Hardware and Software Interoperability
For detailed information about storage switch, operating system and adapter, 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
Note |
Connectivity is tested between the server and the first connected device. Further connections, such as to storage arrays after a switch are not listed in the Cisco UCS Hardware Compatibility List though they may be highlighted in the vendor support matrix for those devices. |
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
Upgrade Paths to Release 4.0
The section provides information on the upgrade paths to release 4.0. Refer to the table for upgrade paths for various Cisco UCS C-series IMC versions.
Upgrade From Release |
Upgrade To Release |
Recommended Upgrade Path |
---|---|---|
All M5 Servers from 3.1 |
4.0 |
Follow below upgrade path:
|
For all M4 servers for releases greater than 3.0(3a) |
4.0 |
Follow these steps to upgrade from releases greater than 3.0(3a) to 4.0:
|
For all M4 servers for release lesser than 3.0(3a) except C460 M4 For C460 M4 servers for release 2.0(4c) to 3.0(3a) |
4.0 |
Follow these steps to upgrade from releases less than 3.0(3a) to 4.0: Upgrade from version less than 3.0(3a) to 3.0(3a)
Upgrade from 3.0(3a) to 4.0
|
For C460 M4 servers for release lesser than 2.0(4c) |
4.0 |
Follow these steps to upgrade from releases less than 2.0(4c) to 4.0: Upgrade from version less than 2.0(4c) to 2.0(4c)
Upgrade from 2.0(4c) to 3.0(3a)
Upgrade from 3.0(3a) to 4.0
|
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
-
DCPMM Memory
-
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:
New Software Features in Release 4.0(4)
New Software Features in Release 4.0(4n)
The following new software features are supported in Release 4.0(4n):
-
Panic and High Watermark BIOS token is added for Cisco UCS C220 M5, C240 M5, C480 M5, and S3260 M5 servers. For more information, see Cisco UCS C-Series Integrated Management Controller GUI Configuration Guide, Release 4.0 or Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 4.0 at Configuration Guides.
-
Memory Refresh Rate BIOS token is added for Cisco UCS C220 M5, C240 M5, C480 M5, and S3260 M5 servers. Default value is set to 1x Refresh. For more information, see Cisco UCS C-Series Integrated Management Controller GUI Configuration Guide, Release 4.0 or Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 4.0 at Configuration Guides.
New Software Features in Release 4.0(4m)
-
New TX parameters are now enabled in firmware. This fixes the link-flapping and links down issue on a 6400 Series Fabric Interconnect connected to VIC 1455/1457 adapter using SFP-H25G-CU3M or SFP-H25G-CU5M cables or on a VIC 1455/1457 adapter connected to 2232PP using a SFP-10GB-CUxM cable.
New Software Features in Release 4.0(4j)
Firmware for the following HDD models are updated in release 4.0(4j):
-
HUH721008AL4200—Firmware updated to version A3Z4
-
HUH721010AL42C0—Firmware updated to version A3Z4
-
HUH721010AL5200—Firmware updated to version A3Z4
-
HUH721010AL52C0—Firmware updated to version A3Z4
-
HUH721010AL4200—Firmware updated to version A3Z4
New Software Features in Release 4.0(4h)
Fault ID
Fault ID is included in the Cisco IMC logs.
Physical NIC Mode
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:
Ensure that the above options are disabled before enabling Physical NIC Mode. |
New Software Features in Release 4.0(4e)
Device Connector on the S3260 servers
Added support to enable Device Connector on the S3260 servers which allows access to Cisco Intersight.
ADDDC Sparing
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.
Disable User on Lockout
Added the Disable User on Lockout feature: When you choose this option it disables the user account on lockout.
New Software Features in Release 4.0(4d)
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.
New Software Features 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.
New Software Features in Release 4.0(4b)
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.
Note |
If you boot in Legacy Boot mode, the Linux kernel displays a warning similar to the following when loading the Cisco-signed driver modules: Request for unknown module key 'Cisco UCS Driver Signing REL Cert:... This warning means that a key is not present to validate the driver signature. However, Linux kernel can still proceed with loading the Cisco drivers. This warning is displayed in Legacy Boot mode because the Cisco cryptographic keys that are used to validate the driver signatures are only available when the UCS chassis is booted in Secure Boot mode. |
New Hardware Features 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 |
New Hardware in Release 4.0(4d)
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(4d) 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.
New Hardware in Release 4.0(4b)
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
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.
Support for Mellanox MCX4121A-ACAT Dual Port 10/25G SFP28 NIC (UCSC-P-M4D25GF)
New Features
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.
SNMP
The supported MIB definition for this release and later releases can be found at the following link:
ftp://ftp.cisco.com/pub/mibs/supportlists/ucs/ucs-C-supportlist.html
Note |
The above link is incompatible with IE 9.0. |
Security Fixes
Security Fixes in Release 4.0(4k)
The following Security Fixes were added in Release 4.0(4k):
Release |
Defect ID |
CVE ID |
Symptom |
---|---|---|---|
4.0(4k) |
CSCvs31877 |
|
Cisco UCS C-Series and S-Series M5 servers, which include an Intel® Ethernet 700 Series Controller are affected by vulnerabilities identified by the following Common Vulnerability and Exposures (CVE) IDs:
|
4.0(4k) |
CSCvs81690 |
|
Cisco UCS C-Series and S-Series M5 servers that are based on Intel® processors are affected by vulnerabilities identified by the following Common Vulnerability and Exposures (CVE) IDs:
|
Security Fixes in Release 4.0(4i)
The following Security Fixes were added in Release 4.0(4i):
Release |
Defect ID |
CVE ID |
Symptom |
---|---|---|---|
4.0(4i) |
CSCvr54415 |
|
Cisco UCS C-Series and S-Series M5 servers that are based on Intel® processors are affected by vulnerabilities identified by the following Common Vulnerability and Exposures (CVE) IDs:
This release includes BIOS revisions for Cisco UCS C-Series M5 generation servers. These BIOS revisions include the updated microcode and Secure Initialization (SINIT) Authenticated Code Modules (ACM), which are required parts of the mitigation for these vulnerabilities. |
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 |
|
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.
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(4n)
The following caveats were resolved in Release 4.0(4n):
Defect ID |
Symptom |
First Affected Release |
Resolved in Release |
---|---|---|---|
CSCvw95072 |
NMPowerManager.c triggers an unexpected power off event during OS run time in Cisco UCS M5 servers. As a result, Cisco IMC shuts down the server and triggers power characterization. This issue is now resolved. |
4.1(2b) |
4.0(4n) |
Defect ID |
Symptom |
First Affected Release |
Resolved in Release |
---|---|---|---|
CSCvw26110 |
For Cisco S3260 servers, HTML based KVM launch using host name and IP address fails on certain web browsers. This issue is now resolved. |
4.0(4m) |
4.0(4n) |
Release 4.0(4m)
The following caveats were resolved in Release 4.0(4m):
Defect ID |
Symptom |
First Release Affected |
Resolved in Release |
---|---|---|---|
CSCvv76975 |
In Cisco UCS C-Series and S-Series M5 servers, NIC driver returns unexpected status to a RSSv2 OID. Due to this, there are issues in Microsoft Azure Stack. This issue is now resolved. |
4.0(4j) |
4.0(4m) |
Release 4.0(4l)
The following caveats were resolved in Release 4.0(4l):
Defect ID |
Symptom |
First Release Affected |
Resolved in Release |
---|---|---|---|
CSCvt64871 |
In rare situations, Cisco UCS C480 M5 servers and Cisco UCS 480 M5 ML servers stop responding and reboot after ADDDC virtual lockstep is activated. The servers get stuck at the memory testing step, which results in boot loop triggering #IERR and M2M timeout in the memory system. For more information, see: This issue is now resolved. |
4.0(4e) |
4.0(4l) |
CSCvu47239 |
Cisco UCS S3260 M5 servers with UCSC-C3260-SIOC VIC adapter and Network Boot enabled (PXE) in legacy or UEFU boot mode, alert CATERR and fail to complete POST. The following messages are displayed: Configuring memoryOR Configuring Platform HardwareIf FRB2 timer is enabled, servers proceed to auto reset after a ten minute period. This warm boot completes the POST and the boot attempt is successful. This issue is now resolved. |
4.0(4h) |
4.0(4l) |
CSCvu14656 |
On upgrade of BIOS to one of the following versions, the booting of Cisco UCS C220 M5, C240 M5, and S3260 M5 servers gets stuck at the memory testing step:
This issue is now resolved. |
4.0(4h) |
4.0(4l) |
CSCvu11155 |
After upgrading the BIOS to one of the following versions, you may experience performance degradation with Cisco UCS C220 M5, C240 M5, and S3260 M5 servers running on Second Generation Intel® Xeon® Scalable Processors:
This issue is now resolved. |
4.0(4k) |
4.0(4l) |
Defect ID |
Symptom |
First Release Affected |
Resolved in Release |
---|---|---|---|
CSCvs92008 |
Socket connection between Cisco IMC and BMC reaches a max limit and blocks further connection with the following error message: OR
This issue is now resolved. |
4.0(4b) |
4.0(4l) and 4.1(1f) |
CSCvp35008 |
SLES/RHEL OS installation in UEFI mode fails on Cisco UCS C-Series M5 servers when they are equipped with Intel Xx710 adapters, and one or more of these adapters has the Option ROM enabled. This issue is now resolved. |
4.0(4b) |
4.0(4l) |
Defect ID |
Symptom |
First Release Affected |
Resolved in Release |
---|---|---|---|
CSCvq53066 |
Upgrading host firmware from any release 4.0(2x) or earlier to release 4.0(4b) using auto-install in a Cisco UCS C240 M5 server, results in SAS controller firmware activation failure. Following faults are seen:
This issue is now resolved. |
4.0(4d) |
4.0(4l) |
Release 4.0(4k)
The following caveats were resolved in Release 4.0(4k):
Defect ID |
Symptom |
First Release Affected |
Resolved in Release |
||
---|---|---|---|---|---|
CSCvs51200 |
On Cisco UCS C-Series M5 servers, UEFU boot LUNs become non-functional under the following conditions:
This issue is now resolved. |
4.0(4f) |
4.0(4k) |
||
CSCvr79388 |
In rare situations, Cisco Intel® processor based M5 servers stop responding and reboot after ADDDC virtual lockstep is activated. This results in #IERR and M2M timeout in the memory system. For more information, see: This issue is now resolved.
|
4.0(4e) |
4.0(4k) |
Defect ID |
Symptom |
First Affected Release |
Resolved in Release |
---|---|---|---|
CSCvq84999 |
Cisco IMC fails to apply fan control policy on Cisco UCS C-Series M5 servers equipped with Cisco UCS 1387 adapter. The following error message is displayed:
This issue is now resolved. |
4.0(1c) |
4.0(4k) |
CSCvr70687 |
New Cisco UCS C240 M5 server discovery fails or does not respond with the following error message:
The same issue may occur for any Cisco UCS C240 M5 server after an FI reboot or upgrade. This issue is now resolved. |
4.0(4d) |
4.0(4k) |
CSCvs86186 |
NIHUU fails to recognize special characters in share server password and the following error message is displayed: Permission denied. This issue is now resolved. |
4.0(2h) |
4.0(4k) |
CSCvt07824 |
NIHUU fails to recognize special characters in share server password and the following error message is displayed: Permission denied. This issue is now resolved. |
4.0(4g) |
4.0(4k) |
Defect ID |
Symptom |
First Affected Release |
Resolved in Release |
---|---|---|---|
CSCvr95365 |
Discovery of a Cisco UCS C240 M5 server, equipped with Cisco 12G Modular SAS HBA controller, fails with one of the following errors:
This issue now resolved. |
4.0(4i) |
4.0(4k) |
Defect ID |
Symptom |
First Affected Release |
Resolved in Release |
---|---|---|---|
CSCvs48461 |
While upgrading Cisco IMC to 4.0(2m) or 4.0(4i) in Cisco UCS S3260 M5 and M4 servers, HUU and NIHUU report HDD firmware updates as failed, even after the actual update is successful. This issue is now resolved. |
4.0(2m) |
4.0(4k) |
Release 4.0(4j)
There are no resolved caveats in 4.0(4j).
Release 4.0(4i)
The following caveats were resolved in Release 4.0(4i):
Defect ID |
Symptom |
First Affected Release |
Resolved in Release |
---|---|---|---|
CSCvo76406 |
Cisco IMC GUI does not support editing the applied namespaces for Cisco UCS C-Series M5 servers. However, the namespaces could be edited using Cisco IMC CLI or XMP API, which caused loss of data and configurations. Editing the applied namespaces through Cisco IMC CLI or XML API is no longer supported. |
4.0(4a) |
4.0(4i) |
CSCvr72565 |
Non-admin users could modify the time zone through Cisco IMC CLI interface for Cisco UCS C240-M5 servers. This issue is now resolved. Non-admin users can no longer modify the time zone through Cisco IMC CLI interface. |
3.0(4n) |
4.0(4i) |
CSCvr43466 |
Cisco UCS C-Series rack servers integrated with Cisco UCS Manager displayed hardware inventory mismatch. This issue is now resolved. |
4.0(4b) |
4.0(4i) |
CSCvo62515 |
Cisco IMC crashed or was non-responsive due to kernel issues with the following error log:kernel BUG at drivers/bmc/cisco_proc_lib /cisco_proc_lib.c log This issue is now resolved. |
3.1(3h) |
4.0(4i) |
CSCvp90030 |
Cisco IMC used to crash with the following kernel error log: log_i2c_tx in the stack trace of oopsThis issue is now resolved. |
4.0(4c) |
4.0(4i) |
CSCvr78701 |
A Cisco UCS Manager integrated C-Series server use to experience a Cisco IMC kernel panic after upgrading Cisco UCS Manager from release 4.0(2b) to release 4.0(4c). This issue is now resolved. |
4.0(4c) |
4.0(4i) |
CSCvr96140 |
In Cisco UCS M5 servers, when IPMI Watchdog Timer is enabled, the operating system use to reboot abruptly with the following Onboard Failure Logging (OBFL) log error message: "oem_common.c:309:Error: the 'messaging' thread is stalled" As a workaround, you could disable Watchdog Timer on the operating system to avoid unintentional reboot. This issue is now resolved. |
4.0(2d) |
4.0(4i) |
Defect ID |
Symptom |
First Affected Release |
Resolved in Release |
---|---|---|---|
CSCvr68316 |
In Cisco C-Series servers, when a UCS VIC 1455/1457 adapter was connected to a switch with port-channel enabled on both the VIC and switch side, the Ethernet and Fibre Channel data paths did not work if port channel configurations were not modified from Cisco IMC, or VIC is reset to factory default configurations. This issue is now resolved. |
4.0(4g) |
4.0(4i) |
Defect ID |
Symptom |
First Affected Release |
Resolved in Release |
||
---|---|---|---|---|---|
CSCvr40547 |
In Cisco UCS C-Series M5 servers, Cisco IMC failed to detect Intel®Youngsville drives. Intel® Youngsville 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 was seen only when Cisco 12G Modular SAS HBA controller was connected with Intel drives and SAS drives. This was observed only in Cisco IMC Out of Band Interface, wherein the drives are shown as healthy in HII/Host interface of the storage controller.
This issue is now resolved. |
4.0(4e) |
4.0(4i) |
Release 4.0(4h)
The following caveat was resolved in Release 4.0(4h):
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:
|
4.0(4e) |
4.0(4h) |
Release 4.0(4f)
The following caveats were resolved in Release 4.0(4f):
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) |
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) |
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) |
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):
|
4.0(4b) |
4.0(4f) |
Release 4.0(4e)
The following caveats were resolved in Release 4.0(4e):
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) |
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) |
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) |
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(4d)
The following caveat was resolved in Release 4.0(4d):
Defect ID |
Symptom |
First Affected Release |
Resolved in Release |
---|---|---|---|
CSCvp74003 |
While downgrading from release 4.0(4d) to any earlier release, HUU and NI-HUU fail to discover DCPMM. This issue is now resolved. |
4.0(4b) |
4.0(4d) |
Release 4.0(4b)
The following caveat was resolved in Release 4.0(4b):
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) |
Defect ID |
Symptom |
First Affected Release |
Resolved in Release |
---|---|---|---|
CSCvn29592 |
Following drives:
|
4.0(2c) |
4.0(4b) |
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) |
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) |
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) |
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(2q)
The following defect was resolved in release 4.0(2q):
Defect ID |
Symptom |
First Release Affected |
Resolved in Release |
---|---|---|---|
CSCvw95072 |
NMPowerManager.c triggers an unexpected power off event during OS run time in Cisco UCS M5 servers. As a result, Cisco IMC shuts down the server and triggers power characterization. This issue is now resolved. |
4.1(2b) |
4.0(2q) |
Release 4.0(2o)
The following defect was resolved in release 4.0(2o):
Defect ID |
Symptom |
First Release Affected |
Resolved in Release |
---|---|---|---|
CSCvv64567 |
UCS Manager fails to discover Cisco UCS S3260 M4 servers due to UCS Manager and BMC version mismatch. This issue is now resolved. |
4.0(2o) |
4.0(2o) |
Release 4.0(2n)
The following defect was resolved in release 4.0(2n):
Defect ID |
Symptom |
First Release Affected |
Resolved in Release |
---|---|---|---|
CSCvu93105 |
For Cisco UCS C125 M5 servers, modifying Memory Interleaving BIOS token from Cisco IMC or BIOS setup window does not trigger the feature functionality even though the BIOS token value is updated correctly. This issue is now resolved. |
4.0(2m) |
4.0(2n) |
Defect ID |
Symptom |
First Release Affected |
Resolved in Release |
---|---|---|---|
CSCvr70687 |
New Cisco UCS C240 M5 server discovery fails or does not respond with the following error message: CimcVMedia Error: Error retrieving vmedia attributes list-MC Error(-6)The same issue may occur for any Cisco UCS C240 M5 server after an FI reboot or upgrade. This issue is now resolved. |
4.0(4d) |
4.0(2n) |
Defect ID |
Symptom |
First Release Affected |
Resolved in Release |
---|---|---|---|
CSCvs48461 |
While upgrading Cisco IMC to 4.0(2m) or 4.0(4i) in Cisco UCS S3260 M5 and M4 servers, HUU and NIHUU report HDD firmware updates as failed, even after the actual update is successful. This issue is now resolved. |
4.0(2m) |
4.0(2n) |
Defect ID |
Symptom |
First Release Affected |
Resolved in Release |
---|---|---|---|
CSCvm59040 |
Cisco UCS C220 servers with an up-time of over 180 days and equipped with Cisco UCS VIC 1225 may report loss of connectivity from the host. This issue is now resolved with the latest firmware version. |
2.0(13f) |
4.0(2n) |
Release 4.0(2m)
The following defect was resolved in release 4.0(2m):
Defect ID |
Symptom |
First Release Affected |
Resolved in Release |
---|---|---|---|
CSCvr91935 |
On Cisco UCS S3260 M4 and M5 servers, the firmware activation of Cisco UCS VIC 1455 and 1495 cards failed after NI-HUU/HUU update. This issue is now resolved. |
4.0(2k) |
4.0(2m) |
CSCvo18736 |
Intel X710 NIC firmware upgrade bundled with HUU version 4.0(2d) or later fails, causing disruption in network connectivity. This issue is now resolved. |
4.0(2d) and later |
4.0(2m) |
CSCvr88803 |
NI-HUU script fails with vmedia mapping has gone bad error. The script may fail on a verify boot when the option: "update_verify = yes" is set in the configuration file. This issue is now resolved. |
4.0(2k) |
4.0(2m) |
CSCvr71907 |
On S3260 M4 servers, NI-HUU firmware upgrade or downgrade may fail with the timeout error. When this happens firmware of only some components are updated and firmware of some components have to be updated again. This issue is now resolved. |
4.0(2k) |
4.0(2m) |
Release 4.0(2l)
There are no resolved caveats in release 4.0(2l).
Release 4.0(2k)
The following defect was resolved in release 4.0(2k):
Defect ID |
Symptom |
First Affected Release |
Resolved in Release |
---|---|---|---|
CSCvr61928 |
While updating the firmware on M4 and M5 servers using NI-HUU, CMC activation fails. This happens when there is no change in BIOS firmware version and there is change in BMC and CMC firmware versions. |
4.0(1a) |
4.0(2k) |
Release 4.0(2i)
The following defects were resolved in release 4.0(2i):
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) |
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):
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):
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) |
Defect ID |
Symptom |
First Affected Release |
Resolved in Release |
---|---|---|---|
CSCvp34583 |
Firmware activation of VIC cards or UCSC-C3260-SIOC card fails for any release prior to 4.0(2c). This happens on all M4 and M5 servers that are in Cisco card mode. |
Any release before 4.0(2c) |
4.0(2g) |
Release 4.0(2f)
The following defects were resolved in release 4.0(2f):
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):
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):
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) |
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) |
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) |
Defect ID |
Symptom |
First Affected Release |
Resolved in Release |
---|---|---|---|
CSCvk76542 |
Activation of Cisco UCS VIC cards or UCSC-C3260-SIOC card fails after upgrading to release 4.0(2c) or later. This happens on all C-Series Servers, and S3260 M5 servers that have these cards. |
4.0(2c) |
4.0(2c) |
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(4l)
The following caveat was opened in Release 4.0(4l):
Defect ID |
Symptom |
Workaround |
First Affected Release |
---|---|---|---|
CSCvt23154 |
In Cisco UCS M5 servers, only CPU2 is listed in the invalid POR fault summary message, even though the fault occurs in both CPUs. |
There is no known workaround. |
4.0(4b) |
Defect ID |
Symptom |
Workaround |
First Affected Release |
---|---|---|---|
CSCvu37394 |
Cisco UCS C480 M5 servers equipped with AMD Firepro 7150X2 16 GB GPU and set to Legacy boot mode, display the following error while booting: System Software Event : Post sensor , System firmware error(Post error) , Unrecoverable video controller failure [0xFF09] was assertedThere is no functionality impact from this issue. |
Change to UEFI boot mode. |
3.1(2b) |
Defect ID |
Symptom |
Workaround |
First Affected Release |
---|---|---|---|
CSCvt86961 |
In Cisco UCS C240 M5 servers, SAS Expander firmware activation fails after an upgrade, or SAS Expander sometimes gets reset after the server is rebooted. |
Perform one of the following using Cisco UCS Manager:
|
4.0(4h) |
Release 4.0(4i)
The following caveat was opened in Release 4.0(4i):
Defect ID |
Symptom |
Workaround |
First Affected Release |
---|---|---|---|
CSCvs13053 |
Cisco UCS S3260 M5 server does not boot after upgrading to release 4.0(4i). The boot process is non responsive at the following stage: Loading Ptu driver This issue occurs due to NVRAM offset caused by the Intel Speed Step, NUMA, and Memory RAS mode BIOS tokens. |
Change the BIOS token value to default for the following:
|
4.0(4i) |
Defect ID |
Symptom |
Workaround |
First Affected Release |
---|---|---|---|
CSCvq77449 |
Restarting CMC2 on Cisco UCS S3260 M5 servers causes all virtual drives configured in both the dual RAID controller to go offline. All other physical drives, except the boot drives, display Foreign Configuration status. |
Reboot the server to auto-import the drive configurations displaying Foreign Configuration status. If auto-import during reboot fails, contact TAC to import the configuration. |
4.0(1a) |
Release 4.0(4f)
The following defect is open in release 4.0(4f):
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:
|
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.
|
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):
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) |
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:
Or
|
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:
This issue occurs only when the drive firmware version before the upgrade is SCV1CS05. Other drive firmware versions are not affected. |
If already impacted by this issue, do the following to recover:
|
4.0(4e) |
Release 4.0(4b)
The following defects are open in release 4.0(4b):
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) |
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) |
CSCvt31090 |
For Cisco UCS S3260 M5 servers, Cisco IMC GUI does not display the list of Local DIMM numbers, to create Namespace, after a DCPMM factory reset. As a result, Namespace creation fails. |
Create Namespace using Cisco IMC CLI or XML API. OR Perform the following steps:
|
4.0(4b) |
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) |
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. |
|
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):
|
Use HUU 4.0(2f) to update the drives. |
4.0(4b) |
CSCvo39645 |
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. |
When this issue occurs, perform a warm reboot. |
4.0(4b) |
Open Caveats in Release 4.0(2)
Release 4.0(2c)
The following defects are open in release 4.0(2c):
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) |
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:
|
4.0(2c) |
Open Caveats in Release 4.0(1)
Release 4.0(1a)
The following defect is open in Release 4.0(1a):
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) |
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:
Known Behaviors
The following section lists known behaviors.
Known Behaviors in Release 4.0(4)
Release 4.0(4m)
The following caveats are the known limitations in Release 4.0(4m):
Defect ID |
Symptom |
Workaround |
First Affected Release |
---|---|---|---|
CSCvr67677 |
Cisco UCS C220 M4 and C240 M4 servers with specific on-board NAND flash, which run Cisco IMC release 3.0(4d) or earlier, fail to upgrade to any new Cisco IMC release due to bad blocks on NAND flash. This issue does not impact server operation, only the ability to upgrade Cisco IMC. Following error is seen while upgrading HUU: ERROR: CIMC Update failed (Error Code 1902)Following FSM state of the server is seen in Cisco UCSM integrated servers: wait-foribmcfw_update-failed |
Cisco recommends that you contact TAC to check for the number of bad blocks in the NAND flash before attempting firmware upgrade. It is recommended to fix the condition before attempting the upgrade rather than fixing it after a failed Cisco IMC firmware upgrade. Debug plug-in is loaded to inspect the bad block and fix the condition if the system is determined to have too many bad blocks on the NAND flash. If you are already facing this issue, contact TAC to verify the bad blocks and recover them. Cisco UCSM deployments require access to an SCP, SFTP, FTP, or TFTP server that is reachable from the Fabric Interconnect. |
4.0(4b) |
Release 4.0(4i)
The following caveats are the known limitations in Release 4.0(4i):
Defect ID |
Symptom |
Workaround |
First Affected Release |
---|---|---|---|
CSCvo76406 |
Cisco IMC GUI does not support editing the applied namespaces for Cisco UCS C-Series M5 servers. However, the namespaces could be edited using Cisco IMC CLI or XML API, which caused loss of data and configurations. Editing the applied namespaces through Cisco IMC CLI or XML API is no longer supported. |
There is no known workaround. |
4.0(4a) |
CSCvo27998 |
In Cisco UCS S3260 servers, exporting the technical support data using TFTP protocol to a server with IPv6 IP address fails. |
|
4.0(4i) |
CSCvr96199 |
Importing DCPMM configuration is supported only on servers where 100% memory mode is enabled and security is disabled. Since Cisco UCS S3260 servers do not support 100% memory mode, importing DCPMM configuration is also not supported. |
There is no known workaround. |
4.0(4i) |
Release 4.0(4e)
The following caveats are the known limitations in Release 4.0(4e):
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) |
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):
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) |
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) |
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:
Known Behaviors in Release 4.0(2)
Release 4.0(2n)
The following caveats are known limitations in Release 4.0(2n):
Defect ID |
Symptom |
Workaround |
First Affected Release |
---|---|---|---|
CSCvu62006 |
SLES15.2 and Ubuntu 20.04 OS successfully install on Cisco UCS C-Series and S-Series M4 servers with UEFI boot entry. However, booting to UEFI default boot entry deactivates after a reboot. |
Perform the following steps:
|
4.0(2m) |
Release 4.0(2m)
The following caveats are known limitations in Release 4.0(2m):
Defect ID |
Symptom |
Workaround |
First Affected Release |
---|---|---|---|
CSCvm36382 |
Storage Controller on Cisco UCS S3260 M4 servers display Invalid hardware configuration error, after swapping the position from motherboard to IO Expander or from the IO Expander to the motherboard. |
Run HUU on the server node after controller swap to update Sub OEMID to correct values. |
4.0(2m) |
Release 4.0(2c)
The following caveats are known limitations in Release 4.0(2c):
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) |
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
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):
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) |
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. |
|
4.0(1a) |
Known Behaviors in the Previous Releases
Refer to the following release notes for Known Behaviors in the previous releases:
Related Documentation
Related Documentation
For configuration information for this release, refer to the following:
-
Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide
-
Cisco UCS C-Series Servers Integrated Management Controller GUI Configuration Guide
-
Cisco UCS Rack-Mount Servers Cisco IMC API Programmer's Guide
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:
-
For information about supported firmware versions and supported UCS Manager versions for the rack servers that are integrated with the UCS Manager for management, refer to Release Bundle Contents for Cisco UCS Software.