First Published: March 31, 2016

Last Updated: October 20, 2019

Cisco UCS C-Series Software Release Notes

Introduction

This document describes the new features, system requirements, open caveats and known behaviors for C- series software release 2.0(10) including Cisco Integrated Management Controller software and any related BIOS, firmware, or drivers. Use this document in conjunction with the documents listed in the “Related Documentation” section.


Note

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

Revision History

Revision

Date

Description

A0

March 31, 2016

Created release notes for Release 2.0(10b).

B0

June 02, 2016

Following changes were made:

C0

July 4, 2016

Following changes were made:

D0

August 30, 2016

Following changes were made:

E0

October 10, 2016

Following changes were made in this release:

F0

December 23, 2016

Following changes were made in this release:

G0

April 06, 2018

Following changes were made in this release:

H0

August 01, 2018

Following changes were made in this release:

I0

August 29, 2018

Update the Security Fixes section.

J0

October 20, 2019

Following changes were made in this release:

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 the Server Models

Overview of Cisco UCS C240 M4 Rack Servers

The enterprise-class Cisco UCS C240 M4 server extends the capabilities of the Cisco UCS portfolio in a 2RU form -factor. Based on the Intel® Xeon® processor E5-2600 v3 and v4 series, it delivers an outstanding combination of performance, flexibility, and efficiency. In addition, the Cisco UCS C240 M4 offers outstanding levels of internal memory and storage expandability with exceptional performance. It delivers:

  • Up to 24 DDR4 DIMMs for improved performance and lower power consumption

  • Up to 6 PCI Express (PCIe) 3.0 slots (4 full-height, full-length)

  • Up to 24 small-form factor drives or 12 large form-factor drives, plus two (optional) internal SATA boot drives

  • Support for 12-Gbps SAS drives

  • A modular LAN-on-motherboard (mLOM) slot for installing a next-generation Cisco virtual interface card (VIC) or third-party network interface card (NIC) without consuming a PCIe slot

  • Supports two double-wide Nvidia graphics processing units (GPUs), providing a graphics-rich experience to more virtual users

  • Excellent reliability, availability, and serviceability (RAS) features with tool-free CPU insertion, easy-to-use latching lid, hot-swappable and hot-pluggable components, and redundant Cisco® Flexible Flash (FlexFlash) SD cards.

The Cisco UCS C240 M4 Rack Server with the Intel Xeon processor E5-2600 v3 and v4 series product family is well suited for a wide range of storage and I/O-intensive applications such as:

  • Big data

  • Collaboration

  • Small and medium-sized business (SMB) databases

  • Virtualization and consolidation

  • Storage servers

  • High-performance appliances

The Cisco UCS C240 M4 can be deployed as standalone servers or as part of the Cisco Unified Computing System, which unifies computing, networking, management, virtualization, and storage access into a single integrated architecture that enables end-to-end server visibility, management, and control in both bare-metal and virtualized environments. Within a Cisco UCS deployment, the Cisco UCS C240 M4 takes advantage of Cisco’s standards-based unified computing innovations, which significantly reduce customers’ total cost-of-ownership (TCO) and increase business agility.

Overview of Cisco UCS C220 M4 Rack Servers

The enterprise-class Cisco UCS C220 M4 server extends the capabilities of the Cisco UCS portfolio in a 1RU form factor. It incorporates the Intel® Xeon® processor E5-2600 v3 and v4 series product family, next-generation DDR4 memory with a supported speed of upto 2400 MHz, and 12-Gbps SAS throughput, delivering significant performance and efficiency gains. The Cisco UCS C220 M4 rack server delivers outstanding levels of expandability and performance in a compact 1RU package:

  • Up to 24 DDR4 DIMMs for improved performance and lower power consumption

  • Up to 8 Small Form-Factor (SFF) drives or up to 4 Large Form-Factor (LFF) drives and PCIe SSDs

  • Support for 12-Gbps SAS Module RAID controller drivesin a dedicated slot; leaving remaining two PCIe Gen 3.0 slots available for other expansion cards

  • A modular LAN-on-motherboard (mLOM) slot that can be used to install a Cisco UCS virtual interface card (VIC) or third-party network interface card (NIC) without consuming a PCIe slot

  • Two embedded 1Gigabit Ethernet LAN-on-motherboard (LOM) ports

The Cisco UCS C220 M4 Rack Server with the Intel Xeon processor E5-2600 v3 and v4 series product family is excellent for a wide range of enterprise workloads, including:

  • IT and web infrastructure

  • High-performance virtual desktops

  • High-performance virtual desktops

  • Middleware

  • Collaboration

  • Public cloud

Cisco UCS C220 M4 can be deployed as standalone servers or in an UCS-managed environment. When combined with Cisco UCS, the Cisco UCS C220 M4 brings the power and automation of unified computing to enterprise applications, including SingleConnect technology that drastically reduces switching and cabling requirements. Cisco UCS Manager with service profiles enables rapid deployment and end-to-end server visibility, management, and control in both virtualized and bare-metal environments. The Cisco UCS C220 M4 is the most versatile general-purpose enterprise infrastructure and application server in the industry.

Overview of the Pre-Installed Cisco Flexible Flash Card

Starting with version 1.5(4), the SD storage device is available to Cisco IMC as a single hypervisor (HV) partition configuration. Prior versions had four virtual USB drives.

Refer to the following documents for more information about these tasks:

  • Replacing a card: Refer to any of the following:

    • Cisco UCS C220 M4 Server Installation and Service Guide

    • Cisco UCS C240 M4 Server Installation and Service Guide

  • Enabling and booting a VD: Cisco UCS C-Series Servers Integrated Management Controller GUI Configuration Guide or the Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide

  • Monitoring and managing a card with Cisco IMC: Cisco UCS C-Series Servers Integrated Management Controller GUI Configuration Guide or the Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide

The links to these documents are in the C-Series documentation road map:

http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/overview/guide/UCS_rack_roadmap.html

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.

Table 1. 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
Table 2. 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 Upgrade Details

Firmware Files

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

CCO Software Type File name(s) Comment
Unified Computing System (UCS) Server Firmware

ucs-c220m4-huu-2.0.10.iso

ucs-c240m4-huu-2.0.10.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.10.iso Drivers
Unified Computing System (UCS) Utilities

ucs-cxxx-utils-efi.2.0.10.iso

ucs-cxxx-utils-linux.2.0.10.iso

ucs-cxxx-utils-vmware.2.0.10.iso

