Guest

Cisco UCS Manager

Release Notes for Cisco UCS Software, Release 2.2

  • Viewing Options

  • EPUB (83.8 KB)
  • PDF (374.1 KB)
  • MOBI (142.0 KB)
  • Feedback

Table of Contents

Release Notes for Cisco UCS Manager, Release 2.2

Contents

Revision History

Introduction

System Requirements

Updating Cisco UCS Releases

Minimum B/C Bundle Version Requirements for Cisco UCS Manager Features

Hardware and Software Interoperability

Internal Dependencies

Capability Catalog

New Hardware Features in Release 2.2

New Software Features in Release 2.2

Behavior Changes

Resolved Caveats

Open Caveats

Known Limitations

Default Zoning is Not Supported in Cisco UCS, Release 2.1(1a) and Later Releases

Cisco UCS Manager Downgrade

Known Limitations and Behaviors

Related Documentation

Obtaining Documentation and Submitting a Service Request

Release Notes for Cisco UCS Manager, Release 2.2

First Published: December 12, 2013
Last Updated: June 18, 2014
Part Number: OL-31127-01

This document describes system requirements, new features, resolved caveats, known caveats and workarounds for Cisco UCS Manager software Release 2.2. This document also includes the following:

  • Current information that became available after the technical documentation was published
  • Related firmware and BIOSes on blade and rack servers and other Cisco Unified Computing System (UCS) components associated with the release

Use this release note as a supplement with the other documents listed in documentation roadmap:

http://www.cisco.com/go/unifiedcomputing/b-series-doc

Contents of the various bundles for this release are described in:

Release Bundle Contents for Cisco UCS Software, Release 2.2

Make sure to review other available documentation on Cisco.com to obtain current information on Cisco UCS Manager.

Revision History

Table 1 shows the revision history:

 

Table 1 Online Change History

Part Number
Revision
Release
Date
Description

OL-31127-01

A0

2.2(1b)

December 12, 2013

Created release notes for Cisco UCS Manager, Release 2.2(1b).

B0

December 20, 2013

Added additional caveats.

C0

2.2(1c)

February 9, 2014

Updated release notes for Cisco UCS Software Release 2.2(1c).

D0

February 19, 2014

Updated release notes for Catalog Release 2.2.1c.T.

E0

April 2, 2014

Updated release notes for Catalog Release 2.2.1d.T.

F0

2.2(1d)

April 10, 2014

Updated release notes for Cisco UCS Software Release 2.2(1d).

G0

May 16, 2014

Added CSCuo78883 to Open Caveats for release 2.2(1d).

H0

2.2(2c)

May 22, 2014

Updated release notes for Cisco UCS Software Release 2.2(2c).

I0

May 24, 2014

Updated to include additional Open Caveats for Cisco UCS Software Release 2.2(2c).

J0

May 30, 2014

Modified several Caveat descriptions.

K0

June 18, 2014

Added CSCul74278 to 2.2(1b) Open Caveats and to 2.2(2c) Resolved Caveats; added ‘Behavior Changes’ section; and corrected three items in Servers list.

Introduction

Cisco UCS™ Manager provides unified, embedded management of all software and hardware components of the Cisco Unified Computing System™ (Cisco UCS) across multiple chassis, rack servers, and thousands of virtual machines. Cisco UCS Manager manages Cisco UCS as a single entity through an intuitive GUI, a command-line interface (CLI), or an XML API for comprehensive access to all Cisco UCS Manager functions.

System Requirements

To use Cisco UCS Manager your computer must meet or exceed the following minimum system requirements:

  • The Cisco UCS Manager GUI is a Java-based application which requires Java Runtime Environment 1.6 or later.
  • Cisco UCS Manager uses web start and supports the following web browsers:

Microsoft Internet Explorer 9.0 or higher

Mozilla Firefox 7.0 or higher

Google Chrome 14.0 or higher

  • Adobe Flash Player 10 or higher is required for some features
  • Cisco UCS Manager is supported on the following operating systems:

Microsoft Windows 7 with minimum 4.0 GB memory

Red Hat Enterprise Linux 5.0 or higher with minimum 4.0 GB memory

  • Cisco UCS Central, Release 1.1(1b) is required for registering with Cisco UCS Central.

Updating Cisco UCS Releases

The Cisco UCS Manager A bundle software (Cisco UCS Manager, Cisco NX-OS, IOM firmware) can be mixed with the previous release’s B or C bundles on the servers (host firmware (FW), BIOS, CIMC, adapter FW and drivers).

Table 2 lists the mixed A, B, and C bundle versions that are supported:

 

Table 2 Mixed Cisco UCS Releases Supported

Infrastructure Versions (A Bundles)
Host FW Versions (B or C Bundles)
1.4(3)
1.4(4)
2.0(1)
2.0(2)
2.0(3)
2.0(4)
2.0(5)
2.1(1)
2.1(2)
2.1(3)
2.2(1)
2.2(2)
1.4(3)

Yes

1.4(4)

Yes

2.0(1)

Yes

Yes

Yes

Yes

2.0(2)

Yes

Yes

Yes

Yes

2.0(3)

Yes

Yes

Yes

Yes

2.0(4)

Yes

Yes

Yes

Yes

2.0(5)

Yes

Yes

Yes

Yes

2.1(1)

Yes

Yes

Yes

Yes

Yes

2.1(2)

Yes

Yes

Yes

Yes

2.1(3)

Yes

Yes

Yes

2.2(1)

Yes

Yes

2.2(2)

Yes


Note • A mix of servers running different B-bundles may be run with a single A-bundle. However, any given server must be running the entire B/C-bundles (with associated drivers). Example: mixing the 2.1(2)B BIOS with the 2.1(3)B CIMC on a server is not supported.

  • The OS hardware and software interoperability is relative to the B/C-bundle on any given server. To see what OS is supported, see the Hardware and Software Interoperability documentation associated with the B-bundle version.
  • The A-bundle version must be at or above the same version(s) of any B/C-bundles running on the servers (see Table 2 ). This applies for patch levels as well, even though they are not displayed on the table. For example, you can mix 2.1(1f)A with 2.1(1b)B, but you cannot mix 2.1(1b)A with 2.1(1f)B.
  • Some features introduced in Cisco UCS Release 2.2 require that both the A-bundle version and the B/C-bundle versions be upgraded to the same version. For example, the lower power budget supported for Cisco UCS Release 2.2 is not supported for servers using 2.1 firmware.

Minimum B/C Bundle Version Requirements for Cisco UCS Manager Features

The following Cisco UCS Manager 2.2 features require the specified minimum B/C bundle version to perform expected operations:

 

Table 3 Minimum Required B/C Bundle Version

Feature
B Bundle Version
C Bundle Version

IPv6 Management Support

2.2(1b)B

2.2(1b)C

usNIC for Low Latency

2.2(1b)B

2.2(1b)C

Support for Virtual Machine Queue (VMQ)

2.2(1b)B

2.2(1b)C

VM-FEX for Hyper-V Management with Microsoft SCVMM

2.2(1b)B

2.2(1b)C

Secure Boot

2.2(1b)B

2.2(1b)C

Local Storage Management

2.2(1b)B

2.2(1b)C

Flash Adapters and HDD Firmware Management

2.2(1b)B

2.2(1b)C

Precision Boot Order Control

