Guest

Cisco UCS Manager

Release Notes for Cisco UCS Software, Release 2.2

  • Viewing Options

  • EPUB (108.8 KB)
  • MOBI (187.7 KB)
  • PDF (521.7 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

LAN and SAN Topology Information Limitation

Default Zoning 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: December 4, 2014

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 roadmaps:

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

http://www.cisco.com/go/unifiedcomputing/c-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

Date
Release
Description

December 12, 2013

2.2(1b)

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

December 20, 2013

Added additional caveats.

February 9, 2014

2.2(1c)

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

February 19, 2014

Updated release notes for Catalog Release 2.2.1c.T.

April 2, 2014

Updated release notes for Catalog Release 2.2.1d.T.

April 10, 2014

2.2(1d)

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

May 16, 2014

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

May 22, 2014

2.2(2c)

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

May 24, 2014

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

May 30, 2014

Modified several Caveat descriptions.

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.

August 1, 2014

2.2(1e)

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

August 21, 2014

Added B22 PID support and updated PID support for other servers in Version Mapping table for 2.2(2c); added ‘Chassis’ section to Internal Dependencies table; added UCSB-5108-AC2, -DC2, and -HVDC to New Hardware Features section; added note to Upgrade section for CSCud81176 consideration; added CSCuj81245 to 2.2(1b) Open Caveats table and to 2.2(2c) Resolved Caveats table.

September 8, 2014

2.2(3a)

Updated release notes for Cisco UCS Software Release 2.2(3a).

September 11, 2014

2.2(2d)

Updated release notes for Cisco UCS Software Release 2.2(2d); updated the Recommended Minimum Software in Table 4.

October 09, 2014

2.2(3b)

Updated release notes for Cisco UCS Software Release 2.2(3b).

October 24, 2014

2.2(2e) 2.2(3c)

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

October 31, 2014

2.2(1f)

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

November 10, 2014

2.2(3a)

Added CSCuo60330 to 2.2(3a) resolved caveats.

November 17, 2014

2.2(3c)

Added missing 2.2(3c) adapter to Internal Dependencies table.

December 4, 2014

Updated release notes for Catalog Release 2.2.3b.T.

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.

This introductory information is provided in the following sections:

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 integration:

Cisco UCS Manager Release 2.2(1) and 2.2(2) can only be registered with Cisco UCS Central, Release 1.1(1b) or higher.

Cisco UCS Manager Release 2.2(3) can only be registered with Cisco UCS Central, Release 1.2(1a) or higher.


Note For more information, see the Feature Support Matrix section of the Cisco UCS Central Installation and Upgrade Guides.


Updating Cisco UCS Releases

The Cisco UCS Manager A bundle software (Cisco UCS Manager, Cisco NX-OS, IOM firmware) can be mixed with previous B or C bundle releases 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)
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)
2.2(3)
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

Yes

2.1(2)

Yes

Yes

Yes

Yes

Yes

2.1(3)

Yes

Yes

Yes

Yes

2.2(1)

Yes

Yes

Yes

2.2(2)

Yes

Yes

2.2(3)

Yes


Note • If upgrading from a pre-2.2(1b) release and running Management Firmware Pack, refer to open caveat information for CSCud81176 in Release Notes for Cisco UCS Software, Release 2.1.

  • If an environment includes a mix of servers, refer to CSCuh61202 for caveat information.
  • 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

2.2(3a)C

Netflow monitoring support:

  • Cisco UCS VIC 1240 and 1280
  • Cisco UCS VIC 1225
  • Cisco UCS VIC 1227
  • Cisco UCS VIC 1340 and 1380

 

2.2(2c)B

2.2(3a)B

 

2.2(2c)C

2.2(3a)C

Stateless Offload for Overlay Networks (NVGRE / VXLAN)


Note Supported only on Cisco UCS
VIC 1340 and VIC 1380 adapters.


2.2(3a)B

BIOS secure boot support

2.2(1b)B

2.2(3a)C

CIMC secure boot support

2.2(1b)B

2.2(3a)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 1
Recommended Software Version
Servers

B22 M3 E5-2400
B22 M3 E5-2400 v2

2.1(3f)
2.2(2e)

2.2(3c)
2.2(3c)

B200 M1 and M2

2.2(2e)

2.2(3c)

B200 M3 E5-2600
B200 M3 E5-2600 v2

2.1(3f)
2.2(2e)

2.2(3c)
2.2(3c)

B200 M4

2.2(3c)

2.2(3c)

B230 M1 and M2

2.1(3f)

2.2(3c)

B250 M1 and M2

2.1(3f)

2.2(3c)

B260 M4

2.2(2e)

2.2(3c)

B420 M3 E5-4600
B420 M3 E5-4600 v2

2.1(3f)
2.2(2e)

2.2(3c)
2.2(3c)

B440 M1 and M2

2.1(3f)

2.2(3c)

B460 M4

2.2(2e)

2.2(3c)

C22 M3 and M3L

2.1(3f)

2.2(3c)

C24 M3, M3L, and M3S2

2.1(3f)

2.2(3c)

C200 M2 and M2 SFF

2.1(3f)

2.2(3c)

C210 M2

2.1(3f)

2.2(3c)

C220 M32

2.1(3f)

2.2(3c)

C220 M4

2.2(3c)

2.2(3c)

C240 M3 2

2.1(3f)

2.2(3c)

C240 M4

2.2(3c)

2.2(3c)

C250 M2

2.1(3f)

2.2(3c)

C260 M2

2.1(3f)

2.2(3c)

C420 M3

2.1(3f)

2.2(3c)

C460 M4

2.2(2e)

2.2(3c)

Adapters

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

2.1(3f)

2.2(3c)

UCS M81KR

2.1(3f)

2.2(3c)

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

2.1(3f)

2.2(3c)

Adapters (cont’d)

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