ucs-cxxx-utils-windows.2.0.10.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 following firmware:

  • Cisco Integrated Management Controller (Cisco IMC)

  • System BIOS

  • SAS-EXPANDER

  • LAN on motherboard (LOM)

    • Intel Ethernet i350 PCI Server Adapter

    • Intel I350 mLOM

  • Cisco VIC Network Controller Adapters

    • Cisco Adapter UCS VIC 1225

    • Cisco Adapter UCS VIC 1225T

    • Cisco Adapter UCS VIC 1227

    • Cisco Adapter UCS VIC 1227T

    • Cisco Adapter UCS VIC 1385

    • Cisco Adapter UCS VIC 1387 MLOM

  • Broadcom PCI adapters:

    • 5709 Dual port adapters

    • 5709 Quad port adapters

  • Intel PCI adapters:

    • i350 Quad port adapter

    • X520 Dual port adapter

    • X540 Dual port adapter

  • QLogic PCI adapters:

    • 2562 dual port adapter

    • 2672 dual port adapter

    • 8362 dual port adapter

    • 8442 10Gb dual port SFP+

    • 8442 10Gb dual port 10 GBaseT

  • Emulex PCI adapters:

    • LightPulse LPe12002 adapter

    • LightPulse LPe16002 adapter

    • OneConnect® OCe14102B dual-port adapter

    • OneConnect® OCe14102 dual-port adapter

  • LSI

    • Cisco UCSC RAID SAS 12G SAS Modular Raid Controller

    • Cisco 12G Modular SAS Pass through Controller

    • LSI MegaRAID SAS 9300-8E

  • Fusion-io

    • Fusion-io ioDrive3 1000G

    • Fusion-io ioDrive3 1300G

    • Fusion-io ioDrive3 1300G-SX350

    • Fusion-io ioDrive3 1600G-SX350

    • Fusion-io ioDrive3 2600G

    • Fusion-io ioDrive3 3200G

    • Fusion-io ioDrive3 3200G-SX350

    • Fusion-io ioDrive3 5200G

    • Fusion-io ioDrive3 6400G

    • Fusion-io ioDrive3 6400G-SX350

  • Nvidia

    • Nvidia GRID K1

    • Nvidia TESLA K10

    • Nvidia TESLA K20

    • Nvidia TESLA K20xm

    • Nvidia GRID K2

    • Nvidia TESLA K40

    • Nvidia TESLA K80

    • Nvidia M60 PG402-060 M60

  • PCIESSD

    • Cisco UCS 1.6 TB 2.5 in NVMe based PCIeSSD

    • Cisco UCS 800GB 2.5 in NVMe based PCIeSSD

  • Hard Disk Drives

    • ST9146853SS

    • ST9300653SS

    • ST300MM0006

    • ST600MM0006

    • ST900MM0006

    • ST9500620SS

    • ST91000640SS

    • MZ6ER200HAGM

    • MZ6ER400HAGL

    • MZ6ER800HAGL

    • ST1000NM0001

    • ST2000NM0001

    • ST500NM0011

    • AL13SEB300

    • AL13SEB600

    • AL13SEB900

    • ST9300605SS

    • ST9600205SS

    • ST9900805SS

    • MK1001TRKB

    • MK2001TRKB

    • ST33000650SS

    • ST3600057SS

    • ST9146803SS

    • ST9300603SS

    • ST9500530NS

    • MTFDDAK100MAR

    • MTFDDAK400MAR

    • ST1000NX0423

    • ST2000NM0033

    • ST6000NM0014

    • SSDSC2BB120G6K

    • SSDSC2BB480G6K

    • SSDSC2BB016G6K

    • SSDSC2BX480G4K

    • SSDSC2BX016G6K

    • MZ7GE240HMGR

    • MZ7GE960HMHP

    • MZIES800HMHP

    • HUC109030CSS600

    • HUC109060CSS600

    • HUC109090CSS600

    • HUC101812CSS200

    • HUC101860CS4200

    • HUC101818CS4200

    • HUS724020ALS640

    • HUS724030ALS640

    • HUS724040ALS640

    • HUS726060AL4210

    • HUH728080AL4200

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

Starting with 1.4 release, separate ISO images of Host Upgrade Utility are available for different server platforms.

The ISO image is now named as ucs-<server_platform>-huu-<version_number>.iso.

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

Updating the Firmware

Use the Host Upgrade Utility to upgrade the C-Series firmware. Host Upgrade Utility can upgrade the following software components:

  • BIOS

  • Cisco IMC

  • CMC

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

Supported Software Features

The following software features are supported in Release 2.0(10b):

  • Added support for Smart Access: Serial that allows offline configuration of C-series servers using the command line interface (CLI) via serial connection. With this setup, you are not required to connect the Cisco IMC to the network in order to access the command line interface.

  • Added a new mount option sec=value under the mount type CIFS for Cisco IMC-mapped vMedia.

Supported Hardware

Release 2.0(10h)

The following hardware is supported in Release 2.0(10h):

  • Intel® Xeon® CPU E5-2699A v4 @ 2.40 GHz

Release 2.0(10b)

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

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

  • Intel® Xeon® processor E5-2600 v4 series

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

Selected Platforms

This section lists the supported platforms for this release:

  • UCS-C220 M4

  • UCS-C240 M4

Security Fixes

Security Fixes in Release 2.0(10l)

The following Security Fixes were added in Release 2.0(10l):

Release

Defect ID

CVE

Symptom

2.0(10l)

CSCvp34786

  • 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 E5 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(10k)

The following Security Fixes were added in Release 2.0(10k):

Release

Defect ID

CVE

Symptom

2.0(10k)

CSCvm03353

  • CVE-2018-3615

  • CVE-2018-3620

  • CVE-2018-3646

Cisco UCS C-Series M4 (except C460 M4) 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 L1 Terminal Fault (L1TF).

  • CVE-2018-3615 (affecting SGX), also known as Foreshadow, is not known to affect any existing Cisco UCS servers because Cisco UCS M5 and earlier generation servers, and HyperFlex M5 and earlier generation servers do not use Intel® SGX technology.

  • CVE-2018-3620 (affecting OS/System Management Mode) and CVE-2018-3646 (affecting Virtual Machine Monitors) are referred to as L1 Terminal Fault attacks by Intel®. These vulnerabilities are mitigated 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 (except 460 M4) generation servers. These BIOS revisions include the updated processor microcode that is a required part of the mitigation for CVE-2018-3620 (OS/SMM) and CVE-2018-3646 (VMM). Operating System and Hypervisor patches from the appropriate vendors may also be required to mitigate these vulnerabilities.

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

2.0(10k)

CSCvj59318

  • CVE-2018-3639

  • CVE-2018-3640

Cisco UCS C-Servers M4 servers are based on Intel® EP 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® EP 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(10i)

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

Release

Defect ID

CVE

Symptom

2.0(10i)

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

Resolved Caveats

Release 2.0(10g)

The following defect was resolved in release 2.0(10g):

Table 3. HDD Firmware
Defect ID Symptom First Affected Release Resolved in Release
CSCux11611 Hard drives spinning idly for a long time are prone to failure. This occurs when the drives continue to spin in a powered system without an OS installed, or in a JBOD configuration without any read or write activity. 2.0(9f) 2.0(10g)

Release 2.0(10f)

The following defects are resolved in release 2.0(10f):

Table 4. BIOS
Defect ID Symptom First Affected Release Resolved in Release

CSCva82009

The OS on servers 2.0(10b) and 2.0(10f) running on the Intel E5 Xeon v4 CPUs may crash with a signature pointing to internal parity errors, page fault , general protection fault or invalid operational code errors.

2.0(10b)

2.0(10f)

Table 5. VIC
Defect ID Symptom First Affected Release Resolved in Release

CSCva29365

Enabling stateless offloads for NVGRE in a third generation Cisco VIC adapters’ configuration with UCSM/CIMC leads to inaccessible vNIC interfaces in the host OS for the following third generation VIC adapters:

  • UCSC-C3260-SIOC

  • UCSB-VIC-M83-8P

  • UCSB-MLOM-40G-02

  • UCSB-MLOM-40G-03

  • UCSC-PCIE-C40Q-03

  • UCSC-MLOM-C40Q-03

This affects only the managed UCS deployments and standalone NIV mode deployments. Classical Ethernet operation is unaffected.

