Chapter 1. Cisco UCS C-Series Software Release Notes

- Introduction

- Security Fixes

Introduction

This document describes the new features, system requirements, open caveats and known behaviors for C-Series software release 2.0(12) 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.

In this release, Intel® Xeon® Processor E7-8800 v4 series CPUs support has been added to the C460 M4 servers.

Note

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

- Revision History

- System Requirements

- Hardware and Software Interoperability

- Transceivers Specifications

Revision History

Revision

Date

Description

A0

July 13, 2016

Created release notes for Release 2.0(12b).

B0

August 29, 2016

Following changes were made:

- Updated the Resolved Caveats section.

- Updated the HUU versions to 2.0(12c). The firmware files in Cisco Host Upgrade Utility for individual releases are available at: Cisco UCS C-Series Integrated Management Controller Firmware Files, Release 2.0

C0

October 10, 2016

Following changes were made:

- Updated the VIC firmware to support Windows 2016 server.

- Updated the HUU versions to 2.0(12d). The firmware files in Cisco Host Upgrade Utility for individual releases are available at: Cisco UCS C-Series Integrated Management Controller Firmware Files, Release 2.0

D0

December 23, 2016

Following changes were made:

- Updated the Supported Hardware section.

- Updated the Resolved Caveats section.

- Updated the HUU versions to 2.0(12e). The firmware files in Cisco Host Upgrade Utility for individual releases are available at: Cisco UCS C-Series Integrated Management Controller Firmware Files, Release 2.0

E0

February 22, 2017

Updated the HUU versions to 2.0(12f). The firmware files in Cisco Host Upgrade Utility for individual releases are available at: Cisco UCS C-Series Integrated Management Controller Firmware Files, Release 2.0

F0

April 06, 2018

Following changes were made:

- Added the Security Fixes section.

- Updated the HUU version of the C460 M4 server to 2.0(12g). The firmware files in Cisco Host Upgrade Utility for individual releases are available at: Cisco UCS C-Series Integrated Management Controller Firmware Files, Release 2.0

G0

August 01, 2018

Following changes were made:

- Updated the Security Fixes section.

- Updated the HUU version of the C460 M4 server to 2.0(12h). The firmware files in Cisco Host Upgrade Utility for individual releases are available at: Cisco UCS C-Series Integrated Management Controller Firmware Files, Release 2.0

H0

October 20, 2019

Following changes were made:

- Updated the Security Fixes section.

- Updated the HUU version of the C460 M4 server to 2.0(12i). The firmware files in Cisco Host Upgrade Utility for individual releases are available at: Cisco UCS C-Series Integrated Management Controller Firmware Files, Release 2.0

System Requirements

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

- Sun JRE 1.8.0_92 or later (Till 1.8.0_121)

- HTML based interfaces are supported on:

- Microsoft Internet Explorer 10.0 or 11

- Mozilla Firefox 30 or higher

- Google Chrome 38 or higher

- Safari 7 or higher

Note

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

- For Classic View - all browsers must have Adobe Flash Player 11 plug-in or higher. Supported browsers are:

- Microsoft Internet Explorer 11 or higher

- Mozilla Firefox 54 or higher

- Google Chrome 61 or higher

- Safari 11 or higher

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

- Transport Layer Security (TLS) version 1.2.

Overview of Cisco UCS C460 M4 Rack Servers

The Cisco UCS® C460 M4 Rack Server provides the performance and reliability to run mission-critical applications and virtualized workloads that require intensive computation processing and very high memory capacity. Applications that are memory-bound (for example, large-scale virtualization, massive database applications, and server consolidation) will benefit from the increased performance and memory footprint of the Cisco UCS C460 M4.

The Cisco UCS C460 M4 is a four-rack-unit (4RU) rack server supporting the Intel® Xeon® E7-4800 v2/v3 and E7-8800 v2/v3/v4 processor families. Product highlights include:

- Up to 6 terabytes (TB) of double-data-rate 3 (DDR3) memory in 96 DIMM slots or double-data-rate 4 (DDR4) memory in 96 DIMM slots

- Up to 12 Small Form Factor (SFF) hot-pluggable SAS, SATA, or SSD disk drives

- Abundant I/O capability with 10 PCI Express (PCIe) Generation 3 (Gen 3) slots supporting the Cisco UCS virtual interface cards (VICs). An internal slot is reserved for a hard-disk drive array controller card

- Two Gigabit Ethernet LAN-on-motherboard (LOM) ports, two 10-Gigabit Ethernet ports, and a dedicated out-of-band (OOB) management port that provides additional networking options

The Cisco UCS C460 M4 Rack Server offers industry-leading performance and advanced reliability well suited for the most demanding enterprise and mission-critical workloads, large-scale virtualization, and database applications. Whether the Cisco UCS C460 M4 is used as a standalone system or in a Cisco Unified Computing System™ (Cisco UCS) deployment, customers gain the benefits of the server’s high-capacity memory when very large memory footprints such as the following are required:

- SAP workloads

- Database applications and data warehousing

- Large virtualized environments

- Real-time financial applications

- Java-based workloads

Hardware and Software Interoperability

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

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

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

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

Transceivers Specifications

The Cisco UCS C-Series servers supports a wide variety of 10 Gigabit Ethernet connectivity options using Cisco 10GBASE SFP+ modules.

Controllers and SFP+ Twinax Transceivers Support Matrix

Controllers (LOM and PCIe)

10GBASE-CU SFP+ Cable 1 Meter, passive

10GBASE-CU SFP+ Cable 3 Meter, passive

SFP-H10GB-CU1M

SFP-H10GB-CU3M

Cisco UCS Virtual Interface Cards

x

x

Intel x520

Broadcom 57712

x

x

Controllers (LOM and PCIe)

10GBASE-CU SFP+ Cable 5 Meter, passive

10GBASE-CU SFP+ Cable 7 Meter, active

10GBASE-CU SFP+ Cable 10 Meter, active

SFP-H10GB-CU5M

SFP-H10GB-ACU7M

SFP-H10GB-ACU10M

Cisco UCS Virtual Interface Cards

x

x

x

Intel x520

Broadcom 57712

x

x

x

Controllers and SFP+Optical Transceivers Support Matrix

Controllers (LOM and PCIe)

Intel SR Optics

JDSU (PLRXPL-SC-S43-22-N) SFP+

Cisco SFP-10G-SR

Cisco UCS Virtual Interface Cards

NA

NA

x

Intel x520

x

NA

NA

Broadcom 57712

NA

x

x

Firmware Files

The C-Series software release 2.0(12) includes the following software files:

CCO Software Type

File name(s)

Comment

