Introduction

This document describes the features, system requirements, resolved caveats, and open caveats for Cisco UCS Server Configuration Utility (Cisco UCS SCU) and any related firmware or drivers. Use this document in conjunction with Cisco UCS Server Configuration Utility User Guide and Cisco Driver Update Utility User Guide, which can be found here.

Revision History

Table 1. Revision History

Revision

Date

Description

M0

October 8, 2021

Created release notes for Release 6.2(1c)

L0

August 4, 2021

Created release notes for Release 6.2(1a)

K0

March 10, 2021

Created release notes for Release 6.1(3c)

J0

September 18, 2020

Created release notes for Release 6.1(2d)

I0

April 22, 2020

Created release notes for Release 6.1(1b)

H0

September 06, 2019

Updated Open and Resolved Caveats for 6.0(4c)

G0

September 04, 2019

Updated Open Caveats for Release 6.0(2b)

F0

June 11, 2019

Created release notes for Release 6.0(4)

E0

February 25, 2019

Created release notes for Release 6.0(2)

D0

October 26, 2018

Created release notes for Release 6.0(1)

C0

April 27, 2018

Created release notes for Release 5.1(3)

B0

November 23, 2017

Created release notes for Release 5.1(2)

A0

October 20, 2017

Created release notes for Release 5.1(1)

Cisco UCS Server Configuration Utility

The Cisco UCS Server Configuration Utility (SCU) is an application that helps you manage Operating System installation on your server. The utility helps you easily set up required OS from a single application. Cisco UCS-SCU guides you through questions to help quickly configure the server through automatic recognition of server hardware, with minimal reboots and an automated unattended operating system installation.

Using SCU, you can perform the following tasks:

  • Install an operating system

  • Configure RAID levels

Beginning with Release 6.1(1b), options provided by Cisco UCS Server Configuration Utility are changed.

Cisco Driver Update Utility

The Cisco Driver Update Utility enables you to install or update drivers for all Cisco supported devices.

With Cisco Driver Update Utility, you can install driver updates individually or collectively.


Note

The DriverPackageInfo.xml file inside the Windows driver zip file is updated.


For more information on performing these tasks, see the Cisco Driver Update Utility.

System Requirements

This section lists the supported operating systems, supported hardware platforms, and hardware requirements for Cisco UCS SCU and Cisco Driver Update Utility.

Supported Operating Systems

For a list of supported Operating Systems on specific servers, use UCS Hardware and Software Compatibility Matrix.

Release 6.2(1c)

Support for the following Operating System was added for release 6.2(1c):

  • Windows Server 2022 - Supported on Cisco UCS C220, C240 M6, C225 and C245 M6 Servers

Release 6.2(1a)

Operating System

Cisco UCS C220 and C240 M6 Servers

Cisco UCS C245 M6 Server

Windows Server 2019

Supported

Supported

Windows Server 2016

Supported

Supported

HyperV 2019

Supported

Supported

HyperV 2016

Supported

Supported

Red Hat Enterprise Linux 8.4

Supported

Supported

Red Hat Enterprise Linux 8.3

Supported

Supported

Red Hat Enterprise Linux 8.2

Supported

Not Supported

Red Hat Enterprise Linux 7.9

Supported

Not Supported

SUSE Linux Enterprise Server 15 (SP3)

Supported

Supported

SUSE Linux Enterprise Server 15 (SP2)

Supported

Supported

Ubuntu 20.04.2

Supported

Supported

Ubuntu 20.04.1

Supported

Supported

VMware ESXi 7.0 U2

Supported

Supported

VMware ESXi 7.0 U1

Not Supported

Supported

VMware ESXi 6.7 U3 patch

Supported

Supported

Release 6.1(3c)

Support for the following Operating Systems were added for release 6.1(3c):

  • Windows Server 2019

  • Windows Server 2016

  • HyperV 2019

  • HyperV 2016

  • CentOS 8 Update 2

  • CentOS 8 Update 1

  • CentOS 8

  • CentOS 7 Update 8

  • CentOS 7 Update 7

  • CentOS 7 Update 6

  • Red Hat Enterprise Linux 8 Update 2

  • Red Hat Enterprise Linux 8 Update 1

  • Red Hat Enterprise Linux 8

  • Red Hat Enterprise Linux 7 Update 8

  • Red Hat Enterprise Linux 7 Update 7

  • Red Hat Enterprise Linux 7 Update 6

  • SUSE Linux Enterprise Server 15 (SP2)

  • SUSE Linux Enterprise Server 15 (SP1)

  • SUSE Linux Enterprise Server 12 (SP5)

  • SUSE Linux Enterprise Server 12 (SP4)

  • Ubuntu 20.04.1

  • Ubuntu 18.04.5

  • Ubuntu 18.04.4

  • Ubuntu 18.04.3

  • Ubuntu 18.04.2

  • Ubuntu 18.04.1

  • Ubuntu 16.04.6

  • Ubuntu 16.04.5

  • VMware ESXi 7.0 U1

  • VMware ESXi 7.0

  • VMware ESXi 6.7 U3

  • VMware ESXi 6.7 U2

  • VMware ESXi 6.5 U3