2.0(10b)

2.0(10f)

CSCva01733

PXE in Legacy Boot mode fails if there is an excessive unicast or multicast high background traffic with a packet size larger than MTU directed to the client server. This was seen with ESXi Autodeploy on a specific setup which likely had unusually high multicast traffic directed at the client server. This traffic was not from the PXE server for file transfer, but from some other source.

2.0(10b)

2.0(10f)

Release 2.0(10e)

The following defects are resolved in release 2.0(10e):

Table 6. BIOS
Defect ID Symptom First Affected Release Resolved in Release

CSCuz10784

You cannot configure Cisco IMC network port speed using the F8 utility.

2.0(10b)

2.0(10e)

CSCuy45141

When a TPM operation is triggered from OS, it results in a server reboot. During the reboot, the BIOS prompt message is truncated; and the "F12" keyword is not visible.

2.0(10b)

2.0(10e)

Table 7. External Controller
Defect ID Symptom First Affected Release Resolved in Release

CSCux53224

A fatal error is observed when you create or remove virtual drives with RAID 5 and RAID 6 controller combination.

2.0(10b)

2.0(10e)

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(10e)

Open Caveats

Release 2.0(10h)

The following defect is open in release 2.0(10h):

Table 8. BIOS
Defect ID Symptom Workaround First Affected Release
CSCvc06842 On the C220 M4 and C240 M4 servers, the VMware ESXI operating system becomes non responsive. Subsequently VMware disconnects and triggers Cisco IMC SEL events such as PROCHOT, MEMHOT and processor configuration error. This happens if you use a Broadcom 5709 card on the server.

Disable the PCI-E ASPM BIOS token. You can disable the token using one of the following interfaces:

  1. BIOS setup—F2 BIOS settings -> Advanced -> PCI Subsystem Settings

  2. Web UI—Under the BIOS tab: Advanced-> PCI Subsystem Settings, set the PCI-E ASPM token to Disable.

  3. CLI—scope bios/advanced and set ASPMSupport disabled

2.0(10h)

Release 2.0(10b)

The following defects are open in release 2.0(10b):

Table 9. VMware
Defect ID Symptom Workaround First Affected Release
CSCux87650 On servers with VMware ESXi 5.5.0 or later, the storecli is able to identify the adapter but unable to communicate with the storage controller. Disable the affected module from the ESXi command line and use the following command to communicate with the controller:

  1. esxcli system module set --enabled=false --module=lsi_mr3

  2. ~# esxcli system module set --enabled=false --module=lsi_mr3

  3. ~# reboot

2.0(10b)
Table 10. BIOS
Defect ID Symptom Workaround First Affected Release
CSCux01460 After you perform a power characterization, under advance power profile it displays an incorrect power range to cap the memory. This results in ineffective memory domain power capping. Run the platform power capping instead. 2.0(10b)
CSCuy42471 In cases when TPM is not available, the SIMBIOS OEM table is populated indicating that TPM is present. None. 2.0(10b)
Table 11. VIC
Defect ID Symptom Workaround First Affected Release
CSCuy23450 On a UCS C-Series server managed using Cisco IMC standalone (not managed by UCS Manager), network connections to Cisco IMC may fail because the IP address assigned to Cisco IMC is not reachable on the IP network. This problem affects servers when a Cisco UCS VIC adapter 1385 or 1387 is used to access Cisco IMC (NIC mode: "Cisco Card") and the VIC adapter uplinks are configured in NIV mode. Unselect VN-Tag mode and select Classical Ethernet mode. 2.0(10b)

Release 2.0(9e)

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

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

Table 13. CMC
Defect ID Symptom Workaround First Affected Release
CSCux55063 On the C3260 server, the Fault History and System Event Log may contain entries incorrectly indicating that all chassis fans were removed, then reinstalled several seconds later. This issue might occur during a CMC reboot or CMC failover event. None. The incorrect entries should be ignored. 2.0(8)
Table 14. BMC
Defect ID Symptom Workaround First Affected Release
CSCux19735 On the C3160 server, the HDD LEDs on the left hand side of the server do not function as expected. None. 2.0(8)
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)
Table 15. External Controllers
Defect ID Symptom Workaround First Affected Release
CSCuw24325 On the C3260 server, when a specific bad drive (or a tentatively bad drive) is used, the LSI controller crashes due to IO timeout when used in single-drive RAID0 configuration. None. Replace the drive with a good one. 2.0(7d)
Table 16. Web Management
Defect ID Symptom Workaround First Affected Release
CSCuv51153 On the C3260 server, you may be prompted to logout from the UI session indicating that a session is already active. Manually clear the browser cookies. 2.0(7d)
Table 17. VIC
Defect ID Symptom Workaround First Affected Release
CSCuv71938 On the C3260 server, the VIC adapter may not be discovered by HUU if the HUU is booted simultaneously on both server nodes. Boot and run HUU on each server node sequentially instead of in parallel. 2.0(7d)
CSCux78046 On the C3260 server, the link state of the SIOC Ethernet port is shown as DOWN when the LR4 or SR-BiDi cables are used. Do not use the said cables with SIOC ports, use other supported media instead. 2.0(9d)
CSCuw26987 On the C3260 server, the "Connector Present" and "Connected Supported" parameters fail with a warning message. The command line output displays 'NA'. None. 2.0(7d)

Release 2.0(9c)

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

Table 18. 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)
Table 19. 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)
CSCuv51716 The C240 M4 server connected to a Magma Chassis GPU Expander with Multiple Tesla (k40/K80) cards, occasionally becomes unresponsive during a reboot using the RedHat Enterprise Linux 6.x operating system. Perform a hard reboot to the server. 2.0(9c)
CSCux28724 On the C240 M4 server, update to the NVidia driver fails on the RedHat Linux Enterprise 7.0 or 7.1 for Tesla K40m and Telsa K80 adapters. Run the driver installation in single-user mode or disable the server before installing the driver. 2.0(9c)
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)
Table 20. 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)

Table 21. LSI
Defect ID Symptom Workaround First Affected Release
CSCuv45574 On C220/C240 M3 systems with LSI 9271-8i controller, after downgrading the firmware to Release 2.0(3f) or lower with HUU update all, the virtual machines running on the ESXi OS become inaccessible. SUSE operating systems are also impacted and will not boot after upgrade. See the following VMware knowledge base: http://kb.vmware.com/kb/1011387 2.0(4c)
CSCuv67943 On the C3160 server, the MSM Application displays a pop-up message reporting a defective slot. However, the error is displayed for one slot number below it. For instance, if slot number 31 is a defective slot, the error displays slot 30 as the defective slot. Add a single number to the error message to view the correct slot number. 2.0(8)
Table 22. 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)
Table 23. External OS Red Hat
Defect ID Symptom Workaround First Affected Release
CSCut38161 On the C240 M4 server, installation of the Red Hat Enterprise Linux fails on the Seagate 1.8TB 4K Drive. None. See the following knowledge base: https://access.redhat.com/solutions/1199273 2.0(4c)

Release 2.0(7d)

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

Table 24. Utilities
Defect ID Symptom Workaround First Affected Release
CSCuv66222 On the C3260 server, the running CMC firmware version is not activated after a firmware update when the HUU firmware update is running on both server nodes. Activate the firmware using WebUI or CLI. 2.0.7(d)

Release 2.0(4c)

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