2.1(3f)

2.2(3c)

UCSB-MLOM-40G-03
UCSB-VIC-M83-8P
UCSC-MLOM-CSC-02

2.2(3c)

2.2(3c)

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

2.1(3f)

2.2(3c)

UCSC-F-FIO-1000MP
UCSC-F-FIO-1300MP
UCSC-F-FIO-2600MP
UCSC-F-FIO-5200MP

2.2(3c)

2.2(3c)

UCSB-FIO-1600MS
UCSB-FIO-1300MS

2.2(3c)

2.2(3c)

UCSC-INVADER-3108
UCSC-NYTRO-200GB

2.2(3c)

2.2(3c)

Chassis 4

N20-C6508

2.2(3c)

2.2(3c)

UCSB-5108-DC

2.2(3c)

2.2(3c)

UCSB-5108-AC2

2.2(3c)

2.2(3c)

UCSB-5108-DC2

2.2(3c)

2.2(3c)

UCSB-5108-HVDC

2.2(3c)

2.2(3c)

Fabric Interconnect

UCS 6120XP

2.2(3c)

2.2(3c)

UCS 6140XP

2.2(3c)

2.2(3c)

UCS 6248UP

2.2(3c)

2.2(3c)

UCS 6296UP

2.2(3c)

2.2(3c)

Fabric Extender or I/OM

UCS 2104

2.2(3c)

2.2(3c)

UCS 2208XP

2.2(3c)

2.2(3c)

UCS 2204XP

2.2(3c)

2.2(3c)

Cisco Nexus 2232PP

2.2(3c)

2.2(3c)

Fabric Interconnect Expansion Modules

N10-E0440
N10-E0600
N10-E0080

2.2(3c)

2.2(3c)

N10-E0060

2.2(3c)

2.2(3c)

UCS-FI-E16UP

2.2(3c)

2.2(3c)

Power Supplies

UCSB-PSU-2500HVDC

2.2(3c)

2.2(3c)

UCSC-PSU-930WDC
UCSC-PSU1-770W
UCSC-PSU2-1400
UCSC-PSU2V2-650W
UCSC-PSU2V2-1200W

2.2(3c)

2.2(3c)

10-GB Connections

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

2.2(3c)

2.2(3c)

SFP-H10GB-ACU7M
SFP-H10GB-ACU10M

2.2(3c)

2.2(3c)

FET-10G

2.2(3c)

2.2(3c)

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

2.2(3c)

2.2(3c)

SFP-H10GB-CU2M
SFP-H10GB-CU1-5M
SFP-H10GB-CU2-5M

2.2(3c)

2.2(3c)

SFP-10G-AOC1M
SFP-10G-AOC2M
SFP-10G-AOC3M
SFP-10G-AOC5M
SFP-10G-AOC7M
SFP-10G-AOC10M

2.2(3c)

2.2(3c)

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

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

2.2(3c)

2.2(3c)

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

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

2.2(3c)

2.2(3c)

1-GB Connections

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

2.2(3c)

2.2(3c)

1.This is the minimum server bundle recommended for this hardware in a mixed firmware configuration, assuming the infrastructure is at the recommended software version.

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

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

4.Recommended minimum software versions do not take into account mixed environments; to determine the minimum software version for your mixed environment, refer to “Mixed Cisco UCS Releases Supported”, Table 2.

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

ucs-catalog.2.2.3b.T.bin 1

2.2(3c)A

Additional Cisco UCS B200 M4 CPUs

UCS-CPU-E52640D, UCS-CPU-E52630D, UCS-CPU-E52630LD, UCS-CPU-E52623D, UCS-CPU-E52620D, UCS-CPU-E52609D, UCS-CPU-E52637D

2.2(3b)A

2.2(3a)A

ucs-catalog.2.2.3a.T.bin 1

Cisco UCS B200 M4 (UCSB-B200-M4)

  • CPU : UCS-CPU-E52699D, UCS-CPU-E52698D, UCS-CPU-E52697D, UCS-CPU-E52695D, UCS-CPU-E52690D, UCS-CPU-E52683D, UCS-CPU-E52680D, UCS-CPU-E52670D, UCS-CPU-E52667D, UCS-CPU-E52660D, UCS-CPU-E52658D, UCS-CPU-E52650D, UCS-CPU-E52643D
  • Memory : UCS-MR-1X081RU-A, UCS-MR-1X162RU-A, UCS-ML-1X324RU-A

Cisco UCS C220 M4 (UCSC-C220-M4) and
Cisco UCS C240 M4 (UCSC-C240-M4)

  • CPU : UCS-CPU-E5-2620, UCS-CPU-E5-2630, UCS-CPU-E5-2630L, UCS-CPU-E5-2640, UCS-CPU-E5-2643, UCS-CPU-E5-2650, UCS-CPU-E5-2650L, UCS-CPU-E5-2660, UCS-CPU-E5-2665, UCS-CPU-E5-2670, UCS-CPU-E5-2680, UCS-CPU-E5-2690
  • Memory : UCS-MR-1X081RU-A, UCS-MR-1X162RU-A, UCS-ML-1X324RU-A

2.2(2e)A

2.2(2d)A

2.2(2c)A

ucs-catalog.2.2.2c.T.bin 1

Cisco UCS B22 M3 (UCSB-B22-M3)

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

2.2(2c)A (cont’d))

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

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

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-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-ML-2X324RY-E, UCS-MR-2X082RY-E, UCS-MR-2X162RY-E

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

Chassis

  • UCSB-5108-HVDC

2.2(1f)A

2.2(1e)A

ucs-catalog.2.2.1d.T.bin

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

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
UCSB-5108-AC2
UCSB-5108-DC2

5.Available for separate download.

Further details are in the Cisco UCS Manager Configuration Guides .

New Hardware Features in Release 2.2

