Created release notes for Cisco UCS Manager, Release 3.0(1c).
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).
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
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.
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.
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)
vIFs and vNICs no longer fail to come up after servers are reset.
Cisco UCS Manager mode- BIOS no longer fails to find local boot device.
dcosAG process no longer crashes after upgrading to Cisco UCS Manager, Release 2.2(1b).
Server no longer reboots after an infra-only upgrade followed by a service profile change.
FI no longer reboots during snmpwalk when ldap config is enabled.
Associated LSP/GSP events are no longer sent every 3 minutes to Cisco UCS Central inventory.
Cisco UCS Manager scheduled backups from Cisco UCS Central no longer fail.
Excessive dropped pings eliminated during vmotion on ESXi VMFEX DVS.
Blades no longer prevent non-disruptive changes if firmware status gets stuck in “activating” state.
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).
Changes to boot order between SAN & other devices via CLI or XML API no longer fails.
FI mgmt0 no longer drops packets coming from blades behind that FI.
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.
Service profile association no longer failing at BIOS post completion stage.
Logical switch GUID no longer gets changed after a backup and restore config event.
CLI now provides the ability to report packet count per QoS class.
LEDs no longer light up for wrong ports when configured with both FC and Ethernet ports.
The following caveats are open in Release 3.0(1c):
Table 4 Open Caveats in Release 3.0(1c)
A hard-pinned vNIC does not go down after VLAN is removed from pin group.
Do not use pin group policy for a vNIC.
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.
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.
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.
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.
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.
In rare cases, when port-channel member interface is flapped, some traffic may get dropped.
This issue has no workaround.
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.
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.
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 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:
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.
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.
For more information, you can access related documents from the following links:
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.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks . Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.