B UCS C-Series RN 4 0 4

Release Notes for Cisco UCS C-Series Software,
Release 4.0(4)
First Published: 2019-04-26
Last Modified: 2021-03-18
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.
Release Notes for Cisco UCS C-Series Software, Release 4.0(4)

1
Revision History
Revision History
Revision Date Description
L1 March 18, 2021 • Added New Software Features

in Release 4.0(4n) section.
• Updated the Resolved Caveats
section.
• Updated the HUU version to
4.0(4n).
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 • Updated the Resolved Caveats
section.
• Updated the Open Caveats
section
4.0(4m).
• New section - Deprecation
Notice

4.0

2
Revision History
J0 July 06, 2020 • Updated the Resolved Caveats

section.
section
4.0(4l).

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 • Updated the Resolved Caveats

section.
section
• Updated the Security Fixes
section.
4.0(4k).

4.0
A1 March 11, 2020 Updated Open Caveats section for

release 4.0(4b).

3
Revision History
H0 December 20, 2019 • Updated the Supported

Features section.
4.0(4j).

4.0
G0 December 09, 2019 • Updated the Supported

Features section.
section.
section
• Updated the Known Behavior
and Limitations section.
4.0(4i).

4.0
F0 September 27, 2019 Following changes were made:

• Updated the Supported
Features section.
section.
4.0(4h).

4.0

4
Revision History
E0 August 26, 2019 Following changes were made:

section.
section.
4.0(4f).

4.0
D0 August 01, 2019 Following changes were made:

Features section.
section.
section.
• Updated the Known Behaviors
section.
4.0(4e).

4.0

5
Supported Platforms and Release Compatibility Matrix
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.
4.0(4d).

4.0
B0 May 17, 2019 Following changes were made:

Features section.
section.
• Added the Security Fixes
section.
4.0(4c).

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

6
Cisco IMC and Cisco UCS Manager Release Compatibility Matrix
• UCS S3260 M5
For information about these servers, see Overview of Servers

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:
Table 1: Cisco IMC and UCS Manager Software Releases for Rack Mount Servers for Cisco IMC 4.0(4) Release
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,

4.0(4l) 4.0(4i) Cisco UCS C220 M5, C240 M5,

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,

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,

4.0(4b) 4.0(4a) Cisco UCS C220 M5, C240 M5,

C480 M5, S3260 M5 and C480 ML
M5 servers

7
4.0(3b) 4.0(3a) Cisco UCS C220 M5 and C240 M5

servers
4.0(2q) 4.0(4l) Cisco UCS C220 M4, C240 M4,

4.0(2p) No support. Cisco UCS C125 M5 servers
4.0(2o) 4.0(4j) Cisco UCS C220 M4, C240 M4,

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

8
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
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
3.1(3k) 3.2(3p) Cisco UCS C480 M5, C220 M5,

3.1(3j) No Support Cisco UCS C480 M5, C220 M5,

Note We support discovery
and upgrade or
downgrade functions
with Cisco UCS
Manager.
3.1(3i) 3.2(3i) Cisco UCS C480 M5, C220 M5,

3.1(3h) 3.2(3h) Cisco UCS C480 M5, C220 M5,

3.1(3g) 3.2(3g) Cisco UCS C480 M5, C220 M5,

3.1(3d) 3.2(3e) Cisco UCS C480 M5, C220 M5,


9
3.1(3c) 3.2(3d) Cisco UCS C480 M5, C220 M5,

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,

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

10
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

11
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
3.0(2b) No Support C220 M4/C240 M4 only

and upgrade or
downgrade functions
with Cisco UCS
Manager.
3.0(1d) No Support All M3/M4 except C420 M3

and upgrade or
downgrade functions
with Cisco UCS
Manager.
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

12
Operating System and Browser Requirements
Cisco IMC Release UCS Manager Release Rack Mount Servers
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

13
Hardware and Software Interoperability
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.
Table 12: Upgrade Paths to Release 4.0
Upgrade From Release Upgrade To Release Recommended Upgrade Path
All M5 Servers from 3.1 4.0 Follow below upgrade path:

• You can use Interactive HUU or
Non-Interactive HUU (NIHUU) script to
update the server.
• While updating the firmware using the
NIHUU tool, use the Python scripts that are
released with version 4.0.
• 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.

14
For all M4 servers for 4.0 Follow these steps to upgrade from releases greater
releases greater than 3.0(3a) than 3.0(3a) to 4.0:
• You can use Interactive HUU or NIHUU
script to update the server.
running).
• If you wish to secure Cimc Boot, set flag
use_cimc_secure as yes in
multiserver_config file present with python
script.

15
For all M4 servers for 4.0 Follow these steps to upgrade from releases less
release lesser than 3.0(3a) than 3.0(3a) to 4.0:
except C460 M4
Upgrade from version less than 3.0(3a) to 3.0(3a)
For C460 M4 servers for
release 2.0(4c) to 3.0(3a)
Non-Interactive HUU (NIHUU) tool, use the
Python scripts that are released with version
3.0(3a).
running).
Upgrade from 3.0(3a) to 4.0

running).
script.

16
For C460 M4 servers for 4.0

release lesser than 2.0(4c)

17

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)
released with version 2.0(4c).
• Use OpenSSL 1.0.0-fips on the client side
running).
script.
Upgrade from 2.0(4c) to 3.0(3a)

released with version 3.0(3a).
running).
script.
Upgrade from 3.0(3a) to 4.0


18
Firmware Upgrade Details

running).
script.
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) ucs-c240m5-huu-4.0.4.iso Host Upgrade Utility
Server Firmware
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
Unified Computing System (UCS) ucs-cxxx-drivers.4.0.4.iso Drivers

Drivers
Unified Computing System (UCS) ucs-cxxx-utils-efi.4.0.4.iso Utilities
Utilities
ucs-cxxx-utils-linux.4.0.4.iso
ucs-cxxx-utils-vmware.4.0.4.iso
ucs-cxxx-utils-windows.4.0.4.iso
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.

19
Host Upgrade Utility
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:
Cisco Host Upgrade Utility User Guide
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):

20
New Software Features in Release 4.0(4m)
• 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
• HUH721010AL52C0—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.

21
New Software Features in Release 4.0(4e)
Note This option cannot be enabled on an adapter that has:

• Port Channel mode (only for 14xx series cards) enabled
• VNTAG mode enabled
• LLDP enabled
• FIP mode enabled
• Cisco IMC Management Enabled value set to Yes
• multiple user created vNICs
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.

22
New Software Features in Release 4.0(4d)
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.

23
New Hardware Features in Release 4.0(4)
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

24
New Hardware in Release 4.0(4b)

• 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 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:
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

25
SNMP
• 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):

26
Security Fixes
Release Defect ID CVE ID Symptom
4.0(4k) CSCvs31877 • CVE-2019-0139

• CVE-2019-0140
• CVE-2019-0142
• CVE-2019-0143
• CVE-2019-0144
• CVE-2019-0145
• CVE-2019-0146
• CVE-2019-0147
• CVE-2019-0148
• CVE-2019-0149
• CVE-2019-0150