Release 2.2(3a) adds support for the following:

  • Cisco UCS B200 M4 servers shipping with Intel E5-2600 v3 series CPUs
  • Cisco UCS C220 M4/C240 M4 servers shipping with Intel E5-2600 v3 Series CPUs
  • Cisco UCS VIC 1227 adapter modular LOM (mLOM) for Cisco UCS C220 M4 & C240M4 servers
  • Cisco UCS VIC 1340 and VIC 1380 adapters modular LOM (mLOM) for Cisco UCS B200 M3 and B200 M4 servers
  • Fusion IO ioMemory for B-series and C-series servers
  • LSI Nytro MegaRaid NMR 8110-4i for C240 M3 server
  • NVIDIA Tesla K40 GPU accelerator for C-Series Servers
  • Emulex OCE14102 CNA
  • FX3S Support
  • 10GB TwinAx cables (1m, 2m, and 5m)
  • 10GB AOC cables (1m, 2m, 3m, 5, 7m, and 10m)

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.
  • Chassis with updated backplane and High Voltage DC support (200v DC - 380v DC) - UCSB-5108-HVDC

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

  • Chassis with updated backplane UCSB-5108-AC2 or UCSB-5108-DC2

New Software Features in Release 2.2

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

  • QPI snoop mode via Service Profile

Release 2.2(3a) adds support for the following:

  • Tiered Port-Licensing for direct-connect C-Series servers
  • Smart Call Home Enhancements
  • BIOS/CIMC secure boot support for C-series servers
  • DIMM blacklisting support for C-series servers
  • ENIC - DPDK Integration
  • Stateless Offload for Overlay Networks (NVGRE / VXLAN)
  • Monitoring of the IOM/FI interfaces
  • LAN and SAN topology information
  • usNIC support for IP-routable transport

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

  • Support for ‘ lacp suspend-individual ’ on Uplink Port-Channel

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 (B-series only)
  • UEFI Boot Support
  • FlexFlash (Local SD card) support
  • Trusted Platform Module (TPM) Inventory
  • DIMM Blacklisting and Correctable Error Reporting (B-series only)
  • C-Series Board Controller Firmware Management

Note 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(3a) introduces the following behavior changes:

  • CSCup09981—Server reboot was required on FlexFlash disable in Local Disk Configuration Policy.

Old behavior: Server reboot was required on FlexFlash disable in Local Disk Configuration Policy.

New behavior: Server reboot is no longer required when FlexFlash is disabled in Local Disk Configuration Policy.

Impact: Customer has to make sure that the FlexFlash SD cards are not being used by the server before disabling.

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.

Impact: 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.

Impact: 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(3c):

 

Table 6 Resolved Caveats in Release 2.2(3c)

Defect ID
Description
First Bundle Affected
Resolved in Release

CSCuq35685

IGMPv2 traffic no longer causes MAC flapping on upstream switches when the FI has multiple uplinks connecting to different switches.

2.2(1b)A

2.2(3c)A

CSCuq46105

UCS Manager now uses power sequencer version 3.0 to address the rare issue of an unexpected reboot to the Cisco UCS 6248 FI.

2.2(1c)A

2.2(3c)A

CSCuq63086

Cisco B200 M3 no longer fails with a ‘Controller 1 on server x/y is inoperable’ error.

2.2(1e)B

2.2(3c)B

CSCur08722

Firmware upgrade FSM no longer fails on the Cisco UCS C240 M3 server with the following error:

IVY Bridge Processor is installed on this server, cannot downgrade to unsupported CIMC version.

2.2(3a)A

2.2(3c)A

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

 

Table 7 Resolved Caveats in Release 2.2(3b)

Defect ID
Description
First Bundle Affected
Resolved in Release

CSCuq63592

Blade association no longer fails on servers with Cisco UCS VIC 1340 or VIC 1380 adapters when some vHBAs manually configured in the service profile on Host Port 1 or Host Port 2 while other vHBAs are placed systematically by setting "Desired Host Port" to ‘ ANY .’

2.2(3a)A

2.2(3b)A

CSCuq64931

Blades with Cisco UCS VIC 1340 or VIC 1380 adapters no longer fail to PXE boot / iSCSI boot/ SAN boot when SRIOV vNICs (PF and VF) are placed on first host port and PXE vNIC/ iSCSI vNIC / SAN boot vHBA are placed on second host port.

2.2(3a)A

2.2(3b)A

CSCuq70724

DIMM I2C controller is automatically reset if there are invalid I2C transactions that prevent the chassis from obtaining temperature readings from blades (which can cause fan speeds to spin at 100%).

2.2(2d)B

2.2(3b)B

CSCuq81262

Cisco UCS Manager no longer becomes unresponsive (after seven days when VM-related data collection begins) if anonymous reporting (AR) is enabled when upgrading to Cisco UCS Manager release 2.2(3b) in an environment specifically configured with VMs that use VM-FEX on any hypervisor.

2.2(3a)A

2.2(3b)A

CSCuq92477

Infra bundle upgrades from Cisco UCS Manager release 2.2(3a) no longer fail if performed from Cisco UCS Central.

2.2(3a)A

2.2(3b)A

CSCur01379

The security vulnerabilities identified by Common Vulnerability and Exposures (CVE) CVE-2014-7169, CVE-2014-6271, CVE-2014-6277, CVE-2014-7186, CVE-2014-7187, and CVE-2014-6278 are addressed.

2.0(1q)A

2.2(3b)A

The following caveats are resolved in Release 2.2(3a):

 

Table 8 Resolved Caveats in Release 2.2(3a)

Defect ID
Description
First Bundle Affected
Resolved in Release

CSCuo60330

IOMs are no longer unreachable after upgrading the FI when upgrading to Cisco UCS Manager, Release 2.2(2) or later.

2.2(1d)A

2.2(3a)A

CSCue93518

