Guest

Cisco UCS Manager

Release Notes for Cisco UCS Manager, Release 3.0, for Cisco UCS Mini

  • Viewing Options

  • EPUB (67.1 KB)
  • MOBI (89.3 KB)
  • PDF (191.3 KB)
  • Feedback

Table of Contents

Release Notes for Cisco UCS Manager, Release 3.0 , for Cisco UCS Mini

Contents

Revision History

Introduction

System Requirements

Hardware and Software Interoperability

Internal Dependencies

New Hardware Features in Release 3.0

New Software Features in Release 3.0

Resolved Caveats

Open Caveats

Known Limitations

Unsupported Features

Default Zoning

Known Limitations and Behaviors

Related Documentation

Obtaining Documentation and Submitting a Service Request

Release Notes for Cisco UCS Manager, Release 3.0, for Cisco UCS Mini

First Published: July 23, 2014
Last Updated: July 23, 2014

This document describes system requirements, new features, resolved caveats, known caveats and workarounds for Cisco UCS Manager software, Release 3.0, which supports only Cisco UCS Mini.

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 3.0

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

Release
Date
Description

3.0(1c)

July 23, 2014

Created release notes for Cisco UCS Manager, Release 3.0(1c).

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 release of Cisco UCS Manager (Release 3.0) is a platform-specific release that runs only on the Cisco UCS 6324 fabric interconnect (FI).

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 a 1.6. x or 1.7. x version of the Java Runtime Environment (JRE).
  • 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.2 or newer is required for use with Cisco UCS Manager, Release 3.0.

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 2 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 2 Internal Dependencies

Component
Recommended Minimum Software Version
Recommended Software Version
Servers

B200 M3

3.0(1c)

3.0(1c)

C220 M3

3.0(1c)

3.0(1c)

C240 M3

3.0(1c)

3.0(1c)

Adapters

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

3.0(1c)

3.0(1c)

UCSC-PCIE-CSC-02

3.0(1c)

3.0(1c)

Chassis

UCSB-5108-AC2

3.0(1c)

3.0(1c)

Fabric Interconnect

Cisco UCS 6324

3.0(1c)

3.0(1c)

Power Supplies

UCSB-PSU-2500ACDV

3.0(1c)

3.0(1c)

40GB Connections

QSFP-4SFP10G-CU1M
QSFP-4SFP10G-CU3M
QSFP-4SFP10G-CU5M

QSFP-4X10G-AC7M
QSFP-4X10G-AC10M

QSFP-4X10G-AOC1M
QSFP-4X10G-AOC3M
QSFP-4X10G-AOC5M
QSFP-4X10G-AOC7M
QSFP-4X10G-AOC10M

10GB Connections

SFP-10G-SR
SFP-10G-SR-X
SFP-H10GB-CU1M
SFP-H10GB-CU3M
SFP-H10GB-CU5M

SFP-H10GB-ACU7M
SFP-H10GB-ACU10M

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

8GB Connections

DS-SFP-FC8G-SW

4GB Connections

DS-SFP-FC4G-SW

1GB Connections

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

New Hardware Features in Release 3.0

Release 3.0(1c) adds support for the following:

  • 6324 fabric interconnect
  • Dual-line power supply unit supporting 110V

New Software Features in Release 3.0

Cisco UCS Manager, Release 3.0 supports most software features that are supported in Cisco UCS Manager, Release 2.2(1b), as well as the following new features:


NoteFor more information, refer to For more information, refer to “Unsupported Features” section.


Release 3.0(1c) adds support for the following:

  • USB support for firmware upgrades
  • Blade-level power capping
  • Staggered Boot
  • QSFP+ (Scalability Port) Breakout Support
  • Licensing Support for QSFP+

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.


Resolved Caveats

The following resolved caveats in release 3.0(1c) are the only caveats resolved in this release since Release 2.2(1b):


NoteCisco UCS Manager, Release 3.0(1c) does not include 2.2(2x) resolved caveats except those specifically listed in Cisco UCS Manager, Release 3.0(1c) does not include 2.2(2x) resolved caveats except those specifically listed in Table 3.


 

Table 3 Resolved Caveats since Release 2.2(1b)

Defect ID
Description

CSCuj48002

vIFs and vNICs no longer fail to come up after servers are reset.

CSCul74278

Cisco UCS Manager mode- BIOS no longer fails to find local boot device.

CSCul96021

dcosAG process no longer crashes after upgrading to Cisco UCS Manager, Release 2.2(1b).

CSCum02561

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

CSCum04646

FI no longer reboots during snmpwalk when ldap config is enabled.

CSCum25003

Associated LSP/GSP events are no longer sent every 3 minutes to Cisco UCS Central inventory.

