Release Notes for Cisco UCS Central, Release 1.1
New Software Features in Release 1.1(2a)
Feature Support Matrix for Release 1.1(2a)
New Software Features in Release 1.1(1b)
New Software Features in Release 1.1(1a)
Known Limitations and Behaviors
Obtaining Documentation and Submitting a Service Request
First Published: July 15, 2013
This document describes system requirements, new features, resolved caveats, known caveats, and open caveats with workarounds for Cisco UCS Central software Release 1.1(1a), 1.1(1b), and 1.1(2a). This document also includes information that became available after the technical documentation was published.
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 Central.
Table 1 shows the revision history:
Added known limitation related to issue reported in CSCus21388. |
|||
Added CSCun84897 in open caveats for 1.1(1b); changed 2.2(1b) heading (in Feature Support Matrix) to 2.2(1 x). |
|||
Added information on Bash Update bin. |
Cisco UCS Central, Release 1.1 allows you to take charge of the data center environment by delivering easy to use, integrated solution for managing multiple Cisco UCS Domains from a single management point with high availability. With Cisco UCS Central 1.1, you can efficiently manage server, storage and network policies, and generate network traffic reports for your entire UCS environment in one or more data centers.
To access the browser based Cisco UCS Central GUI, your computer must meet or exceed the following minimum system requirements:
– Internet Explorer 9 and above
Adobe Flash Player 11.7 and above.
For the Chrome browser, remove the bundled flash player and install the flash player from Adobe.
The released OVA or ISO is supported with ESXi4.1U2, ESXi5.0, ESXi5.1GA and ESXi5.5GA.
The released ISO is supported with Microsoft Hyper-V Server 2008 R2 SP1 and Microsoft Hyper-V Server 2012.
Note If you are using Cisco UCS Release 1.1(2a), you must be running Cisco UCS Release 2.1(2a) or higher. Some features of UCS Central 1.1(2a) may only work with later releases of Cisco UCS Manager.
– Perform remote actions on endpoints in registered UCS domains
– Collect tech support on registered UCS domains
– Copy backup files to a remote location 1
The following table provides a list of features in Cisco UCS Central Release 1.1(2a) and Cisco UCS Manager release versions in which these features are supported.
Note New features such as specifying remote a location for backup image files, 3rd party certificates, and IPv6 inband management support are built in Cisco UCS Central to be compatible with upcoming Cisco UCS Manager releases.
Multi-version management support and viewing supported Cisco UCS Manager features |
|||
To deploy a fresh installation of Cisco UCS Central, Release 1.1(1b) or higher, you can use either the OVA file or the ISO image. See the Cisco UCS Central Install and Upgrade Guides for more information.
To upgrade Cisco UCS Central, you must use the ISO image. The following upgrade paths are supported:
Note To upgrade Release 1.0(1a), you must first upgrade to 1.1(1a). After the upgrade has successfully completed, you can then upgrade to Release 1.1(2a).
UCS Central bash update bin (ucs-central-bash-update-3.2-33.el5_11.4.bin) provides a fix for the Security Vulnerabilities CVE-2014-6271 and CVE-2014-7169. This bash update bin is included in release 1.2(1d) ISO.
Note You are not required to upgrade to 1.2(1d) to use the bash update bin. You can use the bash update bin to just fix the security vulnerabilities on any Cisco UCS Central 1.1 releases. Download the bash update bin from here: Download bash update bin.
Do the following using the Cisco UCS Central CLI to download and install the bash bin update
Note If you have installed Cisco UCS Central in HA setup, make sure to install the bash bin update in both nodes.
The following caveats are resolved in Release 1.1(2a):
The following caveats are resolved in Release 1.1(1b):
The following caveats are resolved in Release 1.1(1a):
The following caveats are found in Release 1.1(2a):
The following caveats are found in Release 1.1(1b):
The following caveats are found in Release 1.1(1a):
On Microsoft Hyper-V, If the storage reserved for disk1, disk 2 or shared storage is exactly 40 GB, Cisco UCS Central installation fails even if the minimum storage requirement is set at 40 GB. |
To install Cisco UCS Central in standalone or high availability mode, the minimum storage requirement for disk 1,disk 2 and shared storage is 45 GB. |
|
When the system boots, you may experience errors when issuing CLI commands before the system has booted successfully. |
Wait for the system to complete the boot process before continuing. |
|
The Cisco UCS Central CLI session might fail to communicate with the data management engine (DME) and return the following error: This occurs when the CLI is accessed immediately after a reboot before the DME is ready. |
Wait a few seconds, then run the Cisco UCS Central CLI command again. |
|
The Status column on the Global Service Profiles table may not match the actual status of the service profile as reported by Cisco UCS Manager. |
To view the actual status of a global service profile, right-click the service profile and choose Properties. The Properties dialog box displays the overall status, assigned status, associated status, and any configuration errors. |
|
Dynamic vNIC connection policy configuration for SRIOV is not supported in Cisco UCS Central, Release 1.1(1a). |
Create a dynamic vNIC connection policy for SRIOV in Cisco UCS Manager, and reference the policy in a local service profile. |
|
The Estimate Impact action states that a reboot is not required when changing from one policy to another, and that the new policy does not exist in Cisco UCS Manager. The Estimate Impact action also states that a reboot is not required when a new host firmware pack with a different firmware version is selected on the global service profile properties page. A reboot is part of the firmware activation and is not being reported by Estimate Impact. |
||
Pending user-acks from maintenance policies defined in Cisco UCS domains are not displayed in Cisco UCS Central. |
To see pending user-acks in Cisco UCS Central, use the schedules defined in Cisco UCS Central. Modify the maintenance policy to refer to a schedule owned by Cisco UCS Central. If you are using the local scheduler, use Cisco UCS Manager to acknowledge the pending acks. |
|
An hrDeviceStatus value is not retrieved for all devices while doing an snmpwalk or snmpGet. A value is only retrieved for interfaces and not for hard disks. |
||
When you modify the UCS Central IP address, Cisco UCS Manager may not be receive the update, and might go into lost-visibility status. |
Unregister the Cisco UCS domain and re-register the domain with Cisco UCS Central. |
|
The following is not supported on the Cisco UCS Central GUI:
Note If Cisco UCS Central is running in High-Availability mode, you can change the IP address under Administration > Service Registry > System > General. |
||
In the Cisco UCS Central GUI, the policies under Operation Management > Domain Group > Operational Policies cannot be saved simultaneously. This includes Time Zone, DNS, Remote Access, SNMP, Debug, Call Home, Security, Equipment, and Identifier policies. |
When you configure an operational policy, click Save before viewing or changing a different policy. |
|
Microsoft Hyper-V Server 2008 and 2012 experience time-drift issues. |
1. Disable the Time Synchronization option on the Central VM Guest OS using Hyper-V Manager. 2. Acquire a Redhat version 5.8 compatible Rescue CD and perfom the boot process. For more information, see http://www.redhat.com/advice/tips/rescue_mode.html 3. After booting the RedHat Rescue CD, mount the /boot filesystem to a temporary mount location, for example, /tmp/boot. 4. Open the grub.conf file, locate the kernel line, and add the following:
# Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that
5. Reboot the system, and verify the change works successfully by monitoring for one hour. |
The following known limitations and behaviors are not otherwise documented:
In a cluster set up, when the RDM link goes down on the primary node, DMEs cannot write to the database. This causes a crash on the primary node and failover to the subordinate node. The subordinate node takes over as the primary node. The database is then mounted in read-write mode on the new primary node. Because the RDM link is down, umount fails on the old primary node. When the RDM link comes up, the database is mounted on the old primary (current subordinate) node in read-only mode. |
Restart pmon services on the current subordinate node or restart the node itself. Either of these processes will unmount the read-only partition and enable proper cleanup. |
|
Running VMware vMotion, suspending a VM, or restoring a suspended VM on a Cisco UCS Central VM that is currently the primary node in a cluster results in process crashes on the node. |
Before triggering a vMotion or suspend operation on the primary Cisco UCS Central VM, use the local-mgmt cluster lead b command in the Cisco UCS Central CLI to do an administrative failover, which changes the primary node to the secondary node. |
|
The Estimate Impact option does not display that a reboot is required under some situations. For example:
|
|
|
A critical disk read speed fault is shown in an UCS Central deployed on a Hyper-V host. |
None. In testing, it was found that the disk read speed measured on Hyper-V guests showed a lower speed in comparison to guests running on ESX on the same datastore. Typically, this didn't result in a functional impact. |
|
When performing maintenance operations such as admin failover or pmon restart on a UCS Central VM running on VMware ESX, the file system goes into read-only state. For more information, see http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&externalId=51306. |
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.