Cisco UCS Director Release Notes, Release 5.2
Introduction 2
System Requirements 3
Installation and Upgrade Notes 4
Supported Upgrade Paths for Cisco UCS Director 4
Supported Upgrade Paths for Baremetal Agent 4
New and Changed Features 6
Open and Resolved Bugs 11
Open Bugs for This Release 11
Resolved Bugs in This Release 11
Workflow Task Changes in This Release 12
Deprecated APIs in This Release 14
Related Documentation 15
Obtaining Documentation and Submitting a Service Request 16
Revised: December 22, 2014,
Introduction
Cisco UCS Director delivers unified, highly secure management for supported compute, network, storage, and virtualization platforms
and for the industry's leading converged infrastructure solutions, which are based on the Cisco Unified Computing System (Cisco
UCS) and Cisco Nexus platforms. Cisco UCS Director extends the unification of computing and network layers through Cisco UCS
to provide data center administrators with comprehensive visibility and management capabilities for compute, network, storage, and
virtualization. For more information, see Cisco UCS Director on Cisco.com.
2
Revised: December 22, 2014,
System Requirements
The system requirements for this release are available in the Cisco UCS Director installation and upgrade guides for the following:
• VMware vSphere
• Microsoft Hyper-V
Supported Browser Versions
Cisco UCS Director supports the following browsers and requires the Adobe Flash Player 11 plug-in for those browsers:
• Internet Explorer 8 or higher
• Google Chrome 4.1 or higher
• Firefox 3.5 or higher
• Safari 4.0 or higher (for Apple Mac or Microsoft Windows)
All browsers must have Adobe Flash Player plug-in version 11 or higher.
Revised: December 22, 2014,
Installation and Upgrade Notes
Cisco UCS Director uses a standard virtual machine that is delivered in OVF format for VMware, and in VHD format for Microsoft
Hyper-V. It can be hosted on VMware vSphere or vCenter, or on Microsoft Hyper-V Manager. For installation instructions, see the
appropriate Cisco UCS Director installation and upgrade guide.
Note
After you apply the upgrade patch and complete that installation, choose the Start Services option of
ShellAdmin to start/restart the Cisco UCS Director services and complete the patch process. The patch
process is not complete or successful until the services have started, Cisco UCS Director is available, the
login screen is displayed, and the admin user can log in.
All Cisco UCS Director services must be stopped before you perform other ShellAdmin procedures, such
as apply additional patches, take a database backup, or restore a database from a backup.
Supported Upgrade Paths for Cisco UCS Director
The upgrade path to Cisco UCS Director, Release 5.2 depends upon your current version of Cisco UCS Director. The following are
the supported upgrade paths for Cisco UCS Director, Release 5.2.
For information about how to upgrade to previous releases of Cisco UCS Director, see the installation and upgrade guide for that
release. For example, if you need to upgrade from Release 3.x, you must first upgrade to Release 4.0 and then follow that upgrade
path.
Current Release
Direct Upgrade Supported
Upgrade Path
Release 4.0.x.x
No
4.0 > 4.1 > 5.1 > 5.2
Release 4.1.x.x
No
4.1 > 5.1 > 5.2
Release 5.0.x.x
Yes
5.0 > 5.2
Release 5.1.x.x
Yes
5.1 > 5.2
Supported Upgrade Paths for Baremetal Agent
The upgrade path to Cisco UCS Director Baremetal Agent (Baremetal Agent), Release 5.2 depends upon your current version of
Baremetal Agent.
For information about how to upgrade to previous releases of Baremetal Agent, see the installation and upgrade guide for that release.
For example, if you need to upgrade from Release 3.x, you must first upgrade to Release 4.0 and then follow that upgrade path.
Current Release
Direct Upgrade Supported
Upgrade Path
Release 4.0.x.x
No
4.0 > 5.0 > 5.2
4
Current Release
Direct Upgrade Supported
Upgrade Path
Release 4.1.x.x
No
4.1 > 5.0 > 5.2
Release 5.0.x.x
Yes
5.0 > 5.2
Note
Baremetal Agent does not have a Release 5.1. If you are using Cisco UCS Director, Release 5.1, your
system includes Baremetal Agent, Release 5.0.
5
Revised: December 22, 2014,
New and Changed Features
This section provides an overview of the significant new and changed features in this release. This section does not provide an
exhaustive list of all enhancements included in this release.
Note
For information about the physical and virtual devices and software supported by Cisco UCS Director in
this release, see the Compatibility Matrix for this release.
Guided Setup Wizards
Cisco UCS Director includes a set of wizards that guide you through configuring certain features.
New Wizards
• Baremetal Agent Setup—This wizard enables you to add and configure a Baremetal Agent account, including its PXE
interface and DHCP.
• Vblock Pod Configuration—This wizard enables you to discover and assign Vblock accounts to pods.
• VSPEX Pod Configuration—This wizard enables you to discover and assign VSPEX accounts to pods.
Changed Wizards
• Device Discovery—This wizard now enables you to discover additional supported devices and assign them to a pod.
• vDC Creation—This wizard now helps you to configure the policies required to successfully provision a VM in a Hyper-V
cloud as well as a vCenter cloud.
Creation of Wizard from Workflow
You can now create a wizard from a valid workflow.
Support for Cisco UCS Mini
You can now inventory, manage, and configure Cisco UCS Mini through a Cisco UCS Manager account. This feature is supported
only with Cisco UCS Manager releases that support Cisco UCS Mini, such as Cisco UCS Manager, Release 3.0.
Documented in Cisco UCS Director Management Guide for Cisco UCS Manager, Release 5.2.
Support for Cisco UCS C-Series and E-Series Rack Servers
You can now inventory, manage, and configure Cisco UCS C-Series and E-Series Rack Servers through rack accounts. This support
includes the following servers:
• Cisco UCS C-Series M3 and M4 servers
• Cisco UCS E-Series M1 and M2 servers
6
The supported features include the following:
• Hardware health status (monitoring)
• Server hardware inventory
• Server management with vKVM Launcher
• Firmware inventory and management
• Call home (e-mail alerts for critical faults)
• Platform grouping and tagging
• Group discovery
Note
We recommend that you add new C-Series and E-Series servers through the Rack accounts. Support for
rack server management through Cisco Rack Server (CIMC) accounts will be deprecated in a future
release.
Support for Cisco Nexus 1000V for Microsoft Hyper-V
With support for Cisco Nexus 1000V for Microsoft Hyper-V, you can configure and edit the following new objects based on the
Microsoft System Center Virtual Machine Manager (SCVMM) SP1 network object model and publish those objects to SCVMM:
• Logical networks
• Network segment pools
• IP pool templates
• Network segments
• Network uplinks
• Inherit port profile
Documented in Cisco UCS Director Network Devices Management Guide, Release 5.2.
Enhancements to Microsoft Hyper-V Support
The enhancements to Microsoft Hyper-V support and the integration with SCVMM include the following:
• Support for the following network models: VLAN-based, private VLAN-based, and network virtualization based
• Network topology views for the following: VM network, host network, and cluster network
• Inventory of host clusters and host groups
• Triggers to execute workflows on Hyper-V hosts based on specified conditions
• Enhancements to the following policies: deployment policy, storage policy, and network policy
• Performance data for hosts, clusters, VMs, and host groups
• Cloudsense reports for SCVMM
Documented in Cisco UCS Director Integration Guide for Microsoft System Center Virtual Machine Manager, Release 5.2.
7
Enhancements to Cisco Application Centric Infrastructure Support
The enhancements to support for Cisco Application Centric Infrastructure include the following:
• Ability to create L3 out domains
• APIC firewall policy
• Support for NetScaler 1000v (DVS support only)
• Support for VPC
• Support for AVS
• AVS support added to VPX
• AVS support added to ASAv
• ASAv VM deployment policy
• Support for tenant onboarding on a cluster or multiple hosts
Documented in Cisco UCS Director APIC Management Guide, Release 5.2.
Enhancements to Resource Groups
The enhancements to resource groups include support for the following:
• EMC VNX
• Clusters
• Multiple hosts
Documented in Cisco UCS Director APIC Management Guide, Release 5.2.
Enhancements to Cisco UCS Director Baremetal Agent
The enhancements to Cisco UCS Director Baremetal Agent include the following:
• Baremetal Agent guided setup wizard to add and configure a Baremetal Agent account
• Ability to configure one or two NICs during OVF deployment
• View of all PXE service requests for a Baremetal Agent account
• NFS mount point support for OS image storage
• View of all OS images provisions for a Baremetal Agent account
• Logs for Baremetal Agent account, including the account log and the DHCP log, are now available through Cisco UCS Director
Documented in Cisco UCS Director Baremetal Agent Installation and Configuration Guide, Release 5.2.
Enhancements to Cisco Unified Fabric Automation Support
Support is now available for to Cisco Unified Fabric Automation, Release 2.0 (formerly Cisco Dynamic Fabric Automation).
Documented in Cisco UCS Director Unified Fabric Automation Management Guide, Release 5.2.
8
Enhancements to EMC RecoverPoint Support
The enhancements to EMC RecoverPoint support include the following:
• Support for Asynchronous Replication Mode
• Support for Group Sets
• New tasks and actions to configure and update group policy, copy policy, journal policy, and link policy
• Updates to existing tasks and actions to support the following:
◦Create Consistency Group task and action support group policy configuration, creation of a consistency group production
copy, and copy journal policy for that production copy during the creation of a consistency group
◦Create Consistency Group Copy task and action support copy policy configuration during the creation of a consistency
group copy
◦Add Link task and action support link policy configuration when you add a link between two consistency groups.
Enhancements to the Cisco UCS Director REST API
The enhancements to the REST API include added or improved APIs for the following:
• Fetching values for a given workflow input type
• User accounts
• Groups
• Reports
• Service containers
• APIC containers
• Application containers
• Workflow operations
• Script operations
Documented in Cisco UCS Director REST Developer Guide, Release 5.2.
Enhancements to Managed Services Provider Support
Support for Managed Services Providers (MSP) has been enhanced to include the following:
• Branding for the MSP
• Resource limits at the MSP organization and container level
• Ability to create a Group Share policy for MSPs
Documented in Cisco UCS Director Administration Guide, Release 5.2.
Other Enhancements to Cisco UCS Director
Other enhancements to Cisco UCS Director include improvements to the following:
• LDAP integration
9
• Email templates
• Icon support
• Approval request reminders and reminder intervals
• Catalogs
• Deployment assessment for catalog items
• VM ownership
• Charge frequency
Documented in Cisco UCS Director Administration Guide, Release 5.2.
10
Revised: December 22, 2014,
Open and Resolved Bugs
The open and resolved bugs for this release are accessible through the Cisco Bug Search Tool. This web-based tool provides you
with access to the Cisco bug tracking system, which maintains information about bugs and vulnerabilities in this product and other
Cisco hardware and software products.
Note
You must have a Cisco.com account to log in and access the Cisco Bug Search Tool. If you do not have
one, you can register for an account.
For more information about the Cisco Bug Search Tool, see the Bug Search Tool Help & FAQ.
Open Bugs for This Release
All open bugs for this release are available in the Cisco Bug Search Tool through the open bug search.
The results of that search include workarounds for the open bugs, if any.
Resolved Bugs in This Release
All resolved bugs for this release are available in the Cisco Bug Search Tool through the fixed bug search.
Revised: December 22, 2014,
Workflow Task Changes in This Release
The following describes the workflow task changes in this release and the impact they may have, if any, on your existing workflows.
Workflow Task
Component
Issue/Error Caused by Change Workaround to Resolve Issue
Create Vlan Pool
Networking
Binding modified for User
Input field: Allocation Mode
(Mandatory)
Delete Subnet to EPG
Networking
Delete Subnet to EPG task no Delete the existing task and
longer exists
add the Delete Subnet From
EPG task to the workflow.
Delete NodeProfile To
ExternalBridgedNetwork
Networking
Delete NodeProfile To
Delete the existing task and
ExternalBridgedNetwork task add the Delete Node Profile
no longer exists
To External Bridged Network
task to the workflow
Configure Context Interface
Networking
Binding modified for User
Input field: Interface Name
(Mandatory)
Add an input field with type
of ASAInsideInterfaceIdentity
to the task.
Configure NAT
Networking
Binding modified for User
Input field: Real Source
(Mandatory)
Add an input field with type
of
NATSourceOrDestinationIdentity
to the task.
Configure Context ACL
Networking
Binding modified for User
Input field: Interface Name
(Mandatory)
Add an input field with type
of ASAInsideInterfaceIdentity
to the task.
Configure Sub Interface
Networking
Binding modified for User
Add an input field with type
Input field: Physical Interface of ASAInsideInterfaceIdentity
Name (Mandatory)
to the task.
Configure Context NAT
Networking
Binding modified for the User Add an input field with type
Input field : Protocol
of NATDeviceProtocolIdentity
to the task.
Create Security Context
Networking
Binding modified for the User Add input fields with the
Input field : Inside Interfaces, following types to the task:
Binding modified for the User
Input field: Outside Interfaces
Add an input field with type
of
ApicVlanPoolAllocationMode
to the task.
• ASAInsideInterfaceIdentity
for Inside Interfaces
• ASAInterfaceIdentity for
OutsideInterfaceName
12
Workflow Task
Component
Issue/Error Caused by Change Workaround to Resolve Issue
Create Logical Switch
Hyper-V
After upgrade to Release 5.2,
a new mandatory field called
Extension is added to the task,
and Create Logical Switch
bindings are removed for
uplink port profiles. Execution
of this task in workflows
created in previous releases
fails with a binding error.
Edit the task and provide
values for the following user
level inputs mapping/task level
inputs and then execute the
task:
• Provide an input for the
Extension field (HyperV
Virtual Extension
Identify). This field
supports creation of a
Nexus 1000V for
Hyper-V logical switch.
• Provide an input for the
HyperV Cloud field
(HyperV Account
Selector). This field type
has been changed from
Generic text to Account
Selector.
13
Revised: December 22, 2014,
Deprecated APIs in This Release
The following APIs have been deprecated in this release:
• userAPISubmitServiceRequest
• userAPISubmitServiceRequestCustom
• userAPICheckFunds
• HYPERV_VM_PROVISION
14
Revised: December 22, 2014,
Related Documentation
In addition to these release notes, you can find documentation for Cisco UCS Director, Release 5.2 in the following locations on
Cisco.com:
• Cisco UCS Director 5.2 Documentation, Download, and Support page
• Cisco UCS Director Documentation Roadmap
• Cisco UCS Director Product Overview Pages
• Cisco UCS Director on Cisco DevNet
Revised: December 22, 2014,
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.
16
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS,
INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH
THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY,
CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB's public domain version
of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS" WITH ALL FAULTS.
CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT
LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS
HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
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.
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: http://
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)
© 2014
Cisco Systems, Inc. All rights reserved.
Americas Headquarters
Cisco Systems, Inc.
San Jose, CA 95134-1706
USA
Asia Pacific Headquarters
Cisco Systems (USA) Pte. Ltd.
Singapore
Europe Headquarters
Cisco Systems International BV
Amsterdam, The Netherlands
Cisco has more than 200 offices worldwide. Addresses, phone numbers, and fax numbers are listed on the
Cisco Website at www.cisco.com/go/offices.