2.2(1b)B

2.2(1b)C

Trusted Platform Module (TPM) Inventory

2.2(1b)B

2.2(1b)C

DIMM Blacklisting and Correctable Error Reporting

2.2(1b)B

Netflow monitoring support with the Cisco UCS VIC 1240, Cisco UCS VIC 1280, and Cisco UCS VIC 1225

2.2(2c)B

2.2(2c)C

For detailed instructions for updating the Cisco UCS software and firmware, see the appropriate Upgrading Cisco UCS document for your installation.

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 this release , located at

http://www.cisco.com/c/en/us/support/servers-unified-computing/unified-computing-system/products-technical-reference-list.html .

Internal Dependencies

Table 4 shows interdependencies between the hardware and versions of Cisco UCS Manager. Server FRU items such as DIMMs are dependent on their server type, and chassis items such as fans and power supplies work with all versions of Cisco UCS Manager.

 

Table 4 Internal Dependencies

Component
Recommended Minimum Software Version
Recommended Software Version
Servers

B22 M3 - Sandy Bridge
B22 M3 - Ivy Bridge

2.1(3c)
2.2(2c)

2.2(2c)

B200 M1, M2, and M3

2.1(3c)

2.2(2c)

B230 M1 and M2

2.1(3c)

2.2(2c)

B250 M1 and M2

2.1(3c)

2.2(2c)

B260 M4

2.2(2c)

2.2(2c)

B420 M3 - Sandy Bridge
B420 M3 - Ivy Bridge

2.1(3c)
2.2(2c)

2.2(2c)
2.2(2c)

B440 M1 and M2

2.1(3c)

2.2(2c)

B460 M4

2.2(2c)

2.2(2c)

C22 M3 and M3L

2.1(3c)

2.2(2c)

C24 M3, M3L, and M3S2

2.1(3c)

2.2(2c)

C200 M2 and M2 SFF

2.1(3c)

2.2(2c)

C210 M2

2.1(3c)

2.2(2c)

C220 M31

2.1(3c)

2.2(2c)

C240 M3 1

2.1(3c)

2.2(2c)

C250 M2

2.1(3c)

2.2(2c)

C260 M2

2.1(3c)

2.2(2c)

C420 M3

2.1(3c)

2.2(2c)

C460 M4

2.2(2c)

2.2(2c)

Adapters

UCS 82598KR-CI
UCS M71KR-E
UCS M71KR-Q

2.1(3c)

2.2(2c)

UCS M81KR

2.1(3c)

2.2(2c)

UCS NIC M51KR-B
UCS CNA M61KR-I2
UCS CNA M72KR-Q
UCS CNA M72KR-E

2.1(3c)

2.2(2c)

UCS-VIC-M82-8P
UCSB-MLOM-40G-01
UCSB-MLOM-PT-01

2.1(3c)

2.2(2c)

UCSC-PCIE-CSC-02
UCSB-MEZ-ELX-03
UCSB-MEZ-QLG-03

2.1(3c)

2.2(2c)

Fabric Interconnect

UCS 6120XP

2.2(2c)

2.2(2c)

UCS 6140XP

2.2(2c)

2.2(2c)

UCS 6248UP

2.2(2c)

2.2(2c)

UCS 6296UP

2.2(2c)

2.2(2c)

Fabric Extender or I/OM

UCS 2104

2.2(2c)

2.2(2c)

UCS 2208XP

2.2(2c)

2.2(2c)

UCS 2204XP

2.2(2c)

2.2(2c)

Cisco Nexus 2232PP

2.2(2c)

2.2(2c)

Fabric Interconnect Expansion Modules

N10-E0440
N10-E0600
N10-E0080

2.2(2c)

2.2(2c)

N10-E0060

2.2(2c)

2.2(2c)

UCS-FI-E16UP

2.2(2c)

2.2(2c)

Power Supplies

UCSB-PSU-2500HVDC

2.2(2c)

2.2(2c)

10-GB Connections

SFP-10G-SR, SFP-10G-LR
SFP-H10GB-CU1M
SFP-H10GB-CU3M
SFP-H10GB-CU5M

2.2(2c)

2.2(2c)

SFP-H10GB-ACU7M
SFP-H10GB-ACU10M

2.2(2c)

2.2(2c)

FET-10G

2.2(2c)

2.2(2c)

SFP-H10GB-ACU7M=
SFP-H10GB-ACU10M=

2.2(2c)

2.2(2c)

8-GB Connections (FC Expansion Module N10-E0060)

DS-SFP-FC8G-SW
DS-SFP-FC8G-L

2.2(2c)

2.2(2c)

4-GB Connections (FC Expansion Module N10-E0080)

DS-SFP-FC4G-SW
DS-SFP-FC4G-LW

2.2(2c)

2.2(2c)

1-GB Connections

GLC-T (V03 or higher)
GLC-SX-MM
GLC-LH-SM

2.2(2c)

2.2(2c)

1.See the Software Advisory for the minimum firmware level required on the Cisco UCS C220 M3 and Cisco UCS C240 M3.

2.N20-AI0002, the Cisco UCS 82598KR-CI 10-Gb Ethernet Adapter, is not supported on the B440 server but is still available for other models. We suggest you use the Cisco UCS CNA M61KR-I Intel Converged Network Adapter in place of the Cisco UCS 82598KR-CI 10-Gb Ethernet Adapter.

Capability Catalog

The Cisco UCS Manager uses the catalog to update the display and configurability of server components such as newly qualified DIMMs and disk drives. The Cisco UCS Manager Capability Catalog is a single image, but it is also embedded in Cisco UCS Manager. Cisco UCS Manager 2.2(x) releases work with any 2.2(x) catalog file, but not the 1.x, 2.0 or 2.1 catalog versions. If a server component is not dependent on a specific BIOS version, using it and having it recognized by Cisco UCS Manager is primarily a function of the catalog version. The catalog is released as a single image in some cases for convenience purposes in addition to being bundled with UCS infrastructure releases. See Table 5 for details on the mapping of versions to bundles.

 

Table 5 Version Mapping

UCS Release
Catalog File
Adds Support for PID

2.2(2c)A

ucs-catalog.2.2.2c.T.bin 1

Cisco UCS B260-M4 (UCSB-EX-M4-1)

  • CPU : UCS-CPU-E52430LB, UCS-CPU-E52420B, UCS-CPU-E52470B, UCS-CPU-E52450B, UCS-CPU-E52403B, UCS-CPU-E52407B, UCS-CPU-E52440B
  • Memory : UCS-ML-1X324RY-A, UCS-MR-1X162RY-A

Cisco UCS B420-M3 (UCSB-B420-M3)

  • CPU : UCS-CPU-E54603B, UCS-CPU-E54627B, UCS-CPU-E54610B, UCS-CPU-E54650B, UCS-CPU-E54607B, UCS-CPU-E54620B, UCS-CPU-E54640B, UCS-CPU-E54657LB
  • Memory : UCS-ML-1X324RZ-A, UCS-MR-1X162RZ-A, UCS-MR-1X082RZ-A