CSCum51025

Cisco UCS Manager scheduled backups from Cisco UCS Central no longer fail.

CSCum57954

Excessive dropped pings eliminated during vmotion on ESXi VMFEX DVS.

CSCum63448

Blades no longer prevent non-disruptive changes if firmware status gets stuck in “activating” state.

CSCum82888

Access to Cisco UCS Manager via GUI or CLI using VIP is no longer blocked if default keyring is deleted after an upgrade to Cisco UCS Manager Release 2.2(1b).

CSCun01514

Changes to boot order between SAN & other devices via CLI or XML API no longer fails.

CSCun19289

FI mgmt0 no longer drops packets coming from blades behind that FI.

CSCun21077

Blades running ESXi OS and vEthernet no longer enforce QoS policy bandwidth cap of 10GB when hardware allows for higher speeds unless such cap is configured by user.

CSCun70365

Service profile association no longer failing at BIOS post completion stage.

CSCun93977

Logical switch GUID no longer gets changed after a backup and restore config event.

CSCuo01287

CLI now provides the ability to report packet count per QoS class.

CSCup43698

LEDs no longer light up for wrong ports when configured with both FC and Ethernet ports.

Open Caveats

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

 

Table 4 Open Caveats in Release 3.0(1c)

Defect ID
Symptom
Workaround

CSCtr05546

A hard-pinned vNIC does not go down after VLAN is removed from pin group.

Do not use pin group policy for a vNIC.

CSCug61578

In some cases, when the mgmt 0 interface on the primary FI goes down, SNMP traps are not triggered.

This issue has no known workaround.

CSCum72579

There is no mac entry on Cisco UCS Mini for IP multicast when viewing debug command output.

Hardware forwarding mechanism is different for Cisco UCS Mini, so debug CLI has changed.

For IP multicast, use show hard int libsdk mtc l3 route-mc valid command to dump fwding entries.

CSCun80871

Cisco UCS Mini does not support some commands that are supported in classic Cisco UCS Manager releases. For example, fex and iom are not supported and all related commands are inapplicable. Additionally, some show commands do not generate output and some scope commands will return an error.

No workaround is required; avoid use of commands not supported in Cisco UCS Manager, Release 3.0.

CSCuo01287

Although output for show queuing interface command displays drop count and per-VL/qos Rx counters, it does not include per-VL Tx statistics.

This issue has no workaround.

CSCuo36944

In some cases when rebooting Cisco UCS Mini while connected to Cisco Nexus 5000, Release 5.1(3) or older via FCoE uplink, VFC may not come up and, as a result, corresponding vSAN on Nexus 5000 may end up isolated.

Work around this issue by performing one of the following tasks:

  • Recover the affected VFC by flapping it.
  • Upgrade Cisco Nexus 5000 to a newer release.

CSCuo74243

In rare cases, when port-channel member interface is flapped, some traffic may get dropped.

This issue has no workaround.

CSCup45483

In some cases, with one or a combination of the following configurations, one or all FC/FCoE up-links will remain down and, if the up-links do come up, there may be traffic disruptions and timeouts on all interfaces:

a. More than one FCoE port channel up-link.

b. More than one FC port channel up-link.

c. More than one FCoE up-link (non port-channel).

d. More than one FC up-link (non port-channel).

For cases a. and b., disable all except one port-channel.

For cases c. and d., it is advisable to convert multiple up-links to a single port-channel.

In general, there should be exactly one up-link connection to the same switch.

CSCup67796

In some cases, after activating Cisco UCS Manager on a single FI-IOM in clustering mode, user is unable to login via the GUI or access Cisco UCS Manager CLI commands.

It takes longer for Cisco UCS Manager HA election to complete on a system with a single FI-IOM in clustering mode (can take several minutes). Until the FI-IOM assumes the role of a primary node, Cisco UCS Manager will be inaccessible until FI-IOM becomes primary. You can check on progress by using the connect local-mgmt command followed by the show cluster state command.

Known Limitations

Unsupported Features

The following features are not supported in Cisco UCS Manager, Release 3.0:

  • Features, defect fixes, and platforms introduced in Cisco UCS Manager, Release 2.2(2c) and newer that are not explicitly called out in New Features or Resolved Caveats sections of this document.
  • Some features introduced in Cisco UCS Manager, Release 2.2(1b) and earlier releases:

Ethernet Switching Mode

FC End Host Mode

Private VLANs

Port Security

KVM Virtualization is not tested (although not explicitly disabled)

Default Zoning

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


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.

Known Limitations and Behaviors

The following known limitations and behaviors are not otherwise documented:

 

Table 5 Known Limitations in Release 3.0

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

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.