Table 25. 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)
Table 26. 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)
Table 27. 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)
Table 28. 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)
Table 29. 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 Caveat in Release 2.0(3f)

The following defect is open in release 2.0(3f):

Table 30. LSI
Defect ID Symptom Workaround First Affected Release
CSCur36216 On the C240 M4 servers, HII may not work on the 9300-8e and 9300-8e controllers and may result in changing the OpROM settings when one of the controller's slot is set to UEFI Only mode and the other to Enabled or Legacy mode. Set both controller slots to UEFI Only in the LOM and PCIe Slots Configuration settings. 2.0(3f)

Open Caveats in Release 2.0(3d)

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

Table 31. CIMC

Defect ID

Symptom

Workaround

First Affected Release

CSCuq11190

Slow network performance between VMs in OVM 3.3.1. None. 2.0(3d)
Table 32. 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)
CSCun24358 C220 M4 and C240 M4 servers do not reboot on pressing F10 after changing the adapter settings using HII interface from BIOS setup. The servers continues to boot and the new settings do not take effect. Manually reboot the servers. 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)

Release 1.5(1)

The following defect is open in release 1.5(1):

Table 33. CIMC

Defect ID

Symptom

Workaround

First Bundle Affected

CSCue00749

When a RAID controller cannot load its drive configuration, no fault is generated.

Check manually whether drive configuration has been lost.

1.5(1)

Open Caveats in Release 1.4(7)

The following defects are open in release 1.4(7):

Table 34. CIMC

Defect ID

Symptom

Workaround

First Affected Release

CSCud18756

LSI storage controllers with external ports (-8e cards) do not show up in CIMC local storage management.

None.

1.4(7)

Known Behaviors

Known Behaviors in Release 2.0(10e)

Following is the known behavior for Release 2.0(10e):

Table 35. External Controllers
Defect ID Symptom Workaround First Affected Release
CSCuy42320 If firmware is downgraded to legacy firmware, or Transport Ready is disabled in the new firmware, Transport Ready is cleared in NVRAM. But if the firmware is not a legacy firmware or it does not have Transport Ready implementation, Transport Ready is not cleared. In this case if Transport Ready aware firmware is flashed again, Transport Ready DGs will reappear. You are then required to manually clear Transport Ready. None. 2.0(10b)
CSCux62038 When the Qlogic QLE8362 card is populated in the set-up, the server is unable to boot to BIOS (F2 menu). Use Cisco IMC to configure all BIOS related settings. 2.0(10b)
Table 36. BIOS
Defect ID Symptom Workaround First Affected Release
CSCuy46516 When connected to a Magma chassis with the K80 populated in the chassis, intermittently the server becomes unresponsive during a BIOS POST. None. 2.0(10b)

Release 2.0(10b)

Following are the known behaviors for release 2.0(10b):

Table 37. External Controllers
Defect ID Symptom Workaround First Affected Release
CSCuy11904 ON the C240 M4 server, when the BCM5709 card is present in the server along with the QLE8442 card, during POST (once the ROM option for BCM5709 is activated), you cannot enter the BCM5709 card BIOS by pressing Ctrl+S. Activate the ROM option for both BCM5709 and QLE8442 cards. 2.0(10b)
Table 38. External Nvidia
Defect ID Symptom Workaround First Affected Release
CSCuy41394 On the C240 M4 server, the Nvidia SMI utility might report incorrect utilization even when the CPU is seen as not using any process. The correct utilization should be seen as 0%. Use the command NVidia-smi-1 or activate the persistence mode when using the command nvidia-smi -pm 1. 2.0(10b)
Table 39. BMC
Defect ID Symptom Workaround First Affected Release
CSCux90039 You cannot download the Tech Support data using the Chrome browser.

Try any one of the following options:

1. Use the "Export Technical Support Data to Remote Server" option to generate tech support data.

2. Use browsers other than Chrome.

3. Disable pepper flash in Chrome browser and use normal Adobe shockwave flash. (This workaround has been disabled in latest versions of Chrome).

2.0(10b)

Known Behaviors in Release 2.0(9d)

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

Table 40. External Controllers
Defect ID Symptom Workaround First Affected Release
CSCuu56166 On the C3260 server, after you perform expansion or raid-level migration operations Virtual Drives (VD) do not display the updated size. Complete the following steps:

  1. Unclaim the disk from usage by powering off all the virtual machines before running the following command: ~ esxcli storage core claiming unclaim ?t device ?d naa.xxx

  2. Ensure that the file naa.xxx disk is not located under /vmfs/devices/disks

  3. Reclaim the disk again using the following command:~ esxcli storage core adapter rescan ?A vmhbaX

  4. Check whether or not the disk is added back with the new size.

2.0.7(d)

Known Behaviors in Release 2.0(9c)

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

Table 41. 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)
Table 42. 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)
Table 43. 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)
Table 44. 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)
Table 45. 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):

Table 46. 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)
Table 47. 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)
Table 48. Utilities
Defect ID Symptom Workaround First Affected Release
CSCuu38979 On the C3160 server, HUU may not discover or upgrade the SAS expander. AC power cycle the server and then boot the HUU. 2.0(6d)
Table 49. 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)
Table 50. BIOS
Defect ID Symptom Workaround First Affected Release
CSCun00121 Cannot create boot option for partitions in SD card. None. 2.0(1)
CSCul46981 On the C24 M3 server, hardware error messages such as the ones shown below are displayed while booting to Linux. This happens on unused CPU ports.

{1}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 1 ?

{1}[Hardware Error]: APEI generic hardware error status

{1}[Hardware Error]: severity: 2, corrected

{1}[Hardware Error]: section: 0, severity: 2, corrected

{1}[Hardware Error]: flags: 0x01

{1}[Hardware Error]: primary

{1}[Hardware Error]: fru_text: CorrectedErr

{1}[Hardware Error]: section_type: PCIe error

{1}[Hardware Error]: port_type: 0, PCIe end point

{1}[Hardware Error]: version: 0.0

{1}[Hardware Error]: command: 0xffff, status: 0xffff

{1}[Hardware Error]: device_id: 0000:80:02.3 ?

{1}[Hardware Error]: slot: 0

{1}[Hardware Error]: secondary_bus: 0x00

{1}[Hardware Error]: vendor_id: 0xffff, device_id: 0xffff ?

{1}[Hardware Error]: class_code: ffffff

None. Ignore the error messages. 2.0(4c)
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)
CSCum79756 On the C220 M3 server, occasionally you cannot select a boot device from F6 screen. None. 2.0(1)
CSCun02543 Port number attributes are missing in the actual boot order for the FC and FCOE cards. None. 2.0(1)
Table 51. 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)
Table 52. 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(7d)

Following are the known behaviors for release 2.0(7d)

