Release Notes for Cisco UCS Server Configuration Utility
Cisco UCS Server Configuration Utility
Hardware Requirements for Cisco UCS SCU
Software Features in Cisco UCS SCU Releases
Cisco UCS SCU Release 3.1(3c.1)
Cisco Driver Update Utility Release 3.1(2)
Cisco Driver Update Utility Release 3.0
Cisco UCS Driver Update Utility
Cisco UCS Driver Update Utility
Known Behavior in Release 4.0(13)
Obtaining Documentation and Submitting a Service Request
First Published Date: March 12, 2012
Revised Date: October 27, 2016
This document describes the features, system requirements, and open caveats for UCS SCU Release 4.0(13) and Cisco Driver Update Utility Release 4.0(13), and any related 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 review the documentation on Cisco.com for any updates.
Table 1 shows the online change history for this document.
This release note discusses the features, and open caveats for the following products:
The Cisco UCS Server Configuration Utility (UCS SCU) is an application that helps you easily set up and manage your servers from a single application. UCS SCU reduces the complexity and time associated with setting up and maintaining Cisco C-series servers. Server deployment time is made easier. It 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.
With UCS-SCU, you can perform the following:
– Quick install - Install an operating system with default settings
– Custom install - Modify the default settings prior to installing an operating system.
For more information on performing these tasks, see the latest version of the Cisco UCS Server Configuration Utility User Guide.
The Cisco Driver Update Utility enables you to install or update drivers for all Cisco supported devices.
With Cisco Driver Update Utility, you can perform the following:
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.
This section lists the supported operating systems, supported hardware platforms, and the hardware requirements for Cisco UCS SCU and Cisco Driver Update Utility.
Cisco UCS-SCU 4.0(13) supports unattended installation of the following operating systems:
UCS-SCU 4.0(13) and Cisco Driver Update Utility 4.0(13) are supported on the following servers:
Note UCS-C3X60 M4 is supported 4.0(13) release onwards.
UCS-SCU 4.0(12) and Cisco Driver Update Utility 4.0(12) are supported on the following servers:
UCS-SCU 4.0(10) and Cisco Driver Update Utility 4.0(10) are supported on the following servers:
UCS-SCU 4.0(9) and Cisco Driver Update Utility 4.0(9) are supported on the following servers:
UCS-SCU 4.0(8) and Cisco Driver Update Utility 4.0(8) are supported on the following servers:
UCS-SCU 4.0(7) and Cisco Driver Update Utility 4.0(7) are supported on the UCS-C3260 server.
UCS-SCU 4.0(5) and Cisco Driver Update Utility 4.0(5) are supported on the UCS-C460 M4 server.
UCS-SCU 4.0(4) and Cisco Driver Update Utility 4.0(4) are supported on the following servers:
UCS-SCU 4.0(3) and Cisco Driver Update Utility 4.0(3) are supported on the following servers:
UCS-SCU 4.0(2) and Cisco Driver Update Utility 4.0(2) are supported on the following server:
UCS-SCU 4.0(1) and Cisco Driver Update Utility 4.0(1) are supported on the following servers:
UCS-SCU 3.1(6) and Cisco Driver Update Utility 3.1(6) is supported on the UCS C460 M4 servers.
UCS-SCU 3.1(5) and Cisco Driver Update Utility 3.1(5) are supported on the following servers:
The following are the minimum hardware requirements for UCS SCU:
Note Currently UCS-SCU supports only Intel adapters.
• Only RAID configuration is supported
• Added RAID support for LSI Embedded MegaRAID.
• Added support for the following:
This section describes the features of UCS Server Configuration Utility that were introduced or modified in release 3.1(4).
For more information on supported drivers, see the Hardware and Software Interoperability for Standalone C-Series Servers in Release 1.5(3) available at the following link:
http://www.cisco.com/en/US/products/ps10477/prod_technical_reference_list.html
This section describes the features of UCS Server Configuration Utility and Cisco Driver Update Utility that were introduced or modified in release 3.1(3).
The following defects were resolved:
Symptom SCU shows PSU faults in Server Health, but PSU state on CIMC does not show any issue.
Symptom "Chassis open status: asserted" warning message logged in SCU for C460 M2 servers.
To run pre-defined diagnostic tests on the server when it is booting.
To synchronize data in the HyperVisor partition of the SD cards to create a RAID 1.
This section describes the features of UCS Server Configuration Utility and Cisco Driver Update Utility that were introduced or modified in release 3.1(2).
This section lists the resolved caveats in the Cisco UCS SCU, Release 4.0(3a).
Symptom On C460 M4 server with Nvidia Grid K2 cards, SCU fails to boot, and stops while trying to load the Nouveau driver.
Symptom Installation of RHEL6.5 on SCU 4.0(3) version fails, and SCU crashes with the following error message:
This section lists the open caveats in the Cisco UCS SCU and the Cisco Driver Update Utility and contains the following topic:
This section lists the open caveats for Cisco UCS SCU and the Driver Update Utility Release 4.0(13).
Symptom Red Hat Enterprise Linux 7.1 installation fails on the virtual drive created on the UCS-SAS 12G Raid Controller using Server Configuration Utility. This happens when you try to install the OS on a virtual drive with a drive space more than 3 terrabytes.
Workaround Install the OS on a virtual drive with a drive space less than 3 terrabytes.
Symptom A blank screen appears after installing Ubuntu 16.04.01 using the server configuration utility.
Workaround After the installation, press Ctlr+Alt+F1 when the blank screen appears. This allows you to log on to the OS.
This section lists the open caveats for Cisco UCS SCU and the Driver Update Utility Release 4.0(8).
Symptom On the C220-M4 server, after installing the CentOS (6.4 and 6.5), and Red Hat Enterprise Linux (6.x and 7.x) using the SCU on a Software RAID configured disk, on reboot, the OS installer fails to detect the disk.
This section lists the open caveats for Cisco UCS SCU and the Driver Update Utility Release 4.0(7).
Symptom SCU mounting fails using CIFS share.
Workaround To resolve this issue do one of the following:
– Use WWW or NFS to mount SCU and run the diagnostic
– Use the build in diagnostic by pressing F7 during POST to run diagnostic
Symptom Unable to display downloaded information when technical difficulty message is displayed during driver zip download.
Workaround Use SCU boot media for installing the drivers.
Symptom Driver Update Utility hangs while installing drivers.
This section lists the open caveats for Cisco UCS SCU and the Driver Update Utility Release 4.0(2).
Symptom Downloading the driver zips from Cisco.com using the Driver Update Utility fails.
Symptom While trying to install the Windows OS using the SCU, when the VIC (enic) drivers are selected, a pop-up message displays prompting you to confirm the unsigned driver install.
Workaround For Custom install ensure that you unselect the VIC (enic) drivers from driver list.
For Quick install confirm the OS install on the pop-up message.
Symptom After installing the CentOS (6.4 and 6.5) using the SCU on a Software RAID configured disk, on reboot, CENTOS installer is does not detect the disk.
Symptom The SCU Web manager crashes when the LSI Nytro card is present.
Workaround Do not boot the SCU on a server that has a LSI Nytro Card.
This section lists the open caveats for Cisco UCS SCU and the Driver Update Utility Release 4.0(2).
Symptom For C3160 servers, solid-state drives (SSD) are not listed for SCU diagnostic.
Symptom ESXi installation on iSCSI LUN configured with Intel i350 boots to mapped ESXi image instead of iSCSI LUN.
Workaround Manually boot to iSCSI LUN from F6 or F2.
Symptom SCU online help has following issues:
– Supported OS list includes Windows storage server R2 instead of Windows storage server 2012 R2
– Under supported peripheral device table, LSI controller name is RAID controller for UCS C3160 storage instead of RAID controller for UCS C3x60 storage.
– Pages such as Installing Operating Systems, Configuring RAID levels, Viewing Logs and Diagnostic Tools does not display any content when clicked at the chapter title level.
Workaround For supported OS and peripheral devices list, refer the SCU user guide. For viewing contents of Installing Operating Systems, Configuring RAID levels, Viewing Logs and Diagnostic Tools chapters, click the sections listed under these chapter.
Symptom During RHEL 6.5 installation, iGB driver is not installed.
This section lists the open caveats for Cisco UCS SCU and the Driver Update Utility Release 4.0(3).
Symptom Boot order is not set correctly when there are multiple virtual drives in the software RAID.
Workaround Set the correct boot virtual drive device by using BIOS software RAID option ROM.
Symptom Unable to run the server snapshot.
To run the server snapshot, follow these steps:
Step 3 Rerun the server snapshot.
Symptom Esxi OS installation does not boot from the correct iSCSI LUN.
Workaround Change the boot order from F2 menu, and make iSCSI LUN as the first boot device.
Symptom Non Uniform Memory Access (NUMA) test fails.
Symptom OS installation is stuck after reboot.
Workaround Go to F2 menu and make the virtual drive as first boot device.
Symptom Unable to get DHCP IP address.
Workaround None. Assign static IP address.
Symptom Device manager displays yellow bang for X520 card.
Symptom In ESXi 5.0 version, assigned static IP address is not reflect after OS installation.
Workaround After OS installation, assign static IP address manually.
Symptom Online help displays Hide/Show button twice.
Workaround None. This will be fixed in the next release.
Symptom Print button is nonfunctional in online help.
Workaround None. This will be fixed in the next release.
Symptom Content related help is not displayed.
Workaround Manually navigate to the required help page.
Symptom When a link opened from the SCU help, Firefox window do not have Close or Minimize button.
Symptom Utility crashes while creating RAID.
Workaround Go to controller option ROM and clear HDD configuration.
Symptom Server snapshot does not list number of DIMMs in C220 M4 and C240 M4 servers.
Symptom eNIC drivers are not present in all the Windows OS installation.
This section lists the open caveats for Cisco UCS SCU and the Driver Update Utility Release 4.0(1).
Symptom Inventory is not displayed if GPT formatted USB is plugged in during boot.
Symptom iSCSI OS installation fails if secondary target is mentioned in ROM option.
Workaround Remove the secondary target details mentioned in the VIC option ROM.
Symptom After installing the Windows OS, the driver versions for the Broadcom cards displays a different versions.
This section lists the open caveats for Cisco UCS SCU and Cisco Driver Update Utility Release 3.1(6).
Symptom: NI-IOD copies Zero byte out put file to the remote location, and while NI-IOD tests are running, no log is saved in the remote share location.
Symptom: BCM5709 driver version mismatch in Driver Update Utility (DUU) for Windows OS. DUU displays wrong driver version in spite of installing correct driver.
This section lists the open caveats for Cisco UCS SCU and Cisco Driver Update Utility Release 3.1(5b)
Symptom: Driver update for MP card fail using Driver Update Utility in case of native OS install.
Workaround: Use the Driver ISO provided by www.cisco.com.
Symptom: Installation of a NIC driver for an Emulex card using Driver Update Utility fails in the case of a native OS installation of Windows 2012 R2 server. The error occurs because of an unsigned driver.
Workaround: Look for a signed driver in the Driver ISO released available on www.cisco.com.
Symptom: Windows 2012 R2 OS cannot be installed in a system with Intel 82576.
Symptom: The error message "Unable to enumerate vdisks. Check CIMC GUI for SD card status." appears as soon as the server is booted to the SCU image.
Workaround: No workaround. Click OK to continue.
Symptom: After installing an OS using UCS SCU, modinfo will show inbox driver version for BNX2.
Workaround: Complete the following steps:
2) Type depmod and press enter.
3) Type modinfo. The correct driver version is displayed.
Symptom: RHEL 6.4 OS installation fails on SW RAID using SCU.
Symptom: After the user is prompted to reboot the server from UCS SCU, the server must automatically boot to the selected VD and continue with the OS installation. But the boot order does not change during OS install.
Workaround: Go to BIOS and manually change the boot order.
Symptom: While using the Custom OS install option, when driver zips are provided from the USB, the installation fails and the following message is displayed:
Workaround: Use the default option of drivers from SCU media or use the drivers from the network or from www.cisco.com.
This section lists the open caveats for Cisco UCS SCU and Cisco Driver Update Utility Release 3.1(4f).
Symptom: Driver Update utility will fail to install a chipset driver or it will give you success message without updating the driver.
Workaround: Install driver manually form Driver CD available on the Cisco website.
Symptom: RHEL 6.4 installation fails on software RAID.
Workaround: Try native install using C600 driver from the Driver ISO available on the Cisco website.
Symptom: While installing Microsoft Windows 2008 R2, or Microsoft Windows 2012 operating systems using Cisco UCS SCU, the users sees an unsigned driver pop-up.
Workaround: None. Continue the installation of the operating system.
Symptom: Microsoft Windows 2012R2 installation from the SCU CD fails and the following error message is displayed:
This section lists the open caveats for Cisco UCS SCU and Cisco Driver Update Utility Release 3.1(4c).
Symptom: When a user attempts to update the chipset driver using the Cisco UCS Driver Update Utility after installing the Microsoft Windows OS, there is no component called Chipset displayed in the utility.
Workaround: Install the chipset driver from the Driver CD available on Cisco.com.
This section lists the open caveats for Cisco UCS SCU and Cisco Driver Update Utility Release 3.1(4) and contains the following topics:
Symptom: Pdisk test may fail during server snapshot even when CIMC displays SDD status as good.
Symptom: SCU is not giving any option to clear SEL log even when SEL is full.
Workaround: Clear SEL from CIMC
Symptom: RHEL OS is not listing drivers for enic, fnic and bnx2x
Workaround: Install the driver from the Driver ISO provided by Cisco.
Symptom: modinfo showing wrong driver for bcm57712 10 base T for RHEL 6.3
Workaround: Install the driver from the Driver ISO provided by Cisco.
Symptom: Unable to install megasr module if RHEL is installed on LSI card.
Workaround: megasr is not required for LSI cards. This driver is only for software RAID.
Symptom: Driver update utility fails to install driver for Intel 82576 for Windows 2012.
Workaround: Install the driver from the Driver ISO provided by Cisco.
This section lists the open caveats for Cisco UCS SCU and Cisco Driver Update Utility Release 3.1(3) and contains the following topics:
Symptom: For UCS C240 SNEBS servers, SCU does not carry any drivers. During the custom OS installation, the following warning message appears:
Symptom: In UCS C240 SNEBS servers, the Web Manager crashes if the License Agreement is accepted within 10 seconds.
Workaround: Wait for 10 seconds before accepting the License Agreement in the SCU screen.
This section lists the open caveats for Cisco UCS SCU and Cisco Driver Update Utility Release 3.1(2) and contains the following topics:
Symptom: The Megasr Driver is not installed along with the Red Hat Enterprise Linux (RHEL) 5.7, 5.8 and 6.2 OS installations.
Workaround: Run the depmod command to solve the problem.
Symptom: While using the Quick Install option to install the Linux OS, the driver version for bnx2 driver does not match the version displayed in Cisco UCS SCU interface.
Workaround: Run the depmod command.
Symptom: When the Custom install option is used to install RHEL 6.1 OS, the installation process fails after the host reboots to initiate the OS installation. The following error message is displayed:
Could not allocate requested partitions....not enough free space on disk.
Workaround: You can perform one of the following workarounds:
– Use the Quick Install option
– Recreate RAID less than 2 TB, and re-attempt OS installation.
This section lists the open caveats for Cisco UCS SCU Release 3.1 and Cisco Driver Update Utility Release 3.0 and contains the following topics:
Symptom : You get the following error when configuring DHCP IP for SCU:
Workaround : Configure the static IP.
Symptom: RAID configuration fails and the following error message is displayed:
Workaround: Wait till the virtual disk (VD) initialization is complete.
Symptom: Clear configuration does not delete created VDs.
Workaround: Go to the Web BIOS of the LSI controller by pressing CTRL + H during POST and clear the configuration from the Web BIOS.
Symptom: Clear configuration does not delete VDs when the HDD status is in the “Drive is exposed and controlled by host" state.
Workaround: Go to the Web BIOS of the LSI controller by pressing CTRL + H during POST and clear the configuration from the Web BIOS.
Symptom : RAID 10 support on LSI Embedded MegaRAID Controller with more than 2 HDD per span fails.
Workaround : None. Currently, RAID 10 only supports up to 4 disks for LSI Embedded MegaRAID, that is, 2 disks per Data Group and only 2 Data Groups per RAID 10.
Symptom : QLE8242 displays as QLE8252 in Custom OS install screen.
Symptom : Automatic setup with redundancy option is not present during RAID configuration.
Workaround : Go to custom and you can create RAID levels which support redundancy.
Symptom: The driver for QLE8242 cannot be installed using the Driver Update Utility.
This section lists the open caveats for Cisco UCS SCU Release 3.0 and Cisco Driver Update Utility Release 3.0 and contains the following topics:
Symptom : While installing RHEL 6.1, the following error message may appear indicating that message server support group does not exist:
Workaround : Press Continue to proceed with the installation.
Symptom: USB flash drives are not detected by UCS SCU. Also, USB flash drives with NTFS format cannot be mounted.
Workaround: Complete the following steps to detect the USB flash drive through UCS SCU:
1. Format the USB flash drive using fat 32 filesystem.
2. Perform USB reset from virtual media and attempt to detect the drive through UCS SCU.
If this procedure does not solve the problem, change the USB flash drive.
Symptom: Clicking the Back button in the Online Help opens the License page of UCS SCU.
Workaround: No workaround exists for this problem.
Symptom: The following error message is displayed while installing Red Hat Enterprise Linux 5.7 servers:
Workaround: Press Cancel when this message appears during installation.
Symptom: While launching the utility, the following error message is displayed:
Workaround: Reboot the server and try again.
Symptom: The Driver Update Utility does not list Broadcom 57712 dual port adapter.
Workaround: Download the latest driver for the adapter from the Cisco Website, or from the driver ISO partition on the Cisco Flexible flash drive.
Symptom Linux mouse emulation is calculated, unlike Windows mouse emulation. There are situations when the KVM Linux mouse emulation gets out of sync with the host's mouse: Novell/SUSE's install DVD for SLES doesn't include mouse acceleration. The X setup for the install DVD is very basic, unlike RHEL's. A mouse will work on SLES once it is installed but lags during the installation.On Linux, you can switch between graphical and text mod using the Ctrl-Alt-F1 for text and Ctrl-Alt-F7 to go back to graphical mode. The KVM Linux mouse emulation sometimes gets out of sync when switching between modes.
Workaround When the mouse gets out of sync in Linux, the user must force KVM to recalculate it. There are two ways to force KVM to recalculate the Linux mouse: 1) In KVM, go to the Tools->Session Options->Mouse tab and press the button for Linux Mouse Acceleration and then press "Apply" and "OK". If the Linux Mouse Acceleration is already selected, the user can still press "Apply" and then "OK" to force it to recalculate. 2) Move the mouse out of the KVM window to the right of the window and back into the KVM window, forcing it to recalculate the mouse position again. (CSCtc12265)
This section lists the known behavior in the Cisco UCS SCU and the Cisco Driver Update Utility Release 4.0(13).
Symptom Upon installing Windows OS using server configuration utility, a pop-up message appears prompting you to confirm the unsigned driver installation.
For configuration information for this release, see the following:
The following related documentation is available for the Cisco Unified Computing System:
For information on obtaining documentation, submitting a service request, and gathering additional information, see What’s New in Cisco Product Documentation at: http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html.
Subscribe to What’s New in Cisco Product Documentation, which lists all new and revised Cisco technical documentation, as an RSS feed and deliver content directly to your desktop using a reader application. The RSS feeds are a free service.