Cisco UCS Manager now displays an alert when users are close to reaching the VLAN port count limit.

2.1(1a)A

2.2(3a)A

CSCug73260

The UCS Manager DME process no longer crashes on the subordinate FI during an upgrade or power outage.

2.1(1a)A

2.2(3a)A

CSCui12868

Some conditions that result in the chassis displaying a thermal sensor reading error due to third-party applications accessing the PCH SMBus or CPU SMBus controller have been fixed.


Note An additional enhancement addressing this same symptom will be included in the upcoming 2.2(3b) patch.


2.0(4b)B

2.2(3a)B

CSCui53234

Call Home alerts now include alert customization and service profile information.

2.0(3a)A

2.2(3a)A

CSCul69513

Interface (error) counters for the fabric ports on the IOM can now be monitored using the UCS Manager GUI and CLI.

2.1(1a)A

2.2(3a)A

CSCum48026

Local vMedia mounts in progress can now be cancelled by the user instead of waiting for a timeout.

2.2(2c)B

2.2(3a)B

CSCun00368

A fault is now raised if the FI has less memory than expected.

2.1(3b)A

2.2(3a)A

CSCun00720

The UCS 6296 FI no longer fails to boot after a software upgrade, reload, or power cycle.

2.0(2m)A

2.2(3a)A

CSCun66874

DIMM blacklisting no longer prevents the host from accessing the DIMM bus.

2.2(2c)A

2.2(3a)A

CSCun84951

MCA and MCE errors are now logged when a Cisco UCS blade server reboots due to a CPU CATERR fault.

2.2(1b)B

2.2(3a)B

CSCuo09991

The primary FI and secondary FI in a HA cluster no longer fail to sync after rebooting.

2.2(1b)A

2.2(3a)A

CSCuo34760

vEthernet interfaces and VIFs no longer remain in down state if the primary FI in a HA cluster is rebooted and comes up as the secondary FI.

2.1(2d)A

2.2(3a)A

CSCuo48978

Cisco UCS Manager now prevents downgrading the BIOS to an unsupported version on Cisco UCS C22, C24, C220, and C240 M3 servers with E5-2600 or E5-2400 v2 series CPUs.

2.1(2a)C

2.2(3a)C

CSCuo51708

Cisco UCS Manager downgrade no longer fails during autoinstall.

2.2(1d)A

2.2(3a)A

CSCuo76425

Ingress CRC errors are no longer seen over TwinA.x cables with rapid link-flaps on the 6248 and 6296 platforms

2.2(3a)A

2.2(3a)A

CSCuo80898

When upgrading an environment from Release 2.1(1a) to newer releases, the SAN port-channels that have member ports with different max speed will not be configured and a fault is raised to indicate this.

2.1(2a)A

2.2(3a)A

CSCup05019

Status of FlexFlash controller no longer shows as ‘ Disconnected Partition From Host ” and SD cards are now visible in the local disks option after inserting those cards into a blade with Flexflash enabled in local storage policy.

2.2(1d)A

2.2(3a)A

CSCup47504

Cisco UCS VIC 1240 adapter no longer fails to complete the PXE boot process due to missing DHCP offer on a Cisco UCS 6200 FI using an ASA as the DHCP relay.

2.2(1d)B

2.2(3a)B

CSCup61601

FI no longer crashes upon executing the show platform software fcoe_mgr info global command when there are too many noncontiguous VLANs configured.

2.2(1d)A

2.2(3a)A

CSCup61947

MAC learning no longer fails after adding 1,000 or more VLANs with a large PV count with 120 or more virtual interfaces each with 1,000 VLANs.

2.2(1d)A

2.2(3a)A

CSCup82677

Line rate is no longer limited to 10GB even when QoS line rate is set to 20GB or 40GB.

2.1(3b)A

2.2(3a)A

CSCup88087

Cisco UCS B200 M3 server with a single CPU no longer reports faults for a second CPU not present in the hardware.

2.1(3a)A

2.2(3a)A

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

 

Table 9 Resolved Caveats in Release 2.2(2e)

Defect ID
Description
First Bundle Affected
Resolved in Release

CSCur01379

The security vulnerabilities identified by Common Vulnerability and Exposures (CVE) CVE-2014-7169, CVE-2014-6271, CVE-2014-6277, CVE-2014-7186, CVE-2014-7187, and CVE-2014-6278 are addressed.

2.0(1q)A

2.2(2e)A

CSCur16493

The UCSC-GPU-VGXK2 GPU adapter firmware has been updated to version 80.04.F5.00.03_2055.0552.01.08.

2.2(2a)B

2.2(2e)B

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

 

Table 10 Resolved Caveats in Release 2.2(2d)

Defect ID
Description
First Bundle Affected
Resolved in Release

CSCui12868

Some conditions that result in the chassis displaying a thermal sensor reading error due to third-party applications accessing the PCH SMBus or CPU SMBus controller have been fixed.

2.0(4b)B

2.2(2d)B

CSCun25692

M71KR-Q no longer runs out of heap and causes SAN boot failure while allocating memory to critical data structure.

2.2(1b)B

2.2(2d)B

CSCun79973

vNIC no longer hangs when QoS policy on a vNIC is changed while a Netflow session with transmit monitoring is active on that vNIC.

2.2(2c)A

2.2(2d)A

CSCuo34760

Veths/VIFs no longer remain in down state on a Primary FI that gets rebooted and comes back up as subordinate FI.

2.1(2d)A

2.2(2d)A

CSCuo79500

A vNIC with a usNIC connection policy no longer falsely shows as a Dynamic vNIC after a second vNIC with a usNIC policy is added.

2.2(1c)A

2.2(2d)A

CSCuo98011