Table 53. Cisco IMC
Defect ID Symptom Workaround First Affected Release
CSCuv34476 On the 3260 server, KVM fails to launch and displays the following message: "Unable to Launch the application" . This happens after swapping or changing a CMC and making it active or master. Regenerate the certificate using the Web UI or CLI and reboot the CMC. 2.0(7d)
CSCuv28734 On the 3260 server, boot or crash file download fails with a Network error, when you use the Chrome 43 version browser for downloading. Use other browsers or use Chrome version 42. 2.0(7d)
CSCuu50850 On the 3260 server, you cannot establish an IPMI session to a BMC when BMC is reset to factory default. Reconfigure user using active CMC. 2.0(7d)
CSCur77980 On the 3260 server, unable to configure users after resetting CMC to factory defaults. This issue occurs when you attempt to configure a user with a different index number after the reset. Use the same index number that was used before the reset to configure a user. 2.0(7d)
CSCuu43406 On the 3260 server, the server does not respond and displays an error message when the GUI is idle for a few minutes. This happens when you use Chrome Version 41. Use other browsers or use Chrome version 42. 2.0(7d)
CSCuu43330 On the 3260 server, unable to login to Web UI when the login screen is left idle for a few minutes. This happens when you use Crome Version 41. Use other browsers or use Chrome version 42. 2.0(7d)
CSCur60690 On the 3260 server, configuring a user using the CLI or Web UI fails with the following message: "Error: User with same name <username> already exists." When a user is configured using the IPMI on BMC the local user, database may not sync with the active CMC. Hence when the same user is configured with a different index on active CMC this error occurs. Check for the user index number on the local user database on BMC using IPMI and use the same index number to configure the user using the active CMC's CLI or Web UI. 2.0(7d)
Table 54. External Controllers
Defect ID Symptom Workaround First Affected Release
CSCuu36101 On the 3260 server, MegaRAID card does not support raid level migration when the card has maximum allowed number of virtual drives created on it.
Note 

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(7d)

Known Behaviors in Release 2.0(6d)

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

Table 55. 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)
Table 56. 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):

Table 57. 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)
CSCul29595 Mounting an ISO for Network ISO Boot or Firmware Update from a folder depth of 2 or more will result in an error. Use a folder with single depth to mount the ISO. 1.5(3)
CSCuh52878 LSI Nytro MegaRAID8110 controllers do not show up in Cisco IMC storage display None. This is intentional behavior. Due to some differences in the display and management of Nytro controllers, their support will be added in a later Cisco IMC release. 1.5(2)
CSCum58699 After you upgrade Cisco IMC from version 1.4(5e) to 1.5(4) or higher, occasionally Cisco IMC and the host fail to detect the HV partition of Flex Flash. This results in the system boot failure to ESX OS running on HV partition of Flex Flash. Upgrade Cisco IMC from 1.4(5e) to 1.5(2) and perform a reset of the Flex controller to load the latest firmware for Flex Flash. Then upgrade Cisco IMC from 1.5(2) to 1.5(4) and perform a reset of the Flex controller which again loads the latest Flex Flash firmware. To perform the Reset of the flex controller, please refer to the User Guide. 1.5(4)
CSCum60563 Firmware version 1.5(4) does not recognize flex flash SD Card properly.

To recognize the SD card correctly, complete these steps:

  1. Install the SD Card.

  2. Downgrade the firmware to version 1.5(3d)

  3. Synchronize the card with SCU

  4. Upgrade the firmware to version 1.5(4).

1.5(4)
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)
CSCug67576 Cisco IMC CLI and WebUI allow provisioning of usNIC and VMFEX at the same time, but both features are not supported simultaneously. Avoid provisioning usNIC and VMFEX at the same time. Use each feature one at the time. 1.5(3)
CSCue52142 Onboard network devices (LOM) does not get enabled on doing CMOS reset. Rebooting the system again one more after CMOS clear will enable the onboard network devices. 1.5(7)
CSCti17492 When updating Cisco IMC firmware through TFTP, if the image file is corrupted, the update status indicator is the same as if the file does not exist. Be aware that this error message can actually indicate either of the above conditions and should make sure that the file both the exists, and is a valid firmware image for the Cisco IMC being upgraded. 1.4(6)
CSCtz77929 The SEL event is not logged in the OS Watchdog timer expiration. None. 1.4(6)
Table 58. BIOS
Defect ID Symptom Workaround First Affected Release
CSCui32274 UEFI PXE boot is not working in C-series servers. None. This feature is currently not supported. 1.5(2)
CSCun02516 For Intel X520 cards the type of FC volumes are shown as ISCSI instead of SAN. None. 2.0(1a)
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)
CSCuo11185 The UEK R3 or higher kernel does not boot, if the server has any one of the following adapters LPe11002, LPe12002, LPe16002, QLE2462, QLE2562, and QLE2762. Disable the respective PCI slot where the EMULEX/QLogic adapter is present in the server using the BIOS Setup Menu. Save the settings and reboot the server. 2.0(1)
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)
CSCuq72696 LEDs at the back of the C3160 server, next to the SSD drive slots, do not work. The SSD drives are connected to the SATA controller and configured in AHCI Mode. When the SSDs are accessed, there is the does not LED blink to indicate the IO activity on the SSD and also the Fault and Locate LED do not work. Use the Intel RSTe driver for the supported Operating systems to operate the activity LEDs and use the Intel tools to use the Locate LED. 2.0(2c)
Table 59. 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)
CSCud27042 RAID CD-ROM Drive appears in the Boot Options. Booting to this option will give blank screen. This is an invalid option and is not usable and should be ignored. 1.5(1)
Table 60. 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)
CSCue56950 In VIC 1225T, when the system is booted in the 1Gbps mode, the MAC sometimes does not detect the link. PHY seems to detect the link. But the MAC shows a link down error. Reset the switch port. Both Phy and Mac will show the link as up after a switch port reset. 1.5(1)
Table 61. External OS
Defect ID Symptom Workaround First Affected Release
CSCuj10535 Cisco IMC Storage, Storage Log will list many "Unexpected sense: Encl PD 10 pathd7fe00bd, CDB: 1a 00 08 00 ff 00, Sense: 5/00/00". These same events will also show up in /var/log/messages file

VMware seems to treat all storage devices the same way, regardless of whether they are SAS disks or just enclosures. The messages you are seeing means that the host (ESX) was sending mode sense commands to the enclosure and the enclosure does not give a valid response because mode sense commands are not a command that should be sent to an enclosure. So the unexpected sense messages from the enclosure are benign info messages. There is a way to "disconnect" the enclosure from the viewpoint of ESX. It should not have an adverse impact as the enclosure is not a usable storage device. For now, you can try the following:

  1. Open the ESX console.

  2. Run this cmd: "esxcli storage core device list" and look for the device that has "Enclosure" in its name.

  3. Note down it's identifier, usually starting with naa....

  4. Run this command: "esxcli storage core device set --state=off ?d naa.x" but replace naa.x with the your device identifier.

This should eliminate the messages from the vmkernel.log and Cisco IMC Storage log.

 1.5(1)
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)
Table 62. 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)
Table 63. Web Management
Defect ID Symptom Workaround First Affected Release
CSCue76985 Occasionally WEB UI shows Reset link for UCS VIC P81E card. None. Refresh the Web UI. 1.5(1)
Table 64. Hardware
Defect ID Symptom Workaround First Affected Release
CSCui82547 When AC Power is removed the following SEL logs may be recorded.

"Power Supply input out-of-range, but present was asserted" "Power Supply input out-of-range, but present was deasserted"

No work around required; this does not affect negatively operation of the unit. 1.5(2)

Known Behaviors in Release 2.0(3d)

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

Table 65. 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)
Table 66. 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)
CSCuq30109 The Cisco IMC bin file upgrade from release 1.5(x) to 2.0(3d) using Web UI fails in both C24 and C240 M3 with the following error message: HTTP file Too big To upgrade from 1.5(x) to 2.0(3d) use RemoteUpdate (TFTP/HTTP/SFTP) or HUU (recommended). 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)
Table 67. 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):

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

