Cisco UCS Director Release Notes, Release 5.3
First Published: 2015-04-17
Last Modified: 2017-02-24
Cisco UCS Director
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.
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)
All browsers must have Adobe Flash Player plug-in version 11 or higher.
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 guide.
Cisco UCS Director Release Notes, Release 5.3
1
Cisco UCS Director
Workflow Prerequisites for Upgrades from Releases Prior to 5.3(0.0)
Note
Cisco UCS Director OVF and VHD zip files are created using zip 3.x in CentOS 6.x. For Linux systems,
you can extract the zip files with unzip 6.x or higher or with the latest version of the 7-Zip archiving tool.
For Windows systems, you can extract the zip files with the native Extract All in Windows Explorer for
Windows 10 and Windows Server 2012 or with the latest versions of archiving tools such as 7-Zip or
WinRAR.
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.
Workflow Prerequisites for Upgrades from Releases Prior to 5.3(0.0)
The structure of the APIC Usecases workflow folder and the names of the workflows in those folders were
changed in Cisco UCS Director, Release 5.3. Before you upgrade to Release 5.3(x.x) from a release prior to
5.3(0.0), you must perform the following steps.
Note
You must create a new Application Profile, or edit the existing one (in order to add the L4-L7 policy
or external/infra tier info), before executing the Create APIC Container workflow.
Note
You must delete the existing APIC Usecases folders and all system workflows in those folders before
you upgrade to Cisco UCS Director, Release 5.3, including the following. After you upgrade, they
will be replaced with the new folder structure and new system workflows.
• APIC Usecases folder and the following subfolders:
◦VNX Storage Usecases folder
◦L4-L7 Usecases folder
◦NetApp Storage Usecases folder
• APIC Container Usecases folder in the following location: Default > Containers > APIC
Container Usecases
Note
If you are enabling the MSP mode, you must delete the Tenant Onboarding with MSP-VNX workflow
before you stop services.
Cisco UCS Director Release Notes, Release 5.3
2
Cisco UCS Director
Supported Upgrade Paths for Cisco UCS Director
Note
Before you upgrade, you must also delete the Common_Tenant_Identity custom task from the
Custom Workflow Tasks tab under Orchestration.
Supported Upgrade Paths for Cisco UCS Director
The upgrade path to Cisco UCS Director, Release 5.3 depends upon your current version of Cisco UCS
Director. The following are the supported upgrade paths for Cisco UCS Director, Release 5.3.
Note
From Release 5.3(1.0) and onwards, the upgrade checks for valid target paths and will upgrade only if the
upgrade path from the appliance version and target version is supported.
Upgrade Paths for Release 5.3(x.x)
The upgrade paths for Cisco UCS Director, Release 5.3(x.x) are as follows:
• From Release 5.3(0.0) to Release 5.3(x.x)
• From Release 5.3(0.1), you must first upgrade to Cisco UCS Director, Release 5.3(1.x) and then upgrade
to Cisco UCS Director, Release 5.3(2.x)
• From Release 5.3(0.2) to Release 5.3(x.x)
• From Release 5.3(1.0) to Release 5.3(x.x)
• From Release 5.3(1.1) to Release 5.3(x.x)
• From Release 5.3(1.2) to Release 5.3(x.x)
• From Release 5.3(2.0) to Release 5.3(2.1)
• From Release 5.3(2.0) to Release 5.3(2.2)
• From Release 5.3(2.1) to Release 5.3(2.2)
• From Release 5.3(2.0) to Release 5.3(2.3)
• From Release 5.3(2.1) to Release 5.3(2.3)
• From Release 5.3(2.2) to Release 5.3(2.3)
• From Release 5.3(2.0) to Release 5.3(2.4)
• From Release 5.3(2.1) to Release 5.3(2.4)
• From Release 5.3(2.2) to Release 5.3(2.4)
• From Release 5.3(2.3) to Release 5.3(2.4)
• From Release 5.3(2.4) to Release 5.3(2.5)
Cisco UCS Director Release Notes, Release 5.3
3
Cisco UCS Director
Supported Upgrade Paths for Bare Metal Agent
Important
Upgrading from Release 5.3(2.1) to Release 5.4 is not supported. You can only upgrade from Release
5.3(2.1) to Release 5.4(0.1) or later releases (when they are made available).
You cannot upgrade from Release 5.3(2.2) or 5.3(2.3) to Release 5.4, 5.4(0.1) or 5.4(0.2) releases. You
can only upgrade from Release 5.3(2.2) or 5.3(2.3) to Release 5.4(0.3) or later releases (when they are
made available).
You cannot migrate from Release 5.3(2.4) to Release 5.4, 5.4(0.1), 5.4(0.2), 5.4(0.3), or 5.4(0.4) releases.
You can only migrate from Release 5.3(2.4) to Release 5.4(0.5) or later releases (when they are made
available).
You can only upgrade from Release 5.3(2.4) to Release 5.3(2.5) or later releases (when they are made
available).
Upgrade Paths for Release 5.2(x.x)
The upgrade paths for Cisco UCS Director, Release 5.2(x.x) are as follows:
• From Release 5.2(0.0) to Release 5.3(x.x)
• From Release 5.2(0.1) to Release 5.3(x.x)
• From Release 5.2(0.2) to Release 5.3(x.x).
• From Release 5.2(0.2A) to Release 5.3(x.x)
• From Release 5.2(0.3) to Release 5.3(1.2) and later
Note
Due to database changes, you cannot upgrade from Release 5.2(0.3) to a release prior to Release 5.3(1.2).
Upgrade Path for Release 5.1(x.x)
You can upgrade directly from Cisco UCS Director, Release 5.1(x.x) to Cisco UCS Director, Release 5.3(x.x).
Upgrade Paths for Release 5.0(x.x) and Earlier Releases
To upgrade from Release 5.0(x.x) or an earlier release, you must first upgrade to Cisco UCS Director, Release
5.1(x.x) and then upgrade to Cisco UCS Director, Release 5.3(x.x).
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.
Supported Upgrade Paths for Bare Metal Agent
The upgrade path to Cisco UCS Director Bare Metal Agent (Bare Metal Agent), Release 5.3 depends upon
your current version of Bare Metal Agent.
Cisco UCS Director Release Notes, Release 5.3
4
Cisco UCS Director
PowerShell Agent Upgrade for Release 5.3(2)
Note
Bare Metal Agent, Release 5.3 is an upgrade patch to Bare Metal Agent, Release 5.2. It is not a complete
OVF.
Upgrade Paths for Release 5.2
You can upgrade directly from Bare Metal Agent, Release 5.2 to Bare Metal Agent, Release 5.3.
Upgrade Paths for Release 5.0 and Earlier Releases
To upgrade from Release 5.0 or an earlier release, you must first upgrade to Bare Metal Agent, Release 5.2.x.x
and then upgrade to Cisco UCS Director, Release 5.3.x.x.
For information about how to upgrade from previous releases of Bare Metal Agent, see the installation and
upgrade guide for that release. For example, if you need to upgrade from Release 4.x, you must first upgrade
to Release 5.0 and then follow that upgrade path.
Note
Bare Metal Agent does not have a Release 5.1. If you are using Cisco UCS Director, Release 5.1, your
system includes Bare Metal Agent, Release 5.0.
PowerShell Agent Upgrade for Release 5.3(2)
After you upgrade to Cisco UCS Director, Release 5.3(2), you must reinstall your PowerShell Agent. You
can download the latest version of the PowerShell Agent from the system that is upgraded to Release 5.3(2).
To upgrade your PowerShell Agent:
1 Uninstall the existing version of PowerShell Agent.
2 Download PowerShell Agent from Cisco UCS Director, Release 5.3(2).
3 Install the downloaded PowerShell Agent, Release 5.3(2).
For more information about how to perform these steps, see the latest version of the Cisco UCS Director
PowerShell Agent Installation and Configuration Guide.
Note
If you do not reinstall your PowerShell Agent, any existing Execute PowerShell Task will fail after you
upgrade to Release 5.3(2).
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.
Cisco UCS Director Release Notes, Release 5.3
5
Cisco UCS Director
New and Changed Features in Release 5.3(2.5)
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.
New and Changed Features in Release 5.3(2.5)
This release includes defect fixes only, and no new features. For information on the defects fixed in this
release, see the fixed bug search for Release 5.3(2.5).
New and Changed Features in Release 5.3(2.4)
This release includes defect fixes only, and no new features. For information on the defects fixed in this
release, see Resolved Bugs in This Release, on page 22.
New and Changed Features in Release 5.3(2.3)
This release includes defect fixes only, and no new features. For information on the defects fixed in this
release, see Resolved Bugs in Release 5.3(2.3), on page 25.
New and Changed Features in Release 5.3(2.2)
SSL Offloading Support for Application Containers with a Load Balancer
The L4-L7 Policy for a load balancer now supports SSL offloading as well as basic load balancing through
HTTP. SSL offloading moves the processing of SSL encryption and decryption from the main Web server to
a separate device designed for that task. This features increases the performance of the Web server and improves
the efficiency of SSL certificate handling. During deployment of an application container, you must provide
an SSL certificate for the SSL offloading.
Documented in Cisco UCS Director Application Container Guide, Release 5.3.
Stateful ASA Failover Support for an Application Container with an ASA Firewall
The configuration of a Cisco ASA firewall in high availability mode now supports stateful failover for the
Cisco ASA. Stateful failover ensures that the active unit continually passes per-connection state information
to the standby unit. If a failover occurs, this confguration ensures that the same connection information is
available at the new active unit.
Documented in Cisco UCS Director Application Container Guide, Release 5.3.
Updated Cisco Network and Fabric Support
Cisco UCS Director, Release 5.3(2.2) includes support for the following:
• MDS 9706
• Nexus 5596 with the following NX-OS software versions:
◦5.2(1)N1(8b)
Cisco UCS Director Release Notes, Release 5.3
6
Cisco UCS Director
New and Changed Features in Release 5.3(2.1)
◦5.2(1)N1(9)
Updated Cisco Application Centric Infrastructure and Related Software Support
Cisco UCS Director, Release 5.3(2.2) includes support for the following:
• Cisco Application Centric Infrastructure Controllers, Release 1.1(4*)
• Cisco ASAv 9.3(1) with device package 1.2(3.15)
• Citrix NetScaler VPX 10.1 with device package: Major Version 1.0, Minor Version: 10.1-129.62
New and Changed Features in Release 5.3(2.1)
Support for VMware vSphere
Cisco UCS Director Release 5.3(2.1) includes support for VMware vSphere vCenter Server version 5.5 Update
3.
Support for Microsoft Hyper-V Version
Cisco UCS Director Release 5.3(2.1) includes support for Microsoft System Center Virtual Machine Manager
(SCVMM) version 3.2.8 rollup 80.
Support for Cisco UCS Manager
Cisco UCS Director Release 5.3(2.1) includes support for Cisco UCS Manager Release 2.2(4c).
Workflow Changes
There are no workflow changes or differences between Release 5.3(2.0) and Release 5.3(2.1)
New and Changed Features in Release 5.3(2.0)
Updated Packages and Libraries for CentOS
All packages and libraries used by Cisco UCS Director have been updated to the latest available versions for
the release of CentOS running on Cisco UCS Director.
Tags and Cost Model for Infrastructure VMs
You can apply a tag to an infrastructure VM, such as a firewall VM or a load balancer VM. You can use this
tag to create a tag-based cost model for infrastructure VMs.
Documented in the Cisco UCS Director Administration Guide, Release 5.3.
Certificate Option in the Shell Admin Interface
The shell admin interface now includes a new option that you can use to generate and import certificates.
Documented in the Cisco UCS Director Shell Admin Guide, Release 5.3.
Cisco UCS Director Release Notes, Release 5.3
7
Cisco UCS Director
New and Changed Features in Release 5.3(2.0)
VMware Site Recovery Manager Integration
With the introduction of Site Recovery Manager (SRM) integration, Cisco UCS Director now provides you
with an inventory view for resource mappings, protection groups and recovery plans. This feature also provides
the ability to create protection groups, protect virtual machines, and unprotect virtual machines using
orchestration workflow tasks.
Documented in the Cisco UCS Director VMware vSphere Management Guide, Release 5.3.
Enhancements to Orchestration Tasks
The following enhancements were made to orchestration tasks:
• Management of versions for a compound task to clarify the behavior of different versions of a workflow
that is used as a compound task in another workflow.
• Suppression of task output by default for a compound task. When you create a compound task, you can
choose to expose the outputs of intermediate tasks as outputs of the compound task. By default, only
the workflow outputs are exposed as outputs of the compound task.
Documented in the Cisco UCS Director Orchestration Guide, Release 5.3.
Changes to REST APIs
The following changes were made to the REST APIs:
• Updated the userAPIGetTabularReports API as userAPIGetTabularReport.
• Updated the return type of the userAPIGetMyApprovalList API as APIApprovalList.
• Ensured that the userAPIgetBMAOSList API cannot be accessed by end users.
• Updated the parameters of the userAPICreateAPICContainer API
• Updated the parameter description of the userAPISubmitWorkflowServiceRequest API.
• Introduced the following new APIs:
◦userAPIAddDiskToBM
◦userAPIGetResourceUsageSummaryReport
◦userAPIGetVMResourceUsageSummaryReport
◦userAPIGetServiceRequestOutputDetails
◦userAPIGetWorkflowOutputDefinition
Documented in the Cisco UCS Director REST API Developer Guide, Release 5.3.
Enhanced APIC Management Support
The following changes were introduced to APIC management in this release:
• Provision to enable disaster recovery support for resource groups, tenant profiles, and tenant onboarding.
• Tenant and container resource limit reports display availability of both virtual and physical resources.
• Provision to control addition of service classes to a service offering.
Cisco UCS Director Release Notes, Release 5.3
8
Cisco UCS Director
New and Changed Features in Release 5.3(1.2)
• Changes to IP pool allocations to enable you to define the IP subnet pool policy or subnet pool policy
per tenant. All infrastructure related end points of the tenant, such as NFS, application container tiers,
and bridge domain subnets, will be assigned IP addresses from the parent tenant's IP subnet pool.
• Provided a use case of the Tenant Onboarding with Private Network(s) workflow.
Documented in Cisco UCS Director APIC Management Guide, Release 5.3.
Enhanced Application Container Support
The following changes were introduced to application container support in this release:
• In an APIC container, provision to create both a firewall and a load balancer in a series between two
networks in a process called L4-L7 service chaining. You can create a service chain in an existing
application container or through an application profile.
• Support for storage affinity rules during that addition of VM to an application container.
• Support for disaster recovery and non-disaster recovery APIC application containers for disaster recovery
tenants.
• Tenant selection based on external network requirements. If the application container template includes
layer 2 configuration, the tenant list includes only those tenants for which layer 2 is configured.
• Provision of resource limits for an application container.
• Provision of one or more application containers for a private network that is created during tenant
onboarding. You can now create multiple application containers for a private network.
• Support for adding a secondary LUN or disk to an existing baremetal server that is provisioned in an
APIC container.
Documented in Cisco UCS Director Application Containers Management Guide, Release 5.3.
New and Changed Features in Release 5.3(1.2)
Changes to Adding a NetApp Account
Prior to adding NetApp accounts in Cisco UCS Director, you must enable SSLv3 on the NetApp device. You
cannot add a NetApp account if SSLv3 is disabled on the NetApp device.
New and Changed Features in Release 5.3(1.0)
Support for Single Arm and Two Arm Load Balancer Service
Cisco UCS Director Release 5.3(1.0) now includes a provision to configure the load balancer service between
consumer and provider in the one-arm mode or the two-arm mode. In addition, you can also configure both,
firewall and load balancer services, between the consumer and provider in the one-arm mode.
For more information, see the Cisco UCS Director APIC Management Guide, Release 5.3.
Support for VMware vSphere 6.0
Cisco UCS Director Release 5.3(1.0) provides backward compatibility of existing Cisco UCS Director features
supported for VMware vSphere 6.0. This release does not support the new features of VMware vSphere 6.0.
Cisco UCS Director Release Notes, Release 5.3
9
Cisco UCS Director
New and Changed Features in Release 5.3
This release does not support the following existing features with VMware vSphere 6.0:
• VM-FEX adapter
• Virtual Security Gateway for VMware vSphere
• VMware Site Recovery Manager 6.0
• Virtual Storage Console for VMware vSphere
For more information on the supported features, see the Cisco UCS Director VMware vSphere Management
Guide, Release 5.3.
Support for VMAX3
Cisco UCS Director Release 5.3(1.0) includes support for VMAX3. This support has introduced some changes
in the product which are documented in the Cisco UCS Director EMC Symmetrix VMAX Management Guide,
Release 5.3.
New and Changed Features in Release 5.3
Support for C880 M4 Server
Cisco UCS Director Release 5.3 includes support for performing management, monitoring and reporting tasks
for Cisco C880 M4 servers. Previously, this support was available as a patch that had to be installed separately.
With this release, you need not perform any additional installation tasks to manage Cisco C880 M4 servers.
For information on managing a C880 M4 server, see the Cisco UCS Director C880 M4 Server Management
Guide, Release 5.3.
Support for VersaStack and IBM Storwize
Cisco UCS Director Release 5.3 includes support for performing management, monitoring and reporting tasks
for IBM Storwize controllers. In prior releases, this support was available as a patch that had to be installed
separately. With this release, you need not perform any additional installation tasks to manage these controllers.
For information on adding and managing IBM Storwize controllers, see the Cisco UCS Director Management
Guide for IBM Storwize, Release 5.3.
Changes to the Reports APIs
In this release, the customer organization name has been replaced with the group name in the following reports
APIs:
• Group Share Policy Report
• User Groups Report
• Catalog Report
• vFilers Report
• Vservers Report
• User Report
• Datastores Report
Cisco UCS Director Release Notes, Release 5.3
10
Cisco UCS Director
New and Changed Features in Release 5.3
• DV PortGroups Report
• Image Report
• Port Groups Report
• Resource Pools Report
• Service Profile Report
• VLAN Report
• VM Network Details Report
• Raid Group Report
• VNX Block RAID Groups Report
• VNX File Storage Pools Report
• Volumes Report
• VDC Report
• DV Port Groups Report
Enhancements to EMC RecoverPoint Support
The enhancements to EMC RecoverPoint support include the following:
• Ability to choose from additional image access options and modes when enabling image access.
◦New image access options include The Latest Image and Specific Point in Time or Bookmark.
◦New image access mode options include Logged Access, Virtual Access and Virtual Access with
Roll.
• Support for indefinite snapshot consolidation when creating a consistency group and creating a consistency
group copy.
Documented in the Cisco UCS Director EMC RecoverPoint Management Guide, Release 5.3.
Enhancements to VMware vSphere Support
The enhancements to VMware vSphere support include the following:
• Support for Virtual SAN cluster management, which covers the following:
• Virtual SAN clusters
• Virtual SAN clusters from physical servers
• Virtual SAN storage profiles
• Virtual SAN qualification policies
• Support for VMware affinity rules for storage. This feature lets you add and manage datastore cluster
DRS rules.
Documented in Cisco UCS Director VMware vSphere Management Guide, Release 5.3.
Cisco UCS Director Release Notes, Release 5.3
11
Cisco UCS Director
New and Changed Features in Release 5.3
Enhancements to EMC Symmetrix VMAX Support
The enhancements to EMC Symmetrix VMAX support include the following:
• The VMAX Account Type is changed to EMC VMAX from EMC VMAX Solution Enabler.
• VMAX Inventory Task label is modified as EMCVMaxInventoryCollector - (Account_Name) from
VMAX-Inventory - (Account_Name)
• The VMAX inventory frequency is changed to 12 hours.
• The VMAX Symmetrix Array ID is required while adding a VMAX account in Cisco UCS Director.
If any VMAX account was added in earlier release, this account is migrated automatically by considering
only the first Symmetrix array available in Solution Enabler. If other arrays need to be managed in Cisco
UCS Director, then you must add the new VMAX account by specifying required Symmetrix Array ID.
• New report titled Disk Groups is added under System reports. The existing Disks report is modified to
a drilldown report under Disk Group to show only the disk that belong to the disk group.
• Support for Regular Device. In addition to supporting Create Regular Device, Delete Regular Device,
support has been added for the following tasks and actions:
◦Create VMAX Meta Device
◦Add Devices to Meta Head
◦Remove Devices from Meta Head
◦Dissolve Meta
◦Add Device to Storage Group
◦Remove Devices from Storage Group
◦Associate Device as Data store.
Documented in Cisco UCS Director EMC Symmetrix VMAX Management Guide, Release 5.3.
Enhancements to Application Containers
The enhancements to application containers include the following:
• Support for creating VMs in an application container by choosing any existing template or using the
template defined in the application profile.
• Support for adding physical servers and VMs to application containers.
• Support for specifiying VM parameters while creating a VM in an application container. You can now
specify the number of virtual CPUs, memory size, and disk size for VMs that you create in an application
container.
• Support for Layer 4 to Layer 7 services in an APIC container. This includes the following:
• You can add, modify, and delete Layer 4 to Layer 7 services in an APIC container.
• You can create Layer 4 to Layer 7 services as part of an APIC application profile, and they are
provisioned when the container is created.
• You can chain a firewall and a load balancer between two tiers in an APIC container. This is
referred to as service chaining.
Cisco UCS Director Release Notes, Release 5.3
12
Cisco UCS Director
New and Changed Features in Release 5.3
Documented in Cisco UCS Director APIC Management Guide, Release 5.3.
Enhancements to Executing Workflows
The enhancements to executing workflows include enhanced support for resubmitting Service Requests. When
you resubmit a service request, the service restarts where it failed in the last execution, even if that is a child
task or a compound workflow.
Documented in Cisco UCS Director Orchestration Guide, Release 5.3.
Enhancements to Managing Versions of a Compound Task
Managing Versions of a Compound Task
A new section in the Cisco UCS Director Orchestration Guide clarifies the behavior of different versions of
a workflow used as a compound task in another workflow.
Documented in Cisco UCS Director Orchestration Guide, Release 5.3.
Enhancements to the Script Module
The enhancements to the script module include the following:
• Introduction of List of Values (LOV)—You can create lists of values (LOVs) to provide a predefined
set of options for a user input.
• Support for Context Mapping— The Context Mapping module allows you to dynamically add a Context
Workflow Mapping. The Context Workflow Mapping creates an action label for a report, and assigns
a workflow to that action label.
• Support for Tabular Reports— You can create tabular reports to allow users to define their predefined
set of values to be passed as input to custom workflows.
Documented in Cisco UCS Director Orchestration Guide, Release 5.3.
Enhancements to the Cisco UCS Director REST API
The enhancements to the REST API include added or improved APIs for the following:
• User details and user accounts
• Service requests
• Service containers
• APIC containers
• Application containers
• Virtual machines
• Workflow operations
• Load balancer service operations
• Firewall service containers
Documented in Cisco UCS Director REST Developer Guide, Release 5.3.
Cisco UCS Director Release Notes, Release 5.3
13
Cisco UCS Director
New and Changed Features in Release 5.3
Enhancements to Network Devices Support
Support for network devices has been enhanced to include the following:
• Provision to enable VXLAN capability in the network device that is configured with Hyper-V.
• Support for adding a MAC ACL rule or an IP ACL rule to the ACL entry of the Cisco Nexus 1000V
switch.
• Introduced new fields and actions to modify the capability of the following objects to support VXLAN:
• Logical network
• Network segment pool
• Network segment
• VXLAN range
• Tenant VRF
Documented in Cisco UCS Director Network Devices Management Guide, Release 5.3.
Enhancements to APIC Management
Support for APIC management has been enhanced to include provision for the following:
• Viewing the function profile groups of tenants.
• Viewing the device cluster state and logical interface.
• Viewing a list of layer 2 domains in the APIC accounts.
• Viewing a list of service functions and the details of the Layer 4 to Layer 7 service function connectors.
• Viewing the details of the contract association with EPGs.
• Adding and managing Layer 4 to Layer 7 service policies.
Documented in Cisco UCS Director APIC Management Guide, Release 5.3.
Enhancements to Managing NetApp Accounts
Support for managing NetApp accounts has been enhanced to include the following:
• New tabs to enhance management of Vserver in the Cluster mode account.
• Independent management of a Vserver account by a Vserver administrator.
• Support for NetAPP Clustered Data ONTAP version 8.3.
Documented in Cisco UCS Director NetApp Management Guide, Release 5.3.
Enhancements to the Cisco UCS Director Open Automation Tools
Enhancements to the Cisco UCS Director Open Automation Tools includes the following:
• Pagination—Provision to manage data split across pages using the CloupiaReportWithActions and
PaginatedReportHandler classes.
Cisco UCS Director Release Notes, Release 5.3
14
Cisco UCS Director
Workflow Task Changes
• Guidelines for internationalization and localization—These guidelines are for developing new reports
and form UI elements in Open Automation modules with proper internationalization and string
externalization to perform localization.
Documented in Cisco UCS Director Open Automation Developer Guide, Release 5.3.
Other Enhancements to Cisco UCS Director
Other enhancements to Cisco UCS Director include improvements to the following:
• Specifying resource limits for MSP organizations and customer groups.
• Capability to assign VM images to groups
• Cost models can now be mapped to application containers
• Cost models now include parameters for physical servers.
• Support for chargeback modules for physical servers within an application container.
Documented in Cisco UCS Director Administration Guide, Release 5.3.
Workflow Task Changes
Workflow Task Changes in Release 5.3(2.2)
The following describes the workflow task changes in this release and the impact they may have, if any, on
your existing workflows.
Workflow Task
What Has Changed
Workaround to Resolve Issue
Activate SAN Zone Set
After upgrading to this release,
No workaround is required. This
when you run this workflow task, change was made to avoid outage
zonesets are not removed from the of network devices.
active list.
In addition, the Rollback disable
check box is no longer available in
the command-line interface.
Workflow Task Changes in Release 5.3(2.0)
The following describes the workflow task changes in this release and the impact they may have, if any, on
your existing workflows.
Cisco UCS Director Release Notes, Release 5.3
15
Cisco UCS Director
Workflow Task Changes in Release 5.3(1.0)
Workflow Task
What Has Changed
Workaround to Resolve Issue
Configure SAN Zoning
After upgrading to this release, when you run Choose a storage adapter
this workflow task, a binding error message from the list for this
is displayed because the input values have
workflow task.
been modified.
For this workflow task, the user-input type
has been modified from Account Name to
Storage_FC_adapter List.
Generic Configure SAN
Zoning
After upgrading to this release, when you run Choose a storage adapter
this workflow task, a binding error message from the list for this
is displayed because the input values have
workflow task.
been modified.
For this workflow task, the user-input type
has been modified from Account Name to
Storage_FC_adapter List.
Delete Interface From EPG
After upgrading to this release, when you run Update the fields of the
this workflow task, a binding error message workflow task.
is displayed because the input values have
been modified.
For this workflow task, the user-input type
has been modified from
L4L7_EPG_ACL_IDENTITY to
EPG_IDENTITY.
Delete Bridge Group Interface After upgrading to this release, when you run Update the fields of the
From EPG
this workflow task, a binding error message workflow task.
is displayed because the input values have
been modified.
For this workflow task, the user-input type
has been modified from GENERIC_TEXT
to GROUP_INTERFACE_IDENTITY.
Delete ACL From EPG
After upgrading to this release, when you run Update the fields of the
this workflow task, a binding error message workflow task.
is displayed because the input values have
been modified.
Workflow Task Changes in Release 5.3(1.0)
The following describes the workflow task changes in this release and the impact they may have, if any, on
your existing workflows.
Cisco UCS Director Release Notes, Release 5.3
16
Cisco UCS Director
Workflow Task Changes in Release 5.3
Workflow Task
What Has Changed
Workaround to Resolve Issue
Create IBM Storwize File
System
After upgrading to this
release, while executing the
"File System Creation with
Single Pool" workflow task
which is used in release 5.3,
the following error message
is displayed:
Create a new workflow task.
Missing field for 'File system
Type'
Workflow Task Changes in Release 5.3
The following describes the workflow task changes in this release and the impact they may have, if any, on
your existing workflows.
Workflow Task
What Has Changed
Register Host with vCenter
The type of the mappable user Change the input type of the Password field
input Password field has
from Generic Text Input to Password.
been modified from Generic
Text Input to Password.
OVF Import to VMware
Cloud
Workaround to Resolve Issue
Setup PXE Boot with BMA
Selection
Add VNX CIFS Server
Mount iSCSI LUN
Execute PowerShell
Command
Custom User Approval
The Approver ID field has Change the input type of the Approver ID
been modified from User ID field from User ID to Multi User ID.
to Multi User ID.
This implies that you can
specify multiple users IDs,
separated by comma, while
executing the workflow.
Associate VMAX ThinDev
as Datastore
The task name has changed Delete the existing task and add the Associate
and new input fields have
VMAX ThinDev as Datastore task to the
been added for Select Host workflow.
and Select Devices to Mount.
Cisco UCS Director Release Notes, Release 5.3
17
Cisco UCS Director
Workflow Task Changes in Release 5.3
Workflow Task
What Has Changed
Workaround to Resolve Issue
Add Device to VMAX
Storage Group
New input fields have been
added for Device Type and
Regular Device Identity.
No workaround required. Device Type
defaults to Thin Device. Open the task and
change the input if necessary.
Create VMAX Meta Device
New input fields have been
added for Device Type and
Regular Device Identity.
No workaround required. Device Type
defaults to Thin Device. Open the task and
change the input if necessary.
Create VMAX Data Device
The input for the Disk Group Open the task and change the input type for
field was changed from
the Disk Group field.
pop-up to drop-down list.
Enable Image Access
New input fields were added Delete the existing task and replace with the
for the following:
new task.
(RecoverPoint task
• Image to Access
• Image Access Mode
• Point-In-Time
• Seconds
• Bookmark
• Exact
• Image Type
• Max Range
Recover Production
(RecoverPoint task
New input fields were added Delete the existing task and replace with the
for the following:
new task.
• Image to Access
• Point-In-Time
• Seconds
• Bookmark
• Exact
• Image Type
• Max Range
Cisco UCS Director Release Notes, Release 5.3
18
Cisco UCS Director
Open and Resolved Bugs
Workflow Task
What Has Changed
Failover Production
New input fields were added Delete the existing task and replace with the
for the following:
new task.
(RecoverPoint task
Workaround to Resolve Issue
• Image to Access
• Point-In-Time
• Seconds
• Bookmark
• Exact
• Image Type
• Max Range
Register iSCSI Storage with
Host Node
(NetApp CMode task)
The Generic Text Input field Open the task and change the input field.
was changed to VMware
Storage Adapter Identity.
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 following searches.
The results of that search include workarounds for the open bugs, if any.
Open Bugs in Release 5.3
You can find detailed information about all open bugs in Release 5.3 through the open bug search for Release
5.3. This search uses the following parameters:
Field
Parameter
Product drop-down list
Choose Series/Model and enter Cisco UCS Director
5.3.
Cisco UCS Director Release Notes, Release 5.3
19
Cisco UCS Director
Open Bugs for This Release
Field
Parameter
Releases drop-down list
Choose Affecting or Fixed in these Releases and
enter 5.3(0.0).
Filter
Choose Open from the Status drop-down list.
Open Bugs in Release 5.3(0.1)
You can find detailed information about all open bugs in Patch Release 5.3(0.1) through the open bug search
for Release 5.3(0.1). This search uses the following parameters:
Field
Parameter
Product drop-down list
Choose Series/Model and enter Cisco UCS Director
5.3.
Releases drop-down list
Choose Affecting or Fixed in these Releases and
enter 5.3(0.1).
Filter
Choose Open from the Status drop-down list.
Open Bugs in Release 5.3(0.2)
You can find detailed information about all open bugs in Patch Release 5.3(0.2) through the open bug search
for Release 5.3(0.2). This search uses the following parameters:
Field
Parameter
Product drop-down list
Choose Series/Model and enter Cisco UCS Director
5.3.
Releases drop-down list
Choose Affecting or Fixed in these Releases and
enter 5.3(0.2).
Filter
Choose Open from the Status drop-down list.
Open Bugs in Release 5.3(1.0)
You can find detailed information about all open bugs in Release 5.3(1.0) through the open bug search for
Release 5.3(1.0). This search uses the following parameters:
Field
Parameter
Product drop-down list
Choose Series/Model and enter Cisco UCS Director
5.3.
Releases drop-down list
Choose Affecting or Fixed in these Releases and
enter 5.3 (1.0).
Cisco UCS Director Release Notes, Release 5.3
20
Cisco UCS Director
Open Bugs for This Release
Field
Parameter
Filter
Choose Open from the Status drop-down list.
Open Bugs in Release 5.3(1.1)
You can find detailed information about all open bugs in Release 5.3(1.1) through the open bug search for
Release 5.3(1.1) . This search uses the following parameters:
Field
Parameter
Product drop-down list
Choose Series/Model and enter Cisco UCS Director
5.3.
Releases drop-down list
Choose Affecting or Fixed in these Releases and
enter 5.3(1.1).
Filter
Choose Open from the Status drop-down list.
Open Bugs in Release 5.3(1.2)
You can find detailed information about all open bugs in Release 5.3(1.2) through the open bug search for
Release 5.3(1.2) . This search uses the following parameters:
Field
Parameter
Product drop-down list
Choose Series/Model and enter Cisco UCS Director
5.3.
Releases drop-down list
Choose Affecting or Fixed in these Releases and
enter 5.3(1.2).
Filter
Choose Open from the Status drop-down list.
Open Bugs in Release 5.3(2.0)
You can find detailed information about all open bugs in Release 5.3(2.0) through the open bug search for
Release 5.3(2.0). This search uses the following parameters:
Field
Parameter
Product drop-down list
Choose Series/Model and enter Cisco UCS Director
5.3.
Releases drop-down list
Choose Affecting or Fixed in these Releases and
enter 5.3(2.0).
Filter
Choose Open from the Status drop-down list.
Cisco UCS Director Release Notes, Release 5.3
21
Cisco UCS Director
Resolved Bugs in This Release
Open Bugs in Release 5.3(2.1)
You can find detailed information about all open bugs in Release 5.3(2.1) through the open bug search for
Release 5.3(2.1). This search uses the following parameters:
Field
Parameter
Product drop-down list
Choose Series/Model and enter Cisco UCS Director
5.3.
Releases drop-down list
Choose Affecting or Fixed in these Releases and
enter 5.3(2.1).
Filter
Choose Open from the Status drop-down list.
Open Bugs in Release 5.3(2.2)
You can find detailed information about all open bugs in Release 5.3(2.2) through the open bug search for
Release 5.3(2.2). This search uses the following parameters:
Field
Parameter
Product drop-down list
Choose Series/Model and enter Cisco UCS Director
5.3.
Releases drop-down list
Choose Affecting or Fixed in these Releases and
enter 5.3(2.2).
Filter
Choose Open from the Status drop-down list.
Resolved Bugs in This Release
All resolved bugs for this release are available in the Cisco Bug Search Tool through the following searches.
Resolved Bugs in Release 5.3
You can find detailed information about resolved bugs in Release 5.3 through the fixed bug search for Release
5.3.
Field
Parameter
Product drop-down list
Choose Series/Model and enter Cisco UCS Director
5.3.
Releases drop-down list
Choose Affecting or Fixed in these Releases and
enter 5.3(0.0).
Filter
Choose Fixed from the Status drop-down list.
Cisco UCS Director Release Notes, Release 5.3
22
Cisco UCS Director
Resolved Bugs in This Release
Resolved Bugs in Release 5.3(0.1)
You can find detailed information about resolved bugs in Patch Release 5.3(0.1) through the fixed bug search
for Release 5.3(0.1).
The above search uses the following parameters:
Field
Parameter
Product drop-down list
Choose Series/Model and enter Cisco UCS Director
5.3.
Releases drop-down list
Choose Affecting or Fixed in these Releases and
enter 5.3(0.1).
Filter
Choose Fixed from the Status drop-down list.
Resolved Bugs in Release 5.3(0.2)
You can find detailed information about resolved bugs in Patch Release 5.3(0.2) through the fixed bug search
for Release 5.3(0.2).
The above search uses the following parameters:
Field
Parameter
Product drop-down list
Choose Series/Model and enter Cisco UCS Director
5.3.
Releases drop-down list
Choose Affecting or Fixed in these Releases and
enter 5.3(0.2).
Filter
Choose Fixed from the Status drop-down list.
Resolved Bugs in Release 5.3(1.0)
You can find detailed information about resolved bugs in Release 5.3(1.0) through the fixed bug search for
Release 5.3(1.0).
The above search uses the following parameters:
Field
Parameter
Product drop-down list
Choose Series/Model and enter Cisco UCS Director
5.3.
Releases drop-down list
Choose Affecting or Fixed in these Releases and
enter 5.3(1.0).
Filter
Choose Fixed from the Status drop-down list.
Cisco UCS Director Release Notes, Release 5.3
23
Cisco UCS Director
Resolved Bugs in This Release
Resolved Bugs in Release 5.3(1.1)
You can find detailed information about resolved bugs in Release 5.3(1.1) through the fixed bug search for
Release 5.3(1.1).
The above search uses the following parameters:
Field
Parameter
Product drop-down list
Choose Series/Model and enter Cisco UCS Director
5.3.
Releases drop-down list
Choose Affecting or Fixed in these Releases and
enter 5.3(1.1).
Filter
Choose Fixed from the Status drop-down list.
Resolved Bugs in Release 5.3(1.2)
You can find detailed information about resolved bugs in Release 5.3(1.2) through the fixed bug search for
Release 5.3(1.2).
Field
Parameter
Product drop-down list
Choose Series/Model and enter Cisco UCS Director
5.3.
Releases drop-down list
Choose Affecting or Fixed in these Releases and
enter 5.3(1.2).
Filter
Choose Fixed from the Status drop-down list.
Resolved Bugs in Release 5.3(2.0)
You can find detailed information about resolved bugs in Release 5.3(2.0) through the fixed bug search for
Release 5.3(2.0).
Field
Parameter
Product drop-down list
Choose Series/Model and enter Cisco UCS Director
5.3.
Releases drop-down list
Choose Affecting or Fixed in these Releases and
enter 5.3(2.0).
Filter
Choose Fixed from the Status drop-down list.
Cisco UCS Director Release Notes, Release 5.3
24
Cisco UCS Director
Resolved Bugs in This Release
Resolved Bugs in Release 5.3(2.1)
You can find detailed information about resolved bugs in Release 5.3(2.1) through the fixed bug search for
Release 5.3(2.1).
Field
Parameter
Product drop-down list
Choose Series/Model and enter Cisco UCS Director
5.3.
Releases drop-down list
Choose Affecting or Fixed in these Releases and
enter 5.3(2.1).
Filter
Choose Fixed from the Status drop-down list.
Resolved Bugs in Release 5.3(2.2)
You can find detailed information about resolved bugs in Release 5.3(2.2) through the fixed bug search for
Release 5.3(2.2).
Field
Parameter
Product drop-down list
Choose Series/Model and enter Cisco UCS Director
5.3.
Releases drop-down list
Choose Affecting or Fixed in these Releases and
enter 5.3(2.2).
Filter
Choose Fixed from the Status drop-down list.
Resolved Bugs in Release 5.3(2.3)
You can find detailed information about resolved bugs in Release 5.3(2.3) through the fixed bug search for
Release 5.3(2.3).
Field
Parameter
Product drop-down list
Choose Series/Model and enter Cisco UCS Director
5.3.
Releases drop-down list
Choose Affecting or Fixed in these Releases and
enter 5.3(2.3).
Filter
Choose Fixed from the Status drop-down list.
Resolved Bugs in Release 5.3(2.4)
You can find detailed information about resolved bugs in Release 5.3(2.4) through the fixed bug search for
Release 5.3(2.4).
Cisco UCS Director Release Notes, Release 5.3
25
Cisco UCS Director
Related Documentation
Field
Parameter
Product drop-down list
Choose Series/Model and enter Cisco UCS Director
5.3.
Releases drop-down list
Choose Affecting or Fixed in these Releases and
enter 5.3(2.4).
Filter
Choose Fixed from the Status drop-down list.
Resolved Bugs in Release 5.3(2.5)
You can find detailed information about resolved bugs in Release 5.3(2.5) through the fixed bug search for
Release 5.3(2.5).
Field
Parameter
Product drop-down list
Choose Series/Model and enter Cisco UCS Director
5.3.
Releases drop-down list
Choose Affecting or Fixed in these Releases and
enter 5.3(2.5).
Filter
Choose Fixed from the Status drop-down list.
Related Documentation
In addition to these release notes, you can find documentation for Cisco UCS Director in the following locations
on Cisco.com:
• Cisco UCS Director Documentation Roadmap
• Cisco UCS Director Product Overview Pages
• Cisco UCS Director on Cisco DevNet
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.
To receive new and revised Cisco technical content directly to your desktop, you can subscribe to the What's
New in Cisco Product Documentation RSS feed. RSS feeds are a free service.
Cisco UCS Director Release Notes, Release 5.3
26
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)
© 2015-2017
Cisco Systems, Inc. All rights reserved.