Release Notes for Cisco UCS Software, Release 2.0
Hardware and Software Interoperability
New Hardware Features in Release 2.0
New Software Features in Release 2.0
Known Limitations and Behaviors
Open Caveats from Prior Releases
Cisco UCS C-Series Rack Mount Server Integration with Cisco UCS Manager
Obtaining Documentation and Submitting a Service Request
First Published: September 19, 2011
Last Updated: January 08, 2016
This document describes system requirements, new features, catalog and bundle images information, resolved caveats, known caveats and workarounds for Cisco UCS Manager Release 2.0(1m), Release 2.0(1q), Release 2.0(1s), Release 2.0(1t), Release 2.0(1w), Release 2.0(1x), 2.0(2m), 2.0(2q), 2.0(2r), 2.0(3a), 2.0(3b), 2.0(3c), 2.0(4a), 2.0(4b), 2.0(4d), 2.0(5a), 2.0(5b), 2.0(5c), 2.0(5d), 2.0(5e), 2.0(5f), 2.0(5g). This document also includes the following:
Use this release notes as a supplement with the other documents listed in documentation roadmap http://www.cisco.com/go/unifiedcomputing/b-series-doc.
Make sure to review other available documentation on Cisco.com to obtain current information on Cisco UCS Manager.
Separate release notes for the VIC card drivers (which may be released out of sync with other software) are available at http://www.cisco.com/en/US/products/ps10281/prod_release_notes_list.html
This document includes the following sections:
Table 1 shows the revision history for this document.
Created release notes for Release 2.0(1m). 1 |
|||
Added ‘The following caveats are common across Release 2.0’ section under Open Caveats. |
|||
Removed CSCua02797 from Resolved Caveats; applies only to VIC Driver release notes. |
|||
Updated release notes for Catalog Release 2.0.5l.T and removed a PID for ucs-catalog.2.0.1m.T.bin. |
|||
Removed a PID from catalog Release 2.0.5l.T that is already listed for a previous release. |
|||
1.This release was removed from the download area due to CSCts96949 and CSCts86890. See the software deferral notice. |
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-mount 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.
To install Cisco UCS Manager your computer must meet or exceed the following system requirements:
– Microsoft Internet Explorer 6.0 or higher
– Mozilla Firefox 3.0 or higher
Adobe Flash Player 10 or higher is required for some features
For a complete list of hardware and software interdependencies, see the Hardware and Software Interoperability for UCSM Managed Servers for a specific Cisco UCS Manager release, here :
http://www.cisco.com/c/en/us/support/servers-unified-computing/unified-computing-system/products-technical-reference-list.html
Note VMware ESX and ESXi 4.0 are not compatible with Intel 56xx processors. 55xx processors are not affected by this limitation. See the interoperability matrix for this release for OS and other support questions.
To update the Cisco UCS software and firmware, see the appropriate Upgrading Cisco UCS document for your installation. All A, B, and C bundles must be at the exact same version and patch level.
Use the scope firmware and show package filename expand CLI commands to view the contents of a given release package. For information about the contents of the Cisco UCS bundle images for each Cisco UCS 2.0 release, see Release Bundle Contents for Cisco UCS Software, Release 2.0.
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.
C220 M32 |
||
C240 M3 1 |
||
UCS NIC M51KR-B |
||
Cisco Nexus 22484 |
||
SFP-10G-SR, SFP-10G-LR |
||
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.The C-series integration using the Cisco Nexus 2248 Fabric Extender is no longer supported as of Release 2.0(2). See the UCS C-Series hardware documentation for details. |
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.0 releases work with any 2.0 catalog file, but not the 1.0 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.
This patch release provides support for UCS B200 M3 blade server configurations with a single CPU, in addition to the previously supported dual CPU configurations.
Note The changes are documented in the Intel public Specification Updates for August 2013.
This section contains resolved caveats for the following releases:
PAA for a SPAN session now works with 8Gb transceivers and Fibre Channel expansion modules on the fabric interconnect. |
|
Using the Cisco UCS Manager GUI, you are now able to disassociate a service profile that is currently bound to a template. |
|
When you assign an organization to a locale in the Cisco UCS Manager GUI, the operation sometimes fails due to an internal error. This error is now corrected. |
|
The PCI Device address of a vNIC will not change after an upgrade of Cisco UCS Manager from Release 1.x to Release 2.0(1q). |
|
When the DHCP server is using an option 67 (RFC 2132) to report the bootfile name to the gPXE client, gPXE will receive the boot parameters and the boot will function normally. |
|
When the BIOS is upgraded on a B230-M1 blade from Cisco UCS Release 1.x to Release 2.0, the PCI address is preserved. Note In the New Hardware Features in Release 2.0, see the BIOS section for issues when upgrading the B230-M1 BIOS from Release 2.0(1m) to Release 2.0(1q) or later. |
|
A B230-M1 blade discovered while running a Cisco UCS 1.4 BIOS Release image and now running a Cisco UCS 2.0 Release BIOS image will associate and disassociate normally. |
|
The show mac address-table aging-time vlan x command or running an SNMP agent querying this SNMP object will no longer cause an unexpected reboot. |
|
If the hostname is configured for the vCenter in Cisco UCS Manager and the DNS server does not reply with the hostname to IP mapping within 30 seconds, the VMS process will no longer crash unexpectedly. |
|
A Blade with a service profile with a 22 character or longer name will boot as expected from the local disk after upgrading the BIOS from a 1.x release to the BIOS in the 2.0(1q) release. |
This section contains open caveats for the following releases:
Under some conditions, the IOM upgrade fails and gets into a continuous reboot after the IOM is activated by the fabric interconnect. Rebooting the fabric interconnect on a failed IOM update does not fix this issue. |
Resolved in Cisco UCS, Release 2.0(4b). Upgrade to Release 2.0(4b). Contact Cisco technical support if you have any issues upgrading to this release. |
|
FC storage traffic through an IOM stops when the IOM is reset or reinserted, or the cable between the IOM and FI is removed or reinserted. |
To avoid being impacted when upgrading from a release prior to 2.1(3a) or 2.2(1b), upgrade the server firmware before performing an infrastructure upgrade. This caveat affects FC traffic on the Cisco 1240, Cisco 1280, and Cisco M81KR adapters and is an exception to the normal upgrade procedures found in Cisco UCS Manager upgrade guides. For more details, please refer to CSCuh61202. |
– Remove and re-seat the IO module, making sure module is firmly in contact with the backplane.
Note Do not upgrade IOM firmware until this error is cleared.
– When an image is activated through the GUI, CLI commands are issued.
– When an image is activated through the CLI, CLI commands are issued from another CLI session.
To avoid this issue, do not issue CLI commands during the process of image activation.
Modify any service profiles or service profile templates with iSCSI vNICs to have unique IQNs. Remove any duplicates. If necessary, use the PowerShell script provided in the upgrade notes to find out which iSCSI vNICs reuse the same iSCSI name.
a. Cisco UCS Manager will throw faults on iSCSI vNICs which have the shared IQN name.
b. Enter the show identity iqn | include iqnname command to find which iSCSI vNIC has the IQN registered.
c. Modify the iSCSI vNIC which is using the same IQN name but is not registered, and then edit the IQN name (manual or pooled).
d. Make any change to the SP (ex:- Fw upgrade or modify description and so on.)
e. Re-run the show identity iqn | include Service Profile name command and make sure that the IQNs are registered in Cisco UCS Manager.
The details of the PowerShell script are provided in the troubleshooting and upgrade guide. (CSCty29247)
To avoid this problem, do the following before upgrading from a 1.3.x release to a 1.4.x or a later release:
1. Change the description field of the organizations that have underscores in their names by removing the underscores and any spaces to help keep the organizations in the database.
2. Create a backup using the All Configuration option before upgrading. If a problem occurs after the upgrade, restore the configuration using the backup file. After importing the configuration file, reacknowledge all blades to restore their VIF status.
This section contains open caveats for the following releases:
Loading multiple driver disks during a RHEL 5.x installation fails. |
See the article at http://kbase.redhat.com/faq/docs/DOC-17753 |
|
Hubs that only use USB 1.0 may not properly present an attached USB device to the UCS server. |
Avoid using USB hubs that are exclusively USB 1.0 capable. Virtually all USB hubs sold today are USB 1.0/2.0 capable. |
|
When using mirroring mode, if a UCE error happens, there is a Redundancy SEL event and also a UCE SEL event. No other details are available for the Data Parity error. |
||
The link from the rack-mount server adapter to the fabric interconnect port remains down if the SFP type is FET (Fabric extender transceiver). Currently the FET type is supported only between a fabric extender and a fabric interconnect. If the SFP used for the link between the IOM and the rack-mount server adapter is an FET, the link will remain down. |
Replace the SFP with one of the supported SFPs for rack-mount server adapters. |
|
The PCIe Address for the Cisco UCS M81KR Virtual Interface Card is not seen in the GUI (or CLI). It causes no functional impact. |
The only workaround is to boot some host OS onto the blade and then determine the PCI address and map it to the MAC address (and subsequently to the VNIC). In a 2.6 kernel based Linux for instance, the /sys/class/net/<device> directory has relevant information. |
|
Modification of trusted CoS policy in Service Profile does not get immediately applied to the server. If you modify the trusted CoS policy of an adapter profile in a service profile that is currently attached to a physical server, a server reboot is needed. Since it is unsafe to automatically reboot an associated server, UCSM currently does not. |
Manually reboot the server or disassociate and reassociate the server to get the CoS policy to be applied. |
|
For each Cisco UCS 82598KR-CI 10 Gigabit Ethernet Adapter, 2 interfaces show up in the OS and ethtool reports Link Detected = yes for both of them. This is only seen on Cisco UCS B250 servers. |
Use the MAC that has the value provisioned in the service profile. |
|
When upgrading from releases prior to 1.1.1, OS-specific default adapter policies will not have the current recommended default values. |
After an upgrade from a release prior to 1.1.1, we recommend manually changing the adapter policy parameters to the following values: |
|
Logon access is denied for user accounts where the password field was left blank during user account creation. |
When creating a user account, ensure that a secure password for the account is specified. |
For more information, you can access related documents from the following links:
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.