Unified Computing System (UCS) Server Firmware

ucs-c460m4-huu-2.0.12.iso

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

Host Upgrade Utility

Unified Computing System (UCS) Drivers

ucs-cxxx-drivers.2.0.12.iso

Drivers

Unified Computing System (UCS) Utilities

ucs-cxxx-utils-efi.2.0.12.iso

ucs-cxxx-utils-linux.2.0.12.iso

ucs-cxxx-utils-vmware.2.0.12.iso

ucs-cxxx-utils-windows.2.0.12.iso

Utilities

Note

Always upgrade the BIOS, the Cisco IMC and CMC from the HUU ISO. Do not upgrade individual components (only BIOS or only Cisco IMC or CMC), since this could lead to unexpected behavior. If you choose to upgrade BIOS, the Cisco IMC and the CMC individually and not from the HUU ISO, make sure to upgrade both Cisco IMC, BIOS and CMC to the same container release. If the BIOS, CMC 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, CMC and all other server components (VIC, RAID Controllers, PCI devices, and LOM) together.

Host Upgrade Utility

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

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

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

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

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

- SIOC

- Cisco VIC Adapters

- LSI Adapters

- LAN on Motherboard Settings

- PCIe adapter firmware

- HDD firmware

- SAS Expander firmware

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:

http://www.cisco.com/c/en/us/support/servers-unified-computing/ucs-c-series-rack-servers/products-user-guide-list.html

Supported Hardware

Release 2.0(12e)

The following hardware is supported in Release 2.0(12e):

- Cisco UCS C460 M4 shipping with Intel® Xeon® Processor E7-8894E series CPUs.

Release 2.0(12b)

The following hardware is supported in Release 2.0(12b):

- Cisco UCS C460 M4 shipping with Intel® Xeon® Processor E7-8800 v4 series CPUs.

- Trusted Platform Module (TPM) version 2.0 - The trusted platform module (TPM) is a small circuit board that connects to a motherboard socket and is secured by a one-way screw.

- DDR4- 2400MHz DIMMS.

Software Utilities

The following standard utilities are available:

- Host Update Utility (HUU)

- BIOS and Cisco IMC Firmware Update utilities

- Server Configuration Utility (SCU)

- Server Diagnostic Utility (SDU)

The utilities features are as follows:

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

Supported Platforms

C460 M4 is the only supported platform in this release.

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 2.0(12i)

The following Security Fixes were added in Release 2.0(12i):

Release

Defect ID

CVE

Symptom

2.0(12i)

CSCvp34790

CSCvp34799

- CVE-2018-12126

- CVE-2018-12127

- CVE-2018-12130

- CVE-2019-11091

Cisco UCS C-Series and S-Series M4 servers are based on Intel® Xeon® Processor E7 v2, v3, and v4 Product Family processors that are vulnerable to variants of exploits that use Microarchitectural Data Sampling (MDS) to gain access to data being processed in the CPU by other applications.

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

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

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

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

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

Security Fixes in Release 2.0(12h)

The following Security Fixes were added in Release 2.0(12h):

Release

Defect ID

CVE

Symptom

2.0(12h)

CSCvj59326

- CVE-2018-3639

- CVE-2018-3640

Cisco UCS C-Servers M4 servers are based on Intel® EX Series processors that are vulnerable to variants of an exploit that uses CPU speculative processing and data cache timing to efficiently leak information, known as Spectre.