Service dcosag no longer crashes during Infra firmware upgrade (ucs-k9-bundle-infra.2.2.2c.A.bin) if upgrade is initiated from Cisco UCS Central, when Cisco UCS Manager is registered to Cisco UCS Central using IPv4 address and image bundles are not present in Cisco UCS Manager.

2.2(2c)A

2.2(2d)A

CSCup07488

ECC sensors no longer read or report invalid “Upper Non-Recoverable” data when there are existing failed PECI transactions on a blade.

2.2(2c)B

2.2(2d)B

CSCup61601

FCOE_MGR no longer crashes when FI is configured with too many noncontiguous VLANs.

2.2(1d)A

2.2(2d)A

CSCup61947

MAC learning no longer fails after adding 1000 or more VLANs with a large PV count with 120 or more virtual interfaces each with 1000 VLANs.

2.2(1d)A

2.2(2d)A

CSCup82677

A Cisco UCS system with ESXi OS is no longer limited to 10Gb speed when QoS is configured with line-rate of 20Gb or 40Gb.

2.2(1d)A

2.2(2d)A

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

 

Table 11 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

CSCuj81245

OS kernel and adapter logs no longer report multiple FNIC aborts when user starts a heavy write operation to SAN disk.

2.2(1b)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 Cisco UCS VIC 1240 and Cisco UCS 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 Cisco 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(1f):

 

Table 12 Resolved Caveats in Release 2.2(1f)

Defect ID
Description
First Affected Bundle
Resolved in Release

CSCuq35685

IGMPv2 traffic no longer causes MAC flapping on upstream switches when the FI has multiple uplinks connecting to different switches.

2.2(1b)A

2.2(1f)A

CSCur01379

The security vulnerabilities identified by Common Vulnerability and Exposures (CVE) CVE-2014-7169, CVE-2014-6271, CVE-2014-6277, CVE-2014-7186, CVE-2014-7187, and CVE-2014-6278 are addressed.

2.0(1q)A

2.2(1f)A

CSCuo34760

vEthernet interfaces and VIFs no longer remain in down state if the primary FI in a HA cluster is rebooted and comes up as the secondary FI.

2.1(2d)A

2.2(1f)A

CSCuq63086

Cisco B200 M3 no longer fails with a ‘Controller 1 on server x/y is inoperable’ error.

2.2(1e)B

2.2(1f)B

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

 

Table 13 Resolved Caveats in Release 2.2(1e)

Defect ID
Description
First Affected Bundle
Resolved in Release

CSCup61947

MAC learning no longer fails after adding 1000 or more VLANs with a large PV count with 120 or more virtual interfaces each with 1000 VLANs.

2.2(1d)A

2.2(1e)A
2.2(2d)A

CSCul44421

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

2.0(5f)B

2.2(1e)B

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(1e)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(1e)A

CSCun25187

Cisco UCS Manager no longer becomes Lost-Visibility in Cisco 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(1e)A

CSCun25692

M71KR-Q no longer runs out of heap and causes SAN boot failure while allocating memory to critical data structure.

2.2(1b)B

2.2(1e)B
2.2(2d)B

CSCun83328

vNIC PCI addresses no longer get changed when downgrading from release 2.2(1e) to 2.0(5).

2.2(1d)B

2.2(1e)B

CSCun84897

Server reboots are no longer triggered when vNIC template is used with global service profile and customer changes MTU setting.

2.1(3a)A

2.2(1e)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(1e)A

CSCuo79500

Cisco UCS Manager no longer falsely displays information that indicates a vNIC with a usNIC connection policy was automatically changed to dynamic vNIC when a customer adds a second vNIC with a usNIC policy.

2.2(1c)A

2.2(1e)A

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

 

Table 14 Resolved Caveats in Release 2.2(1d)

Defect ID
Description
First Bundle Affected
Resolved in Release

CSCui31011

VIFs and vNICs 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 15 Resolved Caveats in Release 2.2(1c)

Defect ID
Description
First Bundle Affected
Resolved in Release

CSCum43435

The Cisco UCS 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 16 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(3b):

 

Table 17 Open Caveats in Release 2.2(3b)

Defect ID
Symptom
Workaround
First Bundle Affected

CSCuq74763

On Windows 2012 hypervisors, vmNICs configured with NVGRE network virtualization fail to initiate network traffic when NVGRE NIC task offloads is enabled.


Note Installing patch KB2779768 resolves the issue for ping operation but does not resolve the issue for TCP/UDP traffic.


To use NVGRE NIC task offload feature, upgrade the hypervisor to Windows 2012 R2.

Alternatively, disable the NVGRE task offload feature using Cisco UCS Manager or in the hypervisor while using Windows 2012.

2.2(3a)A

CSCuq88436

XML Parsing Error due to multiple "jbod" diskState attributes is incorrectly specified when a server with two or more local disks is configured with "No RAID" disk config policy.

This issue has no known workaround.

2.2(3b)A

CSCuq40256

After an IOM is reset, Cisco UCS Manager shows that the IOM interface for the blade is active, but the priority flow control shows that the blade is disabled.

Reset the affected Data Center Ethernet.

Alternatively, you can reboot the IOM.

2.1(3c)C

CSCuq95926

If you unplug the primary management cable when the HA is not complete, the Cisco UCS FI HA status remains in “switchover in progress”.

Restart the primary DME using the pkill dme command, or reboot the FI.

2.2(2c)B

CSCup46033

On a FI with a GEM module installed, the total default quantity of licenses does not match the total quantity of licenses available by default.

This issue has no known workaround.

2.1(1f)A

CSCuq51890

entPhysicalDescr is returning the wrong getnext values during SNMPwalk.

Perform an SNMPwalk of 1.3.6.1.2.1.47.1.1.1.1.2.1 followed by 1.3.6.1.2.1.47.1.1.1.1.2.24 to get the remaining information.

2.2(2c)A

The following caveats are open in Release 2.2(3a):

 

Table 18 Open Caveats in Release 2.2(3a)