27
Security Fixes

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:
• CVE-2019-0139
affects controllers
running firmware
versions earlier than
7.0. Due to
insufficient access
control in the
firmware, this
vulnerability may
allow a privileged
user to potentially
enable an escalation
of privilege, denial
of service, or
information
disclosure through
local access.
• CVE-2019-0140
affects controllers
running firmware
7.0. Due to buffer
overflow in the
firmware, this
vulnerability may
allow an
unauthenticated user
to potentially enable
an escalation of
privilege through an
adjacent access.
• CVE-2019-0142
affects controllers
running firmware
1.33.0.0. Due to
insufficient access
control in the
ilp60x64.sys

28
Security Fixes

driver, this
vulnerability may
allow a privileged
user to potentially
enable escalation of
privilege through
local access.
• CVE-2019-0143
affects controllers
running firmware
7.0. Due to
unhandled
exceptions in
kernel-mode drivers,
this vulnerability
may allow an
authenticated user to
potentially enable a
denial of service
through local access.
• CVE-2019-0144
affects controllers
running firmware
7.0. Due to
unhandled
exceptions in
firmware, this
vulnerability may
allow an
denial of service

29
Security Fixes

• CVE-2019-0145
affects controllers
running firmware
2.8.43. Due to buffer
overflow in i40e
drivers, this
vulnerability may
allow an
potentially enable an
escalation of
privilege through
local access.
• CVE-2019-0146
affects controllers
running firmware
2.8.43. Due to
resource leak in
i40e drivers, this
vulnerability may
allow an
denial of service
• CVE-2019-0147
affects controllers
running firmware
7.0. Due to
insufficient input
validation in i40e
drivers, this
vulnerability may
allow an
denial of service

30
Security Fixes

• CVE-2019-0148
affects controllers
running firmware
7.0. Due to resource
leak in i40e drivers,
this vulnerability
may allow an
denial of service
• CVE-2019-0149
affects controllers
running firmware
2.8.43. Due to
insufficient input
validation in i40e
drivers, this
vulnerability may
allow an
denial of service
• CVE-2019-0150
affects controllers
running firmware
7.0. Due to
insufficient access
control in firmware,
this vulnerability
may allow a
privileged user to
denial of service

31
Security Fixes
4.0(4k) CSCvs81690 • CVE-2020-0548 Cisco UCS C-Series and

S-Series M5 servers that
• CVE-2020-0549 are based on Intel
®
processors are affected by

vulnerabilities identified
by the following Common
Vulnerability and
Exposures (CVE) IDs:
• CVE-2020-0548
affects when cleanup
®
errors in some Intel
processors may
allow an
potentially enable
information
disclosure through
local access.
• CVE-2020-0549
affects when cleanup
errors in some data
cache evictions for
®
some Intel
processors may
allow an
potentially enable
information
disclosure through
local access.
Security Fixes in Release 4.0(4i)

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

32
Security Fixes
4.0(4i) CSCvr54415 • CVE-2019-11135

• CVE-2019-0151
• CVE-2019-0152
• CVE-2019-11136
• CVE-2019-11137
• CVE-2019-11139
• CVE-2019-11109

33
Security Fixes

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:
• CVE-2019-11135 (TSX Asynchronous Abort
Advisory) condition affects certain 2nd
®
Generation Intel® Xeon Scalable Processors,
®
8th Generation Intel CoreTM Processor Family,
®
9th Generation Intel CoreTM Processor Family,
®
and 10th Generation Intel CoreTM Processor
Family that utilize speculative execution, and
may allow an authenticated user to potentially
enable information disclosure through a
side-channel with local access.
• CVE-2019-0151 (CPU Local Privilege
®
Escalation Advisory) affects certain Intel 4th
®
Generation Intel CoreTM Processors, 5th
®
®
Generation Intel Cores Processors, 7th
®
® ®
Generation Intel CoreTM Processors, Intel
Xeon® Processors E3 v2/v3/v4/v5/v6 Family,
® ®
Intel Xeon® Processors E5 v3/v4 Family, Intel
®
Xeon Processors E7 v3/v4 Family, Intel®
® ®
Xeon Scalable Processors 2nd Generation, Intel
® ®
Xeon Scalable Processors, Intel® Xeon
®
Processors D-1500/D-2100), Intel® Xeon
® ®
Processors E-2100/E3100, and, Intel Xeon
Processors W-2100/W-3100 when insufficient
®
memory protection in Intel TXT may allow a
privileged user to potentially enable escalation
of privilege through local access. This could
®
result in bypassing Intel TXT protections.
• CVE-2019-0152 (CPU Local Privilege
® ®
Escalation Advisory) affects certain Intel Xeon
® ®
Scalable Processors, Intel Xeon Processor
® ®
D-2100, D-3100, Intel Xeon Processor
W-2100, W-3100 when insufficient memory
protection may allow a privileged user to
potentially enable an escalation of privilege
through local access. This could result in
bypassing System Management Mode (SMM)
®
and Intel TXT protections.
• CVE-2019-11136 (BIOS 2019.2 IPU Advisory)
® ®
affects 2nd Generation Intel Xeon Scalable
®
Processors, Intel Xeon® Scalable Processors,
® ®
Intel Xeon Processors D Family when

34
Security Fixes

insufficient access control in the system firmware
may allow a privileged user to potentially enable
an escalation of privilege, denial of service, or
information disclosure through local access.
• CVE-2019-11137 (BIOS 2019.2 IPU Advisory)
® ®
affects 2nd Generation Intel Xeon Scalable
® ®
Processors, Intel Xeon Scalable Processors,
® ® ® ®
Intel Xeon Processor D Family, Intel Xeon
® ®
Processor E5 v4 Family, Intel Xeon Processor
® ®
E7 v4 Family, Intel Atom Processor C Series
when insufficient input validation in the system
firmware may allow a privileged user to
potentially enable an escalation of privilege,
denial of service, or information disclosure
• CVE-2019-11139 (Voltage Modulation
Technical Advisory) vulnerability in voltage
® ®
modulation of certain Intel Xeon Scalable
Processors may allow a privileged user to
potentially enable denial of service through local
access.
• CVE-2019-11109 Logic issue in subsystem in
®
Intel Server Platform Services before versions
SPS_E5_04.01.04.297.0,
SPS_SoC-X_04.00.04.101.0, and
SPS_SoC-A_04.00.04.193.0 may allow a
privileged user to potentially enable Denial of
Service through local.
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):

35
Resolved Caveats
Release Defect ID CVE Symptom
4.0(4c) CSCvp34806 • CVE-2018-12126 Cisco UCS M5 servers are based on Intel® Xeon®
Scalable processors that are vulnerable to variants
• CVE-2018-12127 of exploits that use Microarchitectural Data Sampling
• CVE-2018-12130 (MDS) to gain access to data being processed in the
CPU by other applications.
• CVE-2019-11091
• 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.

36
Resolved Caveats in Release 4.0(4)
Release 4.0(4n)
The following caveats were resolved in Release 4.0(4n):
Table 13: BMC
Defect ID Symptom First Affected Release Resolved in Release
CSCvw95072 NMPowerManager.c 4.1(2b) 4.0(4n)

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.
Table 14: Web Management
CSCvw26110 For Cisco S3260 servers, 4.0(4m) 4.0(4n)

HTML based KVM
launch using host name
and IP address fails on
certain web browsers.
This issue is now
resolved.
Release 4.0(4m)
The following caveats were resolved in Release 4.0(4m):
Table 15: External QLogic Controller
Defect ID Symptom First Release Affected Resolved in Release
CSCvv76975 In Cisco UCS C-Series 4.0(4j) 4.0(4m)

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.

37
Release 4.0(4l)
The following caveats were resolved in Release 4.0(4l):
Table 16: BIOS
CSCvt64871 In rare situations, Cisco 4.0(4e) 4.0(4l)

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:
• Intel Errata -
SKX108
• Intel Errata - CLX37
This issue is now

resolved.

38
CSCvu47239 Cisco UCS S3260 M5 4.0(4h) 4.0(4l)

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
memory
OR
Configuring
Platform Hardware
If 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.

39
CSCvu14656 On upgrade of BIOS to 4.0(4h) 4.0(4l)

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:
• C220M5.4.0.4p.0.02242
00755
• C240M5.4.0.4r.0.03052
00743
• S3X60M5.4.0.4o.0.02242
00755
• C220M5.4.1.1c.0.04042
02345
• C240M5.4.1.1c.0.04052
00025
• S3X60M5.4.1.1c.0.04052
00025
This issue is now

resolved.

40
CSCvu11155 After upgrading the BIOS 4.0(4k) 4.0(4l)

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:
• C220M5.4.0.4p.0.02242
00755
• C240M5.4.0.4r.0.03052
00743
• S3X60M5.4.0.4o.0.02242
00755
• C220M5.4.1.1c.0.04042
02345
• C240M5.4.1.1c.0.04052
00025
• S3X60M5.4.1.1c.0.04052
00025
This issue is now

resolved.

41
Table 17: BMC
CSCvs92008 Socket connection 4.0(4b) 4.0(4l) and 4.1(1f)

between Cisco IMC and
BMC reaches a max limit
and blocks further
connection with the
following error message:
Error: Maxed out
all client socket
connections to
remote manager in
BMC. Please retry
after a while
OR
Communication to
peer CMC remote
manager. Internal
Error. Please
retry
This issue is now

resolved.
CSCvp35008 SLES/RHEL OS 4.0(4b) 4.0(4l)

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.

42
Table 18: External Controllers
CSCvq53066 Upgrading host firmware 4.0(4d) 4.0(4l)

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:
• F78413 -
Update Failed
on Storage
Controller
• F0181 - Drive
state:
unconfigured
bad
• F0856 -
Activation
failed and
Activate
Status set to
failed
This issue is now

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

43
Table 19: BIOS
CSCvs51200 On Cisco UCS C-Series 4.0(4f) 4.0(4k)

M5 servers, UEFU boot
LUNs become
non-functional under the
following conditions:
• when OS is ESXi
release 6.0 update 3
or 6.5 update 1
• when IQN is defined
at the profile level
• at least one iSCSI
vNIC is configured
in boot with more
than one target
This issue is now

resolved.

44
CSCvr79388 In rare situations, Cisco 4.0(4e) 4.0(4k)

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:
• Intel Errata -
SKX108
• Intel Errata - CLX37
This issue is now

resolved.
Note This issue is
resolved in
release 4.0(4l)
for Cisco UCS
C480 M5 and
Cisco UCS
480 M5 ML
servers. For
more
information,
see
CSCvt64871
in the
Resolved
Caveats
section.

45
Table 20: BMC
CSCvq84999 Cisco IMC fails to apply 4.0(1c) 4.0(4k)

fan control policy on
Cisco UCS C-Series M5
servers equipped with
Cisco UCS 1387 adapter.
The following error
message is displayed:
The selected Fan
Control Profile could
not
be applied due to
unmanageable PCI card
presence!
Configured Policy: 10,
Derived Policy: 20!
Applied Policy:
Balanced,
Configuration Status:
FAN
POLICY OVERRIDE -
Card(s) "unknown card
PCI-Ids:
0x1137-0x0043-0x1137-0x015D"
present
This issue is now

resolved.
CSCvr70687 New Cisco UCS C240 M5 4.0(4d) 4.0(4k)

server discovery fails or
does not respond with the
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.

46
CSCvs86186 NIHUU fails to recognize 4.0(2h) 4.0(4k)

special characters in share
server password and the
following error message
is displayed:
Permission
denied.
This issue is now
resolved.
CSCvt07824 NIHUU fails to recognize 4.0(4g) 4.0(4k)

special characters in share
server password and the
following error message
is displayed:
Permission
denied.
This issue is now
resolved.
CSCvr95365 Discovery of a Cisco UCS 4.0(4i) 4.0(4k)

C240 M5 server, equipped
with Cisco 12G Modular
SAS HBA controller, fails
with one of the following
errors:
• mc_attrib_set_suboem_id
failed to set the
SubOEM ID
• Cisco IMC is not
able to detect any
drives.
This issue now resolved.

47
Table 22: Host Firmware Upgrade
CSCvs48461 While upgrading Cisco 4.0(2m) 4.0(4k)

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.
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):
Table 23: BMC
Defect ID Symptom First Affected Release Resolved in

Release
CSCvo76406 Cisco IMC GUI does not support 4.0(4a) 4.0(4i)

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.
CSCvr72565 Non-admin users could modify the 3.0(4n) 4.0(4i)

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.

48

Release
CSCvr43466 Cisco UCS C-Series rack servers 4.0(4b) 4.0(4i)

integrated with Cisco UCS Manager
displayed hardware inventory
mismatch.
CSCvo62515 Cisco IMC crashed or was 3.1(3h) 4.0(4i)

non-responsive due to kernel issues
with the following error
log:kernel BUG at
drivers/bmc/cisco_proc_lib
/cisco_proc_lib.c log
CSCvp90030 Cisco IMC used to crash with the 4.0(4c) 4.0(4i)

following kernel error log:
log_i2c_tx in the stack
trace of oops
CSCvr78701 A Cisco UCS Manager integrated 4.0(4c) 4.0(4i)

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).
CSCvr96140 In Cisco UCS M5 servers, when 4.0(2d) 4.0(4i)

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.

49
Table 24: Cisco VIC

Release
CSCvr68316 In Cisco C-Series servers, when a 4.0(4g) 4.0(4i)

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.

50
CSCvr40547 In Cisco UCS C-Series 4.0(4e) 4.0(4i)

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.
Note Sometimes it
use to take
around 15
minutes to
reflect the right
status of
controller and
drives from
Cisco IMC.
This issue is now

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

51
Table 26: Cisco VIC

Release
CSCvr04369 Under rare and specific conditions, 4.0(4e) 4.0(4h)

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
• 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.
Release 4.0(4f)
The following caveats were resolved in Release 4.0(4f):

52
Table 27: Server
CSCvq95077 S3260 M5 servers keep 4.0(4e) 4.0(4f)

rebooting and fail to
power on and do not
complete BIOS POST.
Table 28: BMC

Release
CSCvq26149 M5 server fans run at MAX speed after PECI 4.0(4c) 4.0(4f)
temperature read failure. The fan speed
continues to remain at MAX speed until you
perform a power cycle of the server.
®
CSCvq93258 The Product IDs (PID) of the new Intel 4.0(4d) 4.0(4f)
™
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.
CSCvq86332 PIDs of SED drives present in the system 4.0(4e) 4.0(4f)

are displayed as non-SED drives.

Release
CSCvq58364 Non-Interactive HUU (NIHUU) drive 4.0(4d) 4.0(4f)

updates fail with a timeout error. This
happens while upgrading the HDD firmware
of one or more drives using the NIHUU.

53
CSCvq81930 Firmware update of the 4.0(4b) 4.0(4f)

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
Release 4.0(4e)
The following caveats were resolved in Release 4.0(4e):
Table 31: BIOS

Release
CSCvp39108 On the Cisco UCS M5 servers with Intel 4.0(4b) 4.0(4e)

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.

54
Table 32: BMC

Release
CSCvo55902 Network link activity LED does not display 4.0(4b) 4.0(4e)
the correct LOM port and LED status.

Release
CSCvp43280 When two or more Intel PCI Adapters are 4.0(2c) 4.0(4e)
populated in the UCS C-Series and S-Series
M5 servers, upgrading the firmware using
HUU may fail for the PCI cards.
CSCvo93353 The StorCLI command storcli /cX show all 4.0(2f) 4.0(4e)
does not display the World Wide Number
(WWN) of the drives. This happens when
you use StorCLI version 7.0813 or earlier.
CSCvp08512 The MegaRAID controller firmware does 4.0(4b) 4.0(4e)

not check Hot Spare physical drive size and
allows you to create and assign a Dedicated
Hot Spare of small size.
® ™
Table 34: Intel Optane Data Center Persistent Memory Modules - Intel Resolved Caveats

Release
® ™
CSCvo78920 When a system with Intel Optane 4.0(4b) 4.0(4e)
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.

55

Release
® ™
CSCvp38545 Intel Optane Data Center 4.0(4b) 4.0(4e)
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.
® ™
CSCvp38555 Intel Optane Data Center 4.0(4b) 4.0(4e)
persistent memory modules go into
a "Non-Functional" health state
when it is first powered up.
Release 4.0(4d)
The following caveat was resolved in Release 4.0(4d):
Table 35: HUU
CSCvp74003 While downgrading from 4.0(4b) 4.0(4d)

release 4.0(4d) to any
earlier release, HUU and
NI-HUU fail to discover
DCPMM.
This issue is now
resolved.
Release 4.0(4b)
The following caveat was resolved in Release 4.0(4b):

56
Table 36: BMC

Release
CSCvo97900 On the C480 M5 servers that do not have 4.0(2c) 4.0(4b)

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.
CSCvo18799 While updating the firmware using Cisco 3.0(3e) 4.0(4b)

IMC, Power Sequencer (PWR_SEQ) update
fails with the following message:
Firmware update failed, AC
Cycle system and retry. PWRSEQ
CSCvo15978 On servers with M393A4K40BB2-CTD 4.0(1a) 4.0(4b)

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.
CSCvo02861 Syslog Minimum Severity to report severity 3.1(3a) 4.0(4b)

is not functional.
CSCvo85413 Unable to launch KVM console using Cisco 4.0(2c) 4.0(4b)

IMC on the S3260 servers running on
firmware version 4.0(2c).

57
Table 37: BMC Storage

Release
CSCvn29592 Following drives: 4.0(2c) 4.0(4b)

• 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.
Table 38: BIOS

Release
CSCvn77825 On servers with Windows Hyper-V 2019 4.0(1c) 4.0(4b)

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.
Table 39: CMC

Release
CSCvo25387 On S3260 servers running on 4.0(1b) 4.0(1b) 4.0(4b)

version, chassis may enter a SAFE state and
have the fans spin at 100% RPM due to
missing MEZZ temperature sensor readings.

58
Table 40: CMC Storage

Release
CSCvo03830 SAS Expander link address is set to 0 on 4.0(1a) 4.0(4b)

HGST drives after the expander is
disconnected.

Release
CSCvn34219 UCSC-RAID-M5HD controller fails to boot 4.0(2c) 4.0(4b)

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.
CSCvm94424 After upgrading the S3260 servers to 4.0(1a), 4.0(1a) 4.0(4b)

F1256 equipment-missing informational fault
is logged for empty drive slots .
Release 4.0(2q)
The following defect was resolved in release 4.0(2q):
Table 42: BMC
CSCvw95072 NMPowerManager.c 4.1(2b) 4.0(2q)

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.

59
Release 4.0(2o)
The following defect was resolved in release 4.0(2o):
Table 43: BMC
CSCvv64567 UCS Manager fails to 4.0(2o) 4.0(2o)

discover Cisco UCS
S3260 M4 servers due to
UCS Manager and BMC
version mismatch.
This issue is now
resolved.
Release 4.0(2n)
The following defect was resolved in release 4.0(2n):
Table 44: BIOS
CSCvu93105 For Cisco UCS C125 M5 4.0(2m) 4.0(2n)

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.

60
Table 45: BMC
CSCvr70687 New Cisco UCS C240 M5 4.0(4d) 4.0(2n)

server discovery fails or
does not respond with the
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.
CSCvs48461 While upgrading Cisco 4.0(2m) 4.0(2n)

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.
Table 47: VIC
CSCvm59040 Cisco UCS C220 servers 2.0(13f) 4.0(2n)

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.

61
Release 4.0(2m)
The following defect was resolved in release 4.0(2m):
Table 48: Firmware Upgrade
CSCvr91935 On Cisco UCS S3260 M4 4.0(2k) 4.0(2m)

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.
CSCvo18736 Intel X710 NIC firmware 4.0(2d) and later 4.0(2m)

upgrade bundled with
HUU version 4.0(2d) or
later fails, causing
disruption in network
connectivity.
This issue is now
resolved.
CSCvr88803 NI-HUU script fails with 4.0(2k) 4.0(2m)

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.

62
CSCvr71907 On S3260 M4 servers, 4.0(2k) 4.0(2m)

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.
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):
Table 49: Utilities

Release
CSCvr61928 While updating the firmware on M4 and M5 4.0(1a) 4.0(2k)

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.
Release 4.0(2i)
The following defects were resolved in release 4.0(2i):
Table 50: BIOS

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

63
Table 51: Utilities

Release
CSCvr07491 After upgrading the firmware of multiple 4.0(1a) 4.0(2i)

S3260 servers using the Non-Interactive
HUU, firmware activation fails for a few
server components such as BMC, BIOS,
CMC and SAS Expander.
Release 4.0(2h)
The following defect was resolved in release 4.0(2h):
Table 52: BIOS

Release
CSCvo48006 On the M4 servers, uncorrectable ECC error 4.0(2c) 4.0(2h)

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.
Release 4.0(2g)
The following defects were resolved in release 4.0(2g):
Table 53: BMC

Release
CSCvo15978 On servers with M393A4K40BB2-CTD 4.0(1a) 4.0(2g)

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.

64

Release
CSCvp41543 SSH clients fail to establish a connection to 3.0(4j) 4.0(2g)

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.
CSCvp34583 Firmware activation of Any release before 4.0(2c) 4.0(2g)

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.
Release 4.0(2f)
The following defects were resolved in release 4.0(2f):
Table 55: BMC

Release
CSCvn81570 Modifying the LUN ID for Flex Flash SD 4.0(1c) 4.0(2f)

card VD fails with the following error:
error in configuring device
CSCvn80088 Unable to initiate non-interactive HUU 4.0(1a) 4.0(2f)

update when the remote share password
provided in the NI HUU contains any of the
following special characters ; | ? $ ! @ # %
^*-_+
Release 4.0(2d)
The following defects were resolved in release 4.0(2d):

65
Table 56: Utilities

Release
CSCvn92435 Host Update Utility not booting on the 4.0(2c) 4.0(2d)

following platform: BE7M-M5-K9. HUU
fails with the following error message:
“Host Update Utility is unable
to detect Cisco IMC firmware”
Release 4.0(2c)
The following defects were resolved in release 4.0(2c):
Table 57: BMC

Release
CSCvm12144 PSU input voltage lost assert issue seen 3.1(3b) 4.0(2c)
though there is no physical power loss.
CSCvm27310 C-Series servers with NVIDIA P40 Card 3.1(1d) 4.0(2c)

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.
CSCvn04038 RAID cannot be set up between the two SD 3.1(1d) 4.0(2c)

cards, resulting in the following error:
Controller State: Disconnected
Partition From Host
Table 58: CMC Storage

Release
CSCvj95793 The "show fault-entries" list does not display 4.0(1a) 4.0(2c)
the faults reported from the subordinate
CMC when logged in using the management
IP. It only reports the primary CMC faults.

66
Open Caveats

Release
CSCvj74706 On the M4 servers, physical drives managed 3.(3a) 4.0(2c)

by UCSC-SAS12GHBA displays the
physical drive state as Unconfigured Good
instead of JBOD.
CSCvm83587 On the C220 and 240 M5 servers with 3.1(3a) 4.0(2c)

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.
CSCvk76542 Activation of Cisco UCS 4.0(2c) 4.0(2c)

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.
Table 61: Utilities

Release
CSCvi65660 Cisco VIC adapter firmware may not 4.0(1a) 4.0(2c)

automatically activate when you upgrade the
firmware of the server components using the
HUU. This happens when single server dual
SIOC is enabled.
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):

67
Table 62: BMC
Defect ID Symptom Workaround First Affected Release
CSCvt23154 In Cisco UCS M5 servers, There is no known 4.0(4b)

only CPU2 is listed in the workaround.
invalid POR fault
summary message, even
though the fault occurs in
both CPUs.
Table 63: BIOS
CSCvu37394 Cisco UCS C480 M5 Change to UEFI boot 3.1(2b)

servers equipped with mode.
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 asserted
There is no functionality
impact from this issue.
CSCvt86961 In Cisco UCS C240 M5 Perform one of the 4.0(4h)

servers, SAS Expander following using Cisco
firmware activation fails UCS Manager:
after an upgrade, or SAS
1. Re-acknowledge the
Expander sometimes gets
server.
reset after the server is
rebooted. 2. Change any property
in service profile and
trigger association.

68
Release 4.0(4i)
The following caveat was opened in Release 4.0(4i):
Table 65: BIOS
CSCvs13053 Cisco UCS S3260 M5 Change the BIOS token 4.0(4i)

server does not boot after value to default for the
upgrading to release following:
4.0(4i). The boot process
• Intel Speed Step
is non responsive at the
following stage: • NUMA
Loading Ptu • Memory RAS
driver
This issue occurs due to
NVRAM offset caused by
the Intel Speed Step,
NUMA, and Memory
RAS mode BIOS tokens.
Table 66: Expander
CSCvq77449 Restarting CMC2 on Reboot the server to 4.0(1a)

Cisco UCS S3260 M5 auto-import the drive
servers causes all virtual configurations displaying
drives configured in both Foreign Configuration
the dual RAID controller status.
to go offline. All other
If auto-import during
physical drives, except the
reboot fails, contact TAC
boot drives, display
to import the
Foreign Configuration
configuration.
status.
Release 4.0(4f)
The following defect is open in release 4.0(4f):

69
Defect ID Symptom Workaround First

Affected
Release
CSCvq50290 Cisco IMC fails to recognize SATA disk If this issue occurs, do the 4.0(4b)
UCS-SD960G63X-EP. This happens following:
when you upgrade to 4.0(4) version from
1. Boot to 4.0.(2d) HUU
4.0(2c) or below versions.
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.
CSCvr03037 Intel drives and few of the other SATA Perform Cisco IMC reboot. 4.0(4e)
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.
CSCvr03044 While upgrading Cisco IMC from Update the failed drives or all the 4.0(4e)
4.0(2c) to 4.0(4f), SAS drive firmware drives again for a successful
update may fail when the drives are update.
connected to Cisco 12G Modular SAS
HBA controller.

70

Affected
Release
CSCvr03041 Slot numbers of the connected drives are There is no functional impact as the 4.0(4c)
displayed as NA in Host Update Utility drives are updated successfully.
even after updates are completed
successfully.
This issue is seen only in Software RAID
configurations.
Release 4.0(4e)
The following defects are open in release 4.0(4e):
Table 68: Server
CSCvq95077 S3260 M5 servers keep Power cycle the server to 4.0(4e)

rebooting and fail to recover the setup.
power on and does not
complete BIOS POST.

71

Affected
Release
CSCvq74492 System becomes unresponsive during If this issue occurs, do one of the 4.0(4e)
BIOS post when the Intel X520 PCIe following:
adapter is present on the system and
• Switch to UEFI boot mode.
iSCSI mode is enabled for Intel X550
LOMs. This happens only when boot
Or
mode is set to legacy.
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.

72

Affected
Release
CSCvq26156 Upgrade of UCS C-Series Server 1. Before upgrading to 4.0(4a) 4.0(4e)

firmware to 4.0(4a) or later releases release, upgrade only the
causes Cisco 12G Modular SAS HBA to firmware of the drives to
stop discovering the following drive SCV1CS07, which is part of
models: Release 4.0(4a) or later release
packages.
• SSDSC2KB480G7K - 480GB
2.5-inch Enterprise Value 6G 2. Now proceed with full upgrade
SATA SSD of 4.0(4a) or later release
package.
• SDSC2KB960G7K - 960GB
2.5-inch Enterprise Value 6G
If already impacted by this issue,
SATA SSD
do the following to recover:
• SSDSC2KG019T7K - 1.9TB 1. Downgrade Cisco 12G
2.5-inch Enterprise performance 6G Modular SAS HBA to a
SATA SSD previous working version
• SSDSC2KG480G7K - 480GB (00.00.00.50 or 00.00.00.58
2.5-inch Enterprise performance available in 4.0(1) and 4.0(2)
6GSATA SSD release packages respectively).
• SSDSC2KG960G7K - 960GB 2. Upgrade the firmware of the

2.5-inch Enterprise performance 6G impacted drives to SCV1CS07,
SATA SSD which is part of Release 4.0(4a)
or later release packages.
• SSDSC2KB038T7K - 3.8TB
2.5-inch Enterprise Value 6G 3. After drive firmware is
SATA SSD updated, proceed with upgrade
of Cisco 12G Modular SAS
This issue occurs only when the drive HBA firmware to 09.00.00.06,
firmware version before the upgrade is which is part of Release 4.0(4a)
SCV1CS05. Other drive firmware or later release packages.
versions are not affected.
Release 4.0(4b)
The following defects are open in release 4.0(4b):

73
® ™
Table 70: Intel Optane Data Center Persistent Memory Modules - Intel Open Caveats
Defect ID Symptom Workaround First Bundle

Affected
CSCvn77341 Namespaces created under Red Hat No known workaround. The 4.0(4b)
Enterprise Linux 7.6 by using the namespaces are healthy, and their
in-box ndctl tool, may be seen in functionality is not affected.
"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.
® ™
CSCvn81521 On systems with Intel Optane Examine the MCAOut files to 4.0(4b)
Data Center persistent memory identify the actual failed DIMM
modules in 2LM (memory mode), location.
uncorrectable errors get logged on
the persistent memory modules
when errors occur on DDR4
DIMMs (configured as near
memory) on the same channel.
® ™
CSCvp08356, When Intel Optane Data Center Clear errors by using Reset all 4.0(4b)
CSCvo72182 persistent memory modules are Memory errors in Cisco UCS
populated in the system, and the Manager.
system is operational, occasionally
false uncorrectable errors are
reported on DIMM A1. This has no
functional impact.
®
CSCvp38564 Intel Intelligent Power Technology If persistent memory modules are 4.0(4b)
Node Manager (NM) PTU does not detected in a system, the BIOS will
® ™
work with Intel Optane DC not load NMPTU to prevent
persistent memory modules in App unresponsiveness or an infinite
Direct mode. Hence, the power loop.
characterization accuracy is
reduced.

74
Defect ID Symptom Workaround First Bundle

Affected
CSCvp37389 In some specific situations, in-flight No known workaround. 4.0(4b)

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.
® ™
Table 71: Intel Optane Data Center Persistent Memory Modules - Cisco Open Caveats
Defect ID Symptom Workaround First Affected

Release
CSCvo17390 On the S3260 M5 servers with None. 4.0(4b)

® ™
persistent memory module, fault
engine displays a warning message
that indicates RDIMM size from
SPD is 0.
CSCvp03376 Fault engine displays "mismatch None. 4.0(4b)

FW revision" warning for
persistent memory DIMMs though
the firmware version is the same on
the DIMMs.
® ™
CSCvn93216 On systems with Intel Optane None. 4.0(4b)
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.
CSCvp11872 Duplicate faults are reported for None. 4.0(4b)

® ™
persistent memory module. Existing
persistent memory module faults
are reported again (duplicates) after
every host reboot.
CSCvp13906 Memory is not accessible when None. 4.0(4b)

® ™
persistent memory module is
configured as volatile memory with
NUMA in disabled state.

75

Release
®
CSCvo99814 When security is disabled on Intel None. 4.0(4b)
™
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.
® ™
CSCvp15031 Intel Optane Data Center None. 4.0(4b)
persistent memory module health
state changes to Non-functional
after upgrading its firmware from
2019_WW10 to 2019_WW12BKC.
® ™
CSCvo20670 Intel Optane Data Center None 4.0(4b)
persistent memory module displays
a Fatal Failure message after
performing goal configuration
changes.
®
CSCvo80193 Media errors reported for Intel None. 4.0(4b)
™
memory module while performing
configuration changes. These errors
are seen on both EFI and OS.
® ™
CSCvo85065 For Intel Optane Data Center You can view the errors in the 4.0(4b)
persistent memory module Failure BMC fault logs and Windows or
Conditions, no SEL event is logged Linux SEL through ACPI.
to indicate failure.

76

Release
CSCvt31090 For Cisco UCS S3260 M5 servers, Create Namespace using Cisco 4.0(4b)
Cisco IMC GUI does not display IMC CLI or XML API.
the list of Local DIMM numbers,
OR
to create Namespace, after a
DCPMM factory reset. As a result, Perform the following steps:
Namespace creation fails.
1. Create a new Namespace using
Name, Socket ID, Capacity
and Mode fields.
2. Save the settings but do not
reboot the host to apply the
settings.
3. From Create Memory Usage,
delete the pending Namespace
entry, which was created
without the DIMM number in
Step 2.
4. Now you can create a new
Namespace with local DIMM
number and other fields.
5. Save the settings and reboot
the host to apply the settings.
Table 72: BIOS

Affected
Release
CSCvo46953 Unable to initiate iPXE boot from LOM port Use LOM port 2. 4.0(4b)
1.
CSCvp21118 Precision boot order (L2 boot order) feature You can use BIOS F6 to boot 4.0(4b)
of Cisco UCS C480 M5 servers may not list from the required device.
the external physical USB drives in the boot
order.
CSCvp43349 After upgrading the BIOS firmware to You can add the iSCSI attempt 4.0(4b)
4.0(4b), Cisco UCS M5 servers may lose the from the BIOS setup for third
previously configured (before the upgrade) party Adapters and using the
iSCSI attempts. Cisco IMC GUI for VIC cards.
CSCvp36893 When you run the PTU TDP test on the None. 4.0(4b)
Cisco UCS M5 servers with some CPU
SKUs, CPU domain max power limit reaches
only half the actual CPU TDP.

77

Affected
Release
CSCvp11474 While updating firmware on multiple drives Manually update the firmware 4.0(4b)
using HUU, an error indicating that the drive of the drive reported by HUU
update for a particular drive has "Failed" is or ignore the error and continue
displayed even though the firmware is with the reboot step as
updated. firmware is already updated.
CSCvo3964, CATERR/IERR occurs on multiple reboots Perform warm reboot. 4.0(4b)

and the system becomes unresponsive during
CSCvo89921
POST. This issue occurs on servers with
NVMe drives on mSwitch connected
configuration.
CSCvm15304 On the C480 M5 servers with two Intel None. 4.0(4b)

ColdStream drives on PCI Switch1 and PCI
Switch Rear, Intel ColdStream Next 750GB
drive link goes to degraded state after a few
reboots.
CSCvp30283 On servers with QL45412H card, iSCSI 1. Enter the F2 BIOS setup 4.0(4b)
configuration restores to default settings after menu and access the
updating the adapter firmware. This happens Advanced tab of iSCSI
when you configure iSCSI using the Qlogic configuration.
HII configuration utility from the BIOS
menu. 2. Enter the iSCSI Initiator
Name and Target Name.
3. Save and Exit.
CSCvq81930 Firmware update of the following Intel drives Use HUU 4.0(2f) to update the 4.0(4b)
fail while upgrading from 4.0(2c) to 4.0(4b) drives.
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

78

Affected
Release
CSCvo39645 CATERR/IERR occurs on multiple reboots When this issue occurs, 4.0(4b)
and the system becomes unresponsive during perform a warm reboot.
POST. This issue occurs on servers with
NVMe drives on mSwitch connected
configuration.
Release 4.0(2c)
The following defects are open in release 4.0(2c):
Table 74: BIOS

Affected
Release
CSCvn09309 While trying to boot to PXE by pressing the Press the F6 or F2 key and 4.0(2c)
F12 key during POST, F12 network boot select Cisco FastlinQ
will not work for Cisco FastlinQ QL45611HLCU 100GBE
QL45611HLCU 100GBE adapter. adapter for PXE boot.

Affected
Release
CSCvm78123 ISCSI Boot protocol for Intel® None 4.0(2c)

XXV710-DA2 and X710-T4 cards is not
displayed in the Boot Utility (bootutil) for
the servers with firmware version 4.0(1a).
CSCvm78419 ISCSI lun may not be able establish TCP/IP Use the following command on 4.0(2c)
connection with the Cisco Etherent switch:
Converged NIC X710-DA2, Intel X710-DA4 conf t
, and Intel XL710QDA2 PCIe cards after the no lldp tlv-select
firmware is updated to version 4.0(1a ). dcbxp
Release 4.0(1a)
The following defect is open in Release 4.0(1a):

79
Known Behaviors
Table 76: BIOS

Affected
Release
CSCvk58997 On the M4 servers, booting IPv6 based UEFI Use IPv4 UEFI PXE. 4.0(1a)
PXE using Windows WDS application fails
with a server time out error. This happens
with all M4 servers in UEFI mode.
CSCvo77732 After upgrading the C460 M4 servers with Downgrade to 3.0(x) version. 4.0(1a)
Intel® Xeon® Processor v2 to 4.0(1a)
version, server encounters a CATERR fault
and the server becomes unresponsive.
Table 77: VIC

Affected
Release
CSCvq64055 Cisco VIC1455 and VIC 1457 interfaces take Use shorter copper passive 4.0(1a)
more than four minutes to recover to cables (SFP-25G-CU1M.
Link-Up state after the far end Switch SFP-25G-CU2M,
configuration is changed to no shut. This SFP-25G-CU3M).
happens when a 25G 5M copper passive
Or
cable (SFP-H25G-CU5M) cable is
connecting the VIC1455 or VIC 1457 and Use optical cables.
the N9K-C93180YC-EX switch.
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(4m)
The following caveats are the known limitations in Release 4.0(4m):

80
Table 78: BMC
CSCvr67677 Cisco UCS C220 M4 and Cisco recommends that 4.0(4b)

C240 M4 servers with you contact TAC to check
specific on-board NAND for the number of bad
flash, which run Cisco blocks in the NAND flash
IMC release 3.0(4d) or before attempting
earlier, fail to upgrade to firmware upgrade. It is
any new Cisco IMC recommended to fix the
release due to bad blocks condition before
on NAND flash. attempting the upgrade
rather than fixing it after
This issue does not impact
a failed Cisco IMC
server operation, only the
firmware upgrade.
ability to upgrade Cisco
IMC. Debug plug-in is loaded
to inspect the bad block
Following error is seen
and fix the condition if the
while upgrading HUU:
system is determined to
ERROR: CIMC have too many bad blocks
Update failed on the NAND flash.
(Error Code 1902)
If you are already facing
Following FSM state of this issue, contact TAC to
the server is seen in Cisco verify the bad blocks and
UCSM integrated servers: recover them.
wait-foribmcfw_update-failed Cisco UCSM
deployments require
access to an SCP, SFTP,
FTP, or TFTP server that
is reachable from the
Fabric Interconnect.
Release 4.0(4i)
The following caveats are the known limitations in Release 4.0(4i):

81
Table 79: BMC

Affected
Release
CSCvo76406 Cisco IMC GUI does not There is no known workaround. 4.0(4a)
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.
CSCvo27998 In Cisco UCS S3260 servers, • Export the configurations one at a time. For 4.0(4i)
exporting the technical support example: CMC, BMC, VIC and so on.
data using TFTP protocol to a
server with IPv6 IP address • Update the firmware using other shares.
fails.
CSCvr96199 Importing DCPMM There is no known workaround. 4.0(4i)

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.
Release 4.0(4e)
The following caveats are the known limitations in Release 4.0(4e):

82
Table 80: BMC

Affected
Release
CSCvp65147 Despite user account being Enable the Disable user on Lockout feature using 4.0(4c)
locked due to multiple the CLI or XML API or WebUI interface. This
incorrect login attempts, user will disable the locked user and IPMI commands
can execute IPMI commands will not work for the user.
after successful user
authentication through IPMI
during the account lockout
period.

Affected
Release
CSCvq20893 All the supported SN200 series drives are None. 4.0(4e)
displayed as SN200 in device manager page
or Hardware info page of ESXi. Specific
version of the drive is not displayed.
CSCvq20302 HGST SN200 NVMe drives connected to None. 4.0(4e)

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.
Release 4.0(4b)
The following caveats are the known limitations in Release 4.0(4b):
® ™
Table 82: Intel Optane Data Center Persistent Memory Modules

Affected
Release
CSCvo21859 You cannot scope into CLI Do not create namespaces with empty name from 4.0(4b)
when a namespace is host tools.
configured with an empty
name using the host tools (F2).

83

Affected
Release
CSCvo59901 You cannot scope into CLI or Do not use special characters for namespace 4.0(4b)
delete a namespace using CLI names other than the following supported ones:
when you create a namespace #, - and _
(using the host tools (F2)) that
has special characters in the
name.
CSCvo21881 When a Goal is created in None. 4.0(4b)

mixed mode, the actual
capacity allocated for volatile
and persistent memories does
not match with the calculation
done using the % of memory
mode configured.
Table 83: BMC

Affected
Release
CSCvo13512 Power consumption does not None. 4.0(4b)

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

Affected
Release
CSCvn72355 Unable to create a virtual drive (VD) with None. 4.0(4b)

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).
Known Behaviors in the Previous Releases

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

84
Release 4.0(2n)
The following caveats are known limitations in Release 4.0(2n):
Table 85: BIOS
CSCvu62006 SLES15.2 and Ubuntu Perform the following 4.0(2m)