CVE-2018-3639 (Spectre/Variant #4) and CVE-2018-3640 (Spectre/Variant #3a) are addressed by applying the updated processor microcode from Intel included in the server firmware bundle, and the relevant Operating System and Hypervisor patches from the appropriate vendors.

This release includes BIOS revisions for Cisco UCS M4 generation servers that are based on Intel® EX Series processors. These BIOS revisions include the updated processor microcode that is a required part of the mitigation for CVE-2018-3639 (Spectre/Variant #4) and CVE-2018-3640 (Spectre/Variant #3a).

For more information, please see the Cisco Security Advisory at: CPU Side-Channel Information Disclosure Vulnerabilities: May 2018

Security Fixes in Release 2.0(12g)

The following Security Fixes were added in Release 2.0(12g):

Release

Defect ID

CVE

Symptom

2.0(12g)

CSCvh51224,

CSCvg97979

- CVE-2017-5715

- CVE-2017-5753

- CVE-2017-5754

Cisco UCS C-Series servers are based on Intel processors that are vulnerable to exploits that use CPU speculative processing and data cache timing to potentially identify privileged information. These exploits are collectively known as Spectre and Meltdown.

- CVE-2017-5753 Spectre/Variant 1 – is addressed by applying relevant Operating System and Hypervisor patches from the appropriate vendors.

- CVE-2017-5715 Spectre/Variant 2 – is addressed by applying the updated microcode included in the UCS C-Series release as well as the relevant Operating System and Hypervisor patches from the appropriate vendors.

- CVE-2017-5754 Meltdown – is addressed by applying the relevant operating system patches from the appropriate vendors.

This UCS C-Series release includes the BIOS revisions for Cisco UCS M4 generation servers that includes the updated microcode that is a required part of the mitigation for CVE-2017-5715 (Spectre/Variant 2).

For more information, please see the Cisco Security Advisory at: https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20180104-cpusidechannel

Release 2.0(12e)

The following defect is resolved in release 2.0(12e):

External Controllers

Defect ID

Symptom

First Affected Release

Resolved in Release

CSCux96072

During heavy I/O, the Cisco 12G Modular RAID controller may go offline with the "Storage Controller SLOT HBA inoperable" message logged in the Cisco IMC event logs.

2.0(8g)

2.0(12e)

Release 2.0(12c)

The following defect is resolved in release 2.0(12c):

BIOS

Defect ID

Symptom

First Affected Release

Resolved in Release

CSCva38325

On the C460 M4 servers, under a heavy CPU or memory load, Machine Check Exceptions (MCE) in the Linux syslog and/or correctable QPI errors in the System Event Log (SEL) may be reported. These MCE and SEL logs do not impact the system operation.

2.0(12b)

2.0(12c)

Release 2.0(9e)

The following defects are open in release 2.0(9e):

BIOS

Defect ID

Symptom

Workaround

First Affected Release

CSCuy15543

On the Cisco IMC Web UI and CLI the actual boot order is displayed incorrectly when you configure the IpmiBootOrder from Cisco IMC using the Configpolicy.xml file that is used to configure the precision boot order policy.

None. The incorrect boot order should be ignored. The functionality works as expected and the BIOS setup displays the actual boot order correctly.

2.0(9e)

Release 2.0(9d)

The following defects are open in release 2.0(9d):

BMC

Defect ID

Symptom

Workaround

First Affected Release

CSCut36603

An error message stating that the Supercap has degraded is displayed during a transparent learn cycle. This issue occurs when the server contains a RAID controller using a SuperCap and is running a Cisco IMC firmware lower than 2.0(4c). Additionally, the Supercap in the learn cycle has a low charge.

Configure the SNMP monitoring tools to ignore this fault.

2.0(1b)

Release 2.0(9c)

The following defects are open in release 2.0(9c):

BMC

Defect ID

Symptom

Workaround

First Affected Release

CSCux43338

On the Mozilla Firefox web browser 42.0, when you click the 'Paste Server Certificate' option on the Web UI, the pop-up dialog box eclipses the 'Save Certificate' and 'Cancel' buttons.

Move the dialog box so as to make the 'Save Certificate' and 'Cancel' buttons visible, or use a different web browser such as Google Chrome or Microsoft Internet Explorer.

2.0(9c)

CSCux31845

The Web UI is unresponsive when you swap a virtual drives physical drive with an external physical drive more than once.

Power cycle the system and wait for the BIOS POST to completely recover the unresponsive UI page.

2.0(9c)

CSCuw76431

While installing Red Hat Enterprise Linux 7.1 operating system on the UCS C-Series servers, a critical SEL entry similar to this is created: The 2015-10-12 10:35:07 critical "System Software event: OS Event sensor, unknown event".

None.

2.0(9c)

External Controllers

Defect ID

Symptom

Workaround

First Affected Release

CSCuw86750

When physical drives containing all Virtual drives are removed or replaced, the system displays a fault "configuration lost" which remains unchanged until a virtual drive is created or the configuration is cleared using WebBIOS or Ctrl +R function.

Create a virtual drive or clear a configuration using Web BIOS or Ctrl+R function.

1.5(1)

CSCux44506

If a boot virtual drive is marked hidden after setting a different virtual drive as boot drive, and if the system is running from the previously configured boot virtual drive, the system may shut down based on the operating system.

None.

2.0(9c)

CSCux05183

Enabling the "Pass for password at boot time" feature when enabling controller Security to support SED drives (self encrypting drives) feature from LSI host applications such as MSM or StorCli results in the boot time password to be entered multiple times when the system is rebooted.

This feature is not supported at this time due to multiple issues. You can enable drive security but not check the box for enabling the "Pause for password at boot time". The "Pause for password at boot time" is secondary layer of security and is an optional feature.

2.0(9c)

CSCuw64844

The PXE boot is disabled by default on the Emulex adapter. This issue might occur when the adapter is set to factory default settings or the PXE is manually disabled from the option ROM.

Enable the PXE option ROM on the adapter using BIOS or the Emulex HBAnyware Command Line tool (hbacmd).

2.0(9c)

CSCuw83402

Unable to install the be2iscsi drivers using shell script on SUSE Linux Enterprise 11 Service Pack 4.

The be2iscsi drivers available in the driver iso are packaged in the tar.gz format. Untar the tar.gz and intall the rpm file manually; using rpm -ivh file.rpm

2.0(9c)

VIC

Defect ID

Symptom

Workaround

First Affected Release

CSCuv49700

While using RoCE on a Cisco VIC interface, other features such as VMQ, NVGRE, VxLAN, and usNIC should not be configured on the same VIC interface in order to avoid hardware resource conflict.

None

2.0(7d)

CSCuw10248

With Cisco VIC adapter, NetFlow, usNIC, VM-FEX, VMQ and iSCSI functionality will not work when VXLAN is enabled on the vNIC.

None. Stateless offloads with VXLAN cannot be used with NetFlow, usNIC, VM-FEX, VMQ and iSCSI.

2.0(7)

CSCuv42027

The Priority Flow Control (PFC) mode is always set to 'Standard' on the Cisco VIC adapter if the corresponding switchport's PFC mode is set to ON. This results in the PFC mode not being enabled.

Set the switchport's PFC mode to 'Auto'.

2.0(9c)

CSCux40259

Booting SLES 12 SP1 the first time fails with the message "dracut: FATAL: FCoE requested but kernel/initrd does not support FCoE". The issue occurs only with a SAN install or boot, when you provide the async driver during installation.

Continue installation with inbox driver and subsequently, update the driver.

2.0(9c)

CSCuw17399

When you check the transceiver details after an active optical cable of length seven meters is connected from the Cisco UCS VIC 1387 adapter to a Nexus 3016Q switch, it fails to detect the QSFP type. When we check the transceiver details, it does not detect the QSFP type of connector.

None.

2.0(9c)

Release 2.0(8d)

The following defects are open in release 2.0(8d)

BIOS

Defect ID

Symptom

Workaround

First Affected Release

CSCuv41113

The Windows server 2012 R2 is unresponsive when you install or boot a pre-installed image on a TXT enabled C460 M4 server. This happens only when TXT is enabled using BIOS.

None.

2.0(7)

CSCuv82922

You cannot disable the drive security from the Human Interface Infrastructure (HII) of MSM on the C220 M4 BIOS. This happens with the self-encrypting drives on the C220 M4.

Use the keys Ctrl + R on the legacy BIOS setup to disable security.

2.0(8)

Release 2.0(4c)

The following defects are open in release 2.0(4c):

Cisco IMC

Defect ID

Symptom

Workaround

First Affected Release

CSCul95481

The DIMM temperature sensors are not displayed in the Web UI or CLI interfaces.

No workaround. However, use raw IPMI commands to access these sensor readings, which are located in the Cisco Extended SDR.

2.0(4c)

CSCuj63232

Certain long running operation data may show erroneous data. In other words, it may indicate that an operation is currently running when it is not. For example, the consistency check operation shows 0% progress and is stuck at that status. This problem can occur at any time, but commonly it has been seen after doing a CIMC upgrade.

There is no known way to clear the data. To verify that the data is erroneous, use an LSI tool such as WebBios or MegaCli to see if an operation is in progress.

2.0(4c)

BIOS

Defect ID

Symptom

Workaround

First Affected Release

CSCut07986

OS fails to boot with max VD count (i.e 64) created in LSI controllers. This issue would happen with the Servers configured with max number of VD count in LSI controller. in

Please create lesser than 32 VD count in the LSI controller

2.0(4c)

CSCut37666

In the JBOD mode, after creating the precision boot order for the HDDs connected to the Cisco 12G Modular SAS Pass through controller, the HDDs do not appear in the created order. This issue applies to LSI controllers with JBOD capability.

Use F6/Setup Boot order control for controlling the System boot order

2.0(4c)

LOM

Defect ID

Symptom

Workaround

First Affected Release

CSCun71765

The 10GE LOM port (X540 based) flaps when the host reboots while the CIMC is in Shared LOM 10G network mode. This event may drop connections to the CIMC including the Virtual Media and vKVM.

- CIMC network mode is Shared LOM 10G

- Host reset 10GE LOM PHY. Usually happens on host reboot, driver load/unload or speed change

Do not use Shared LOM 10G network mode if using Virtual Media or vKVM during host boot.

2.0(4c)

HUU

Defect ID

Symptom

Workaround

First Affected Release

CSCus94537

HDD firmware update using HUU takes time as the HDD firmware is updated sequentially. This increases the time to upgrade a server which has many HDD

None

2.0(3d)

LSI

Defect ID

Symptom

Workaround

First Affected Release

CSCun50408

Creating VD from StorCli and WebBIOS, the default disk policy shown after creation is inconsistent in different UI. MegaRAID Storage Manager shows Unchanged and StorCli shows "Disk's default"

None. Both Unchanged and Disk's Default means the same in this case. Cisco supported Drives have disk cache policy = Disabled so in this case the Disk's Default or Unchanged refer to the same indicating the Disk cache is disabled.

2.0(4c)

CSCuq35761

LSI applications such as StorCli and MSM and CIMC Storage management allows JBOD with Operating system or File system to be converted to Unconfigured Good drives without meaningful error message indicating there could be data loss in such cases.

Users should be aware that there is going to be data loss when JBOD which has OS or File system is converted to Unconfigured Good. LSI Applications like MSM and StorCli prompt users with "Are you sure" message so users need to be careful to understand there will be data loss in such cases if they chose to convert JBOD with OS or File system to Unconfigured good drives. CIMC storage management allows JBOD to be converted to Unconfigured Good without any Warning Pop-Up message. Again users need to be make sure that there is no OS or Filesystem when they choose to convert JBOD to Unconfigured Good drives.

2.0(4c)

Open Caveats in Release 2.0(3d)

The following defects are open in release 2.0(3d):

CIMC

Defect ID

Symptom

Workaround

First Affected Release

CSCuq11190

Slow network performance between VMs in OVM 3.3.1.

None.

2.0(3d)

BIOS

Defect ID

Symptom

Workaround

First Affected Release

CSCup56423

Actual boot order does not have the information to identify which LUN is assigned to LSI sSATA, LSI SATA, and different HDDs in AHCI mode.

Set the ROM mode option to UEFI only.

2.0(3d)

CSCup51154

The HII interface for 9300 is blank when 9300 external LSI adapter is present and ROM mode option is enabled.

None.

2.0(3d)

CSCuq35131

Correctable error is sometimes displayed in SEL after installing the device driver for the Nvidia K40 adapters.

Reboot the server.

2.0(3d)

CSCuq15093

Unable to choose the EFI boot options using the PCHStorage policy device from Cisco IMC, when BIOS boot mode is in EFI and EFI OS is installed in any of the SATA drives.

Press F6 to choose the required EFI boot option to boot from.

2.0(3d)

Release 2.0(2c)

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

Defect ID

Symptom

Workaround

First Affected Release

CSCuq56061

The WebUI stops responding when BIOS/CMC is updated using Internet Explorer 10.0 browser client.

Launch the WebUI using any other version of Internet Explorer other than 10.0 or use any other browser client.

2.0(2c)

Defect ID

Symptom

Workaround

First Affected Release

CSCuq15528

In the legacy boot mode, a few boot options do not appear in the menu or boot override page. This is an intermittent issue and happens when there are multiple boot options with SATA/RAID connected and UEFI boot options are disabled in the boot options.

If you want to boot from a particular option which does not appear on the menu or the override options, run the policy from Cisco IMC, or press F2 and set the device as the first boot device. All the devices will be listed correctly on the boot options page.

2.0(2c)

CSCup19648

You may see intermittent I/O timeout when the virtual drives are configured in Cached-IO mode. This is limited to virtual RAID volumes created in Cached-IO mode to take full advantage of the RAID Cache and to reduce the drive speed overhead and keep using slow drives. When the virtual drives are created in the Cached-IO mode set, and since the virtual drives are inconsistent, background initialization happens to make the virtual drives consistent. At this time, if the host I/Os are issued to load the drives and RAID cache in full load, the I/Os are blocked for short intervals which exceed the host OS expectations of the I/O time and they timeout.

1. Perform a full initiation of the virtual drive when created.

2. Set the host or application I/O timeout to a higher value.

2.0(2c)

CSCun63438

If the host I/Os are at high loads with continuous write access to the drives, the completion time for the background operations exceeds a month.

Increase the background operation rate to 100%. This reduces the operation time.

2.0(2c)

Known Behaviors in Release 2.0(12b)

Following is the known behavior for Release 2.0(12b):

Cisco IMC

Defect ID

Symptom

Workaround

First Affected Release

CSCuz30387

On the C460 M4 servers, host serial port (PMCLI) does not work when the host is powered off.

Power on the host.

2.0(12b)

Known Behaviors in Release 2.0(9c)

Following are the known behaviors for release 2.0(9c)

BMC

Defect ID

Symptom

Workaround

First Affected Release

CSCun99348

When virtual KVM is disabled, the Play Recording action on the Troubleshooting screen fails.

Enable Virtual KVM on the Remote Presence tab.

2.0(1)

CSCuv08978

Management port MTU cannot be configured due to hardware limitations.

None.

1.5(4)

CSCuj36245

After restoring to factory defaults, when you import the BIOS tokens on the target machine, the values remain unchanged.

Power on the target machine and try the import operation after the BIOS post is completed.

2.0(1)

BIOS

Defect ID

Symptom

Workaround

First Affected Release

CSCun99297

Cannot select specific USB thumb drive under boot option priorities.

Use F6 from the boot selection menu to select specific USB drives.

2.0(1)

CSCuo08591

System becomes unresponsive in the POST after the SD card removal when the host is powered on.

1. AC cycle the system after removing the SD card.

2. Reinsert the SD card.

2.0(4c)

CSCun91835

Boot order varies when enabling or disabling the Option ROM.

None.

2.0(1)

CSCur61234

In the secure boot mode, a security violation error is triggered. This issue could also occur while trying to perform an AC power cycle, when the power characterization is enabled in the UEFI secure mode.

None.

2.0(4)

LSI

Defect ID

Symptom

Workaround

First Affected Release

CSCum87051

Random behavior of system freeze at boot @ BIOS POST screen for around 2 minutes followed by "Waiting for Battery Pack" message on LSI Ctrl-R BIOS for another 2 minutes. This only happens if there is a learn cycle pending for the supercap and the host is restarted (either AC/DC/reboot). At all other reboot/power cycle, this does not happen.

There is no work-around at this time.

2.0(4c)

CSCuu86314

On M4 servers, the iMR (Zero-memory) RAID Controller supports up to 32 virtual drives, but the command to create virtual drives in a single drive group allows only 16 virtual drives.

None. The RAID controller supports 32 virtual drives across all drive groups and only 16 drives in a single drive group.

2.0(6)

CSCum87232

Cisco IMC storage BBU info shows the Pack Energy value below the design capacity. This is also seen in the storcli /cX /cv show all command. On the current shipping 6G SAS RAID Controllers with Supercap, the Pack energy is always above the design capacity. This is a change in behavior confuses the user and makes the user think the supercap has or is going bad and gets a worrisome situation of the data integrity.

There is no work-around at this time. This is just a display issue and does not impact the actual functionality or data integrity.

2.0(4c)

CSCuw69844

On the servers with 2008M-8i, the VMware ESXi 5.5 Update 1 install fails while loading the installer.

1. Go to System BIOS (Press F2)

2. Choose PCI configuration > MMCFG

3. Change the value from Auto to 2 GB

4. Change the value of Memory Mapped IO above 4G to Enabled

5. Save and reboot the system.

2.0(7)

External Controllers

Defect ID

Symptom

Workaround

First Affected Release

CSCuw42070

The MegaRAID Storage Manager fails to detect a new 6TB HGST drive with yellow amber LED. This happens when the drive is corrupted and displays an SAS link failure.

None.

2.0(8)

CSCuw55045

SAS Flash and MSM utilties are unable to downgrade the IT firmware if the Network Virtualization (NV) data version changes. To downgrade the NV data version, use the FlashOEM tool bundled with the Host Upgrade Utility (HUU).

Do not use SAS Flash and MSM utilities to downgrade the IT firmware. Use these to only use the HUU.

2.0(9c)

CSCuw09414

Powering off Virtual machines (VM) with the Virtual Graphics Processor unit (vGPU) takes 90 to 120 seconds in VMware ESXi 6.0.

Power off smaller number of VMs at one time.

2.0(4c)

External OS

Defect ID

Symptom

Workaround

First Affected Release

CSCuw80507

According to the knowledge base at https://access.redhat.com/solutions/21322, using IPMI commands on the Red Hat Enterprise Linux results in the over use of CPU resources.

Add the following command at the end of the kernel line in /etc/grub.conf: ipmi_si.kipmid_max_busy_us=<time in microseconds>

1.5(2)

Known Behaviors in Release 2.0(8d)

Following are the known behaviors for release 2.0(8d):

BMC

Defect ID

Symptom

Workaround

First Affected Release

CSCul16923

The fault code F0181 is raised by CIMC when the local disk is removed while the rack server was in use. This fault is visible through CIMC WebUI, CLI and SNMP interfaces. But the same fault is not retrievable through the XML API interface.

None.

1.5(4)

CSCuj40520

Upgrading firmware with Host Upgrade Utility (HUU) can cause temporary storage faults while the upgrade is in progress. These faults are benign and will clear once the upgrade is complete.

None.

1.5(4)

Cisco IMC

Defect ID

Symptom

Workaround

First Affected Release

CSCuq23984

Cisco IMC does not respond during OOB update of utility virtual drives (SCU/HUU/Drivers) on flex flash.

It is recommended that host reboot actions are not performed while running OOB update of utility virtual drives on flex flash.

2.0(3d)

Web Management

Defect ID

Symptom

Workaround

First Affected Release

CSCuv63101

User gets logged out of the Web UI occasionally, after upgrading the Cisco IMC firmware from 2.0(6) to 2.0(8). This happens when browser cookies are not cleared.

Clear the browser cookies.

2.0(7)

BIOS

Defect ID

Symptom

Workaround

First Affected Release

CSCun00121

Cannot create boot option for partitions in SD card.

None.

2.0(1)

CSCul84767

The system locks up while running memtest86 from memtest.org. The problem is seen only with memtest86 from memtest.org.

Do no use memtest86 from memtest.org on C460 M4. Please use PassMark or any other memory test tools that have the support for IvyBridge EX platforms instead.

2.0(4c)

CSCun02543

Port number attributes are missing in the actual boot order for the FC and FCOE cards.

None.

2.0(1)

External Controllers

Defect ID

Symptom

Workaround

First Affected Release

CSCut92393

On the C240 M4 servers, on rare occasions, the Cisco 12 Gigabyte SAS Modular RAID Controller displays an error when you try deleting a virtual drive.

None.

2.0(6)

CSCuv34371

When creating new virtual drives of any RAID type, the write cache policy defaults to 'write through' even with a fully functional BBU or super-capacitor battery. When a BBU is present, the default write cache policy should be 'write back with good BBU'. This happens on the C240 M4 and C220 M4 servers with 12 gigabyte SAS mezzanine RAID controllers.

In the standalone mode, on the Ciso IMC storage tab of the Web UI, edit the virtual drive to set the write caching policy to 'write back with good BBU'. You can also modify the setting using the LSI command line option rom config utility .

2.0(3d)

CSCuv36714

The MegaRAID Storage Manager displays consistency check errors on RAID 1 volume in Windows. This happens when you try writing data to the drive 20 to 30 minutes after a consistency check (which appears to be normal).

This is a known Microsoft limitation. For more information, see https://support.microsoft.com/en-us/kb/2713398

2.0(4c)

External GPU Expanders

Defect ID

Symptom

Workaround

First Affected Release

CSCuv04922

On the C240 M4 server, A "PCI Resource Error" message is seen with the Magma Chassis GPU Expander configuration due to a CPU I/O space limitation which supports a maximum of 64K. This happens when all or some of the PCI slots are occupied by different third party adapters.

For Nvidia Grid K1 configuration: (where one Nvidia Grid K1 is internally connected on the C240 M4, and two Nvidia Grid K1 adapters are externally connected through the Magma Chassis)

- Local Boot: Cisco 12 Gigabyte SAS Modular RAID controller (HBA slot), Intel I350 LOM (L slot), Nvidia Grid K1 (slot2), Magma Expander HBA (slot5), Teradici APEX2800(slot6), Fusion IO drive(slot4)

- iSCSI Boot: Intel i350 LOM (L slot), Nvidia Grid K1(slot2), Magma Expander HBA (slot5), Teradici APEX2800(slot6), Fusion IO drive(slot4)

- SAN Boot: CISCO VIC1227(MLOM), Nvidia GRID K1 (slot2), Magma Expander HBA (slot5), Teradici APEX2800(slot6), Fusion IO drive(slot4)

For Nvidia Grid K2 configuration: (where one Nvidia GridK2 is internally connected on the C240 M4, and four Nvidia Grid K2 adapters are externally connected through the Magma Chassis)

- Local Boot: CISCO 12G SAS Modular RAID controller (HBA slot),Intel I350 LOM (L slot), Nvidia GRID K2 (slot2), Magma Expander HBA (slot5), Teradici APEX2800(slot6), Fusion IO drive(slot4)

- iSCSI Boot: Intel i350 LOM(L slot), Nvidia Grid K2 (slot2), Magma Expander HBA (slot5), Teradici APEX2800(slot6), Fusion IO drive(slot4)

- SAN Boot: CISCO 1227 SAN (MLOM), Nvidia Grid K2 (slot2), Magma Expander HBA (slot5), Teradici APEX2800(slot6), Fusion IO drive(slot4)

2.0(4c)

Known Behaviors in Release 2.0(6d)

Following are the known behaviors for release 2.0(6d):

External Controller

Defect ID

Symptom

Workaround

First Affected Release

CSCui64842

Hardware configuration settings of Broadcom 57810 adapters reset after firmware update. This issue happens on all 57810 adapters. The following settings are reset:

- DCB Protocol

- SRIOV

- Number of VFs per PF

Reconfigure the settings.

1.5(3)

CSCuu35160

While downgrading or upgrading LSI firmware, Cisco IMC log reports several CMD over OOB errors. This is expected behavior and the error messages are due to the controller being briefly unresponsive on out-of-band during firmware update.

None.

2.0(3e)

CSCuu36101

MegaRAID card does not support raid level migration when the card has maximum allowed number of virtual drives created on it.

Note

This is a limitation of the MegaRAID software stack that requires a temporary or ghost VD to do the RLM operation.

Do not create maximum number of allowed virtual drives.

2.0(6d)

VIC

Defect ID

Symptom

Workaround

First Affected Release

CSCuu56903

Data traffic between VMs where the vNICs have the same uplink on VIC 1225, could not be switched upstream.

Assign vnic0,vnic1 pinned to Uplink-1 and vnic6,vnic7 to Uplink-2.

1. Note This may affect the physical uplink redundancy.

2.0(3e)

Known Behaviors in Release 2.0(4c)

Following are the known behaviors for release 2.0(4c):

Cisco IMC

Defect ID

Symptom

Workaround

First Affected Release

CSCut76388

For the C220 M4 and the C240 M4 servers, power consumption with 1400W PSUs fluctuates when power cap enabled and the power cap value is set towards a lower value within the allowed range.

Set a higher power cap value. For example, if the allowed power cap range is 350W-650W, then set a value higher than 500W.

2.0(4c)

CSCuq39610

The following error appears while configuring SD cards: ERROR_METADATA_EXSISTS

Remove and insert the SD card and re-configure. If the error persist, replace the SD card.

2.0(3d)

BIOS

Defect ID

Symptom

Workaround

First Affected Release

CSCur74413

Watchdog timer policy values change while upgrading or downgrading the BIOS firmware between 2.0(3d) and 2.0(3f) versions.

Reset the values after the BIOS firmware upgrade or downgrade.

2.0(3d)

CSCut05524

TxT getting disabled after few reboots.

Use the TPM Clear command in the BIOS to reset the counter and start over again.

2.0(3e)

LSI

Defect ID

Symptom

Workaround

First Affected Release

CSCus54600

LSI9271-8i shows Storage Controller Inoperable? fault in UCSM (PMU Fault present in event log)

Replace the LSI9271-8i adapter

2.0(3i)

CSCus68862

Ubuntu (all versions available today) does not have the inbox drivers for any of the IT-based adapters.

None

2.0(3d)

VIC

Defect ID

Symptom

Workaround

First Affected Release

CSCut78400

Resetting a VIC adapter to default configuration, using the CLI command adapter-reset-defaults, may result in changing of the default MAC addresses. This may require configuration of the DHCP and OS to correct the changes to the default MAC addresses. The occurs for releases 2.0(4) and later due to moving of the default MAC address range to address certain VIC relates issues.

None.

2.0(4c)

External OS

Defect ID

Symptom

Workaround

First Affected Release

CSCuq75761

During installation of Red Hat Enterprise Linux 7, SAN LUNs mapped will not be visible. Server experiences kernel panic, when Red Hat Enterprise Linux 7 OS is installed on local storage and a SAN LUN is mapped.

No workaround. A driver update disk may be available later to address this issue.

2.0(2c)

External Controllers

Defect ID

Symptom

Workaround

First Affected Release

CSCuq43129

OL 5.9 and OL 5.10 operating systems do not recognize QLE2672 SAN LUN during installation.

None.

2.0(3d)

CSCuq60947

Citrix XenCenter 6.2 configured VM instances fails to boot when driver is passed and vGPU is disassociated.

Perform the following steps to disassociate vGPU from VM instance:

1. From the VM console, choose Start > Control Panel > Hardware and Sound > Device Manager > Display Adapters > Nvidia K1 or K2.

2. Right click and choose Uninstall .

3. Power off the VM from XenCenter console.

4. In th eXenCenter console, open VM Properties.

5. Right click the GPU in left column and choose GPU type: > None.

6. Boot up the VM.

2.0(3d)

Known Behaviors in Release 2.0(3d)

Following are the known behaviors for release 2.0(3d):

BIOS

Defect ID

Symptom

Workaround

First Affected Release

CSCuq99268

For the ESXi 5.5 and later updates, you can install the OS on a disk behind Cisco 9300 HBA using the native inbox driver (lsi-msgpt3). However, lsi_msgpt3 is not fully supported. Therefore it must be disabled and the async drivers must be installed.

After installing the OS, complete the following steps to install the mpt3sas drivers:

1. #esxcli software vib install -v file:/{FULL_PATH_TO_YOUR_VIB(...xxx.vib)}

2. Disable lsi-msgpt3 (native driver) using the following command: #esxcfg-module ?d lsi-msgpt3

3. If the system is restarted, as a rule, the mpt3sas driver should take over. Verify this using the following command:

~ # esxcli storage core adapter list: HBA Name Driver Link State UID Description -------- ------- ----------- ---------- ----------------------------------------------- vmhba0 ahci link-n/a sata.vmhba0 Intel Corporation Patsburg 6 Port SATA AHCI .. vmhba1 mpt3sas link-n/a sas.xxxxxxx LSI / Symbios Logic SAS3008 PCI-Express .. vmhba32 ahci link-n/a sata.vmhba32 Intel Corporation Patsburg 6 Port SATA AHCI .. vmhba33 ahci link-n/a sata.vmhba33 Intel Corporation Patsburg 6 Port SATA AHCI .. vmhba34 ahci link-n/a sata.vmhba34 Intel Corporation Patsburg 6 Port SATA AHCI .. vmhba35 ahci link-n/a sata.vmhba35 Intel Corporation Patsburg 6 Port SATA AHCI .. vmhba36 ahci link-n/a sata.vmhba36 Intel Corporation Patsburg 6 Port SATA AHCI ..

4. If the driver name is still listed as lsi-msgpt3 for the above command, try removing (instead of disabling) lsi-msgpt3 using the following command: #esxcli software vib remove ?n lsi-msgpt3

5. Restart the system.

2.0(3d)

CSCup89033

The Power Monitoring graph is displayed on top of all pages if the Power Monitoring page is loading and you navigate to any other page.

Navigate back to the Power Monitoring page and wait till the page loads and then navigate to any other page.

2.0(3d)

CSCuq00837

On C220 M4 and C240 M4 servers, TPM fails to initialize after installing ESXi 5.1 U2 Patch 05, and enabling and activating TPM and TXT.

No workaround.

2.0(3d)

CSCuq04009

ESXi installer does not detect any SD card in xHCI mode.

Disable USB xHCI mode in the BIOS.

2.0(3d)

CSCuo28585

HII Drive Management and Enclosure Management menu displays only one port/connection (0-3) and not the other (4-7) when an expander is connected to a controller through two ports.

No workaround.

2.0(3d)

CSCuq14862

With inbox IGB driver in SLES 11 SP3, ethtool shows incorrect firmware version for Intel i350 LOM after installing the drivers for Intel i350 LOM from 2.0(3d) drivers ISO(5.2.5).

Update the igb version to 5.2.5. Unload and load the igb.

2.0(3d)

CSCuq24196

After installing the Windows Server 2012 to an iSCSI LUN, few network adapters display a yellow bang in the device manager (code 10) with the following description: This device is not working properly because Windows cannot load the drivers required for this device This occurs only on the NICs that are used for iSCSI boot.

Perform one of the following: A hotfix is available for Windows 8 and Windows Server 2012. Run this fix in the Windows OS image and then perform iSCSI installs. For more information on the fix, see http://support.microsoft.com/kb/2822241 OR Complete the following steps

:

1. Un-install the drivers for the device which is showing yellow bang without deleting the device.

2. Re-install the drivers.

3. Restart the server.

2.0(3d)

CSCup82749

Windows 2K12 R2 iSCSI Boot with Intel i350 and Pinecrest adapters displays BSOD when it is installed using the inbox drivers.

While installing the W2K12 R2 iSCSI, skip the Intel drivers from the drivers ISO. Reboot the server once the installation is finished.

2.0(3d)

CSCuq92331

Bandwidth test fails while running synthetic benchmarks, like the nvqual. This happens when the processor power management is enabled.

Disable the processor power management option using the BIOS setup.

2.0(3e)

CSCuo05774

Setting the boot mode to UEFI or Legacy requires two reboots for the change to reflect.

Reboot the server twice.

2.0(3e)

CSCul04884

Server enters BIOS setup menu when the boot devices that are configured in the service profile are not found. This impacts only C-series servers that are managed by Cisco UCS Manager.

None.

2.0(3e)

CSCuj28644

UEFI PXE boot or UEFI iSCSI boot does not work when the boot mode is set to UEFI.

Use the legacy boot mode when using PXE or iSCSI boot.

2.0(3e)

Cisco IMC

Defect ID

Symptom

Workaround

First Affected Release

CSCuo26946

When you upgrade from releases 1.5(x) to 2.0(x) or downgrade from 2.0(x) to 1.5(x) or migrate from legacy to precision boot order, and if the SD card has four partitions, BIOS boot order mismatch occurs for the SD cards.

No workaround. You have to re-configure the boot order.

2.0(3d)

CSCuq32910

When the server boots with 2.0.3d release firmware, it fails to update the HUU firmware version and displays the current version of the Emulex OCe14102/Oce11102 as Not .

Reboot the server.

2.0(3d)

External Controller

Defect ID

Symptom

Workaround

First Affected Release

CSCup87719

i350 adapter with default factory configuration dispatches the boot protocol Option ROM only for the first port. It does not dispatch Option ROM for the remaining 3 ports of the i350 card.

Enable the boot option for required ports using boot Util.

2.0(3d)

Known Behaviors in Release 2.0(1b)

Following are the known behaviors for Release 2.0(1b):

Cisco IMC

Defect ID

Symptom

Workaround

First Affected Release

CSCup49368

When you click Update All to upgrade from version 1.5.7 to 2.x using the Cisco Host Upgrade Utility the chassis firmware does not get updated.

Using the Web UI, complete these steps to upgrade the chassis firmware:

1. In the Navigation pane, click the Server tab.

2. On the Server tab, click Summary.

3. In the Actions area, click Power Off Server.

4. Click OK to power off the server and updates the system firmware.

Using the CLI, complete these steps to upgrade the chassis firmware:

1. Server# scope chassis

2. Server /chassis # scope firmware

3. Server /chassis/firmware # show detail: Firmware update required on some components, please run update-all (under chassis/firmware scope).

4. Server /chassis/firmware # update-all

2.0(1b)

CSCup58906

When you downgrade to 2.0(1a), Cisco IMC Web UI displays warning messages and critical events.

A/C Power cycle the sever.

2.0(1b)

Known Behaviors in Release 2.0(1)

Following are the known behaviors for the Release 2.0(1):

Cisco IMC

Defect ID

Symptom

Workaround

First Affected Release

CSCth84883

The LED sensor color is red or amber or blue (or any supported color) even though the LED state is set to OFF.

Ignore the LED color when the LED state is set to OFF.

2.0(1)

CSCtt08424

Cisco IMC power capping is not supported on VMware ESXi 5.0.

When Cisco IMC is upgraded to 1.4(2), the Cisco IMC will automatically disable power capping. Power capping must manually be re-enabled to use it.

2.0(1)

CSCun97225

When you downgrade from release 2.0(1a) to a 1.5(x) release, you see only seven platform event filters instead of 12 filters.

Restore factory default settings or run the Cisco OEM function command on the ipmitool raw 0x36 0x03 0xAA .

2.0(1)

CSCuo40835

When you downgrade from release 2.0(1a) to a 1.5(x) release, if you have set the SNMP port value to anything other than the default value (161), you cannot reset this number.

Before downgrading, set the SNMP port to 161 or after downgrading restore factory defaults.

2.0(1)

CSCun10320

Cannot upgrade Cisco IMC firmware version from 1.5(3d) to 2.0(1a) using FTP.

Use a browser or SCP client upgrade.

2.0(1)

CSCum70086

Downloaded DVR player fails to play offline for Java versions 6 and below on Windows OS.

Edit and update the script_win.bat file with the correct Java version.

2.0(1)

CSCun66062

While using the CLI to define the precision boot order, if multiple devices' orders are changed by scoping to an individual device, the final order of the devices may not appear as what it was changed to.

Use the rearrange-boot-device command to set the boot order for multiple devices. Or use the Cisco IMC Web UI.

2.0(1)

CSCum26002

A delay occurs while pinging to check the connectivity to the DNS servers before a DDNS update is triggered.

You can manually check the connectivity to the preferred and alternate DNS servers for both the IPv4 and IPv6 addresses the using the ping option available in this release.

2.0(1)

CSCun11979

Cannot configure legacy boot order using the Cisco IMC Web UI.

Use CLI or XML API.

2.0(1)

CSCuo71634

After upgrading the Cisco IMC firmware and activating secure boot mode, when you immediately try to reboot Cisco IMC, it does not respond.

After the upgrade, reboot Cisco IMC after about 10 minutes.

2.0(1)

Known Behaviors in Release 1.5.7

Following are the known behaviors for Release 1.5(7):

CIMC

Defect ID

Symptom

Workaround

First Affected Release

CSCul62033

During heavy I/O transactions on the SD card, read errors may be seen in CIMC.

Use Cisco FlexFlash 3.0 cards

1.5(7)

CSCua94308

There is no CIMC notification of Closed Loop Thermal Throttling (CLTT) when it occurs. CLTT happens automatically when the DIMM temperature crosses the UC (upper critical) temperature.

None.

1.5(7)

CSCuo18891

UCScfg_X64.exe batch - ignore set t.txt command displays "Error: Invalid Number of Arguments" error message, when the input file is in Unicode format.

Use ANSI format input file. (

1.5(7)

CSCud84978

SEL has memory entries, but no entries are seen in the fault page. Cisco UCSM fault codes are unavailable for these SEL.

None. SEL has to be used to decode the memory related events.

1.5(1)

OS

Defect ID

Symptom

Workaround

First Affected Release

CSCun77988

After installation of ESXi in UEFI mode, the OS fails to boot up. The installation completes, but on the subsequent reboot, the server does not boot ESXi OS.

To resolve this issue, complete these steps:

1. Boot to Shell.

2. Determine fsxx (xx is where ESX is installed. It will be typically 0 i.e fs0:) This can be verified by using fsxx:\EFI\Boot\BOOTX64.EFI command.

3. To get the current list of EFI Boot options use, bcfg boot dump command.

Note

Save the last boot number for further use.

4. Use the following command to add new Boot Option at position LAST_BOOT_NO + 1. Last parameter in quotes can be any description for this new Boot Option. This is displayed during BIOS F6 menu - bcfg boot add LAST_BOOT_NO + 1 fsxx:\EFI\BOOT\BOOTX64.EFI "UEFI: ESXi"

5. Make the newly created Boot Option for ESX as the first by using bcfg boot mv LAST_BOOT_NO + 4 1 command.

Reset the platform by issuing reset command at the shell. Press F6 when BIOS is booting to get into BIOS Boot Selection menu. Verify that newly created Boot Option is displayed. Select this and boot to ESX.

1.5(7)

NVIDIA

Defect ID

Symptom

Workaround

First Affected Release

CSCuo39368

Nvidia GPU cards non functional or erratic behavior on system beyond 1 TB of memory.

This is an Nvidia GPU limiation due to 40 bit addressing on the GPU's. The memory should be 1 TB or less for the GPU's to be functional.

1.5(7)

LSI

Defect ID

Symptom

Workaround

First Affected Release

CSCue88244

Prepare for removal prepares a Hard drive for removal but LED on the HDD does not blink AMBER to indicate the drive is ready to be replaced. This happens only on direct connect C260 M3 configurations.

None.

1.5(4)

CSCui29979

BBU Charging Status shows either Charging or Discharging all the time. This could lead to confusion to customers as Charging or Discharging indicate that battery is not in optimal state.

Customers should use the BBU Status field to determine if the battery is in optimal state. If the BBU status is optimal, it will indicate a good battery. If the BBU status indicates battery needs replacement, then the BBU is bad and needs to be replaced. Charging Status is working as designed and will always indicate Charging or Discharging because Firmware keeps checking the battery charge and ensures that the charge does not fall below the band gap. It charges the battery when it is in lower limits and once it reaches the upper limit of the band, it will stop charging. There can be leakage current which can discharge the battery and bring it back to lower threshold. When this happens, the firmware initiates charging.

1.5(2)

Best Practices to Install VMWare

Workaround for Installing VMWare on First Generation (Gen 1) SD Cards in Expert Mode

Once you start the installer application, find the partition where you want to install VMWare. In the following example the partition is vmhba33:C0:T0:L0.

1. Press Alt+F1 to enter the VMWare recovery console.

2. Create a GUID Partition Table (GPT) on the disk:

/dev/disks # partedUtil mklabel mpx.vmhba33:C0:T0:L0 gpt

3. Verify the GPT:

/dev/disks # partedUtil get mpx.vmhba33:C0:T0:L0

3785 255 63 60817408

4. Return to installing VMWare.

Upgrading BIOS and Cisco IMC Firmware

Cisco provides the Cisco Host Upgrade Utility to assist you in upgrading the BIOS, Cisco IMC, CMC LOM, LSI storage controller, and Cisco UCS Virtual Interface Cards firmware to compatible levels. On the C220 M3, C240 M3, C22 M3, and C24 M3 servers, we recommend that you reboot Cisco IMC before performing the Cisco IMC and BIOS firmware update using NIHUU, HUU, web UI, CLI, or XML API.

Note

When upgrading the Cisco IMC firmware for the UCS C-series platforms, ensure that you update using the full image (for example upd-pkg-cXXX-mx-Cisco IMC.full.*.bin).

The correct and compatible firmware levels for your server model are embedded in the utility ISO.

To use this utility, use the Cisco Host Upgrade Utility User Guide which includes the instructions for downloading and using the utility ISO. Select the guide from this URL:

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

Related Documentation

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

- Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide

- Cisco UCS C-Series Servers Integrated Management Controller GUI Configuration Guide

- Cisco UCS Rack-Mount Servers Cisco IMC API Programmer's Guide

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

- 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

Notices