Release 6.1(2d)

Support for the following Operating Systems were added for release 6.1(2d):

  • Windows Server 2019

  • Windows Server 2016

  • Windows Server 2012 R2

  • HyperV 2019

  • HyperV 2016

  • CentOS 8 Update 2

  • CentOS 8 Update 1

  • CentOS 8

  • CentOS 7 Update 8

  • CentOS 7 Update 7

  • CentOS 7 Update 6

  • CentOS 7 Update 5

  • CentOS 7 Update 4

  • CentOS 6 Update 10

  • CentOS 6 Update 9

  • Red Hat Enterprise Linux 8 Update 2

  • Red Hat Enterprise Linux 8 Update 1

  • Red Hat Enterprise Linux 8

  • Red Hat Enterprise Linux 7 Update 8

  • Red Hat Enterprise Linux 7 Update 7

  • Red Hat Enterprise Linux 7 Update 6

  • Red Hat Enterprise Linux 7 Update 5

  • Red Hat Enterprise Linux 7 Update 4

  • Red Hat Enterprise Linux 6 Update 10

  • Red Hat Enterprise Linux 6 Update 9

  • SUSE Linux Enterprise Server 15 (SP1)

  • SUSE Linux Enterprise Server 15

  • SUSE Linux Enterprise Server 12 (SP5)

  • SUSE Linux Enterprise Server 12 (SP4)

  • SUSE Linux Enterprise Server 12 (SP3)

  • Ubuntu 18.04.4

  • Ubuntu 18.04.3

  • Ubuntu 18.04.2

  • Ubuntu 18.04.1

  • Ubuntu 18.04

  • Ubuntu 16.04.6

  • Ubuntu 16.04.5

  • Ubuntu 16.04.4

  • VMware ESXi 7.0

  • VMware ESXi 6.7 U3

  • VMware ESXi 6.7 U2

  • VMware ESXi 6.7 U1

  • VMware ESXi 6.7

  • VMware ESXi 6.5 U3

  • VMware ESXi 6.5 U2

  • VMware ESXi 6.5 U1

  • VMware ESXi 6.0 U3

Release 6.1(1b)

Support for the following Operating Systems were added for release 6.1(1b):

  • Windows Server 2019

  • Windows Server 2016

  • Windows Server 2012 R2

  • HyperV 2019

  • HyperV 2016

  • CentOS 8

  • CentOS 7 Update 7

  • CentOS 7 Update 6

  • CentOS 7 Update 5

  • CentOS 7 Update 4

  • CentOS 7 Update 3

  • CentOS 6 Update 10

  • CentOS 6 Update 9

  • Red Hat Enterprise Linux 8 Update 1

  • Red Hat Enterprise Linux 8

  • Red Hat Enterprise Linux 7 Update 7

  • Red Hat Enterprise Linux 7 Update 6

  • Red Hat Enterprise Linux 7 Update 5

  • Red Hat Enterprise Linux 7 Update 4

  • Red Hat Enterprise Linux 7 Update 3

  • Red Hat Enterprise Linux 6 Update 10

  • Red Hat Enterprise Linux 6 Update 9

  • SUSE Linux Enterprise Server 15 (SP1)

  • SUSE Linux Enterprise Server 15

  • SUSE Linux Enterprise Server 12 (SP5)

  • SUSE Linux Enterprise Server 12 (SP4)

  • SUSE Linux Enterprise Server 12 (SP3)

  • SUSE Linux Enterprise Server 12 (SP2)

  • Ubuntu 18.04.2

  • Ubuntu 18.04.1

  • Ubuntu 18.04

  • Ubuntu 16.04.5

  • Ubuntu 16.04.4

  • Ubuntu 16.04.3

  • Ubuntu 16.04.2

  • VMware ESXi 6.7 U3

  • VMware ESXi 6.7 U2

  • VMware ESXi 6.7 U1

  • VMware ESXi 6.7

  • VMware ESXi 6.5 U3

  • VMware ESXi 6.5 U2

  • VMware ESXi 6.5 U1

  • VMware ESXi 6.5

  • VMware ESXi 6.0 U3

  • VMware ESXi 6.0 U2

  • VMware ESXi 6.0 U1