Table 69. 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)
Table 70. BIOS
Defect ID Symptom Workaround First Affected Release
CSCug79131 Software RAID(SWRAID) setup option is visible in the BIOS setup menu for C24 M3 24 HDD Model Servers even though it is not supported feature in this model. By default this option is set to disabled. Do not set this option to enable, as it would cause undefined behavior if set to enabled. 1.5(2)

Known Behaviors in Release 1.5.7

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

Table 71. 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)
Table 72. 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)
Table 73. 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)
Table 74. 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)

Known Behaviors in Release 1.5(4)

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

Table 75. BIOS
Defect ID Symptom Workaround First Affected Release

CSCul36732

SAN boot using Emulex adapters may fail on C-series servers managed by Cisco UCS Manager. This behavior occurs only on servers managed by Cisco UCS Manager.

During the BIOS post, press the hotkey to enter the Emulex Option ROM configuration screen and enable "EDD", save and exit.

1.5(4)

CSCub21433

UEFI OS install is not supported on Software RAID (Onboard SCU controller).

None. Use legacy mode OS installs when using Software RAID.

1.5(4)

CSCtz11862

Continuous beep sound is heard when the system is switched on.

Do not switch on the CIMC and the host simultaneously. Switch on the host 3 minutes after switching on the power supply.

1.5(4)

Table 76. CIMC
Defect ID Symptom Workaround First Affected Release

CSCuj89681

After moving an SD card to the single partition mode, if you downgrade to releases prior to 1.5(4x), all 4 partitions are visible in the WebUI/CLI.

None.

1.5(4)

CSCuj84718

SD card partition sizes appear as trash values for SCU,HUU and drivers during downgrade.

Upgrade to release 1.5(4x) and create a single partition, and then downgrade to a prior release. The partition sizes then appear to be 2097151 MB.

1.5(4)

CSCuj67995

Changing multiple configuration with Port parameter fails from CIMC configuration only.

Complete the following steps:

  1. Set the mode to Dedicated and the redundancy to None.

  2. Save the changes to the system.

  3. Set the auto-negotiation field to Yes.

1.5(4)

CSCuj52943

In the transition from 4 partition configuration to a single partition, only configuration details are modified. Data on the SD remains intact. So after migrating to a single partition (HV), the HV partition will retain SCU data only if SCU has a valid file system during configuration migration.

After migrating to a single partition (HV) configuration, format and install the required OS on the HV partition.

1.5(4)

CSCul50285

ucs-c220-m3# scope bios/advanced

ucs-c220-m3 /bios/advanced #

ucs-c220-m3 /bios/advanced # set ConsoleRedir COM_0

ucs-c220-m3 /bios/advanced *# set BaudRate 115200

ucs-c220-m3 /bios/advanced *# set FlowCtrl None

ucs-c220-m3 /bios/advanced *# set TerminalType VT100+

ucs-c220-m3 /bios/advanced *# commit

ucs-c220-m3 /bios/advanced #

Use the following process:

ucs-c220-m3# scope bios

ucs-c220-m3 /bios #scope advanced

ucs-c220-m3 /bios/advanced # set ConsoleRedir COM_0

ucs-c220-m3 /bios/advanced # commit

Changes to BIOS set-up parameters will require a reboot.

Do you want to reboot the system?[y|N]

1.5(4)

CSCue10121

The PWRGD Sensor's Normal events are logged in the SEL during the CIMC boot and Host boot.

These are expected events and can be ignored.

1.5(4)

CSCuj41445

Auto complete for few fields is done.

Upgrade to 1.5(x) build.

1.5(4)

CSCud17092

Occasionally after a CIMC upgrade, one may see an error dialog box "Error: Unexpected error" in Web UI on main page upon the very first login. The Storage data may also be blank or invalid. Sometimes occurs during the very first login after a CIMC upgrade. It may be related to upgrade from 1.4x to 1.5.

Logging out and back in will fix it, but probably just because it takes time; therefore, just waiting a few minutes and refreshing the WebUI may fix the problem, also.

1.5(4)

Table 77. Cisco usNIC
Defect ID Symptom Workaround First Affected Release

CSCul56178

CIMC limits the configurable vNICs, and usNICs to 229.

None. The remaining vNICs are reserved for the internal adapter usage. Of these remaining vNICs, 4 are mandatory- 2 eNICss, and 2 fNICs. When you configure 16 vNICs (including the 2 mandatory eNICs), you are left with 229-2(fNICs)-16(eNICs)= 211 usNICs.

1.5(4)

Table 78. LSI
Defect ID Symptom Workaround First Affected Release

CSCuj83316

The battery is in a degraded state because it requires a manual (user initiated) relearn cycle.This is required of batteries that have been in use for over 1 year to accurately measure the battery's remaining capacity.

A manual (deep cycle) relearn must be started by the user. This can be done via the MegaCLI utility or from the Storage tab of the server CIMC. A relearn can take several hours and up to a day to complete. It the battery still has sufficient capacity after the relearn is complete, it will go to optimal state and the VDs will switch back to WriteBack mode if that is how they configured prior to the relearn.

1.5(4)

Table 79. Web Management
Defect ID Symptom Workaround First Affected Release

CSCtx16030

The WebUI DIMM "Operability" field in the memory inventory does not indicate failed DIMMs correctly.

The issue is observed only in the memory inventory reported by the WebUI. The BIOS reports the DIMM status properly in the BIOS Setup. So, if WebUI shows any DIMM as Inoperable, please check the status of all DIMMs on all the memory risers at Advanced -> Memory Configuration page of the BIOS Setup to get the correct status on the DIMMs.

1.5(4)

Known Behavior in Release 1.5(3)

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

Table 80. Firmware Upgrade
Defect ID Symptom Workaround First Affected Release
CSCui82263 Downgrading from release version 1.5(3) to 1.5(1) release version does not throw an error in Host Upgrade Utility. This is not an issue. Though an error is not reported, the update will not proceed. 1.5(3)

Known Behaviors in Release 1.5(2)

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

Table 81. CIMC
Defect ID Symptom Workaround First Affected Release
CSCuf52723 C240 M3 does not power up after firmware upgrade to 1.5(1B). While upgrading via HUU from firmware 1.4(6c) to 1.5(1b), HUU did not upgrade CIMC to 1.5(1b) even though it reported as successfully completed. Manually force CIMC and BIOS update to fix it. 1.5(2)
CSCug78887 Base Distinguished Name (base-dn) parameter syntax is different in new LDAP implementation. Use the following syntax: /ldap # set base-dn DC=Scom,DC=msdn,DC=com

instead of

/ldap # set base-dn Scom.msdn.com

