Cisco UCS Director Release Notes, Release 5.4
First Published: November 05, 2015
Last Modified: July 05, 2016
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.
Revision History
Release
Date
Description
5.4
November 5, 2015
Created release notes for Cisco
UCS Director, Release 5.4
5.4
November 5, 2015
Added information about the
compression of the OVF and VHD
zip files and recommendation for
uncompressing them.
5.4
November 6, 2015
Updated the New and Changed
Features section.
5.4
November 9, 2015
Updated information about the
compression of the OVF and VHD
zip files and recommendation for
uncompressing them.
5.4(0.1)
December 23, 2015
Added information on upgrade to
and open and resolved caveats for
Release 5.4(0.1).
Cisco UCS Director Release Notes, Release 5.4
1
Cisco UCS Director
System Requirements
Release
Date
Description
5.4(0.2)
February 2, 2016
Added information on the
following for Release 5.4.(0.2)
• New and Changed Features
• Upgrade Information
• Open and resolved caveats
5.4(0.3)
April 20, 2016
Added information on the
following for Release 5.4(0.3)
• Open and resolved caveats
5.4(0.4)
July 5, 2016
Added information on the
following for Release 5.4.(0.4)
• Upgrade Information
• Open and resolved caveats
System Requirements
Cisco UCS Director can be hosted on VMware vSphere.
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.
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.4
2
Cisco UCS Director
Upgrade to Cisco UCS Director, Release 5.4
Note
Cisco UCS Director 5.4 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.
Upgrade to Cisco UCS Director, Release 5.4
Overview of the Upgrade to Cisco UCS Director, Release 5.4
Cisco UCS Director Release 5.4 uses a new version of Java and the CentOS operating system. Due to this,
the upgrade procedure for Release 5.4 is different from previous upgrades.
In previous releases, you applied the new release to the existing Cisco UCS Director appliances as a patch
and the software and database schema were upgraded. For Cisco UCS Director, Release 5.4, you need to
create new VMs, deploy the software, and then migrate the database and other configuration files from the
Release 5.3 VMs to the Release 5.4 VMs. This process is required because you are upgrading the following
in addition to Cisco UCS Director and Cisco UCS Director Baremetal Agent:
• CentOS version 5.4 to version 6.6
• Java version 1.6 to version 1.8
Note
Cisco UCS Director, Release 5.4 requires a memory capacity of 12 GB.
Supported Upgrade Paths to Cisco UCS Director , Release 5.4
The upgrade path to Cisco UCS Director, Release 5.4 depends upon your current version of Cisco UCS
Director.
The following are the supported upgrade paths for Cisco UCS Director, Release 5.4 .
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.
Cisco UCS Director Release Notes, Release 5.4
3
Cisco UCS Director
Upgrade to Cisco UCS Director, Release 5.4
Upgrade Paths for Release 5.3(x.x) Platform
• From Release 5.3(0.0) to Release 5.4
• From Release 5.3(0.1) to Release 5.4
• From Release 5.3(0.2) to Release 5.4
• From Release 5.3(1.0) to Release 5.4
• From Release 5.3(1.1) to Release 5.4
• From Release 5.3(1.2) to Release 5.4
• From Release 5.3(2.0) to Release 5.4
Upgrade Paths for Release 5.2(x.x) Platform
• From Release 5.2(0.0), you must first upgrade to Cisco UCS Director, Release 5.3(0.x), 5.3(1.x), or
5.3(2.x)
• From Release 5.2(0.1), you must first upgrade to Cisco UCS Director, Release 5.3(0.x), 5.3(1.x), or
5.3(2.x)
• From Release 5.2(0.2), you must first upgrade to Cisco UCS Director, Release 5.3(0.x), 5.3(1.x), or
5.3(2.x)
• From Release 5.2(0.2A), you must first upgrade to Cisco UCS Director, Release 5.3(0.1) or later, 5.3(1.x),
or 5.3(2.x)
• From Release 5.2(0.3), you must first upgrade to Cisco UCS Director, Release 5.3(1.2), or 5.3(2.x)
Upgrade Paths for Release 5.1(x.x)
From Release 5.1(x.x), you must first upgrade to Cisco UCS Director, Release 5.3(0.0).
Upgrade Paths for Release 5.0(x.x) and Earlier Releases
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 Baremetal Agent, Release 5.4
The upgrade path to Cisco UCS Director Baremetal Agent (Baremetal Agent), Release 5.4 depends upon your
current version of Baremetal Agent.
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. Baremetal Agent does not have a Release 5.1. If you are upgrading from Cisco UCS Director,
Release 5.1, your system includes Baremetal Agent, Release 5.0.
Upgrade Paths for Baremetal Agent, Release 5.3
From Release 5.3, you can upgrade directly to Release 5.4.
Cisco UCS Director Release Notes, Release 5.4
4
Cisco UCS Director
Upgrade to Cisco UCS Director, Release 5.4(0.1)
Upgrade Paths for Baremetal Agent, Release 5.2
From Release 5.2, you can upgrade directly to Release 5.4.
Upgrade Paths for Baremetal Agent, Release 5.0
From Release 5.0, you can upgrade directly to Release 5.4.
Upgrade Paths for Baremetal Agent, Release 4.1 and Earlier Releases
From Release 4.1 or an earlier release, you must first upgrade to Baremetal Agent, Release 5.0 and then
upgrade to Baremetal Agent, Release 5.4.
For information about how to upgrade to previous releases of Baremetal Agent, see the installation and
configuration guide for that release.
PowerShell Agent Upgrade for Release 5.4
After you upgrade to Cisco UCS Director, Release 5.4, you must reinstall your PowerShell Agent. You can
download the latest version of the PowerShell Agent from the system that has been upgraded to Release 5.4.
For more information about how to upgrade PowerShell Agent, see the Cisco UCS Director Upgrade Guide.
Note
If you do not reinstall your PowerShell Agent, any existing Execute PowerShell Task will fail after you
upgrade to Release 5.4.
Upgrade to Cisco UCS Director, Release 5.4(0.1)
Supported Upgrade Paths to Cisco UCS Director, Release 5.4(0.1)
The upgrade path to Cisco UCS Director, Release 5.4(0.1), depends upon your current version of Cisco UCS
Director.
The following are the supported upgrade paths for Cisco UCS Director 5.4(0.1).
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.4
To upgrade from Release 5.4(0.0) to Release 5.4(0.1), you must apply the Release 5.4(0.1) patch to your
Release 5.4(0.0) appliance. For more information, see the Cisco UCS Director Upgrade Guide, Release 5.4.
Cisco UCS Director Release Notes, Release 5.4
5
Cisco UCS Director
Upgrade to Cisco UCS Director, Release 5.4(0.1)
Upgrade Paths for Release 5.3(x.x)
Note
To upgrade from Release 5.3(x.x) to Release 5.4(0.1), you must apply the 5.4(0.1) patch to the Release
5.4 VM before you migrate your 5.3(x.x) appliance.
• From Release 5.3(2.1), deploy a 5.4(0.0) VM, apply the Release 5.4(0.1) patch to your Release 5.4
appliance, and migrate from 5.3(2.1) to 5.4(0.1).
• From Release 5.3(2.0), you must first migrate to a Release 5.4(0.0) VM, and then apply the Release
5.4(0.1) patch to your Release 5.4 appliance.
• From Release 5.3(1.2), you must first migrate to a Release 5.4(0.0) VM, and then apply the Release
5.4(0.1) patch to your Release 5.4 appliance.
• From Release 5.3(1.1), you must first migrate to a Release 5.4(0.0) VM, and then apply the Release
5.4(0.1) patch to your Release 5.4 appliance.
• From Release 5.3(1.0), you must first migrate to a Release 5.4(0.0) VM, and then apply the Release
5.4(0.1) patch to your Release 5.4 appliance.
• From Release 5.3(0.2), you must first migrate to a Release 5.4(0.0) VM, and then apply the Release
5.4(0.1) patch to your Release 5.4 appliance.
• From Release 5.3(0.1), you must first migrate to a Release 5.4(0.0) VM, and then apply the Release
5.4(0.1) patch to your Release 5.4 appliance.
• From Release 5.3(0.0), you must first migrate to a Release 5.4(0.0) VM, and then apply the Release
5.4(0.1) patch to your Release 5.4 appliance.
Upgrade Paths for Release 5.2(x.x)
• From Release 5.2(0.0), you must first upgrade to Cisco UCS Director, Release 5.3(0.x), 5.3(1.x), or
5.3(2.x)
• From Release 5.2(0.1), you must first upgrade to Cisco UCS Director, Release 5.3(0.x), 5.3(1.x), or
5.3(2.x)
• From Release 5.2(0.2), you must first upgrade to Cisco UCS Director, Release 5.3(0.x), 5.3(1.x), or
5.3(2.x)
• From Release 5.2(0.2A), you must first upgrade to Cisco UCS Director, Release 5.3(0.x), 5.3(1.x), or
5.3(2.x)
• From Release 5.2(0.3), you must first upgrade to Cisco UCS Director, Release 5.3(0.x), 5.3(1.x), or
5.3(2.x)
Upgrade Paths for Release 5.1(x.x)
From Release 5.1(x.x), you must first upgrade to Cisco UCS Director, Release 5.3(0.0).
Upgrade Paths for Release 5.0(x.x) and Earlier Releases
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).
Cisco UCS Director Release Notes, Release 5.4
6
Cisco UCS Director
Upgrade to Cisco UCS Director, Release 5.4(0.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.
Upgrade to Cisco UCS Director, Release 5.4(0.2)
Supported Upgrade Paths to Cisco UCS Director, Release 5.4(0.2)
The upgrade path to Cisco UCS Director, Release 5.4(0.2), depends upon your current version of Cisco UCS
Director.
The following are the supported upgrade paths for Cisco UCS Director 5.4(0.2). For more information, see
the Cisco UCS Director Upgrade Guide, Release 5.4.
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.4(x.x)
To upgrade from Release 5.4(x.x) to Release 5.4(0.2), you must apply the Release 5.4(0.2) patch to your
Release 5.4(x.x) appliance.
• From Release 5.4(0.1) to Release 5.4(0.2), apply the Release 5.4(0.2) patch to your Release 5.4(0.1)
appliance.
• From Release 5.4(0.0) to Release 5.4(0.2), apply the Release 5.4(0.2) patch to your Release 5.4 appliance.
Upgrade Paths for Release 5.3(x.x)
• From Release 5.3(2.1), deploy a 5.4(0.0) VM, apply the Release 5.4(0.1) patch to your Release 5.4
appliance, migrate from 5.3(2.1) to 5.4.(0.1), and then apply the Release 5.4(0.2) patch to your Release
5.4(0.1) appliance.
• From Release 5.3(2.0), you must first migrate to a Release 5.4(0.0) VM, and then apply the Release
5.4(0.2) patch to your Release 5.4 appliance.
• From Release 5.3(1.2), you must first migrate to a Release 5.4(0.0) VM, and then apply the Release
5.4(0.2) patch to your Release 5.4 appliance.
• From Release 5.3(1.1), you must first migrate to a Release 5.4(0.0) VM, and then apply the Release
5.4(0.2) patch to your Release 5.4 appliance.
• From Release 5.3(1.0), you must first migrate to a Release 5.4(0.0) VM, and then apply the Release
5.4(0.2) patch to your Release 5.4 appliance.
• From Release 5.3(0.2), you must first migrate to a Release 5.4(0.0) VM, and then apply the Release
5.4(0.2) patch to your Release 5.4 appliance.
• From Release 5.3(0.1), you must first migrate to a Release 5.4(0.0) VM, and then apply the Release
5.4(0.2) patch to your Release 5.4 appliance.
• From Release 5.3(0.0), you must first migrate to a Release 5.4(0.0) VM, and then apply the Release
5.4(0.2) patch to your Release 5.4 appliance.
Cisco UCS Director Release Notes, Release 5.4
7
Cisco UCS Director
Upgrade to Cisco UCS Director, Release 5.4(0.3)
Upgrade Paths for Release 5.2.x.x
• From Release 5.2(0.0), you must first upgrade to Cisco UCS Director, Release 5.3(0.x), 5.3(1.x), or
5.3(2.x)
• From Release 5.2(0.1), you must first upgrade to Cisco UCS Director, Release 5.3(0.x), 5.3(1.x), or
5.3(2.x)
• From Release 5.2(0.2), you must first upgrade to Cisco UCS Director, Release 5.3(0.x), 5.3(1.x), or
5.3(2.x)
• From Release 5.2(0.2A), you must first upgrade to Cisco UCS Director, Release 5.3(0.x), 5.3(1.x), or
5.3(2.x)
• From Release 5.2(0.3), you must first upgrade to Cisco UCS Director, Release 5.3(0.x), 5.3(1.x), or
5.3(2.x)
Upgrade Paths for Release 5.1(x.x)
From Release 5.1(x.x), you must first upgrade to Cisco UCS Director, Release 5.3(0.0).
Upgrade Paths for Release 5.0(x.x) and Earlier Releases
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.
Upgrade to Cisco UCS Director, Release 5.4(0.3)
Supported Upgrade Paths to Cisco UCS Director, Release 5.4(0.3)
The upgrade path to Cisco UCS Director, Release 5.4(0.3), depends upon your current version of Cisco UCS
Director.
The following are the supported upgrade paths for Cisco UCS Director 5.4(0.3). For more information, see
the Cisco UCS Director Upgrade Guide, Release 5.4.
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.4(x.x)
To upgrade from Release 5.4(x.x) to Release 5.4(0.3), you must apply the Release 5.4(0.3) patch to your
Release 5.4(x.x) appliance.
• From Release 5.4(0.2) to Release 5.4(03), apply the Release 5.4(0.3) patch to your Release 5.4(0.2)
appliance.
Cisco UCS Director Release Notes, Release 5.4
8
Cisco UCS Director
Supported Upgrade Paths to Cisco UCS Director, Release 5.4(0.3)
• From Release 5.4(0.1) to Release 5.4(0.3), apply the Release 5.4(0.3) patch to your Release 5.4(0.1)
appliance.
• From Release 5.4(0.0) to Release 5.4(0.3), apply the Release 5.4(0.3) patch to your Release 5.4 appliance.
Upgrade Paths for Release 5.3(x.x)
• From Release 5.3(2.3), deploy a 5.4(0.0) VM, apply the Release 5.4(0.3) patch to your Release 5.4
appliance, and then migrate from 5.3(2.3) to 5.4.(0.3).
• From Release 5.3(2.2), deploy a 5.4(0.0) VM, apply the Release 5.4(0.3) patch to your Release 5.4
appliance, and then migrate from 5.3(2.2) to 5.4.(0.3).
• From Release 5.3(2.1), deploy a 5.4(0.0) VM, apply the Release 5.4(0.1) patch to your Release 5.4
appliance, migrate from 5.3(2.1) to 5.4.(0.1), and then apply the Release 5.4(0.3) patch.
• From Release 5.3(2.0), you must first migrate to a Release 5.4(0.0) VM, and then apply the Release
5.4(0.3) patch to your Release 5.4 appliance.
• From Release 5.3(1.2), you must first migrate to a Release 5.4(0.0) VM, and then apply the Release
5.4(0.3) patch to your Release 5.4 appliance.
• From Release 5.3(1.1), you must first migrate to a Release 5.4(0.0) VM, and then apply the Release
5.4(0.3) patch to your Release 5.4 appliance.
• From Release 5.3(1.0), you must first migrate to a Release 5.4(0.0) VM, and then apply the Release
5.4(0.3) patch to your Release 5.4 appliance.
• From Release 5.3(0.2), you must first migrate to a Release 5.4(0.0) VM, and then apply the Release
5.4(0.3) patch to your Release 5.4 appliance.
• From Release 5.3(0.1), you must first migrate to a Release 5.4(0.0) VM, and then apply the Release
5.4(0.3) patch to your Release 5.4 appliance.
• From Release 5.3(0.0), you must first migrate to a Release 5.4(0.0) VM, and then apply the Release
5.4(0.3) patch to your Release 5.4 appliance.
Upgrade Paths for Release 5.2.x.x
• From Release 5.2(0.0), you must first upgrade to Cisco UCS Director, Release 5.3(0.x), 5.3(1.x), or
5.3(2.x)
• From Release 5.2(0.1), you must first upgrade to Cisco UCS Director, Release 5.3(0.x), 5.3(1.x), or
5.3(2.x)
• From Release 5.2(0.2), you must first upgrade to Cisco UCS Director, Release 5.3(0.x), 5.3(1.x), or
5.3(2.x)
• From Release 5.2(0.2A), you must first upgrade to Cisco UCS Director, Release 5.3(0.x), 5.3(1.x), or
5.3(2.x)
• From Release 5.2(0.3), you must first upgrade to Cisco UCS Director, Release 5.3(0.x), 5.3(1.x), or
5.3(2.x)
Upgrade Paths for Release 5.1(x.x)
From Release 5.1(x.x), you must first upgrade to Cisco UCS Director, Release 5.3(0.0).
Cisco UCS Director Release Notes, Release 5.4
9
Cisco UCS Director
Upgrade to Cisco UCS Director, Release 5.4(0.4)
Upgrade Paths for Release 5.0(x.x) and Earlier Releases
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.
Upgrade to Cisco UCS Director, Release 5.4(0.4)
Supported Upgrade Paths to Cisco UCS Director, Release 5.4(0.4)
The upgrade path to Cisco UCS Director, Release 5.4(0.4), depends upon your current version of Cisco UCS
Director.
The following are the supported upgrade paths for Cisco UCS Director 5.4(0.4). For more information, see
the Cisco UCS Director Upgrade Guide, Release 5.4.
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.4(x.x)
To upgrade from Release 5.4(x.x) to Release 5.4(0.4), you must apply the Release 5.4(0.4) patch to your
Release 5.4(x.x) appliance.
• From Release 5.4(0.3) to Release 5.4(0.4), apply the Release 5.4(0.4) patch to your Release 5.4(0.3)
appliance.
• From Release 5.4(0.2) to Release 5.4(0.4), apply the Release 5.4(0.4) patch to your Release 5.4(0.2)
appliance.
• From Release 5.4(0.1) to Release 5.4(0.4), apply the Release 5.4(0.4) patch to your Release 5.4(0.1)
appliance.
• From Release 5.4(0.0) to Release 5.4(0.4), apply the Release 5.4(0.4) patch to your Release 5.4 appliance.
Upgrade Paths for Release 5.3(x.x)
• From Release 5.3(2.3), deploy a 5.4(0.0) VM, apply the Release 5.4(0.4) patch to your Release 5.4
appliance, and then migrate from 5.3(2.3) to 5.4.(0.4).
• From Release 5.3(2.2), deploy a 5.4(0.0) VM, apply the Release 5.4(0.4) patch to your Release 5.4
appliance, and then migrate from 5.3(2.2) to 5.4.(0.4).
• From Release 5.3(2.1), deploy a 5.4(0.0) VM, apply the Release 5.4(0.1) patch to your Release 5.4
appliance, migrate from 5.3(2.1) to 5.4.(0.1), and then apply the Release 5.4(0.4) patch.
• From Release 5.3(2.0), you must first migrate to a Release 5.4(0.0) VM, and then apply the Release
5.4(0.4) patch to your Release 5.4 appliance.
Cisco UCS Director Release Notes, Release 5.4
10
Cisco UCS Director
New and Changed Features
• From Release 5.3(1.2), you must first migrate to a Release 5.4(0.0) VM, and then apply the Release
5.4(0.4) patch to your Release 5.4 appliance.
• From Release 5.3(1.1), you must first migrate to a Release 5.4(0.0) VM, and then apply the Release
5.4(0.4) patch to your Release 5.4 appliance.
• From Release 5.3(1.0), you must first migrate to a Release 5.4(0.0) VM, and then apply the Release
5.4(0.4) patch to your Release 5.4 appliance.
• From Release 5.3(0.2), you must first migrate to a Release 5.4(0.0) VM, and then apply the Release
5.4(0.4) patch to your Release 5.4 appliance.
• From Release 5.3(0.1), you must first migrate to a Release 5.4(0.0) VM, and then apply the Release
5.4(0.3) patch to your Release 5.4 appliance.
• From Release 5.3(0.0), you must first migrate to a Release 5.4(0.0) VM, and then apply the Release
5.4(0.3) patch to your Release 5.4 appliance.
Upgrade Paths for Release 5.2.x.x
• From Release 5.2(0.0), you must first upgrade to Cisco UCS Director, Release 5.3(0.x), 5.3(1.x), or
5.3(2.x)
• From Release 5.2(0.1), you must first upgrade to Cisco UCS Director, Release 5.3(0.x), 5.3(1.x), or
5.3(2.x)
• From Release 5.2(0.2), you must first upgrade to Cisco UCS Director, Release 5.3(0.x), 5.3(1.x), or
5.3(2.x)
• From Release 5.2(0.2A), you must first upgrade to Cisco UCS Director, Release 5.3(0.x), 5.3(1.x), or
5.3(2.x)
• From Release 5.2(0.3), you must first upgrade to Cisco UCS Director, Release 5.3(0.x), 5.3(1.x), or
5.3(2.x)
Upgrade Paths for Release 5.1(x.x)
From Release 5.1(x.x), you must first upgrade to Cisco UCS Director, Release 5.3(0.0).
Upgrade Paths for Release 5.0(x.x) and Earlier Releases
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.
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.4
11
Cisco UCS Director
New and Changed Features in Release 5.4(0.2)
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.4(0.2)
Enhancements to APIC Management
The following changes were introduced to APIC management in this release:
• Tag support in datastore —Provision to add the data store tags with multiple tag values in the virtual
storage service class level
• AVS VXLAN support—Cisco UCS Director offers AVS support in both VLAN and VXLAN mode.
Documented in the Cisco UCS Director APIC Management Guide, Release 5.4.
Enhancements to Application Containers
The enhancements to application containers in Cisco UCS Director include support for the following:
• SSL Offload Support—Changes to the L4-L7 Policy for load balancer (LB) to support both basic LB
(HTTP) and SSL offload. During deployment of an application container, SSL certificate must be
provided for the SSL offload function for the web servers.
• Support for advanced load balancer parameters—Network device system parameter policy sets the NTP
and SNMP parameters that are needed to be configured on a load balancer device.
• LB vServer Support—The application container has the ability to view, add, or delete the load balancer
L4-L7 services. The newly created VMs are added as real servers to the L4-L7 service.
Documented in the Cisco UCS Director Application Container Guide, Release 5.4.
New and Changed Features in Release 5.4
Enhancements to Application Containers
The enhancements to application containers in Cisco UCS Director include support for the following:
• Deleting a disk in the bare metal server—The APIC Container has the ability to delete the Logical Unit
Numbers (LUNs) operation on the physical server within the specified resource limits.
• Adding VMs—You cannot add the VMs to the container through the Add VMs to Container or Add
VMs to APIC Container workflow. You can add VMs only by clicking Add VMs or through API.
• Service Chaining—If Enable Network Management is disabled for a vDC, specific configurations are
performed by default.
Documented in the Cisco UCS Director Application Container Guide, Release 5.4.
Cisco UCS Director Release Notes, Release 5.4
12
Cisco UCS Director
New and Changed Features in Release 5.4
Support for Cisco IMC Supervisor
For C-Series standalone servers, native support is now available for Cisco IMC Supervisor 1.1 features
Documented in the Cisco UCS Director Management Guide for Rack Servers, Release 5.4 and the Cisco UCS
Director Compatibility Matrix, Release 5.4.
Deprecated Support for Legacy Cisco IMC Accounts
Cisco Rack Server (CIMC) accounts are no longer supported in Cisco UCS Director, Release 5.4 in either a
new installation or after upgrade. If you have existing Cisco Rack Server (CIMC) accounts, you must delete
those accounts and add them as Rack accounts.
Documented in the Cisco UCS Director Management Guide for Rack Servers, Release 5.4.
Enhancements to Cisco UCS Manager Support
Cisco UCS Director is now compatible with Cisco UCS Manager, Release 2.2(6*).
Documented in the Cisco UCS Director Compatibility Matrix, Release 5.4.
Enhancements to Cisco UCS Central Support
The following changes were added to Cisco UCS Central support in this release:
• Support for Cisco UCS Central, Release 1.3(1*)
• Operating system deployment enhancements
• Task library enhancements
Documented in the Cisco UCS Director Compatibility Matrix, Release 5.4 and in the Task Library available
inside Cisco UCS Director.
Enhancements to Windows Operating System Deployment with Cisco UCS Director Baremetal Agent
The following changes were made to Windows operating system deployment:
• Ability to deploy a single Windows operating system flavor with a Single Baremetal Agent
• Ability to simultaneously deploy multiple Windows operating flavors with multiple Baremetal Agents
Documented in the Cisco UCS Director Baremetal Agent Installation and Configuration Guide, Release 5.4.
Enhancements to APIC Management Support
The following changes were introduced to APIC management in this release:
• APIC reports—Provision to view the fabric configured switch interfaces.
• Private network—Provision to view the private networks created for the tenant, and to view the supernet
and subnet pools of the private network.
• Consumed Contract Interface—Provision to view and manage consumed contract interface in EPG.
• LUN and HLU across the main and disaster recovery sites—For handling fail over scenario for a tenant
with the disaster recovery (DR) support, same LUN ID and host LUN (HLU) ID are needed in the
primary and secondary sites. During tenant onboarding, the same LUN ID and HLU ID are reserved on
Cisco UCS Director Release Notes, Release 5.4
13
Cisco UCS Director
New and Changed Features in Release 5.4
the primary and secondary sites based on the availability of the selected VNX account and VMware
host.
• FlexPod ACI - Tenant Infrastructure Configuration workflow, FlexPod ACI - Enable Tenant Infrastructure
Support For Guest Attached ISCSI workflow— If the NetApp device uses ONTAP 8.3 operating system,
ensure that the following tasks are added before the Create Failover Group tasks:
• custom BroadcastDomain_CLI
• SSH command
• Compatibility with APIC version 1.1(3*)
Documented in the Cisco UCS Director APIC Management Guide, Release 5.4 and the Cisco UCS Director
Compatibility Matrix, Release 5.4.
Enhancements to VMware vSphere and Virtual SAN Support
The enhancements to VMware vSphere and Virtual SAN support include the following:
• Virtual SAN Pod Reports—Provides ability to view Virtual SAN clusters, Virtual SAN qualification
policies, and related system tasks for the Virtual SAN pod.
• Virtual SAN cluster management at pod level—Provides ability to define Baremetal servers, LAN boot
policies, Service Profile templates, and Virtual SAN networking policies at the pod level.
• Virtual SAN hardware topologies—Provides ability to view Virtual SAN hardware topologies.
• Virtual SAN host maintenance mode—Provides ability to move Virtual SAN hosts to maintenance
mode.
• Managing infrastructure as a service for Virtual SAN—Provides ability to manage Virtual SAN
infrastructure resources, including VMs, Virtual SAN storage profiles, Virtual SAN VDCs, and Virtual
SAN catalogs.
• Managing Virtual SAN disks and disk groups—Provides ability to view, add, and claim disks for Virtual
SAN.
• ESXi 6.0 Baremetal operating system deployment
• Support for Virtual SAN 6.0
Documented in the Cisco UCS Director VMware vSphere Management Guide, Release 5.4 and the Cisco
UCS Director Compatibility Matrix, Release 5.4.
Enhancements to NetApp Support
The following changes were made to NetApp support:
• Adding a NetApp account—Before adding NetApp accounts in Cisco UCS Director, you must enable
the Transport Layer Security (TLS) option on the NetApp device. Cisco UCS Director cannot discover
a NetApp account if the TLS option is disabled on the NetApp device.
• Compatibility with ONTAP 8.3.1 C-mode
Cisco UCS Director Release Notes, Release 5.4
14
Cisco UCS Director
New and Changed Features in Release 5.4
Before adding NetApp accounts in Cisco UCS Director, you must enable the Transport Layer Security (TLS)
option on the NetApp device. Cisco UCS Director cannot discover a NetApp account if the TLS option is
disabled on the NetApp device.
Documented in the Cisco UCS Director NetApp Management Guide, Release 5.4 and the Cisco UCS Director
Compatibility Matrix, Release 5.4.
Enhancements to EMC Support
The following changes were made to EMC support:
• Support for EMC VNXe
• Enhancements to support for EMC VMAX3
Documented in the Cisco UCS Director VNXe Management Guide, Release 5.4 and the Cisco UCS Director
Compatibility Matrix, Release 5.4.
Changes to Writing Scripts for Custom Workflows
The JDK version for the Cloupia Script platform has been upgraded from 1.6 to 1.8 for this release. As a
result, the syntax and usage of certain functions and classes in the script have changed.
Documented in the Cisco UCS Director Custom Task Getting Started Guide, Release 5.4.
Enhancements to Executing Workflows
The enhancements to executing workflows include support for the following:
• Viewing details of custom workflow components.
• Renaming a workflow while editing the workflow.
• Deleting multiple workflows simultaneously.
• Re-ordering inputs of a workflow using drag-and-drop.
Documented in Cisco UCS Director Orchestration Guide, Release 5.4.
Additional Enhancements to Cisco UCS Director
Other enhancements to Cisco UCS Director include the following:
• Overlapped IP subnet pool support
• Disabling and enabling users.
• Set expiration date for a user account while creating the account.
• Additional group and user filters while adding an LDAP account.
• Users can be part of multiple LDAP groups.
• Improved response times in integrating with large AD/LDAP environments
• Introduction of a VM management policy that you can map to a VDC.
• Support for creating application categories at the system level.
• New cost computation information is displayed when you perform actions such as creating or resizing
a VM, or creating a VM disk.
Cisco UCS Director Release Notes, Release 5.4
15
Cisco UCS Director
New Documentation Deliverables in this Release
• Support for special characters in the names for users, groups, and VDCs.
• VM management tasks defined by user role and end-user self-service policy.
Documented in the Cisco UCS Director Administration Guide, Release 5.4..
Support for Cisco UCS Director Express for Big Data in Cisco UCS Director
With the appropriate licenses, you can now enable Cisco UCS Director Express for Big Data features and
functionality from within Cisco UCS Director.
Documented in the Release Notes for Cisco UCS Director Express for Big Data, Release 2.0 and other Cisco
UCS Director Express for Big Data documentation for Release 2.0.
Localization Enhancements
Cisco UCS Director now includes French language support.
New Documentation Deliverables in this Release
The following are the new documentation deliverables available with Cisco UCS Director, Release 5.4:
• Cisco UCS Director Upgrade Guide—Includes information on how to upgrade to Release 5.4 for all
components.
• Cisco UCS Director API Integration and Customization Guide—Provides an overview of the API
integration and customization options available for Cisco UCS Director.
• Cisco UCS Director Multi-Node Installation and Configuration Guide—Includes information on how
to install and set up a multi-node system.
• Cisco UCS Director REST API Getting Started Guide—Includes information from the Cisco UCS
Director REST API Developer Guide that has been moved to this guide.
• Cisco UCS Director PowerShell API Getting Started Guide—Includes information from the Cisco UCS
Director PowerShell API User Guide that has been moved to this guide.
Workflow-Related Changes
Workflow Task Changes in Release 5.4
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.4
16
Cisco UCS Director
Known Behavior of Tenant Onboarding with MSP - VNX workflow
Workflow Task
What Has Changed
Workaround to Resolve Issue
Add Static Path To EPG
After upgrading to this release,
Open the task and change the input
when you run this workflow task, field
a binding error message is
displayed because the input values
have been modified.
For this workflow task, the
user-input type has been modified
from UpdateVMM Domain and
Static path to EPG.
Expand VSAN cluster
After upgrading to this release,
Open the task and change the input
when you run this workflow task, field
an error message is displayed that
states that a mandatory entry for
Dvswitch is missing.
Virtual SAN PXE Boot on SD
After upgrading to this release, the Open the task and change the input
input provided for the Boot Policy field
field in the prior release is not
retained.
Known Behavior of Tenant Onboarding with MSP - VNX workflow
If you have not enabled the service provider feature in Cisco UCS Director, the Tenant Onboarding with MSP
- VNX workflow will be in the validation failed state.
To enable the service provider feature, choose Administration > System > Service Provider Feature, and
check the Enable Service Provider Feature (Requires System Restart) check box. Restart the service and
validate the Tenant Onboarding with MSP - VNX workflow.
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.
Cisco UCS Director Release Notes, Release 5.4
17
Cisco UCS Director
Open Bugs for This Release
The results of that search include workarounds for the open bugs, if any.
Open Bugs in Release 5.4
You can find detailed information about all open bugs in Release 5.4 through the open bug search for Release
5.4. This search uses the following parameters:
Field
Parameter
Product drop-down list
Choose Series/Model and enter Cisco UCS Director
5.4.
Releases drop-down list
Choose Affecting or Fixed in these Releases and
enter 5.4(0.0).
Filter
Choose Open from the Status drop-down list.
Open Bugs in Release 5.4(0.1)
You can find detailed information about all open bugs in Release 5.4(0.1) through the open bug search for
Release 5.4(0.1). This search uses the following parameters:
Field
Parameter
Product drop-down list
Choose Series/Model and enter Cisco UCS Director
5.4.
Releases drop-down list
Choose Affecting or Fixed in these Releases and
enter 5.4(0.1).
Filter
Choose Open from the Status drop-down list.
Open Bugs in Release 5.4(0.2)
You can find detailed information about all open bugs in Release 5.4(0.2) through the open bug search for
Release 5.4(0.2). This search uses the following parameters:
Field
Parameter
Product drop-down list
Choose Series/Model and enter Cisco UCS Director
5.4.
Releases drop-down list
Choose Affecting or Fixed in these Releases and
enter 5.4(0.2).
Filter
Choose Open from the Status drop-down list.
Cisco UCS Director Release Notes, Release 5.4
18
Cisco UCS Director
Resolved Bugs in This Release
Open Bugs in Release 5.4(0.3)
You can find detailed information about all open bugs in Release 5.4(0.3) through the open bug search for
Release 5.4(0.3). This search uses the following parameters:
Field
Parameter
Product drop-down list
Choose Series/Model and enter Cisco UCS Director
5.4.
Releases drop-down list
Choose Affecting or Fixed in these Releases and
enter 5.4(0.3).
Filter
Choose Open from the Status drop-down list.
Open Bugs in Release 5.4(0.4)
You can find detailed information about all open bugs in Release 5.4(0.4) through the open bug search for
Release 5.4(0.4). This search uses the following parameters:
Field
Parameter
Product drop-down list
Choose Series/Model and enter Cisco UCS Director
5.4.
Releases drop-down list
Choose Affecting or Fixed in these Releases and
enter 5.4(0.4).
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.4
You can find detailed information about resolved bugs in Release 5.4 through the fixed bug search for Release
5.4.
Field
Parameter
Product drop-down list
Choose Series/Model and enter Cisco UCS Director
5.4.
Releases drop-down list
Choose Affecting or Fixed in these Releases and
enter 5.4(0.0).
Filter
Choose Fixed from the Status drop-down list.
Cisco UCS Director Release Notes, Release 5.4
19
Cisco UCS Director
Resolved Bugs in This Release
Resolved Bugs in Release 5.4(0.1)
You can find detailed information about resolved bugs in Release 5.4(0.1) through the fixed bug search for
Release 5.4(0.1).
Field
Parameter
Product drop-down list
Choose Series/Model and enter Cisco UCS Director
5.4.
Releases drop-down list
Choose Affecting or Fixed in these Releases and
enter 5.4(0.1).
Filter
Choose Fixed from the Status drop-down list.
Resolved Bugs in Release 5.4(0.2)
You can find detailed information about resolved bugs in Release 5.4(0.2) through the fixed bug search for
Release 5.4(0.2)
Field
Parameter
Product drop-down list
Choose Series/Model and enter Cisco UCS Director
5.4.
Releases drop-down list
Choose Affecting or Fixed in these Releases and
enter 5.4(0.2).
Filter
Choose Fixed from the Status drop-down list.
Resolved Bugs in Release 5.4(0.3)
You can find detailed information about resolved bugs in Release 5.4(0.3) through the fixed bug search for
Release 5.4(0.3)
Field
Parameter
Product drop-down list
Choose Series/Model and enter Cisco UCS Director
5.4.
Releases drop-down list
Choose Affecting or Fixed in these Releases and
enter 5.4(0.3).
Filter
Choose Fixed from the Status drop-down list.
Resolved Bugs in Release 5.4(0.4)
You can find detailed information about resolved bugs in Release 5.4(0.4) through the fixed bug search for
Release 5.4(0.4)
Cisco UCS Director Release Notes, Release 5.4
20
Cisco UCS Director
Related Documentation
Field
Parameter
Product drop-down list
Choose Series/Model and enter Cisco UCS Director
5.4.
Releases drop-down list
Choose Affecting or Fixed in these Releases and
enter 5.4(0.4).
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, Release 5.5 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.4
21
Cisco UCS Director
Obtaining Documentation and Submitting a Service Request
Cisco UCS Director Release Notes, Release 5.4
22
© 2015-2016
Cisco Systems, Inc. All rights reserved.