Guest

Cisco UCS Manager

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

  • Viewing Options

  • PDF (243.2 KB)
  • EPUB (82.3 KB)
  • MOBI (104.9 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

Capability Catalog

New Hardware Features in Release 3.0

New Software Features in Release 3.0

New Software Features in Release 3.0(1)

New Software Features in Release 3.0(2)

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: March 20, 2015

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

3.0(1d)

November 4, 2014

Updated release notes for Cisco UCS Manager, Release 3.0(1d).

December 4, 2014

Updated release notes for Catalog Release 3.0.1d.T.

January 20, 2015

Updated release notes for Catalog Release 3.0.1e.T.

3.0(1e)

February 2, 2015

Updated release notes for Cisco UCS Manager, Release 3.0(1e).

3.0(2c)

March 13, 2015

Updated release notes for Cisco UCS Manager, Release 3.0(2c).

3.0(2c)

March 20, 2015

Replaced CSCut09526 with CSCut08588 in resolved caveats.

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 available as either a Java-based application or a HTML5 GUI.

Note KVM functionality requires Java whether you use the Java-based application or HTML5 GUIs.


  • Cisco UCS Manager GUI Java-based application requires a 1.6. x or 1.7. x version of the Java Runtime Environment (JRE). The Java-based GUI 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

  • Cisco UCS Manager HTML5 GUI supports the following web browsers:

Microsoft Internet Explorer 10 or higher

Mozilla Firefox 26 or higher

Google Chrome 30 or higher

Apple Safari version 7 or higher

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

3.0(2c)

C220 M3

3.0(1d)

3.0(2c)

C240 M3

3.0(1d)

3.0(2c)

B200 M4

3.0(2c)

3.0(2c)

B420 M3

3.0(2c)

3.0(2c)

B22 M3

3.0(2c)

3.0(2c)

C220 M4

3.0(2c)

3.0(2c)

C240 M4

3.0(2c)

3.0(2c)

Adapters

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

3.0(1d)

3.0(2c)

UCSB-MLOM-40G-03
UCSB-VIC-M83P-8P

3.0(2c)

3.0(2c)

UCSC-PCIE-CSC-02

3.0(1d)

3.0(2c)

Chassis

UCSB-5108-AC2

3.0(1e)

3.0(2c)

Fabric Interconnect

Cisco UCS 6324

3.0(1e)

3.0(2c)

Power Supplies

UCSB-PSU-2500ACDV

3.0(1e)

3.0(2c)

40GB Connections

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

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

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

10GB Connections

SFP-10G-LR
SFP-10G-LR-X
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
DS-SFP-FC8G-LW

4GB Connections

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

1GB Connections

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

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 3.0(x) releases work with any 3.0(x) catalog file, but not any other 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 3 for details on the mapping of versions to bundles.

 

Table 3 Version Mapping

UCS Release
Catalog File
Adds Support for PID

3.0(1c)A

3.0(1d)A

ucs-catalog.3.0.1d.T.bin1

ucs-catalog.3.0.1e.T.bin 1

3.0(1e)A

3.0(2c)A

ucs-catalog.3.0.2c.T.bin

Cisco UCS B200 M4 (UCSB-B200-M4)
Cisco UCS B420 M3 (UCSB-B420-M3)
Cisco UCS B22 M3 (UCSB-B22-M3)
Cisco UCS C220 M4 (UCSC-C220-M4)
Cisco UCS C240 M4 (UCSC-C240-M4)
Cisco UCS VIC 1340 Adapter (UCSB-MLOM-40G-03)
Cisco UCS VIC 1380 Adapter (UCSB-VIC-M83P-8P)

1.Available for separate download.

New Hardware Features in Release 3.0

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

  • B200 M4 blade server
  • B420 M3 blade server
  • B22 M3 blade server
  • C220 M4 rack server
  • C240 M4 rack server
  • Cisco UCS VIC 1340 and VIC 1380 adapters modular LOM (mLOM) for Cisco UCS B200 M3 and B200 M4 servers

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


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.


New Software Features in Release 3.0(1)

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


Note For more information, refer to the “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+

New Software Features in Release 3.0(2)

Cisco UCS Manager, Release 3.0(2) supports the following software features that are supported in Cisco UCS Manager, Release 2.2(2c) and Release 2.2(3a):

  • 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
  • Monitoring of the IOM/FI interfaces
  • LAN and SAN topology information
  • Scriptable vMedia
  • NetFlow support
  • Pre-Upgrade Validation Checks
  • GPU Firmware Management
  • Cisco VIC Driver Enhancements:

Adaptive Interrupt Coalescing (AIC)

Accelerated Receive Flow Steering (ARFS)

netQueue Support

  • Wear-Level Monitoring on Flash Adapters
  • KVM/vMedia Client Enhancements
  • Support for ‘ lacp suspend-individual ’ on Uplink Port-Channel

Note For information on unsupported features, refer to the “Unsupported Features” section.


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

  • Fibre Channel NPV support
  • HTML5 GUI
  • PSU Firmware Management
  • Ethernet Switch Mode

Resolved Caveats

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

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

 

Table 4 Resolved Caveats in Release 3.0(2c)

Defect ID
Description
First Bundle Affected
Resolved in Release

CSCut08588

Installing the license on the Cisco UCS Mini scalability port no longer fails with the following error message:

License file SKU is different than supported in FI

3.0(1d)A

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

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

3.0(2c)A

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

3.0(2c)B

CSCum43435

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

2.2(1b)B

3.0(2c)B

CSCum51025

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

2.2(1b)A

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

3.0(2c)A

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

3.0(2c)A

CSCum95854

Cisco UCS Manager no longer frequently closes with an "event sequencing is skewed" error.

2.2(2c)A

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

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

3.0(2c)B

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

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

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

3.0(2c)B

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

3.0(2c)B

CSCup88161

6248 fabric interconnects no longer crash if a memory location that was freed is being used.

2.1(1d)A

3.0(2c)A

CSCuq09971

VIC cards no longer fail with an “identify failed” message when attempting to access the card from CIMC.

2.1(2c)A

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

3.0(2c)A

CSCuq74472

Unnecessary thermal events on IOM stating that the thermal sensor reading is not available no longer occur.

2.1(3c)A

3.0(2c)A

CSCuq92477

Infra bundle upgrades from no longer fail if performed from Cisco UCS Central.

2.2(3a)A

3.0(2c)A

CSCur29264

The security vulnerability identified by Common Vulnerability and Exposures (CVE) CVE-2014-3566 is addressed.

2.2(3a)A

3.0(2c)A

CSCur66094

Multiple components no longer stick in discovery or upgrade state with no FSM progression.

2.2(2c)A

3.0(2c)A

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

 

Table 5 Resolved Caveats in Release 3.0(1e)

Defect ID
Description
First Bundle Affected
Resolved in Release

CSCur86084

Packets with an IP header matching the hex value of 0x67 are no longer dropped by the Cisco UCS 6324 FI.

3.0(1c)A

3.0(1e)A

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

 

Table 6 Resolved Caveats in Release 3.0(1d)

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

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

3.0(1d)A

CSCuq04083

Trunking on uplink port-channel no longer fails when VSANs are mapped to VLANs with the same ID.

3.0(1c)A

3.0(1d)A

CSCuq00171

Zone server crashes no longer occur when you reduce the zone database size.

3.0(1c)A

3.0(1d)A

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


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


 

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

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

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

 

Table 8 Open Caveats in Release 3.0(2c)

Defect ID
Symptom
Workaround

CSCus12618

When installing RHEL 7 on an iSCSI LUN using iBFT with multiple paths to the target, the OS installs without issues, but after each reboot, the OS takes a long time to come up.

This issue occurs on all supported Cisco UCS B-Series servers with VIC adaptor on RHEL 7 installation where the ip=ibft kernel parameter was passed on the kernel command line for iSCSI multipath installation.

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

  • Use a single path during installation, and add a second path after the installation is complete.
  • Forcefully bring the other interfaces in the same subnet in which the iFBT interfaces are configured, which allows the iSCSI session to go through those interfaces. Use the kickstart file to bring interfaces up during installation.

CSCur86104

When the FC is directly connected via the FC storage port on the FI, if the physical connection is manually disconnected, for example, pulling the cable from the SFP or rebooting the storage processor on an appliance, the FC connectivity does not reconnect after the cable has been reconnected or the storage processor has completely reboot itself.

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

  • Reseat the SFP.
  • Hard code the link speed to 4 Gigs.
  • Change the word fill from "ARBFF" to "IDLE".
    UCSM > FI > FC Interface > Interface Properties > select "IDLE" fill word.
  • Bounce the ports.

CSCut04335

The License State and License Grace Period for the scalability port may not be in sync with the Operational State and Grace Period Used displayed in UCS Manager.

Enabling or disabling the break out ports on the peer FI may correct this issue.

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

 

Table 9 Open Caveats in Release 3.0(1c)

Defect ID
Symptom
Workaround

CSCur86104

When the FC is directly connected via the FC storage port on the FI, if the physical connection is manually disconnected, for example, pulling the cable from the SFP or rebooting the storage processor on an appliance, the FC connectivity does not reconnect after the cable has been reconnected or the storage processor has completely reboot itself.

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

  • Reseat the SFP.
  • Hard code the link speed to 4 Gigs.
  • Change the word fill from "ARBFF" to "IDLE".
    UCSM > FI > FC Interface > Interface Properties > select "IDLE" fill word.
  • Bounce the ports.

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

Upgrade Cisco Nexus 5000 to a newer release than 5.1(3).

REWRITE SYMPTOM

CSCuo74243

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

This issue has no known 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(1):

  • 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 (supported as of Release 3.0(2c))

FC End Host Mode (supported as of Release 3.0(2c))

Private VLANs

Port Security

KVM Virtualization is not tested (although not explicitly disabled)

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

  • 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(3a) and earlier releases:

usNIC support for IP-routable transport

Stateless Offload for Overlay Networks (NVGRE / VXLAN)

PVLAN Enhancements

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 10 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 delivers 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.