Defect ID
Symptom
Workaround
First Bundle Affected

CSCuo11544

In some cases, NicAG gets stuck when getting events from adapter when that adapter is busy performing other tasks.

To work around this issue, perform one of the following options:

  • Check for servers that are stuck in discovery, association, or disassociation state and, if found, decommission them. Then confirm that firmware update on adapters succeeds.
  • Instead of performing adapter firmware updates on multiple servers, perform a firmware update on servers in batches.

2.2(3a)B

CSCuq09577

In some cases, a system running a 6100 FI setup with a large number of rack servers becomes unresponsive due to a high number of error messages overfilling the Cisco UCS Manager log file when an insufficient number of FEX/IOM uplinks are configured.

Make sure a sufficient number of IOM/FEX uplinks are configured so that vNICs configured on each service profile do not exceed the limit.

2.2(2c)A

CSCuq14172

Windows 2012 and Windows 2012R2 systems hang (boot and installation) when TXT is enabled via BIOS setup.

This issue has no known workaround. Disable TXT and reboot.

2.2(2a)B

CSCuq28367

Host continuously reboots if scriptable vMedia mount fails and the same device type is also configured in boot policy.

Uncheck to disable the “Retry on mount fail” option in scriptable vMedia policy.

2.2(3a)A

CSCuq33306

SAN boot with Emulex adapter fails with the first vHBA created when creating a Cisco UCS Manager service profile boot policy to boot from SAN LUN from the first vHBA.

Use the second vHBA for booting and map boot targets to the second vHBA in the Emulex adapter.

2.2(3a)A

CSCuq44049

In rare cases, when adding SD cards dynamically (without powering down server) to a server without SD cards or when dynamically adding one SD card to a server with only one SD card, the server gets stuck in sync mode and disconnects existing drives accessed by host from an SD card.

To avoid potential data loss, first disable HOST VD access (from WEB UI or CLI) if VD access is enabled. Then, after confirming each SD card is plugged in properly, execute reset of the flex flash controller (from WEB UI or CLI).

2.0(3b)A

CSCuq63592

In some cases, blade association fails on servers with Cisco UCS VIC 1340 or Cisco UCS VIC 1380 adapters when some vHBAs are placed manually on Host Port 1 or Host Port 2 and some are placed by system when "Desired Host Port" is set to ‘ANY.’

Place all vHBAs manually on host ports 1/2 or allow system to place all vHBAs.

2.2(3a)A

CSCuq64931

Blades with Cisco UCS VIC 1340 or Cisco UCS VIC 1380 adapters fail remote OS boots when SRIOV vNICs are placed on first host port and static vNICs (PXE, iSCSI, or vHBA) are placed on second host port.

Place the SRIOV vNICs on the second host port manually via GUI or CLI options to set host port when configuring service profile.

2.2(3a)A

CSCuq81262

If anonymous reporting (AR) is enabled after upgrading Cisco UCS Manager to release 2.2(3a) in an environment specifically configured with VMs that use VM-FEX on any hypervisor, then Cisco UCS Manager becomes unresponsive after seven days when VM-related data collection begins.

Disable AR feature in Cisco UCS Manager if running any VMs that use VM-FEX on any hypervisor. (The AR feature is disabled by default.)

If this issue (with AR enabled) is encountered, contact Cisco TAC for solution.

2.2(3a)A

CSCuq92477

Infra bundle upgrades from Cisco UCS Manager release 2.2(3a) fail if performed from Cisco UCS Central when upgrade process becomes unresponsive during 'PollActivateOfUCSM' stage if Cisco UCS Manager does not already contain the management image.

Manually download the Cisco UCS management image or the complete infra bundle to Cisco UCS Manager before triggering the infra upgrade from Cisco UCS Central.

2.2(3a)A

Resolved in 2.2(3b)A.

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

 

Table 19 Open Caveats in Release 2.2(2d)

Defect ID
Symptom
Workaround
First Bundle Affected

CSCuo87059

In rare cases, backplane ports on an IOM that is providing a NULL serial number to Cisco UCS Manager may be missing after chassis decommission and recommission.

Perform an additional decommission and recommission cycle.

2.2(2c)B

CSCup00833

In rare cases, B440 M1 and M2 servers may fail discovery after CIMC activation during upgrade from release 2.0(2q).

In Cisco UCS Manager CLI, use reset slot x/y where "x/y" designates the B-series server.

2.1(3c)B

CSCup05598

SNMP Community string shows blank text field even after adding and saving the string.

This issue has no known workaround.

This is a different convention than previously used but running a simple snmpget or snmpwalk against Cisco UCS Manager VIP with the string just saved should confirm that SNMP is functional.


Note Although the field is blank, the display of the 'Set: yes' or 'Set: No' notifier indicates the value is present.


2.2(1d)A

CSCup20961

Unable to add VIFs to a service profile or make modifications that require a new VIF on an existing interface, such as when adding fabric failover.

Restart svc_sam_dme process.

2.2(1d)A

CSCup38317

In some rare instances, typically during host power on, a board fails to discover and one of the following errors is displayed:

" Reason: CIMC did not detect storage controller " or " CIMC storage subsystem not yet initialized. "

Decommission and reacknowledge the server.

2.2(2c)B

CSCup40056

In some rare cases, if hypervisor and VM storage traffic are sharing the same fNIC(s) and FI is in switching mode and configured with Cisco VIC 1240 and with NPIV on Windows 2012R2, live migrations may fail.

Assign separate fNICs for hypervisor and VM storage traffic.


Note For more information, refer to troubleshooting technote #117929.


2.2(1d)B

CSCup40441

In some cases, attempts to remove a service profile that contains two vNICs and two vHBAs from a B200 M3 server with a 61xx FI and a M73KR-Q adapter running release 2.1(3b) will fail with the following error:

Unconfigure server from service profile pre-boot environment (FSM-STAGE:sam:dme:ComputePhysicalDisassociate:PnuOSUnconfig)
Error 4106 - Unable to find FC Device.
 

and Discovery fails with this error:

Discovery Fail Error: Unable to get Fibre Channel Device Information from the system (sam:dme:ComputeBladeDiscover:PnuOSInventory)

This issue is caused by an unsupported WWPN in the service profile. If WWPN has the multicast bit set ( Ex.20:01:01:01:31:00:00:23 ), then Qlogic flags the WWPN as invalid.

To avoid this issue, always use WWPN with multicast bit turned off
( Ex. 20:01:00:01:31:00:00:23/20:01:
00:00:31:00:00:23
).


Note This issue can also be avoided by creating WWPN pool from Cisco UCS Manager WWPN template.


Once the problem occurs, the solution requires an RMA for the card.

2.1(3b)B

CSCup45930

When upgrading Cisco UCS B230 M2 server from release 2.2(1 x ) to 2.2(2 x ) or from 2.2(2 x ) to 2.2(3 x ), or when upgrading Cisco UCS C460 M4 server from release 2.2(2 x ) to 2.2(3 x ), association fails with “ Unable to find storage controller ” error.

Reacknowledge the server.

2.2(1e)A

CSCup88161

In certain race conditions when running 2.2(1d) or later firmware, if a memory location which was freed is being used, the 6248 FI kernel crashes with no core.

This issue has no known workaround. If this condition occurs, the system will auto-reboot to a stable condition.

2.1(1d)A

CSCuq14172

Windows 2012 and Windows 2012R2 systems hang (boot and installation) when TXT is enabled via BIOS setup.

This issue has no known workaround. Disable TXT and reboot.

2.2(2a)B

CSCuq22707

In some cases, vMotion of multiple VMs at the same time causes stale MAC addresses after VM migration, which results in traffic loss between blades attached to the same FI.

This issue has no known workaround. The stale MAC addresses will eventually age out.

2.2(2c)A

CSCuq46105

In some rare cases, the Cisco UCS 6248 FI will unexpectedly reboot with following FI OBFL log in show tech:

Uptime: 10964, 0 days 3 hour(s) 2 minute(s) 44 second(s)
Reset Reason: Unknown (0)
Reset Reason SW: Unknown (0)
Reset Reason (HW): uC reset code: 0x0100
ADM1066 Power Good Triggered Reset
Card Mode..........................: Runtime

This issue has no known workaround.

2.2(1c)A

Resolved in 2.2(3c)A.

CSCuq53385

In some cases, when attempting to regenerate expired self-signed Cisco UCS Manager certificate, Cisco UCS Manager will return the following regarding regeneration of default Key Ring:

Cannot Create Certificate Request for default KeyRing
 

This is accompanied by the following error messages in svc_sam_dme log file in Cisco UCS Manager techsupport log bundle:

=========
[INFO][0xac56abb0][Aug 6 05:20:47.182][exception_handling:rep] FATAL[5|702]: ../feature/nuova/sam/sam/src/app/sam/dme/imp/pki/MuPkiEpEndExplicitUpdateCbImp.cc(279):validateKeyRingNodes pkiKeyRing[sys/pki-ext/keyring-default] : Cannot Create Certificate Request for default KeyRing
 
[INFO][0xac56abb0][Aug 6 05:20:47.183][exception_handling:rep] ERROR[3|702] ../feature/nuova/sam/sam/src/lib/framework/core/proc/Doer.cc(874):exceptionCB: exception encountered during processing: "Cannot Create Certificate Request for default KeyRing" [702] Cannot Create Certificate Request for default KeyRing
=========

To work around this issue, try the following:

1. When possible, use third-party CA signed keyring from internal or external CA; or

2. Contact TAC to resolve the error and to regenerate self-signed certificate.


Note Cisco UCS Manager does not support creating cert-req for default key ring.


2.1(3d)A

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

 

Table 20 Open Caveats in Release 2.2(2c)

Defect ID
Symptom
Workaround
First Bundle Affected

CSCur05013

Messages.log file on a Cisco UCS B200 M2 blade fails when the log file fills with messages including:

364:BMC lost control of the bus.[0xd 0x0].

This issue has no known workaround.

2.2(2c)B

CSCur38408

When a PCIe card is present in slot 2 and riser 2 is missing, fabric interconnect HA failover can cause the attached Cisco UCS C460 M4 servers to reboot.

To work around this issue, try one of the following:

  • Move the card in slot 2 to a different slot.
  • Add PCIe riser 2.

2.2(2c)A

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 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(2c)A