Release 6.0(4)


Note

Supported Operating Systems on a server varies depending on the processor type. For example:

  • Servers with Second Generation Intel® Xeon® Scalable processors support Ubuntu 18.04.1 LTS and 18.04.2 LTS

  • Servers with Intel® Xeon® Scalable processors support Ubuntu 18.04 LTS, 18.04.1 LTS, 18.04.2 LTS, 16.04.4 LTS, 16.04.5 LTS, and 16.04.6 LTS.


Support for the following Operating Systems were added for release 6.0(4):

  • Windows Server 2012 R2

  • Windows Server 2016

  • Windows Server 2019

  • Red Hat Enterprise Linux 6 Update 9

  • Red Hat Enterprise Linux 6 Update 10

  • Red Hat Enterprise Linux 7 Update 3

  • Red Hat Enterprise Linux 7 Update 4

  • Red Hat Enterprise Linux 7 Update 5

  • Red Hat Enterprise Linux 7 Update 6

  • VMware ESXi 6.0

  • VMware ESXi 6.5

  • VMware ESXi 6.7

  • SUSE Linux Enterprise Server 12 Update 2

  • SUSE Linux Enterprise Server 12 Update 3

  • SUSE Linux Enterprise Server 12 Update 4

  • SUSE Linux Enterprise Server 15

  • SUSE Linux Enterprise Server 15 SP1

  • CentOS 6.9

  • CentOS 6.10

  • CentOS 7.3

  • CentOS 7.4

  • CentOS 7.5

  • Ubuntu 16.04

  • Ubuntu 18.04

Release 6.0(2)

Support for the following Operating Systems were added for release 6.0(2):

  • Windows Server 2012 R2

  • Windows Server 2016

  • Windows Server 2019

  • Red Hat Enterprise Linux 6 Update 9

  • Red Hat Enterprise Linux 6 Update 10

  • Red Hat Enterprise Linux 7 Update 3

  • Red Hat Enterprise Linux 7 Update 4

  • Red Hat Enterprise Linux 7 Update 5

  • Red Hat Enterprise Linux 7 Update 6

  • VMware ESXi 6.0

  • VMware ESXi 6.5

  • VMware ESXi 6.7

  • SUSE Linux Enterprise Server 12 Update 2

  • SUSE Linux Enterprise Server 12 Update 3

  • SUSE Linux Enterprise Server 12 Update 4

  • SUSE Linux Enterprise Server 15

  • CentOS 6.9

  • CentOS 6.10

  • CentOS 7.3

  • CentOS 7.4

  • CentOS 7.5

  • Ubuntu 16.04

  • Ubuntu 18.04

Release 6.0(1)

Support for the following Operating Systems were added for release 6.0(1):

  • Windows Server 2012 R2

  • Windows Storage Server 2012 R2

  • Windows Server 2016

  • Red Hat Enterprise Linux 6 Update 9

  • Red Hat Enterprise Linux 6 Update 10

  • Red Hat Enterprise Linux 7 Update 3

  • Red Hat Enterprise Linux 7 Update 4

  • Red Hat Enterprise Linux 7 Update 5

  • VMware ESXi 5.5

  • VMware ESXi 6.0

  • VMware ESXi 6.5

  • SUSE Linux Enterprise Server 12 Update 1

  • SUSE Linux Enterprise Server 12 Update 2

  • SUSE Linux Enterprise Server 12 Update 3

  • SUSE Linux Enterprise Server 15

  • CentOS 6.9

  • CentOS 6.10

  • CentOS 7.3

  • CentOS 7.4

  • CentOS 7.5

  • Ubuntu 16.04

  • Ubuntu 18.04

Release 5.1(3)

Support for the following Operating Systems were added for release 5.1(3):

  • Windows Server 2012 R2

  • Windows Server 2016

  • Red Hat Enterprise Linux 6 Update 9

  • Red Hat Enterprise Linux 7 Update 3

  • Red Hat Enterprise Linux 7 Update 4

  • VMware ESXi 6.0

  • VMware ESXi 6.5

  • SUSE Linux Enterprise Server 12 Update 2

  • SUSE Linux Enterprise Server 12 Update 3

  • CentOS 6.9

  • CentOS 7.3

  • CentOS 7.4

Release 5.1(2)

Support for the following Operating Systems were added for release 5.1(2):

  • Windows Server 2012 R2

  • Windows Server 2016

  • Red Hat Enterprise Linux 6 Update 9

  • Red Hat Enterprise Linux 7 Update 3

  • Red Hat Enterprise Linux 7 Update 4

  • VMware ESXi 6.0

  • VMware ESXi 6.5

  • SUSE Linux Enterprise Server 12 Update 2

  • SUSE Linux Enterprise Server 12 Update 3

  • CentOS 7.3