Cisco UCS B460-M4 (UCSB-EX-M4-1)

  • CPU : UCS-CPU-E72850B, UCS-CPU-E72870B, UCS-CPU-E72880B, UCS-CPU-E72890B, UCS-CPU-E74809B, UCS-CPU-E74820B, UCS-CPU-E74830B, UCS-CPU-E74850B, UCS-CPU-E74860B, UCS-CPU-E74870B, UCS-CPU-E74880B, UCS-CPU-E74890B, UCS-CPU-E78857B, UCS-CPU-E78880LB, UCS-CPU-E78891B, UCS-CPU-E78893B
  • Memory : UCS-MR-2X082RY-E, UCS-MR-2X162RY-E, UCS-ML-2X324RY-E

2.2(2c)A (cont’d)

 

Drives

  • HDD : UCS-HD12T10KS2-E, UCS-HD450G15KS2-E, UCS-HD600G15KS2-E, UCS-HDD300GI2F105
  • SDD : UCS-SD200G0KS2-EP, UCS-SD240G0KS2-EV, UCS-SD400G0KS2-EP, UCS-SD800G0KS2-EP, UCS-SD960G0KS2-EV

2.2(1d)A

ucs-catalog.2.2.1d.T.bin 1

ucs-catalog.2.2.1d.T.bin 1

UCS-HD12T10KS2-E
UCS-ML-1X324RY-A
UCS-MR-2X041RY-B
UCS-MR-2X082RY-B

ucs-catalog.2.2.1c.T.bin3

UCS-MR-1X041RY-A
UCS-MR-1X082RY-A
UCS-MR-1X082RZ-A
UCS-MR-2X041RX-C
UCS-MR-2X082RX-C
UCS-MR-2X162RX-C

2.2(1c)A

ucs-catalog.2.2.1b.T.bin

2.2(1b)A

ucs-catalog.2.2.1b.T.bin

UCS-ML-1X324RZ-A
UCS-SD200G0KS2-EP
UCS-SD400G0KS2-EP
UCS-SD800G0KS2-EP

3.Available for separate download.

Further details are in the Cisco UCS Manager Configuration Guides .

New Hardware Features in Release 2.2

Release 2.2(2c) adds support for the following:

  • B22 M3 servers shipping with Intel E5-2400 v2 CPUs.
  • B420 M3 servers shipping with Intel E5-4600 v2 CPUs.
  • B260 M4 servers shipping with two Intel E7-2800 v2 or E7-4800 v2 or E7-8800 v2 CPUs.
  • B460 M4 servers shipping with four Intel E7-4800 v2 or E7-8800 v2 CPUs.
  • C22 M3/C24 M3 servers shipping with Intel E5-2400 v2 CPUs.
  • C460 M4 servers shipping with two or four Intel E7-4800 v2 or E7-8800 v2 CPUs.
  • 380V DC Power Supply and UCS Chassis.

New Software Features in Release 2.2

Release 2.2(2c) adds support for the following:

  • Scriptable vMedia
  • NetFlow Support
  • PVLAN Enhancements
  • Pre-Upgrade Validation Checks
  • GPU Firmware Management
  • Wear-Level Monitoring on Flash Adapters
  • KVM/vMedia Client Enhancements
  • Cisco VIC Driver Enhancements:

Adaptive Interrupt Coalescing (AIC)

Accelerated Receive Flow Steering (ARFS)

netQueue Support

Release 2.2(1b) adds support for the following:

  • IPv6 Management Support
  • Cisco Integrated Management Controller (CIMC) In-band Management
  • Fabric scaling: VLAN, VIFs, IGMP, Network Adapter Endpoints
  • Uni-Directional Link Detection (UDLD) Support
  • User Space NIC (usNIC) for Low Latency
  • Support for Virtual Machine Queue (VMQ)
  • C-Series Servers Direct Connect to FI without FEX
  • Two-factor Authentication for UCS Manager Logins
  • VM-FEX for Hyper-V Management with Microsoft SCVMM
  • Direct KVM Access
  • Server Firmware Auto Sync
  • Enhanced Local Storage Management
  • Flash Adapters and HDD Firmware Management
  • Precision Boot Order Control
  • Secure Boot
  • UEFI Boot Support
  • FlexFlash (Local SD card) Support
  • Trusted Platform Module (TPM) Inventory
  • DIMM Blacklisting and Correctable Error Reporting
  • C-Series Board Controller Firmware Management

NoteIf you want to refer to a list of supported OS in this release, check the Hardware and Software Interoperability Matrix for this release. If you want to refer to a list of supported OS in this release, check the Hardware and Software Interoperability Matrix for this release.


Behavior Changes

Release 2.2(2c) introduces the following behavior changes:

  • CSCul74278—Adding or deleting a local storage device in boot policy will cause PNUOS boot irrespective of "Reboot on Update" flag settings.

Old behavior: PNUOS boot occurs only when local device is added and SAN device is removed (or vice versa) in boot policy.

New behavior: PNUOS boot always occurs after a local storage device is added or removed in boot policy.

Cause: This change allows enabling or disabling of the boot BIOS on local storage controller even in the presence of SAN boot devices in boot policy.

  • CSCuj81638—The system no longer returns "empty-pool" faults for empty default pools under the root org.

Old behavior: When a new system comes online for the first time, "empty-pool " faults get raised for all empty default pools (compute-pool-default, ip-pool-ext-mgmt, ip-pool-iscsi-initiator-pool, mac-pool-default, uuid-pool-default, wwn-pool-default, and wwn-pool-node-default) under the root org. (These fault IDs include F0463, F0464, F0465, F0466, and F0476.)

New behavior: An "empty-pool" fault will no longer be raised for any empty default pool under the root org. Instead, the "empty-pool" fault will only be raised for user-generated empty pools.

Cause: This change allows default pools to remain empty when user has pools under a created org.

Resolved Caveats

Resolved caveats are provided in the following release-specific tables:

The following caveats are resolved in Release 2.2(2c):

 

Table 6 Resolved Caveats in Release 2.2(2c)

Defect ID
Description
First Bundle Affected
Resolved in Release

CSCtf73879

Cisco UCS Manager (GUI or CLI) no longer fails to report the local disk failures, faults, alarms, status, or disk errors/error codes from MegaRAID controller.

1.4(1)

2.2(2c)

CSCuh89441

RHEL6.3 SAN boot on M73KR-E no longer fails.

2.2(1b)

2.2(2c)

CSCuh92027

The cluster no longer gets stuck in "switchover in progress" mode when unplugging the primary FI's management port.

2.1(1a)A

2.2(2c)A

CSCuh99542

New SNMP user configured via Cisco UCS Manager now shows up in UCS NX-OS CLI.

2.1(1e)A

2.2(2c)A

CSCuj74570

B420 M3 with UCSB-MLOM-PT-01 installed no longer reboots for discovery when first IOM is upgraded to 2204XP.

2.1(2a)B

2.2(2c)B

CSCuj81385

GUI no longer returns "PSUs have failed, please check input" fault.

2.1(3a)B

2.2(2c)B

CSCuj84543

IOM no longer incorrectly reports that grid redundancy is lost while all PSUs are in "Active PS" state.

2.1(3a)A

2.2(2c)A

CSCul03508

Kernel memory no longer runs out and causes FI to reboot when running CA AIM tool with Cisco UCS Manager.

2.1(1d)A

2.2(2c)A

CSCul15865

Remote user logged in as admin with valid locales is now able to create, modify, and delete in other organizations apart from the locales downloaded so long as locales restriction is not applied to the admin profile.

2.2(1b)A

2.2(2c)A

CSCul44421

Error no longer encountered when accessing shared-storage during FI reboot, upgrade, or IOM reset.

2.1(2d)A

2.2(2c)A

CSCul74278

The server no longer fails to boot from the local disk in cases where the boot policy was initially configured only for SAN devices and is later modified to add local disk or local HDD device.

2.2(1b)A

2.2(2c)A

CSCul87625

FI no longer reports PSU failure when there is no real outage.

2.1(3a)A

2.2(2c)A

CSCul95341

Server no longer becomes unreachable after vNIC failover/failback.

2.2(1b)A

2.2(2c)A

CSCum10869

IO throttle count option on the FC adapter policy is now 256 by default and range changed to ‘256 to 1024’ to remove confusion caused by default value of 16, which was interpreted by driver to mean 2048.

2.1(1f)A

2.2(2c)A

CSCum18805

Error message no longer received when pinging from peer FI's local-mgmt.

2.2(1b)

2.2(2c)A

CSCum19106

HDDs are displayed appropriately now in both Cisco UCS Manager and in BIOS for B200 M3.

2.2(1b)B

2.2(2c)B

CSCum19132

httpd_cimc.sh crash no longer seen when changing switch mode from End-Host to Switch mode and vice versa.

2.2(1b)A

2.2(2c)A

CSCum20965

Service profile now correctly disassociates from the blade when selecting “Disassociate Service Profile” from Cisco UCS Manager GUI.

2.2(1b)

2.2(2c)A

CSCum51302

User no longer receives ' switchport trunk allowed vlan none ' configuration error on vEthernet configuration for VLAN change.

2.2(1b)A

2.2(2c)A

CSCum57954

Ping requests no longer timeout when configuring a B200 M3 with VIC 1240 and VIC 1280 with VM-FEX on the ESXi DVS while vMotioning a VM between two blades.

2.2(1b)

2.2(2c)A

CSCum60793

Cisco UCS Manager no longer reports ‘mount suspend success’ to operations manager errors when UCS becomes unreachable or unregistered with Cisco UCS Central.

2.1(2c)

2.2(2c)A

CSCum63448

A Cisco UCS compute blade no longer requests a reboot for minor changes when a component firmware in an "Activating" state after an upgrade is completed.

2.1(2c)A

2.2(2c)A

CSCum82385

Allowed VLANs in vNIC now matches the allowed VLANs in vEthernet in NX-OS and vNICs no longer get updated when the service-profile is renamed.

2.1(3a)A

2.2(2c)A

CSCum84239

No longer have to be logged in as admin to be able to connect adapter.

2.2(1b)A

2.2(2c)A

CSCum84618

Installation of Win2008R2 no longer fails to reload after loading the disk.sys driver, preventing final installation steps to be completed.

2.1(3a)B

2.2(2c)B

CSCum87525

The httpd.sh process on the subordinate FI no longer crashes after upgrading to 2.2(2c) from 2.1(3a) via auto install.

2.2(1b)A

2.2(2c)A

CSCum95778

Incorrect sorting results are no longer displayed when attempting to sort a listing of service profiles and ORGs.

2.2(1b)A

2.2(2c)A

CSCum98771

User no longer receives config failure message ‘ Flexflash controller error, probably not supported, not equipped or inoperable ’ when Cisco UCS Manager is updated from 2.1(2a) or above to 2.2(1) with FlexFlash State enabled.

2.2(1b)A

2.2(2c)A

CSCun13327

A Cisco UCS system with a high number of blade or rack-servers no longer experiences a high number of messages collected in the bladeAG logs, causing logs to overflow and prevent user from collecting necessary data for troubleshooting purposes.

2.1(3a)A

2.2(2c)A

CSCun14140

UCSB-B200-M3 Kernel no longer panics or hangs.

2.1(3b)B

2.2(2c)B

CSCun19372

User is no longer prevented from adding interface from both fabrics to the VLAN when launching the LAN Uplink Manager from the Equipment > Fiber Interconnects > Fabric Interconnect A (or B) path.

2.2(1b)A

2.2(2c)A

CSCun24381

Customers using the Cisco UCS PowerTool will no longer experience problems when scraping the Java log file for XML parsing of config changes when running Java version 7 update 45.

2.2(1b)A

2.2(2c)A

CSCun25187

Cisco UCS Manager no longer becomes Lost-Visibility in UCS-Central when keyring with certificate chain is configured for https communication if third-party certificates are signed by subordinate CA instead of root CA.

2.1(2a)A

2.2(2c)A

CSCun42280

Messages log no longer overfilled with "BMC is suspecting that palo is in boot block. Leaving I2C bus alone." messages.

2.1(2a)B

2.2(2c)B

CSCun43320

Linux PXE server no longer fails to boot from gPXE server.

2.1(2a)B

2.2(2c)A

CSCun46196

A Cisco UCS running 2.2(2c) that has a M1 or M2 blade no longer reports a minor fault related to Inband configuration when there is actually no Inband configuration intended for that blade.

2.2(1b)

2.2(2c)A

CSCun94906

The Cisco UCS Manager DME no longer crashes when a SP is referring to a SP template and Cisco UCS Manager is connected to Cisco UCS Central during policy ownership conflict checks.

2.2(1b)B

2.2(2c)B

CSCun95096

During association, the service profile no longer fails with an error stating that the RAID configuration is invalid due to an attempt to mix different drive technologies simply because one drive has an incorrect capability catalog technology field (set to "HDD" when it should be set to "SSD").

2.2(1b)T

2.2(2c)T

CSCuo06886

Cisco UCS Manager no longer populates the "Created at" field with a strange number in the wrong format instead of the date when exporting events in CSV format.

2.2(1b)A

2.2(2c)A

CSCuo09527

A blade running on a 2-socket B420 M3 no longer boots to the BIOS screen after an update if the boot order is configured in the Cisco UCS Manager and the BIOS is set to strict mode.

2.2(1b)A

2.2(2c)A

CSCuo12965

KVM console no longer fails to launch when user tries to launch from the Equipment tab in Cisco UCS Manager or from the KVM Launch Manager due to erroneous ‘No management IP address set’ error message when server has no management IP addresses assigned but the associated service profile does.

2.2(1b)A

2.2(2c)A

CSCuo23630

User no longer receives “There are uncommitted changes” prompt after applying a port license to FI and, then, trying to move to another screen.

2.2(1c)A

2.2(2c)A

CSCuo30572

Intel v2 processors no longer cause PSOD with Microsoft Windows 2008 R2 VM guests.

2.1(3a)A

2.2(2c)A

CSCuo36008

User no longer receives the ‘ peer connectivity: disconnected ’ warning after re-seating the IOM(A).

2.2(1c)A

2.2(2c)A

CSCuo78883

Cisco UCS Manager and KVM users or admins using JRE version 1.7 update >= 40 no longer encounter a pop-up window with the ' Application Blocked by Security Settings ' dialog.

2.0(1m)A

2.2(2c)A

The following caveats are resolved in Release 2.2(1d):

 

Table 7 Resolved Caveats in Release 2.2(1d)

Defect ID
Description
First Bundle Affected
Resolved in Release

CSCui31011

VIF's and VNIC's on the subordinate no longer fail to come up after FI failover.

2.1(2a)A

2.2(1d)A

CSCul38768

“Management services are unresponsive” fault no longer displayed in Cisco UCS Manager unless there is actually an HA condition failure.

2.1(1e)A

2.2(1d)A

CSCul96021

Frequent crashing of dcosAG process no longer occurs after Cisco UCS Manager upgrade.

2.2(1b)A

2.2(1d)A

CSCum02561

Server no longer reboots after infra-only upgrade that is followed by a service profile change.

2.2(1b)A

2.2(1d)A

CSCum04646

FI no longer reboots while doing SNMP Walk with LDAP configuration enabled.

2.2(1b)A

2.2(1d)A

CSCum09954

Erroneous minor faults “FCoE” or “FC uplink is down” are no longer displayed in Cisco UCS Manager when FC uplink interfaces are admin shut.

2.2(1b)A

2.2(1d)A

CSCum75266

FIs no longer go to bash prompt during upgrade to 2.2 release.

2.2(1b)A

2.2(1d)A

CSCum82888

Access to Cisco UCS Manager, FIs, and Virtual IP is no longer blocked after upgrade or reboot if default keyring was deleted.

2.2(1b)A

2.2(1d)A

CSCun01514

Boot Order change via CLI or XML API no longer fails between SAN & other devices.

2.2(1b)A

2.2(1d)A

CSCun19289

The mgmt0 interface on an FI no longer drops traffic coming from blades behind that FI.

2.2(1b)B

2.2(1d)B

CSCun21077

Blades running ESXi OS will no longer hit a speed cap of 10GB when running on hardware that allows for higher speeds.

2.2(1b)A

2.2(1d)A

CSCun59192

Secure properties, such as authentication passwords and community strings, are no longer reset when importing a backup configuration that was created while being registered to Cisco UCS Central with admin policies managed globally.

2.2(1c)A

2.2(1d)A

The following caveats are resolved in Release 2.2(1c):

 

Table 8 Resolved Caveats in Release 2.2(1c)

Defect ID
Description
First Bundle Affected
Resolved in Release

CSCum43435

The Cisco VIC 1280 adapter on a Cisco UCS B440 M2 blade no longer hangs during PXE boot.

2.2(1b)B

2.2(1c)B

CSCul44120

Cisco UCS blade servers performing a PXE boot from a Citrix PVS system no longer fail after the initial bootloader initialization with a “No API found” error.

2.1(2a)B

2.2(1c)B

CSCum51025

Cisco UCS Manager domains registered in Cisco UCS Central no longer fail during scheduled backups.

2.2(1b)A

2.2(1c)A

CSCum25003

Associated local and global service profile inventory information is no longer sent to Cisco UCS Central when no changes are made.

2.2(1b)A

2.2(1c)A

The following caveats are resolved in Release 2.2(1b):

 

Table 9 Resolved Caveats in Release 2.2(1b)

Defect ID
Description
First Bundle Affected
Resolved in Release

CSCug93342

After rebooting the FI during an upgrade, the FI no longer boots to the Loader prompt.


Note To ensure the new power sequencer firmware is installed properly, you must power cycle the FI after the upgrade is completed.


2.1(3a)A

2.2(1b)A

CSCuc19701

The 2204 IOM no longer reboots when the FI is reset.

2.1(1a)A

2.2(1b)A

CSCuf90470

When Call Home is enabled, Online Insertion and Removal (OIR) or failure of hardware modules in the FI no longer causes the FI to reboot.

2.1(1b)A

2.2(1b)A

CSCui45963

Some of the text and controls are no longer truncated when you create a service profile or service profile template using the wizard.The edit option for storage settings is enabled.

2.1(2a)A

2.2(1b)A

CSCuj84421

Installing Java 7 update 45 no longer causes UCS Manager GUI failures.

2.1(1f)A

2.2(1b)A

CSCuc38783

Firmware upgrade no longer fails on BRCM 57712 adapter.

2.1(1a)A

2.2(1b)A

CSCuj77813

Associating service profile to a C-series server integrated with Cisco UCS Manager no longer fails.

2.1(3a)C

2.2(1b)A

CSCui43905

When you try to create an iSCSI NIC on a service profile, UCS Manager no longer displays any warning messages.

2.1(2a)B

2.2(1b)A

CSCuj32124

During normal operation IOM no longer unexpectedly reboots with CPU reset.

1.4(2b)A

2.2(1b)A

CSCui41165

Cisco UCS Manager no longer displays “error accessing shared-storage”error or have the following issues:

  • Call home fan alerts are sent and cleared immediately
  • Errors during IOM boot-up

1.4(2b)A

2.2(1b)A

CSCuj78099

FC traffic between a Cisco UCS FI and a Cisco MDS switch is no longer disrupted when the FI is in switch mode.

2.1(3a)A

2.2(1b)A

CSCuj61839

With the 2.2(1b)B bundle, Cisco UCS Blade servers on a Cisco M81KR VIC adapter no longer encounter "ASSERT FAILED @ mips/ecpu_pani.c:138" errors.

2.1(2a)A

2.2(1b)A

CSCuj10564

Discard TX on a FC trunk port are no longer seen after hot-swapping the Cisco UCS-FI-E16UP expansion module on the Cisco UCS 6248UP FI.

2.1(1f)A

2.2(1b)A

CSCuf77316

Windows 2012 installed on a FlexFlash card no longer fails Microsoft certifcation.

2.1(2a)B

2.2(1b)A

CSCui87195

The FLS process on Cisco CNA M72KR-E no longer cores with the following message:

130820-19:06:33.645547 fls.fc vnic 15: Local port down for lif 4.

2.0(5c)C

2.2(1b)A

CSCuj99958

During heavy FC traffic, the server no longer stops responding with an ASSERT FAILED (Exception 2 triggered!) @ mips/ecpu_panic.c:138 error.

2.1(1f)A

2.2(1b)A

CSCug89448

The tech support collection no longer fails on the Cisco UCS Manager GUI.

2.0(1s)A

2.2(1b)A

CSCug63368

PXE boot no longer fails in vPC environments if the DHCP relay agent is installed as the gateway IP address during a PXE boot instead of the HSRP IP address.

2.1(1d)B

2.2(1b)A

CSCui82679

FlexFlash storage is no longer disconnected from a Cisco B200 M3 server after booting ESX or ESXi from a FlexFlash card.

2.1(2a)A

2.2(1b)A

CSCuc52981

Downloaded license files for FIs continue to be displayed in the downloads area after installation.

2.0(3a)A

2.2(1b)A

CSCti39470

RAID 50 and RAID 60 configurations can now be created and managed by Cisco UCS Manager.

1.4(1i)A

2.2(1b)A

Open Caveats

Open caveats are provided in the following release-specific tables:

Open caveats may be listed in association with the release in which they were first noticed or in the release identified as the first affected. Users should review open caveats in all releases to avoid overlooking a defect that may impact their release.

The following caveats are open in Release 2.2(2c):

 

Table 10 Open Caveats in Release 2.2(2c)

Defect ID
Symptom
Workaround
First Bundle Affected

CSCuj09403

When installing RHEL 6.3 in UEFI mode with M73KR-Q or M73KR-E adapters, the system hangs with a ‘ cannot exit boot services ’ message.

This issue has no known workaround with M73KR-Q or M73KR-E adapters.

Use VIC1240 adapter or use legacy boot.

2.2(1b)B

CSCuj63232

In some instances, most commonly after doing a CIMC upgrade, certain long running operation data may indicate that an operation is currently running when it isn't. For example, the consistency check operation may report 0% progress and be stuck in that status.

This issue has no known workaround.

To verify that the data is erroneous, use an LSI tool, such as WebBios or MegaCli, to confirm the operation is still in progress.

2.2(1b)A

CSCul85363

Redhat 6.x installation fails on a B200 M3 that uses a Seagate ST300MM0006 single drive JBOD configuration with the No RAID policy.

To work around this issue:

1. Install the OS using custom layout by selecting "Create custom layout” when prompted for installation type.

2. Create custom layout and swap partition.

2.2(1b)A

CSCum91845

Server reboots on changing any management policy when Service Profile is derived from update Service Profile Template that has no vNICs.

This issue has no known workaround.

2.2(2c)A

CSCun16169

Ethernet uplink port channel member interfaces are permanently down on primary FI after 20 iterations of port channel flap from Cisco UCS Manager.

Remove and add port channel.

2.2(2c)A

CSCun22459

In some cases when the port is in trunk mode containing more than one isolated-primary VLAN pair, the VM comes up with vNIC configured with two isolated-primary pairs and does not get dynamic IP address.

Use one of the following two options to resolve this issue:

1. Do not put the port in trunk mode and configure one isolated-primary VLAN pair per port.

2. Do not set the native VLAN and, instead, explicitly tag the traffic with one of the VLANs.

2.2(2c)A

CSCun29274

In rare cases and only if blade is already discovered with a network adapter and user replaces it with storage adapter, the association or disassociation of that blade server may fail with error/fault reported as “ Invalid adapter connectivity, no adapter found .”

Decommission and recommission the affected blade.

2.2(2c)A

CSCun79973

In some conditions, when a Cisco UCS Manager user changes the QoS policy on a VNIC where Netflow session is actively enabled on a VNIC with transmit monitoring, the VNIC will hang.

To workaround this issue:

1. Disable the Netflow session on the VNIC.

2. Change the QoS policy.

3. Reenable the Netflow session.

2.2(1b)A

CSCun82594

DIMMS are mapped out during MRC (BIOS POST) when lockstep or mirroring are enabled in configurations with Ivy Bridge or Sandy Bridge CPU and with the following DIMM configurations:

  • 1866 Hynix - Lockstep/Mirroring - 3 DIMMs Per Channel.
  • 1866 Samsung - Lockstep/Mirroring - 3 DIMMs Per Channel.

The fix is provided via the Intel Memory Reference Code update.

2.2(2c)B

CSCuo12665

In some cases, when user sets SAN boot for boot policy in service profile, the configured boot policy is not reflected on a blade equipped with a M71KR-Q adapter after association so the blade will not boot from SAN.

One of the following workarounds may resolve this issue:

1. Reset the blade

2. Upgrade the server firmware version to match with infra bundle version (FI's / IOM's / Cisco UCS Manager)

2.2(1d)A 2.1(3b)B

CSCuo34760

In some rare cases, if Primary FI gets rebooted and comes back up as subordinate FI, some Veths/VIFs will remain in down state on the newly subordinate FI (while previous subordinate FI becomes Primary).

One of the following workarounds will recover the affected servers:

1. CIMC reset of the affected servers will also force shallow discovery of the server which will fix the issue. This will not reboot the server and most preferred workaround.

2. IOM reset (which is connected to the affected FI) will also recover, however, any traffic going through that IOM for all blade servers on that chassis will be impacted unless there is failover adapter configs supported which will redirect traffic through other working IOM/FI

3. REACK of affected servers, however, server will get rebooted during re-ack operation

2.2(2c)A

CSCuo38990

In some rare conditions, servers lose network connectivity during failover.

Reboot subordinate FI to recover.

2.1(3b)A

CSCuo41491

If boot policy has PXE boot listed prior to local disk / HBA, a blade my sometimes boot to pnuos instead of following normal boot policy when rebooted.

Re-associate Service Profile.

2.2(1b)A

CSCuo45351

When running a B200 M3 blade with VIC 1240 adapter, the VFC on a server bay returns " error disabled " message after the reboot because vEthernet to which the VFC is attached is stuck in "Initializing" state.

Reset the DCE interface. This will bring up the vEthernet and the VFC interfaces.

2.2(1c)A

CSCuo51708

In some cases when attempting downgrade in middle of autoinstall upgrade, Cisco UCS Manager autoinstall downgrade will fail.

Manually activate UCSM version to the higher revision, and then let auto-install downgrade it.

2.2(1d)A

CSCuo55182

IPMITool version 14 or 14rc2 cannot obtain any IPMI information on the slave blade in a B460-M4 configuration four-socket configuration.

Use ipmitool version 13.

2.2(2c)B

CSCuo65728

In some instances, a MAC move is not learned by the Cisco UCS FI after a VM is vMotioned between blades when the Cisco UCS FI is enabled with vNIC Fabric Failover and hypervisor is configured to utilize active/standby for vNICs.


Note This is not a Cisco UCS best practices configuration.


Reset the vEthernet interface on the target vMotion host to force a MAC relearn.

2.2(1c)A

CSCuo68579

In some cases after a firmware upgrade, FC traffic stops working on fabric interconnect. However, blades in those chassis have successful flogi into the fabric.

On the upstream fabric switch fc4 feature types are missing when checking "show fcns database detail" for the affected blades.

Reboot affected Fabric Interconnect

2.1(3b)A

CSCuo81734

In some cases, the FNIC driver bundled with the driver disk does not load when installing on a standalone C-series server and does not return an error to indicate the failure.

Perform RPM installation after system is up using the inbox FNIC driver.

2.2(1b)A

CSCuo98011

Cisco UCS Manager can crash (dump
core) during Infra firmware upgrade (ucs-k9-bundle-infra.2.2.2c.A.bin) when upgrade is initiated from Cisco UCS Central if Cisco UCS Manager is registered to Cisco UCS Central using IPv4 address and image bundles are not present in Cisco UCS Manager.

Note The core dump is associated with the "svc_sam_dcosAG" process and that process does restart itself after the crash.

Avoid this issue by using either of two workarounds:

1. Download the Cisco UCS Manager 2.2(2c) Infra bundle (ucs-k9-bundle-infra.2.2.2c.A.bin) directly on to Cisco UCS Manager before initiating the firmware upgrade from Cisco UCS Central.

2. Download the firmware image into Cisco UCS Manager and initiate the upgrade directly from Cisco UCS Manager after using the following commands to ensure policy control resolution is set to "Local"

CLI in UCSM

>scope system
>scope control-ep policy
>set infra-pack-ctrl source local

GUI in UCSM

Go to Admin > UCS Central > Policy Resolution Control (Right Pane)

2.2(2c)A

The following caveats are open in Release 2.2(1d):

 

Table 11 Open Caveats in Release 2.2(1d)

Defect ID
Symptom
Workaround
First Bundle Affected

CSCul44421

You may see the “error accessing shared-storage” fault in Cisco UCS Manager. This message may appear any time but is seen more often during an FI reboot, upgrade, or IOM reset when running release 2. x of Cisco UCS Manager.

This issue has no known workaround.

This fault is auto-cleared and transient so should not persist. The HA framework remains INTACT as long as show cluster extended output reports state as PRIMARY_OK.

2.1(2d)A

CSCum98771

Upgrading from Cisco UCS Manager 2.1(2a) or higher to release 2.2(1 x ) with FlexFlash State enabled in local disk policy of service profiles on servers causes the “FlexFlash controller error, probably not supported, not equipped or inoperable” config-failure.

This condition prevents updates to Blade and Rack firmware package bundles using auto-install or host firmware pack.

Avoid this error using either of two workarounds:

1. Disable FlexFlash in local disk policy of service profile. This will resolve the config-failure and CIMC can be upgraded using auto-install and host firmware pack. Since disabling FlexFlash requires host reboot, host downtime is required.

2. Modify host firmware pack in service profile to use empty blade and rack package versions. Then directly update and activate CIMC firmware (Equipment > Chassis > Server > Inventory > CIMC).

2.2(1b)A

CSCun25187

When using third-party certificates with Cisco UCS Central, if a keyring with a certificate chain is configured to use https communication, the status of Cisco UCS Manager might be displayed in Cisco UCS Central as 'Lost-Visibility'. This occurs when certificates are signed by subordinate CA instead of root CA.

Use third-party certificates that are signed directly by root CA for UCS Central https communication.

2.1(2a)A

CSCun86873

In some cases, during initial discovery or following upgrade-initiated discovery, B230 M2 shows only 8 of 10 cores available.

Reacknowledge the blade.

2.2(1c)A

CSCuo12230

When the VNIC of a service profile is configured to allow a VLAN that is defined in the appliances cloud in the LAN configuration, the show run interface vethernet <x> command output and the show interface vethernet <x> switchport command output report different VLANs allowed on the virtual Ethernet interface.

Check the outputs listed in the symptoms to confirm the problem. If the output shows the problem, then move the VLAN from the appliance cloud to the LAN cloud.

2.2(1c)A

CSCuo78883

‘Application Blocked by Security Settings’ error when starting the Cisco UCS Manager GUI or KVM Console application.

Because the Java Code Signing Certificate expired, users on Java 7 update 40 or higher might see the following message:

Application Blocked by Security Settings.
Your security settings have blocked an application signed with an expired or not-yet-valid certificate from running.

To fix this issue, you can either temporarily lower your Java security settings to add Cisco UCS Manager as an exception or, if you are using Java 7 update 51 or higher, you can add the Cisco UCS Manager host IP address to the Exception Site list.

To perform one of these workarounds, perform the corresponding steps below:

To temporarily lower your security settings:

1. Start your Java Control Panel. The location may vary depending on your operating system and browser preferences.

2. Lower the Security level to Medium.

3. Start Cisco UCS Manager.

4. At the warning message, check the “I accept the risk and want to run this application'” checkbox and click Run.

5. Return to the Java Control Panel and reset your security level.

To add the IP address to the exception site list (for Java 7 version 51 and higher):

1. Start your Java Control Panel. The location may vary depending on your operating system and browser preferences.

2. In the Security area, click the Edit Site button to add the IP address to the list.

Note If you use HTTPS to access Cisco UCS Manager, ensure that you have the correct prefix.

3. Click OK .

2.2(1b)A

The following caveats are open in Release 2.2(1c):

 

Table 12 Open Caveats in Release 2.2(1c)

Defect ID
Symptom
Workaround
First Bundle Affected

CSCum82888

After upgrading to Release 2.2(1b), you may see the following errors:

  • No access to the Cisco UCS Manager GUI.
  • The virtual IP is not reachable.
  • The virtual IP cannot be accessed by the GUI or CLI/SSH.
  • Individual FIs can be accessed using SSH but not with http.

This occurs when the default keyring is deleted before upgrade, or if the default keyring is deleted after the upgrade and the system is rebooted.

To avoid this issue, do not delete the default keyring.

If this issue occurs, stop the bladeAG process.

2.2(1b)B

Resolved in 2.2(1d)B

CSCum09954

If an FC uplink interface is set to administratively shut, after upgrading to Release 2.2(1b) you may see a “FCoE or FC uplink is down on Vsan 202” error.

This issue is cosmetic and the error message can be safely ignored.

2.2(1b)A

Resolved in 2.2(1d)A

CSCum60793

You may see the following fault in Cisco UCS Manager:

[FSM:STAGE:RETRY:]: Report mount suspend success to operations manager errors

This occurs if Cisco UCS Central is not reachable or the domain has been unregistered.

Restore connectivity to Cisco UCS Central, or register the domain again.

2.1(2c)A

The following caveats are open in Release 2.2(1b):

 

Table 13 Open Caveats in Release 2.2(1b)

Defect ID
Symptom
Workaround
First Bundle Affected

CSCuj63448

When upgrading to a catalog that supports new DIMMs, some of the DIMM information is not displayed.

Reacknowledge the blade server.

1.4(4k)A

CSCui67824

When you disable port security from a network control policy with Hyper-V port profile, security is disabled on the nested port-profile, but security remains enabled on a few interfaces.

This issue has no known workaround.

2.2(1b)A

CSCuj26767

Attempting to install UEFI OS second time sets incorrect boot order and stops installation.

Clean initial installation in the disk and restart installation.

2.2(1b)A

CSCui52680

When the blade appears to be in normal operation state, Cisco UCS Manager SEL message list might display the following error:

EFI Load Image Security Violation

If all blade functions appear to be normal, ignore this error message.

2.2(1b)A

CSCud75506

The UUID is translated incorrectly when you upgrade ESXi from version 4.1 or 5.1 on the Cisco UCS B200 M3, B220 M3, or B440 M3 blade servers.

This is a display issue only, and does not affect the service profiles associated with the blades. This issue has no known workaround.

2.0(2r)A

CSCug25894

During Cisco 2100 Series IOM boot and chassis reacknowledgement, sysmgr cores are seen.

The system resumes normal behavior after process restart. This should take approximately three minutes.

2.0(4a)A

CSCul74278

In some cases, if the boot policy is initially configured only for SAN devices and the policy is later modified to add local disk or local HDD device, the server fails to boot from the local disk.

Reacknowledge the server.

2.2(1b)A

Resolved in 2.2(2c)A

CSCum02561

When upgrading to 2.2(1b) from 2.1(3a), if you upgrade the infrastructure (A bundle) before the host firmware (B and C bundles), and then modify the service profile you may experience one or more of the following issues:

1. The configured boot order in the Cisco UCS Manager GUI does not display SAN and local disk.

2. The server reboots every time the service profile is modified.

1. To view missing entries for the configured boot order, use the Cisco UCS Manager CLI to scope into the server and run show boot-order .

2. To avoid server reboots, uncheck the Reboot on Boot Order Change checkbox before upgrading.

3. Upgrade the B and C bundles.

2.2(1b)A

Resolved in 2.2(1d)A

CSCuj74570

A Cisco UCS B420 M3 blade with a VIC 1240 and a port expander is successfully discovered in a chassis with a 2104XP IOM, even though it is unsupported. When upgrading to the 2204XP IOM, the blade reboots for discovery.

This issue has no known workaround.

The B420 M3 blade with port expander is not supported with the 2104XP IOM.

2.1(2a)B

CSCul72408

During upgrade, the following issues occured:

  • The IOM backplane ports show admin down in the Cisco UCS Manager GUI.
  • The VIF's show non-participating.
  • The adapter shows DCE interfaces down.

Reboot the IOM in the affected chassis.

2.1(3a)A

CSCul95501

IOM FSM failed after downgrading from 2.2(1b). Connectivity between the IOM and the FI could not be established.

Reboot the FI.

2.1(3a)A

CSCuh89441

On B420 M3, the installed OS fails to boot from SAN LUN with Gen-3 E.

Enable EDD 3.0 using the Emulex M73KR-E FCoE option ROM.

2.2(1b)A

CSCuj89557

In some rare conditions, it is observed during Cisco UCS Manager upgrade, downgrade, or FI reload in a cluster setup that Cisco UCS Manager may fail on the secondary FI due to database corruption.

If you detect a db corruption in the secondary FI, erase the database from the FI and reconnect it to the cluster. The secondary syncs up with the primary FI and recreates the db.

2.2(1b)A

CSCtl04654

Changing native VLAN on uplink ports will cause the ports state to change and traffic disruption.

If native VLAN changes are required on uplink ports, we recommend that they be performed during a maintenance window.

2.1(1a)A

CSCuj78615

The EFI Shell boot option is disabled in the BIOS Setup Utility > Boot Options page. Shell Boot option is not automatically launched by the BIOS.

Boot UEFI shell by using either one of the following two options:

  • Enter BIOS set up utility and select Shell boot option from the Exit & Save page.
  • Hit F6 to access boot override menu.

2.2(1b)A

CSCuh13333

When you install ESXi in UEFI mode, the OS fails to boot-up. Even when you seem to have a smooth installation, the server does not boot the ESXi OS.

Do the following:

1. Boot to Shell.

2. Determine fsxx (xx is where ESX is installed. It will be typically 0 i.e fs0:) Make sure you have the following:

fsxx:\EFI\Boot\BOOTX64.EFI

3. Use following command to get current list of EFI Boot Options

bcfg boot dump
Note last boot option number to use as LAST_BOOT_No +1

4. Use the following command to add new Boot Option at position LAST_BOOT_NO + 1

Last paramter in quotes can be any description for this new Boot Option.
This will be displayed during BIOS F6 menu.
bcfg boot add LAST_BOOT_NO + fsxx:\EFI\BOOT\BOOTX64.EFI "UEFI : ESXi "

5. Make the newBoot Option for ESX as the first by using the following

bcfg boot mv LAST_BOOT_NO + 4 1

6. Issue reset command at the shell and reset the platform. Press F6 when BIOS is booting to get into BIOS Boot Selection menu. Make sure the new Boot Option is displayed and select this option to Boot EXSi.

2.2(1b)A

CSCuj31559

Installing Windows EFI PXE using UEFI is slow when compared to the installation using vNIC on MLOM.

This issue has no known workaround.

2.2(1b)A

CSCuh34516

Installing Linux PXE using UEFI fails with the following message:

Trying to allocate 971 pages for VMLINUZ.

This issue has no known workaround.

2.2(1b)A

CSCuj34520

TFM information in UCS Manager inventory contains invalid characters.

This issue has no known workaround.

2.1(2a)A

Known Limitations

Default Zoning is Not Supported in Cisco UCS, Release 2.1(1a) and Later Releases

Default zoning has been deprecated in Cisco UCS, Release 2.1(1a). Cisco has not supported default zoning in Cisco UCS since Cisco UCS, Release 1.4 in April 2011. Fibre Channel zoning, a more secure form of zoning, is available in Cisco UCS, Release 2.1(1a) and later releases. For more information about Fibre Channel zoning, see the Cisco UCS Manager configuration guides for the release to which you are planning to upgrade.


Caution All storage connectivity that relies on default zoning in your current configuration will be lost when you upgrade to Cisco UCS, Release 2.1(1a) or a later release. We recommend that you review the Fibre Channel zoning configuration documentation carefully to prepare your migration before you upgrade to Cisco UCS, Release 2.1(1a) or later. If you have any questions or need further assistance, contact Cisco TAC.

Cisco UCS Manager Downgrade

Before performing any upgrade or downgrade operation, make sure to perform an all configuration backup of your system. The backup will ensure a seamless downgrade or upgrade, if required.

The following defects are related to downgrade issues:

  • CSCul55683 - When downgrading the Cisco UCS Manager image from Release 2.2 to any prior version, you must downgrade Cisco UCS Manager before you downgrade the infrastructure firmware on the FI. If you downgrade the FI first, some FI processes will crash.

Contact Cisco TAC to recover from this issue.

  • CSCuj87553 - If you downgrade the Cisco UCS Manager image from Release 2.2 to any version prior to Release 2.0(4) before the fabric interconnect images are downgraded, the Cisco UCS Manager GUI may not work.

To recover from this issue, downgrade the kickstart and sytem images on the FI to the same version as the downgraded Cisco UCS Manager image. The Cisco UCS Manager GUI will be able to reconnect successfully after the FI is running the same version as Cisco UCS Manager.

  • CSCul54029 - When you downgrade a B22 board controller to 2.1(2) version using auto-install, the activate status shows as failed. Also if you initiate individual board activation, the board control firmware downgrade is blocked.

To recover from this status, use “force” option to activate the board controller to the same version as the active one. This clears the fault and brings activate status to “Ready”.

Known Limitations and Behaviors

The following known limitations and behaviors are not otherwise documented:

 

Table 14 Known Limitations in Release 2.2

Defect ID
Symptom
Workaround
First Bundle Affected

CSCui95113

Blade discovery fails with the following error:

Warning F77960 2013-08-29T17:47:46.044 18211988 [FSM:STAGE:REMOTE-ERROR]: Result: end-point-unavailable Code: unspecified Message: sendSamDmeAdapterInfo: identify failed(sam:dme:ComputeBladeDiscover:NicPresencePeer)
Warning F16520 2013-08-29T17:47:35.122 18211986 [FSM:STAGE:RETRY:]: detect mezz cards in 6/1(FSM-STAGE:sam:dme:ComputeBladeDiscover:NicPresencePeer)

This issue was caused by manufacturing sending out adapters in DIAG mode.

For information on how to fix this issue, see the following Tech Zone post:

https://techzone.cisco.com/t5/B-Series/How-to-debug-and-fix-M3-blades-with-VIC-1240-1280-failing/m-p/361283

2.1(2a)B

CSCun25132

On platforms with OOB storage controller, Cisco UCS Manager displays usable (coerced) value in disk inventory section, which is different than the raw 'NumberOfBlocks' value displayed in catalog section.

This is a non-issue; Cisco UCS Manager is designed to report the coerced, or usable, size as reported by the LSI controller. Both the host and OOB interfaces report this same value.

2.2(1b)T

Related Documentation

For more information, you can access related documents from the following links:

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, using the Cisco Bug Search Tool (BST), submitting a service request, and gathering additional information, see What’s New in Cisco Product Documentation at: http://www.cisco.com/c/en/us/td/docs/general/whatsnew/whatsnew.html .

Subscribe to What’s New in Cisco Product Documentation , which lists all new and revised Cisco technical documentation, as an RSS feed and deliver content directly to your desktop using a reader application. The RSS feeds are a free service.

This document is to be used in conjunction with the documents listed in the “Known Limitations” section.