Resolved in 2.2(2d)

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 (FIs / IOMs / 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 vEthernet interfaces 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. (Preferred) CIMC reset of affected servers will force shallow discovery of the server which fixes this issue. This will not reboot the server.

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

3. Reacknowledge affected servers. However, server gets rebooted.

2.1(2d)A

Resolved in 2.2(2d)

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

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

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

Resolved in 2.2(2d)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, FNIC driver bundled with driver disk does not load when installing on a standalone C-series server and does not return error to indicate failure.

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

2.2(1b)A

CSCup07488

ECC sensors report invalid “Upper Non-Recoverable” data when there are existing failed PECI transactions on a blade.

Restart the ipmi stack while the host is up and running and BIOS_POST_COMPLETE is asserted. However, if PECI failures persist on the blade, this task will need to be repeated.

2.2(2c)B

Resolved in 2.2(2d)B

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

 

Table 21 Open Caveats in Release 2.2(2a)

Defect ID
Symptom
Workaround
First Bundle Affected

CSCur16493

Customers with the UCSC-GPU-VGXK2 GPU adapter should update to release 2.2(3f) to receive updated firmware.

Upgrade to release 2.2(2e) and verify that the UCSC-GPU-VGXK2 firmware has been updated to version 80.04.F5.00.03_2055.0552.01.08.

2.2(2a)B

Resolved in 2.2(2e)B.

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

 

Table 22 Open Caveats in Release 2.2(1f)

Defect ID
Symptom
Workaround
First Bundle Affected

CSCur37260

FI upgrade or downgrade may fail due to lack of disk space in /mnt/pss. The following error may be seen:

PL20-B %SYSMGR-2-NON_VOLATILE_DB_FULL: System non-volatile storage usage is unexpectedly high at 99%

Contact Cisco TAC to recover from this issue.

2.1(3c)A

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

 

Table 23 Open Caveats in Release 2.2(1e)

Defect ID
Symptom
Workaround
First Bundle Affected

CSCuo97907

Blades using a BIOS policy that utilizes the core multi- processing option do not honor changes made to the policy.

Disable the cores using the operating system.

2.1(3b)A

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

 

Table 24 Open Caveats in Release 2.2(1d)

Defect ID
Symptom
Workaround
First Bundle Affected

CSCuo11700

In rare cases, a context switch while applying a new sam.config triggers a race condition that causes the httpd.sh or ucssh process to crash.

The httpd.sh process will recover after the crash.

To fix the ucssh process crash, re-launch the Cisco UCS Manager CLI.

2.2(1d)A

CSCuo60330

After upgrading the fabric interconnect to release 2.2(2) or later, the IOMs are unreachable, HA is not ready, and previous server interfaces show no configuration.

Contact Cisco TAC to recover from this issue.

2.2(1d)A

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

Resolved in 2.2(1e)A and 2.2(2c)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

Resolved in 2.2(1e)A and 2.2(2c)A

CSCun25187

When using third-party certificates with Cisco UCS Central, status of Cisco UCS Manager might be displayed in Cisco UCS Central as 'Lost-Visibility' if a keyring with a certificate chain is configured to use https communication. 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

Resolved in 2.2(1e)A and 2.2(2c)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 vNIC of a service profile is configured to allow a VLAN defined in appliances cloud in the LAN configuration, the show run interface vethernet <x> and show interface vethernet <x> switchport command outputs 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 Java Control Panel. (Location may vary depending on operating system and browser preferences.)

2. Lower the Security level to Medium.

3. Start Cisco UCS Manager.

4. In warning popup, check “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 Java Control Panel. (Location may vary depending on operating system and browser preferences.)

2. In Security area, click Edit Site button to add 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

Resolved in 2.2(1e)A and 2.2(2c)A

CSCup61601

FCOE_MGR crashes if FI is configured with too many noncontiguous VLANs.

Decrease the number of noncontiguous VLANs on the FI.

2.2(1d)A

Resolved in 2.2(2d)A

CSCup61947

In some cases, MAC learning fails after adding 1000 or more VLANs with a large PV count with 120 or more virtual interfaces each with 1000 VLANs.

To account for this issue, monitor the dleft_lif_vlan_mbr table to ensure total VLANs does not exceed 16,000.

If VLAN total approaches or exceeds this limit, reduce VLAN count and then reboot the FI as needed to recover from a MAC learning failure state.

2.2(1d)A

Resolved in 2.2(2d)A

CSCup82677

A Cisco UCS system with ESXi OS will not exceed 10Gb speed even when QoS is configured with line-rate of 20Gb or 40Gb.

To resolve this issue, set the Rate(Kbps) value in the QoS policy to be the desired value above 10000000. The value must be numeric, such as 20000000 or 40000000.

2.2(1d)A

Resolved in 2.2(2d)A

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

 

Table 25 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

CSCuo79500

Service dcosag falsely displays information that indicates a vNIC with a usNIC connection policy was automatically changed to dynamic vNIC when a customer adds a second vNIC with a usNIC policy.

This issue does not effect functionality. The usNIC policies are properly set; the radio button selection falsely displays the selection of dynamic vNIC policy. Saved changes can be seen by clicking on the usNIC radio button.

2.2(1c)A

Resolved in 2.2(2d)A

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

 

Table 26 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 reacknowledgment, 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 VIFs 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 parameter in quotes can be any description for 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

CSCuj81245

Multiple FNIC aborts in OS kernel and adapter logs when user starts a heavy write operation to SAN disk.

Change IO throttle count from 16 to 256.

2.2(1b)A

Resolved in 2.2(2c)B

CSCun25692

Under certain timing conditions while allocating memory to critical data structure, M71KR-Q could run out of heap resulting in SAN boot failure."

To restore expected CNA behavior, downgrade to 2.1(3a) release or upgrade to version where this issue has been resolved.

2.2(1b)B

Resolved in 2.2(1e)B and 2.2(2d)B

Known Limitations

Known limitations for Cisco UCS Manager 2.2 releases are described in the following sections:

LAN and SAN Topology Information Limitation

LAN and SAN topology information is available only through XML and CLI. This information is not exposed in the Cisco UCS Manager GUI.

Default Zoning 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 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 27 Known Limitations in Release 2.2

Defect ID
Symptom
Workaround
First Bundle Affected

CSCtq79496

FCoE traffic may experience momentary disruption when system QoS policy is being modified.

This issue has no known work around. To avoid this issue, all QoS policy changes should be made during a maintenance window.

2.0(1m)A

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 is found when adapters are in DIAG mode.

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

CSCuo14624

When FlexFlash member of dual SD card setup fails and needs to be replaced, the OS needs to be reinstalled, as well.

This issue has no workaround.

2.1(2a)B

CSCup18983

MAC address changes after upgrade from 2.1 to 2.2.


Note This behavior is expected due to fix for CSCtg93294, which offsets MAC address by 1.


Update MAC security on port with new MAC address. From local-mgmt for each FI, use show mgmt-ip-debug command to find mac address.

2.2(1b)A

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.