1.5(2)
CSCuh71550 With Windows Active Directory, the child domain user login will fail with partial login name. Provide fully qualified login name to make it work. 1.5(2)
CSCuh39061 Intel VTD and ATS are required BIOS setting for usNIC. However, there is no warning message in CIMC if these parameters are not enabled when usNIC is configured. Make sure Intel VTD and ATS are enabled in BIOS setting when usNIC is configured. 1.5(2)
CSCuf08450 When upgrading the C24 M3 from 1.4.7a to 1.4.7f using the HUU (option to upgrade all), the servers fans run at almost double the speed they were running at on 1.4.7a. None 1.5(2)
CSCug65160 Sometimes, a VIC link on a SFP+ copper cable goes down after a VIC reboot or CIMC reboot. Cables whose serial number starts with MOC1238 through MOC1309 could be affected. AC power cycle the chassis to recover. 1.5(2)
CSCtx43305 The PSU firmware revision may only be partially available when the PSU does not have AC power. Connect the AC power to the PSU. The full firmware revision will be available. 1.5(2)
Table 82. LSI
Defect ID Symptom Workaround First Affected Release
CSCue10144 When booting a Cisco C22x or C24x server, RAID levels are displayed when loading the LSI Option ROM. However, not all supported RAID levels are displayed. This is done to distinguish between different 9240 controllers. Some of them support RAID5, and some do not. There are 2 products under the same 9240 name. However, there is not enough space in the name field to list every possible RAID level supported. This is why a partial list of RAID levels is displayed. 1.5(2)
CSCug95648 BBU charging status always shows as Charging and percentage of charging never reaches to 100%. It always shows 67%. This is the new change in the firmware. The Battery re-learn cycle is completed successfully and battery is charged back to 67% which is in the band gap where charging will be stopped by LSI firmware and battery will be declared optimal. This is the charge needed to retain data upto 48 hours. The Charging Status showing "Charging" as there will be some leakages and battery will slowly loose charge and hence the battery will be charging. 1.5(2)
CSCuh82265 BBU status is showing as discharging and the charge % is stuck at 64%. Battery replacement alerts on the server. Server is showing battery discharging and there is a moderate alert which says Status: Learning Cycle Needed? None 1.5(2)
CSCud13257 Hang occurs when using 64-bit MSM 12.08.03.03. Use 32 bit version of MSM. 1.5(2)
Table 83. Host Upgrade Utility
Defect ID Symptom Workaround First Affected Release
CSCui09482 Firmware Update on Emulex LPe16002 will fail when tried from HUU on certain servers. Emulex LPe16002 is already at the same firmware level of what HUU is carrying. So effectively an update is not needed. alternatively move the card to another server and try update. 1.5(2)
Table 84. SNMP
Defect ID Symptom Workaround First Affected Release
CSCug37639 When doing a MIB walk on several MIBs, they give a "No more variables left in this MIB View (It is past the end of the MIB tree)" error at the end. Failing MIBs: snmpVacmMIB

Sample good output:

[root@pebbles-iptv mibs]#

snmpwalk -v2c -c public localhost notificationLogMIB NOTIFICATION-LOG- MIB::nlmConfigGlobalAgeOut.0 = Gauge32: 1440 minutes NOTIFICATION-LOG- MIB::nlmStatsGlobalNotificationsLogged.0 = Counter32: 33 notifications NOTIFICATION-LOG- MIB::nlmStatsGlobalNotificationsBumped.0 = Counter32: 33 notifications [root@pebbles-iptv mibs]# **

Notice MIB ends cleanly, and there is no error.

** Sample bad output:

[snmp@sv-repo ~]$ snmpwalk -t 120 -v3 -u glasco -l AuthPriv -a MD5 -A enuf4me2do -x DES -X tqbFjotlCow 14.17.2.45 .1.3.6.1.6.3.16.1.5.2.1.6

SNMP-VIEW-BASED-ACM-MIB::vacmViewTreeFamilyStatus."all".1.1 = INTEGER: active(1) SNMP-VIEW-BASED- ACM-MIB::vacmViewTreeFamilyStatus."_all_".1.0 = INTEGER: active(1) SNMP-VIEW-BASED-ACM- MIB::vacmViewTreeFamilyStatus."_all_".1.1 = INTEGER: active(1) SNMP-VIEW-BASED-ACM- MIB::vacmViewTreeFamilyStatus."_all_".1.2 = INTEGER: active(1) SNMP-VIEW-BASED-ACM- MIB::vacmViewTreeFamilyStatus."_none_".1.0 = INTEGER: active(1) SNMP-VIEW-BASED-ACM- MIB::vacmViewTreeFamilyStatus."_none_".1.1 = INTEGER: active(1) SNMP-VIEW-BASED-ACM- MIB::vacmViewTreeFamilyStatus."_none_".1.2 = INTEGER: active(1) SNMP-VIEW-BASED-ACM- MIB::vacmViewTreeFamilyStatus."_none_".1.2 = No more variables left in this MIB View (It is past the end of the MIB tree) [snmp@sv-repo ~]$

To have, "No more variables left in this MIB View" when there are more mibs left to walk. The final oid seen is 1.3.6.1.6.3.16.1.5.2.1.6, and within the error-status of the get-response packet, we get noSuchName(2), and this should be noError(0).

None. 1.5(2)
Table 85. Web Management
Defect ID Symptom Workaround First Affected Release
CSCuc19323 Sometime with Windows 2008 and IE 8.0 CIMC WEB UI login prompt will not be seen Add CIMC IP to IE 8.0 trusted sites list. In the Internet Explorer browser window, select Tools -> Internet options -> Security -> Trusted Sites -> Sites -> Add 1.4(7)
CSCuh76949 After clicking on "Add Exception", user is prompted with a window which says "certificate is valid" and the "Confirm Security Exception" button is greyed out. Clear the cache or refresh multiple times the issue will be resolved. 1.5(2)

Known Behaviors in Release 1.5(1f)

Following are the known behaviors for Release 1.5(1f):

Table 86. CIMC
Defect ID Symptom Workaround First Affected Release
CSCuf53059 FlexFlash operational profile is not preserved on downgrade from 1.5(1x), resulting in all FlexFlash partitions being visible to the operating system. Set the operational profile again after downgrade. 1.5(1f)
Table 87. Intel RSTe
Defect ID Symptom Workaround First Affected Release
CSCuf02487 Creating RAID volumes from Intel RSTe software RAID Option ROM (Control-I) is not supported. Use LSI software RAID, LSI hardware RAID, or OS SW RAID. 1.5(1f)
CSCue72256 Hard drive Critical events are seen in SEL during server bootup when using Intel RSTe. This is not a real hard drive fault. The HDD Critical events reported becomes normal after system boots up and can be ignored. If real HDD fault, then Critical event generated on HDD will be persistent and does not indicate normal even after server has booted up and in this case, user need to take action to replace that HDD. 1.5(1f)

Known Behaviors in Release 1.5(1)

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