20.04 OS successfully steps:
install on Cisco UCS
1. Enter BIOS setup and
C-Series and S-Series M4
create an admin
servers with UEFI boot
password.
entry. However, booting
to UEFI default boot entry 2. Go to Advanced >
deactivates after a reboot. Trusted Computing
and select TCG_2 for
TPM 1.2 or 2.0 UEFI
version.
3. Press F10 to save and
exit.
Release 4.0(2m)
The following caveats are known limitations in Release 4.0(2m):
Table 86: BMC

Affected
Release
CSCvm36382 Storage Controller on Cisco UCS S3260 M4 Run HUU on the server node 4.0(2m)
servers display Invalid hardware after controller swap to update
configuration error, after swapping the Sub OEMID to correct values.
position from motherboard to IO Expander
or from the IO Expander to the motherboard.
Release 4.0(2c)
The following caveats are known limitations in Release 4.0(2c):

85
Table 87: BMC

Affected
Release
CSCvm08504 During a server firmware downgrade using None. 4.0(2c)

the HUU, LLF (1050W PSUs) update fails
when downgrading the firmware version
from 4.0(1) to any previous releases.
Table 88: External GPU Expander

Affected
Release
CSCvm92237 The nvidia-smi tool GPU slot To map lspci GPU slot nr/BusID to 4.0(2c)
mapping does not match with the nvidia-smi GPU slot nr/BusID, run the
lspci output and the C480-M5ML following command (see the example below):
Silkscreen slot numbering.
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)

86
Repeat same steps for the other GPUs
Table 89: External OS

Affected
Release
CSCvj48637 HDD activity and locate LEDs are not None. 4.0(2c)
working for AHCI controller. This happens
when the Red Hat Enterprise Linux OS is
installed.
CSCvk15263 During installation, iSCSI LUN is not visible None. 4.0(2c)

on Cavium OCP 41232 adapters with XEN
7.2, 7.3 or 7.4 OS versions.
Release 4.0(1a)
The following caveat is a known limitation in Release 4.0(1a):
Table 90: CMC

Affected
Release
CSCvi46521 On the 3260 servers, when you You must enable the single server dual VIC 4.0(1a)
are using a dual VIC single feature to use the second VIC.
server configuration, you
cannot access the second VIC.

Affected
Release
CSCvk11921 On the C125 servers with QL41232H 25G 1. Enter the BIOS setup. 4.0(1a)
OCP card, the link does not work. This
happens when OCP card is connected to the 2. Navigate to Advanced >
switch using a 5M SFP cable. The network Qlogic QL41232 Option
LED is not on and the network is not > Port Level
functional. configuration
3. Change the link Speed to
25Gbps.
4. Press F10.
5. Save and exit.

87
Related Documentation
Known Behaviors in the Previous Releases

Refer to the following release notes for Known Behaviors in the previous releases:
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:
• Cisco UCS C-Series Rack Servers Install and Upgrade Guides
The following related documentation is available for the Cisco Unified Computing System:
• Cisco UCS C-Series Servers Documentation Roadmap
• Cisco UCS Site Preparation Guide
• Regulatory Compliance and Safety Information for Cisco UCS
• 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.
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:
• Cisco UCS Manager Release Notes
• Cisco UCS C Series Server Integration with Cisco UCS Manager Guides

88

B UCS C-Series RN 4 0 4

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

B UCS C-Series RN 4 0 4

Uploaded by

Copyright:

Available Formats

Release Notes for Cisco UCS C-Series Software,

Cisco UCS C-Series Servers

Deprecated Release 4.0(4k)

Release Notes for Cisco UCS C-Series Software, Release 4.0(4)

L1 March 18, 2021 • Added New Software Features

The firmware files in Cisco Host

K1 December 17, 2020 Updated Known Behaviors in

The firmware files in Cisco Host

Release Notes for Cisco UCS C-Series Software, Release 4.0(4)

Revision Date Description

J0 July 06, 2020 • Updated the Resolved Caveats

The firmware files in Cisco Host

A3 May 21, 2020 Updated the Open Caveats section

D2 April 9, 2020 Updated the Open Caveats section

I1 April 2, 2020 Updated the Resolved Caveats

I0 March 23, 2020 • Updated the Resolved Caveats

The firmware files in Cisco Host

A1 March 11, 2020 Updated Open Caveats section for

Release Notes for Cisco UCS C-Series Software, Release 4.0(4)

Revision Date Description

H0 December 20, 2019 • Updated the Supported

The firmware files in Cisco Host

G0 December 09, 2019 • Updated the Supported

The firmware files in Cisco Host

F0 September 27, 2019 Following changes were made:

The firmware files in Cisco Host

Release Notes for Cisco UCS C-Series Software, Release 4.0(4)

Revision Date Description

E0 August 26, 2019 Following changes were made:

The firmware files in Cisco Host

D0 August 01, 2019 Following changes were made:

The firmware files in Cisco Host

Release Notes for Cisco UCS C-Series Software, Release 4.0(4)

Revision Date Description

C0 July 15, 2019 Following changes were made:

The firmware files in Cisco Host

B0 May 17, 2019 Following changes were made:

The firmware files in Cisco Host

A0 April 26, 2019 Created release notes for 4.0(4b).

Supported Platforms and Release Compatibility Matrix

Release Notes for Cisco UCS C-Series Software, Release 4.0(4)

For information about these servers, see Overview of Servers

Cisco IMC and Cisco UCS Manager Release Compatibility Matrix

4.0(4n) 4.0(4l) Cisco UCS C220 M5, C240 M5,

4.0(4m) 4.0(4j) Cisco UCS C220 M5, C240 M5,

4.0(4l) 4.0(4i) Cisco UCS C220 M5, C240 M5,

4.0(4k) 4.0(4h) Cisco UCS C220 M5, C240 M5, and

4.0(4j) No Support Cisco UCS S3260 M5 servers

4.0(4i) 4.0(4g) Cisco UCS C220 M5, C240 M5,

4.0(4h) 4.0(4e) Cisco UCS C220 M5, C240 M5,

4.0(4f) 4.0(4d) Cisco UCS C220 M5, C240 M5,

4.0(4e) 4.0(4c) Cisco UCS C220 M5, C240 M5,

4.0(4d) No Support Cisco UCS C220 M5, C240 M5,

4.0(4b) 4.0(4a) Cisco UCS C220 M5, C240 M5,

Release Notes for Cisco UCS C-Series Software, Release 4.0(4)

4.0(3b) 4.0(3a) Cisco UCS C220 M5 and C240 M5

4.0(2q) 4.0(4l) Cisco UCS C220 M4, C240 M4,

4.0(2p) No support. Cisco UCS C125 M5 servers

4.0(2o) 4.0(4j) Cisco UCS C220 M4, C240 M4,

4.0(2n) No support. Cisco UCS C220 M5, C240 M5,

4.0(2m) No support. Cisco UCS S3260 M4 and M5 servers

4.0(2l) No support. Cisco UCS C220 M5, C240 M5,

4.0(2k) No support. Cisco UCS S3260 M4 and M5 servers