Release 5.1(1)

Support for the following Operating Systems were added for release 5.1(1):

  • Windows Server 2012 R2

  • Windows Server 2016

  • Red Hat Enterprise Linux 6 Update 9

  • Red Hat Enterprise Linux 7 Update 3

  • Red Hat Enterprise Linux 7 Update 4

  • VMware ESXi 6.0

  • VMware ESXi 6.5

Supported Platforms

Release 6.2(1c)

UCS-SCU 6.2(1c) and Cisco Driver Update Utility 6.2(1c) are supported on the following servers:

  • UCS-C220 M6

  • UCS-C240 M6

  • UCS-C225 M6 (2nd and 3rd Gen AMD EPYC CPUs)

  • UCS-C245 M6 (2nd and 3rd Gen AMD EPYC CPUs)

Release 6.2(1a)

UCS-SCU 6.2(1a) and Cisco Driver Update Utility 6.2(1a) are supported on the following servers:

  • UCS-C220 M6

  • UCS-C240 M6

  • UCS-C245 M6 (with 3rd Gen AMD EPYC CPUs)

Release 6.1(3c)

UCS-SCU 6.1(3c) and Cisco Driver Update Utility 6.1(3c) are supported on the following servers:

  • UCS-C240 SD M5

  • UCS-C125 M5

  • UCS-C220 M5

  • UCS-C240 M5

  • UCS-C480 M5

  • UCS-C480 M5 ML

  • UCS-S3260 M5

  • UCS-S3260 M4

Release 6.1(2d)

UCS-SCU 6.1(2d) and Cisco Driver Update Utility 6.1(2d) are supported on the following servers:

  • UCS-C240 SD M5

  • UCS-C125 M5

  • UCS-C220 M5

  • UCS-C240 M5

  • UCS-C480 M5

  • UCS-C480 M5 ML

  • UCS-S3260 M5

  • UCS-C220 M4

  • UCS-C240 M4

  • UCS-C460 M4

  • UCS-S3260 M4

Release 6.1(1b)

UCS-SCU 6.1(1b) and Cisco Driver Update Utility 6.1(1b) are supported on the following servers:

  • UCS-C220 M5

  • UCS-C240 M5

  • UCS-C480 M5

  • UCS-C480 M5 ML

  • UCS-S3260 M5

  • UCS-C220 M4

  • UCS-C240 M4

  • UCS-C460 M4

  • UCS-S3260 M4

Release 6.0(4)

UCS-SCU 6.0(4) and Cisco Driver Update Utility 6.0(4) are supported on the following servers:

  • UCS-C220 M5

  • UCS-C240 M5

  • UCS-C480 M5

  • UCS-C480 M5 ML

  • UCS-S3260 M5

Release 6.0(2)

UCS-SCU 6.0(2) and Cisco Driver Update Utility 6.0(2) are supported on the following servers:

  • UCS-C125 M5

  • UCS-C220 M5

  • UCS-C240 M5

  • UCS-C480 M5

  • UCS-C480 M5 ML

  • UCS-S3260 M5

  • UCS-C220 M4

  • UCS-C240 M4

  • UCS-C460 M4

  • UCS-S3260 M4

Release 6.0(1)

UCS-SCU 6.0(1) and Cisco Driver Update Utility 6.0(1) are supported on the following servers:

  • UCS-C125 M5

  • UCS-C220 M5

  • UCS-C240 M5

  • UCS-C480 M5

  • UCS-S3260 M5

  • UCS-C220 M4

  • UCS-C240 M4

  • UCS-C460 M4

  • UCS-S3260 M4

Release 5.1(3)

UCS-SCU 5.1(3) and Cisco Driver Update Utility 5.1(3) are supported on the following servers:

  • UCS-C220 M5

  • UCS-C240 M5

  • UCS-C480 M5

  • UCS-S3260 M5

Release 5.1(2)

UCS-SCU 5.1(2) and Cisco Driver Update Utility 5.1(2) are supported on the following servers:

  • UCS-C220 M5

  • UCS-C240 M5

  • UCS-C480 M5

Release 5.1(1)

UCS-SCU 5.1(1) and Cisco Driver Update Utility 5.1(1) are supported on the following servers:

  • UCS-C220 M5

  • UCS-C240 M5

Hardware Requirements for Cisco UCS SCU

The following are the minimum hardware requirements for UCS-SCU:

  • CD-ROM drive—A USB CD/DVD-ROM drive is required to be able to boot and run the UCS-SCU. You can also use the virtual media option in the CMC KVM to boot UCS-SCU.

  • Mouse—Some functions require a standard mouse (PS/2 or USB) for navigation.

  • USB disk on key device—Functions such as saving UCS-SCU logs require a USB disk on key.

  • RAM—A minimum of 1 GB RAM. If the available RAM is less than the minimum recommended value, UCS-SCU will not function properly.

  • Network adapter—Some optional functions, such as, downloading the OS drivers from support.cisco.com, require network access. Any single onboard NIC adapter connection is supported.


    Note

    Network Configuration is not supported for 6.0(4) release.


  • RAID Cards—RAID configuration and OS installation are supported on select controllers.


Note

From release 6.0(4) onwards, SCU supports JBOD mode installation.

When the drive is in JBOD mode, the state is displayed as: “Drive is exposed and controlled by host”. In this state, the SCU will allow the user to go ahead with the OS installation on the drive. In case, the drive is in “Unconfigured good” state, it is required to configure a logical or virtual drive before proceeding with the OS installation.



Note

Currently UCS-SCU supports only Intel adapters.

RAID Cards—RAID configuration and OS installation are supported on select controllers.


New Features

New Features in Release 6.2(1a)

Beginning with release 6.2(1a), Server Configuration Utility supports Cisco FlexMMC – The SCU iso image can be uploaded and mapped from the User Files partition of the FlexMMC.

New Features in Release 6.1(3c)

Beginning with release 6.1(3c), Server Configuration Utility supports UEFI secure boot feature, which can boot in secure boot enabled mode.


Note

This functionality works only when BMC and BIOS are in release 4.1(3b) or later.


New Features in Release 6.1(2d)

New Features in Release 6.1(2d)

  • UCS-M2-HWRAID - Cisco boot optimized M.2 Raid controller is supported on Cisco UCS C125.

New and Deprecated Features in Release 6.1(1b)

New Features in Release 6.1(1b)

  • Cisco UCS SCU now supports installation of many new operating systems. For more information, see Supported Operating Systems.

  • Cisco UCS SCU now supports quick installation for ESXi.

  • Cisco UCS SCU now supports OS installation on physical disks, virtual disks, NVMe disks, SD cards, M.2 disks, and SW RAIDs.


Note

Once the Windows or Linux OS installation is complete, use the factory default password Pa55w0rd@.


Deprecated Features

Cisco UCS SCU no longer supports the following:

  • Partition customization in SCU Custom Install UI.

  • Server Inventory

  • Server Health

  • Server Diagnostics

  • In the new GUI, there is no toolbar.

New Features in Release 6.0(4c)

Support for OS installation on legacy M.2 drives

Beginning with Release 6.0(4c), NI-SCU supports OS installation on M.2 form factor SSD in AHCI mode.

Support for drive detection based on serial number/VD ID for NI-SCU OS installation


Note

This feature is not supported for legacy M.2 drives.


NI-SCU script uses the osDrive:/dev/sdk field to decide the OS installation disk. However, if a server has multiple storage devices like virtual disks, physical disks, SD cards, or USB devices, user cannot identify the OS installation disk before the installation.

For example, if you try to install the OS on a server with multiple physical disk, there is no way to control which disk the OS installation may happen.

Release 6.0(4c) introduces the following NI-SCU config file parameters to resolve this issue:

  • DriveSerialNumber: This is the serial number of the physical drive.

  • StorageControllerSlotID: Controller Slot ID. If DriveSerialNumber is present, this parameter is ignored.

  • VirtualDriveNumber: VD Number

The value of the above parameters can be obtained using python get_storage_details.py script (part of the NI-SCU package). This script uses the Cisco IMC IP address, user name, and password as arguments. You must edit the NI-SCU configuration file with these parameters and then proceed with installation. This ensures that the script selects the desired disk for OS installation even if the server has multiple disks.


Note

NI-SCU script with osDrive:/dev/sdk field is still applicable.


Resolved Caveats

Release 6.1(1b)

This section lists the resolved caveats in the Cisco UCS SCU, Release 6.1(1b):

Table 2. Release 6.1(1b)

Defect ID

Symptom

Workaround

Resolved in Release

CSCvt55184

NI-HUU script displays the following error when SCU or OS ISO is mapped from HTTPS file share and is running BMC version is 4.1.1C or 4.1.1B

Operation failed. Failed to map OS ISO

This issue is now resolved.

Use HTTP or NFS or CIFS share for ISO mapping.

You can also use BMC version above 4.1.1C.

6.1(1b)

Release 6.0(4)

This section lists the resolved caveats in the Cisco UCS SCU, Release 6.0(4c):

Table 3. Release 6.0(4)

Defect ID

Symptom

Workaround

Resolved in Release

CSCvq64911

Stale Cisco VIC management drivers are listed under SCU even when the drivers are physically not present in the system.

This issue is now resolved.

There is no known workaround for this issue.

There is no functional impact on the system.

6.0(4)

Release 5.1(2)

This section lists the resolved caveats in the Cisco UCS SCU, Release 5.1(2):

Table 4. Release 5.1(2)

Defect ID

Symptom

Workaround

Resolved in Release

CSCvg09045

OS installation does not complete and stalls with SCU waiting for user input at the license page. This happens when you trigger NI-SCU while the network mode is in the dedicated mode.

This issue is now resolved.

Change the Cisco IMC network mode to Shared LOM mode.

6.0(4)

Open Caveats

Release 6.1(3c)

This section lists the open caveats in the Cisco UCS SCU, Release 6.1(3c):

Table 5. Release 6.1(3c)

Defect ID

Symptom

Workaround

CSCvw01188

Drivers for Mellanox cards fail to install for certain OS (Cent, RHEL, SLES) on Cisco UCS servers when secure boot is enabled.

Disable secure boot.

CSCvw01171

Drivers for Emulex cards fail to install for certain OS (Cent, RHEL, SLES) on Cisco UCS servers when secure boot is enabled.

Disable secure boot.

CSCvw01154

Drivers for Qlogic cards fail to install for certain OS (Cent, RHEL, SLES) on Cisco UCS servers when secure boot is enabled.

Disable secure boot.

Release 6.1(2d)

This section lists the open caveats in the Cisco UCS SCU, Release 6.1(2d):

Table 6. Release 6.1(2d)

Defect ID

Symptom

Workaround

CSCvv44907

OS installation failed in Cisco UCS S3260 M5 server fails under the following condition:

  • SCU ISO on a CIFS share with mount option = ntlm mentioned in NISCU configuration file

Keep the SCU ISO in a CIFS share that does not require the mount option = ntlm and retry the installation.

CSCvv57805

Cisco UCS C125 server chipset drivers fail to install during Windows OS installation.

There is no known workaround.

CSCvv37520

NISCU OS ISO vmedia mapping from HTTP or HTTPS share server over IPv6 fails on Cisco UCS S3260 M4 and M5 servers.

In the config file, if you mention http or https for IPv6 address, then you must specify the port also.

Release 6.1(1b)

This section lists the open caveats in the Cisco UCS SCU, Release 6.1(1b):

Table 7. Release 6.1(1b)

Defect ID

Symptom

Workaround

CSCvt83366

OS installation on Cisco UCS S3260 fails under the following conditions:

  • Installation media is virtual drive or physical disk.

  • Installation media is connection to SBMEzz1 and SBMezz2 slots and UCS-S3260-M5 mode.

Following error is displayed:

Harddisk preparation failed

Use release 6.0(4c) or use BMC version above 4.1.1F.

CSCvt78954

Windows 2019 server OS installation fails on Cisco UCS C125 servers equipped with Cisco boot optimized m.2 RAID controller.

There is no known workaround.

CSCvt90187

OS installation fails on Cisco UCS S3260 servers equipped with NVMe drives.

There is no known workaround.

CSCvt87288

Driver firmware installation through driver update utility on Windows 2019 server OS fails.

Update the driver firmware using the respective driver .iso from Software Download.

Release 6.0(4c)

This section lists the open caveats in the Cisco UCS SCU, Release 6.0(4c):

Table 8. Release 6.0(4c)

Defect ID

Symptom

Workaround

CSCvq98140

Windows 2012R2, Windows2016 and Windows2019 OS installation fails on Cisco UCS M5 servers, which have

SATA HDDs attached to LSI embedded RAID Controllers. The following error message is displayed:

Windows could not parse or process the unattend answer file

There is no known workaround for this issue.

SCU does not support OS installation on SATA HDDs attached to software RAID/LSI embedded controller.

CSCvq85323

RHEL 7.6 installation fails on M.2 drives attached to the Cisco boot optimized M.2 RAID controller with the following error message:

error checking storage configuration

Create a VD and then install RHEL 7.6.

CSCvq90605

When an IPv6 address is provided for the OS ISO source remote share, NI-SCU script fails with the following error message:

NISCU OS Installation failed for CIMC - xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx Reason - OS media not found. Please provide proper OS media

Use IPv4 address for OS file share

Release 6.0(4a)

This section lists the open caveats in the Cisco UCS SCU, Release 6.0(4a):

Table 9. Release 6.0(4a)

Defect ID

Symptom

Workaround

CSCvp74380

During custom windows 2016/2019 install, warning message Assertion failed in ItemFileWriteStore appears.

This issue is seen only in interactive SCU and Windows OS Custom installation.

Click OK to proceed installation.

CSCvp63203

Internet Security warning message appears when navigating to other tabs from OS Custom Install page without completing the existing configuration on custom install page.

Select Allow and remember the decision option to proceed further.

CSCvp91904

If the running version of Qlogic QL4XXXX card is 8.37.35 in device manager, then DUU driver update fails for QL4XXXX card.

8.37.35 version is the latest version for 6.0(4a). Hence, skip update from DUU.

CSCvq00372

XML parsing error appears in NISCU, if SFTP or TFTP protocol is specified in NISCU configuration file.

Use SCP or HTTP protocol in NISCU configuration file.

CSCvq00466

NISCU will boot into interactive mode if the NISCU configuration has SFTP or TFTP protocol as file share for answer and config file.

Use SCP or HTTP protocol in NISCU configuration file.

CSCvp81504

In Windows OS, after successful installation of chipset driver, SCU DUU displays Reboot required option as NO.

DUU will continue to show the Reboot required option as NO. User has to reboot the host to get the updated chipset drivers applied.

CSCvp76597

SCU IOs Inventory tab displays incorrect WWPN for Emulex storage adapters.

Refer BIOS for correct WWPN values.

CSCvp93110

Server Inventory and Server Health details displayed in SCU may be inaccurate for certain components.

Refer Cisco IMC/BMC for the most current and accurate information.

CSCvp61260

Server Inventory and Server health details displayed in SCU may be inaccurate for certain components.

Refer Cisco IMC/BMC for the most current and accurate information.

CSCvp61184

SCU IOs inventory, lists MAC address as NA for Qlogic adapters.

Refer Cisco IMC/BMC for the most current and accurate information.

CSCvp98744

SCU UI with regard to OS list drop-down will list UBUNTU 18.04, even though it is not supported in Cisco UCS C220 M5 and C240 M5 servers.

UBUNTU 18.04 supports all the minor versions. Hence, UBUNTU 18.04.01 is also supported.

To install UBUNTU 18.04.01, you can select UBUNTU 18.04.

CSCvp98703

During ESXI 6.7 installation following error message appears:

Unable to successfully execute 'tryFormatdevice' after 3 retries. Installation cannot continue

Create RAID0 from Intel SSD and then install OS.

Release 6.0(2)

This section lists the open caveats in the Cisco UCS SCU, Release 6.0(2b):

Table 10. Release 6.0(2b)

Defect ID

Symptom

Workaround

CSCvq98740

Two chipset options are displayed when DUU is launched on a Cisco UCS C460M4 server. One of these chipset shows a discrepancy in the current driver version and available driver version even after the chipset drivers are updated successfully.

There is no known workaround for this issue.

You can ignore the discrepancy as the latest drivers are already installed successfully.

CSCvq99969

On Cisco UCS C460M4 servers, while installing Win2012R2 through NI-SCU script, the NI-SCU script displays the following error even if the installation is successful:

Handling Process pending work
Handling Process pending work
Process Process-1:
Traceback (most recent call last):
File "/usr/lib64/python2.7/multiprocessing/process.py", 
line 258, in _bootstrap
self.run()
File "/usr/lib64/python2.7/multiprocessing/process.py", 
line 114, in run
self._target(*self._args, **self._kwargs)
File "run_snapshot_niosi.py", line 2280, in 
IodHandleSnapshotTests
responseData = IodProcessPendingWork(logger, work)
File "run_snapshot_niosi.py", line 2246, in 
IodProcessPendingWork
work.osiStatus(logger)
File "run_snapshot_niosi.py", line 702, in osiStatus
if "OS media not found. Please provide proper OS media." 
in responseData :
TypeError: argument of type 'NoneType' is not iterable"

There is no known workaround for this issue. You can ignore the error message because the installation is a success despite of the error message.

CSCvr01665

Cisco UCS Server Configuration Utility launch page shows incorrect download page for SCU software. SCU also does not support BIOS and CIMC firmware upgrade and interactive offline diagnostics, as stated on the launch page.

You can search and download the SCU software from Software Download.

CSCvr08867

In Cisco UCS C220M4 servers with Windows 2012R2 OS, DUU does not display Qlogic and Broadcom device

drivers.

There is no known workaround for this issue.

There is no functionality impact. Inbox drivers are available in Win2k12 for Qlogic and Broadcom devices.

CSCvr09421

In Cisco UCS C220M4 servers with Windows 2012R2 OS, inbox driver displays incorrect LSI controller driver version.

There is no known workaround for this issue.

CSCvr09464

In Cisco UCS C220M4 servers, DUU does not respond while updating driver for Cisco 12G Modular SAS Pass-through controller.

Download the driver .iso file from www.cisco.com and update the driver using the same.

CSCvr01571

In Cisco UCS S3260M5 servers with more than 26 VDs, SCU displays one of the following error for RAID configuration:

Malformed response, no response element
Error: Unable to load http://127.0.0.1/SCU/fastcgi

Create VDs from Cisco IMC Web GUI or XML API.

Release 6.0(2a)

This section lists the open caveats in the Cisco UCS SCU, Release 6.0(2a):

Table 11. Release 6.0(2a)

Defect ID

Symptom

Workaround

CSCvo45452

While running NISCU, SCU boots into License page and OS installation fails.

Re-trigger NISCU.

Release 6.0(1)

This section lists the open caveats in the Cisco UCS SCU, Release 6.0(1):

Table 12. Release 6.0(1)

Defect ID

Symptom

Workaround

CSCvm67025

Windows installation fails in UEFI mode.

Clear the partitions on the other disk and retry installation.

Known Behavior

Release 6.2(1c)

This section lists the known behavior in the Cisco UCS SCU, Release 6.2(1c):

Table 13. Release 6.2(1c)

Defect ID

Symptom

Workaround

CSCvz68868

In the servers installed with Windows 2022, yellow bang error is displayed on Inventory only Storage controller cards that do not have an active connection. This error is not seen on network controllers.

Connection should be given to all the peripherals in the servers installed with Windows 2022.

Release 6.2(1a)

This section lists the known behavior in the Cisco UCS SCU, Release 6.2(1a):

Table 14. Release 6.2(1a)

Defect ID

Symptom

Workaround

CSCvz17448

User maps SCU iso on UCS M6 server with Windows 2016 Server and Intel x550 adapter. When the user runs DUU on the server to get the list of drivers installed, the DUU UI displays x1 as the device name instead of the adapter name.

No known workaround.

CSCvz13950

User maps SCU iso on UCS M6 server with Windows 2016 Server and Emulex LPe35002 adapter. When the user runs DUU on the server, the DUU UI displays the value 12.8.334.6 for the Current Driver Version and Available Driver Version fields for lpexx00x. The DUU UI also displays action as Force Update.

So the user selects lpexx00x and clicks on the Install button to perform force update.

If the current installed driver version and available driver version are the same, then uninstall the driver from Windows Device Manager and update using the DUU UI.

Release 6.1(3c)

This section lists the known behavior in the Cisco UCS SCU, Release 6.1(3c):

Table 15. Release 6.1(3c)

Defect ID

Symptom

Workaround

CSCvw19061

ESXi OS installation fails with the following error message in Interactive HUU or Non-Interactive HUU mode on Cisco UCS M5 servers when secure boot is enabled:

Unrecognized tardisks

Disable secure boot.

CSCvx25397

SLES 15 OS installation fails with the following error message on Cisco UCS M5 servers:

repomd.xml repository error

No known workaround.

Release 6.0(2)

This section lists the known behavior in the Cisco UCS SCU, Release 6.0(2):

Table 16. Release 6.0(2)

Defect ID

Symptom

Workaround

CSCvg30801

After installation, the host will not boot to ESXi Operating System.

OS installation is done in UEFI mode.

Add a new boot option from BIOS with boot option file path as \EFI\BOOT\BOOTx64.EFI and then reboot host.

CSCvo25932

After Windows installations, nVidia GPU drivers are not installed.

On Windows installation on servers having nVidia GPU cards, you can download the driver ISO for windows posted on cisco.com and manually install the driver after OS installation.

Release 5.1(1)

This section lists the known behavior in the Cisco UCS SCU, Release 5.1(1):

Table 17. Release 5.1(1)

Defect ID

Symptom

Workaround

CSCvg23396

The NI-SCU script terminates with a timeout error, However OS installation continues and completes. This occurs on network with low bandwidth between the ISO repository and Cisco IMC.

There is no known workaround.

There is no functionality impact.

CSCvg42114

GLIBC_2.14' not found (required by ./ucs_duu) error message appears while running ucs_duu on Red Hat Enterprise Linux 6 Update x.

Perform these steps:

  1. mkdir ~/glibc_install; cd ~/glibc_install

  2. wget http://ftp.gnu.org/gnu/glibc/glibc-2.14.tar.gz

  3. tar zxvf glibc-2.14.tar.gz

  4. cd glibc-2.14: mkdir build: cd build

  5. make -j4

  6. make -j4

  7. export LD_LIBRARY_PATH=/opt/glibc-2.14/lib