Table 88. BIOS
Defect ID Symptom Workaround First Affected Release
CSCuc75369 LSI Web BIOS may not launch on pressing Ctrl+H. During BIOS post, press F6 to bringup the boot override list and select the appropriate entry to launch the web bios. 1.5(1)
CSCuc60934 BIOS Boot order is getting changed when a virtual media device is mounted and unmounted through CIMC WebUI vKVM console or CIMC CLI. After unmounting the virtual media device, restore the boot order by re-configuring the boot order through either BIOS Setup or CIMC. 1.5(1)
CSCtf54851 Serial port B cannot be enabled for console redirection in the Server Management -> Console Redirection page of the BIOS setup. Serial port B is primarily used for SOL functionality. The BIOS will start redirecting console messages to serial port B if SOL is enabled. You should enable SOL through BMC to get console redirection messages through serial port B. 1.5(1)
CSCth71350 If the current CIMC networking mode is shipping mode, then the BIOS F8 CIMC configuration utility does not allow a new networking mode and IP address to be set at the same time. Set the new networking mode, save, then set the new IP address and save again. 1.5(1)
CSCtq84425 When BIOS console redirection is enabled, the keyboard can stop working in the Broadcom PCIe Option ROM at some baud rates. Disable the BIOS console redirection. 1.5(1)
CSCtx27907 Occasionally, when BIOS starts, the following message is displayed: Error on Getting Cisco IMC IP/MAC Address. This message can be ignored. 1.5(1)
CSCtx92042 When Broadcom 5709 Gigabit Ethernet adapter is plugged into one of the PCIE slots, the server gets stuck at the BIOS post screen during the booting process. Upgrade the firmware on the Broadcom 5709 Gigabit Ethernet adapter to version 5.2.7 or later. 1.5(1)
CSCtr93601 BIOS downgrade using the iFlash32 utility, from 1.4.x to the older version 1.2.x fails. Use the startup.nsh script available in the 1.2.x container for the downgrade. This script will execute the BIOS downgrade successfully. 1.5(1)
Table 89. CIMC
Defect ID Symptom Workaround First Affected Release
CSCuf05110 CIMC CLI does not report PID of HDD when using Intel RSTe. None 1.5(1)
CSCue54670 For a server with Virident card (or any card for which fan control has specific modifications), if CIMC is reset to factory defaults when host is on, then the fan control will go back non-card specific settings. This might imply lower fan speeds and can cause heating up of cards if there are cards present that require higher fan speeds (ex: Virident FlashMaxII card). This is because information about cards is available to CIMC from host, and when a factory default is done, this information is erased. Reboot the host, so that CIMC can get card specific information and bump up fan speeds as required. 1.5(1)
CSCtg92856 When you power on the chassis with some PS power cables disconnected, the system health LED on the front panel stays green, though some power supplies have no input voltage. Connect all cables from APC power to the power supply securely. 1.5(1)
CSCtz52715 USB Key which is inserted on a Mac can be forced to be read-only. Mac users must unmount the removable drive before mapping.

  1. Run the following command from the command line interface: diskutil unmount /Volumes/<Volume name>

  2. In the KVM/vMedia client, clear the Read Only checkbox. At this point, the user may be prompted asking if they wish to stop automatic mounting of the drive. Click Yes .

  3. Proceed with mapping the drive.

These steps are time-sensitive, as the Mac OS is aggressive about re-mounting drives that have been unmounted. If the drive does get re-mounted by the OS before completing the steps, repeat the steps. Alternatively, unmap the USB stick, use the Finder to eject the device, wait for the device to disappear from the vMedia Client view, and then physically remove and re-insert it while the vMedia session is running. As above, click Yes to the questions asking about preventing automatic mounting of the drive. 		1.5(1)
CSCua63839 On some Macs with spaces enabled, the vKVM popup notification that the session has ended can not be closed because trying to click the button causes the focus to move away from the space with the popup. Move the vKVM main window to the same space with the popup notifier. Then, the popup can be dismissed by clicking on the button. 1.5(1)
CSCtr37876 SNMPv1 traps are sent when SNMPv2 and SNMPv3 traps are enabled. None. 1.5(1)
CSCtx00839 The KVM screen displays a blank screen. Use the physical monitor to change the screen resolution. The following resolutions are supported:
  •  

    640x480 (8bpp)

  •  

    800x600 (8bpp)

  •  

    1024x768 (8bpp)

  •  

    1280x1024 (8bpp)

  •  

    1600x1200 (8bpp)

  •  

    1920x1080 (8bpp)

  •  

    1920x1200 (8bpp)

  •  

    640x480 (16bpp)

  •  

    800x600 (16bpp)

  •  

    1024x768 (16bpp)

  •  

    1280x1024 (16bpp)

  •  

    1600x1200 (16bpp)

  •  

    1920x1080 (16bpp)

  •  

    1920x1200 (16bpp)

  •  

    640x480 (24bpp)

  •  

    800x600 (24bpp)

  •  

    1024x768 (24bpp)

  •  

    1280x1024 (24bpp)

  •  640x480 (32bpp)

  • 800x600 (32bpp)

  •  

    1024x768 (32bpp)

  •  

    1280x1024 (32bpp)

1.5(1)
CSCtx88183 After firmware updates, the CIMC Web GUI and CLI might not display the Virtual Drive Information under the Virtual Drive tab and might display the Virtual Drive count as zero even though the Virtual Drive tab displays the list of virtual drives present in the system. Restart the Cisco IMC. 1.5(1)
CSCty58229 The SNMP Hard Disk Inventory starts numbering with 0 while the CIMC HDD sensor starts with 1. None. This symptom occurs because the SNMP Hard disk inventory matches with the storage inventory and both starts with index 0. The hard disk sensor numbering starts with 1 because it matches with the label in the SKU. You need to be aware of the difference and map it accordingly while browsing for a specific HDD detail across sensors and storage inventory. 1.5(1)
CSCty60975 The HDD presence cannot be viewed through SNMP. Use either alternate interfaces or do SNMP query again for the HDD inventory after the action. 1.5(1)
CSCua11831 Duplicate SNMP traps are obtained when you insert Fan 2,4 and 5 in Cisco C22. None. 1.5(1)
CSCuc87936 "Unable to communicate with FlexFlash" error message is seen after downgrading CIMC to version 1.4. User should select the Reset Flex Controller button twice if the SD card is of type SD253. If not, select the button only once. 1.5(1)
Table 90. Intel Adapters
Defect ID Symptom Workaround First Affected Release
CSCuc52172 When multiple Intel network adapters are present and you enter the iSCSI configuration from one card, it allows you to change the configuration on all Intel cards. After the change, when one of the cards is removed, it appears that the Option ROM of the remaining cards is overwritten by the card that was removed. Enter the iSCSI configuration of the card that must be modified. Do not modify other cards when they are visible. This issue is only with iSCSI configuration and not with PXE configuration. 1.5(1)
Table 91. LSI
Defect ID Symptom Workaround First Affected Release
CSCtg25373 If the number of Virtual Drives created in the LSI MegaRAID controller is greater than or equal to 50, the system will not boot from any of these Virtual Drives. None. The system boots from MegaRAID Virtual Drives only if the number of Virtual Drives are lesser than or equal to 49. 1.5(1)
CSCua03604 RHEL 6.2 Install to iSCSI target hangs when 2008 MEZZ card Option ROM is disabled on C220/C240 M3 servers. 2008 LSI OPROM must always be enabled in System BIOS when it is present in the server. If users want to disable it, then during OS Installs, depending on the OS, they would need to blacklist the LSI MegaRAID driver for the 2008 MEZZ card so that system will not hang during install. 1.5(1)
CSCts37240 The following error message is displayed in some LSI RAID controllers when you navigate to Cisco IMC > Inventory > Storage > Battery Backup Unit . Error: required HW is missing ( i.e Alarm or BBU ) The server did not have BBU installed on it and it should have confirmed the absence of the unit. None. This issue is currently under investigation. 1.5(1)
Table 92. Web UI
Defect ID Symptom Workaround First Affected Release
CSCtc22985 Printing from Web UI is not supported. Print a screenshot of Web UI. 1.5(1)

Known Behavior in Release 1.4(3)

Following is the known behavior for Release 1.4(3):

Table 93. CIMC
Defect ID Symptom Workaround First Affected Release
CSCun24570 Unable to set all numeric CN from the WebUI. Update the CN from CLI 1.4(3)

Recommended Best Practices

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

Related Documentation

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

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

The following related documentation is available for the Cisco Unified Computing System:

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: