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

6.5

July 11, 2017

Published release notes for Cisco UCS Director, Release 6.5.

6.5(0.1)

October 9, 2017

Added information for Release 6.5(0.1). See following sections:

Bare Metal Agent Patch Release 6.5(0.2)

October 30, 2017

Added information for Bare Metal Agent Patch Release 6.5(0.2). See the following sections:

6.5(0.2)

January 2, 2018

Added information for Release 6.5(0.2). See the following sections:

6.5(0.3)

February 5, 2018

Added information for Release 6.5(0.3). See the following sections:

6.5(0.4)

September 9, 2019

Added information for Release 6.5(0.4). See the following sections:

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:

For HTML-5

  • Internet Explorer 8 or higher

  • Firefox 12 or higher (PC and Apple MAC)

  • Safari 6 or higher

  • Google Chrome 18 or higher

  • Opera 12 or higher (PC and Apple MAC)

For Classic View - all browsers must have Adobe Flash Player 11 plug-in or higher

  • Internet Explorer 8 or higher

  • Google Chrome 4.1 or higher

  • Firefox 3.5 or higher

  • Safari 4.0 or higher (for Apple Mac)

Minimum System Requirements for a Single-Node Setup on VMware vSphere

The minimum system requirements depend on the number of VMs you plan to manage. We recommend deploying a Cisco UCS Director VM on a local datastore with a minimum of 25 MBps I/O speed, or on an external datastore with a minimum of 50 MBps I/O speed.


Note

  • For optimal performance, reserve additional CPU and memory resources. We recommend that you reserve the following resources in addition to the minimum system requirements listed in the tables below: CPU resources of more than or equal to 3000MHz, and memory reservation of more than or equal to 1 GB. You should add more vCPUs if the Cisco UCS Director VM’s CPU usage is consistently high.

  • The minimum memory required for the inframgr service is automatically set during deployment. However, if you want to modify the memory for the inframgr service, edit the inframgr.env file available in the following location:

    /opt/infra/bin/inframgr.env

    In this file, update the "MEMORY_MAX" parameter to the value you want. After changing this parameter, restart the service for the changes to take effect. The default memory settings are MEMORY_MIN=6144 m and MEMORY_MAX=6144 m.


For information about minimum system requirements for a multi-node setup, see the Cisco UCS Director Multi-Node Installation and Configuration Guide.

Up to 2,000 VMs

If you plan to manage up to 2,000 VMs, the Cisco UCS Director environment must meet at least the minimum system requirements in the following table.

Table 1. Minimum System Requirements for up to 2,000 VMs
Element Minimum Supported Requirement

vCPU

4

Memory

16 GB

Primary Disk (Hard Disk 1)

100 GB

Secondary Disk (Hard Disk 2)

100 GB

Up to 5,000 VMs

If you plan to manage no more than 5,000 VMs, the Cisco UCS Director environment must meet at least the minimum system requirements and recommended configurations in the following tables.

Table 2. Minimum System Requirements for up to 5,000 VMs
Element Minimum Supported Requirement

vCPU

8

Memory

20 GB

Primary Disk (Hard Disk 1)

100 GB

Secondary Disk (Hard Disk 2)

100 GB

Table 3. Minimum Memory Configuration

Service

Recommended Configuration

File Location

Parameter

inframgr

8192m

/opt/infra/bin/ inframgr.env

MEMORY_MIN

inframgr

8192m

/opt/infra/bin/ inframgr.env

MEMORY_MAX

The following configuration must be updated in the /etc/my.cnf file.

Table 4. Minimum Database Configuration
Element Minimum Supported Configuration

thread_cache_size

100

max_connections

1000

innodb_lock_wait_timeout

100

query_cache_size

128 MB

innodb_buffer_pool_size

4 GB

max_connect_errors

10000

connect_timeout

20

innodb_read_io_threads

64

innodb_write_io_threads

64


Note

After updating and saving the /etc/my.cnf file, you need to restart the Cisco UCS Director database.


For optimal performance, ensure that you follow the below recommendations:

Table 5. Minimum Requirements

Element

Minimum Supported Requirement

vCPU

8 CPU cores

Memory

16 GB

IOPS

1200

Minimum System Requirements for a Multi-Node Setup

The minimum system requirements for a multi-node setup depends upon the number of VMs that need to be supported by Cisco UCS Director. We recommend deploying a Cisco UCS Director VM on a local datastore with a minimum of 25 Mbps I/O speed, or on an external datastore with a minimum of 50 Mbps I/O speed. The following table describes the number of VMs supported by each deployment size.

Deployment Size Number of VMs Supported

Small

5,000 to 10,000 VMs

Medium

10,000 to 20,000 VMs

Large

20,000 to 50,000 VMs

Minimum System Requirements for a Small Multi-Node Setup

The small multi-node setup supports from 5,000 to 10,000 VMs. We recommend that this deployment include the following nodes:

  • One primary node

  • Two service nodes

  • One inventory database

  • One monitoring database


Note

For optimal performance, reserve additional CPU and memory resources.


Minimum Requirements for each Primary Node and Service Node

Element Minimum Supported Requirement

vCPU

4

Memory

16 GB

Hard disk

100 GB

Minimum Requirements for the Inventory Database

Element Minimum Supported Requirement

vCPU

4

Memory

30 GB

Hard disk

100 GB (SSD Type Storage)

Minimum Requirements for the Monitoring Database

Element Minimum Supported Requirement

vCPU

4

Memory

30 GB

Hard disk

100 GB (SSD Type Storage)

Minimum Memory Configuration for Cisco UCS Director Services on Primary and Service Nodes

Service Recommended Configuration File Location Parameter

inframgr

8 GB

/opt/infra/bin/inframgr.env

MEMORY_MAX


Note

To modify the memory settings for the inframgr service, in the inframgr.env file, update the "MEMORY_MAX" parameter to the value you want. After changing this parameter, restart the service for the changes to take effect.


Minimum System Requirements for a Medium Multi-Node Setup

The medium multi-node setup supports between 10,000 and 20,000 VMs. We recommend that this deployment include the following nodes:

  • One primary node

  • Three service nodes

  • One inventory database

  • One monitoring database


Note

For optimal performance, reserve additional CPU and memory resources.


Minimum Requirements for each Primary Node and Service Node

Element Minimum Supported Requirement

vCPU

8

Memory

30 GB

Hard disk

100 GB

Minimum Resource Requirements for the Inventory Database

Element Minimum Supported Requirement

vCPU

8

Memory

60 GB

Hard disk

100 GB (SSD type storage)

Minimum Resource Requirements for the Monitoring Database

Element Minimum Supported Requirement

vCPU

8

Memory

60 GB

Hard disk

100 GB (SSD type storage)

Minimum Memory Configuration for Cisco UCS Director Services on Primary and Service Nodes

Service Recommended Configuration File Location Parameter

inframgr

12 GB

/opt/infra/bin/inframgr.env

MEMORY_MAX

To modify the memory settings for the inframgr service, in the inframgr.env file, update the "MEMORY_MAX" parameter to the value you want. After changing this parameter, restart the service for the changes to take effect.

Minimum Inventory Database Configuration

Component Minimum Supported Configuration

thread_cache_size

2000

max_connections

2000

innodb_lock_wait_timeout

100

query_cache_size

128 MB

innodb_buffer_pool_size

43,008 MB

max_connect_errors

10,000

connect_timeout

20

innodb_read_io_threads

64

innodb_write_io_threads

64

Make these changes in the /etc/my.cnf file.

Minimum Monitoring Database Configuration

Component Minimum Supported Configuration

thread_cache_size

2000

max_connections

2000

innodb_lock_wait_timeout

100

query_cache_size

128 MB

innodb_buffer_pool_size

43,008 MB

max_connect_errors

10,000

connect_timeout

20

innodb_read_io_threads

64

innodb_write_io_threads

64

Make these changes in the /etc/my.cnf file.

Minimum System Requirements for a Large Multi-Node Setup

The large multi-node setup supports between 20,000 and 50,000 VMs. We recommend that this deployment include the following nodes:

  • One primary node

  • Six service nodes

  • One inventory database

  • One monitoring database


Note

For optimal performance, reserve additional CPU and memory resources.


Minimum Resource Requirements for each Primary Node and Service Node

Element Minimum Supported Requirement

vCPU

8

Memory

60 GB

Hard disk

100 GB

Minimum Resource Requirements for the Inventory Database

Element Minimum Supported Requirement

vCPU

8

Memory

120 GB

Hard disk

200 GB (SSD type storage)

Minimum Resource Requirements for the Monitoring Database

Element Minimum Supported Requirement

vCPU

8

Memory

120 GB

Hard disk

600 GB (SSD type storage)

Minimum Memory Configuration for Cisco UCS Director Services on Primary and Service Nodes

Service Recommended Configuration File Location Parameter

inframgr

24 GB

/opt/infra/bin/inframgr.env

MEMORY_MAX

To modify the memory settings for the inframgr service, in the inframgr.env file, update the "MEMORY_MAX" parameter to the value you want. After changing this parameter, restart the service for the changes to take effect.

Minimum Inventory Database Configuration

Component Minimum Supported Configuration

thread_cache_size

4000

max_connections

4000

innodb_lock_wait_timeout

100

query_cache_size

128 MB

innodb_buffer_pool_size

86,016 MB

max_connect_errors

10,000

connect_timeout

20

innodb_read_io_threads

64

innodb_write_io_threads

64

Make these changes in the /etc/my.cnf file.

Minimum Monitoring Database Configuration

Component Minimum Supported Configuration

thread_cache_size

4000

max_connections

4000

innodb_lock_wait_timeout

100

query_cache_size

128 MB

innodb_buffer_pool_size

86,016 MB

max_connect_errors

10,000

connect_timeout

20

innodb_read_io_threads

64

innodb_write_io_threads

64

Make these changes in the /etc/my.cnf file.

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 6.5 is installed on two disks in the virtual machine (VM). The primary disk (Hard Disk 1) hosts the operating system and the Cisco UCS Director application. The secondary disk (Hard Disk 2) hosts the Cisco UCS Director database. For information on the system requirements for both these disks, see the Cisco UCS Director installation guide or the Cisco UCS Director Upgrade Guide.


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.


Supported Upgrade Paths for Cisco UCS Director, Release 6.5(0.4)


Important

Prior to upgrading to Cisco UCS Director Release 6.5(0.4), you must upgrade the Bare Metal Agent to version 6.5(0.2). See Supported Upgrade Paths for Bare Metal Agent Patch Release 6.5(0.2).



Important

Cisco UCS Director Release 6.5(0.4) includes fixes for security vulnerabilities reported in releases 6.5, 6.5(0.1), 6.5(0.2), and 6.5(0.3). Cisco UCS Director Releases 6.5, 6.5(0.1), 6.5(0.2), and 6.5(0.3) are no longer available for download. For information on the security vulnerabilities reported in releases 6.6 and 6.6(1.0), see the security advisories for CVE-2019-1938, CVE-2019-1935, CVE-2019-1974, CVE-2019-1937, CVE-2019-12634 and CVE-2019-1936 available at this link:

https://tools.cisco.com/security/center/publicationListing.x


The following are the supported upgrade paths to Cisco UCS Director, Release 6.5(0.4):

  • From Release 6.5(0.3) to Release 6.5(0.4)

  • From Release 6.5(0.2) to Release 6.5(0.4)

  • Fom Release 6.5(0.1) to Release 6.5(0.4)

  • Fom Release 6.5 to Release 6.5(0.4)

Supported Upgrade Paths from Release 6.0

The following are the supported upgrade paths to Cisco UCS Director, Release 6.5(0.4):

  • From Release 6.0(1.3) to Release 6.5(0.1) to Release 6.5(0.4)

  • From Release 6.0(1.2) to Release 6.5(0.0) to Release 6.5(0.4)

  • From Release 6.0(1.1) to Release 6.5(0.0) to Release 6.5(0.4)

  • From Release 6.0(1.0) to Release 6.5(0.0) to Release 6.5(0.4)

Supported Upgrade Paths for Bare Metal Agent Patch Release 6.5(0.2)

The following are the supported upgrade paths for the Bare Metal Agent Patch Release 6.5(0.2):

  • From Release 6.5(0.1) to Patch Release 6.5(0.2)

  • From Release 6.5 to Patch Release 6.5(0.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.


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 Cisco UCS Director Release 6.5(0.4)

Cisco UCS Director Release 6.5(0.4) includes fixes for security vulnerabilities reported in releases 6.5, 6.5(0.1), 6.5(0.2) and 6.5(0.3). Cisco UCS Director Release 6.5, 6.5(0.1), 6.5(0.2) and 6.5(0.3) are no longer available for download. For information on the security vulnerabilities reported in releases 6.5, 6.5(0.1), 6.5(0.2) and 6.5(0.3), see the security advisories for CVE-2019-1938, CVE-2019-1935, CVE-2019-1974, CVE-2019-1937, CVE-2019-12634 and CVE-2019-1936 available at this link:

https://tools.cisco.com/security/center/publicationListing.x

New and Changed Features in Cisco UCS Director Patch Release 6.5(0.2)

Collecting Diagnostics in a Multi-Node Setup

The Collect Diagnostics option is supported in a multi-node setup to collect information required for debugging purposes.

Documented in the Cisco UCS Director Shell Guide, Release 6.5.

Changes in the Administrator Portal User Interface

In Cisco UCS Director release 6.5 and release 6.5(0.1), the user interface has a + sign to expand or collapse a tabular field in which you could select one or more fields using a check box. In some instances, after selecting the fields, you need to click Validate to proceed.

With this patch release, the above behavior has been replaced with a Select button. The user interface now displays a Select button. When you click this button, a new screen displays a list of items. In this screen, select the items using the check boxes to proceed with completing the task.

Updated Support in Release 6.5(0.1)

This section provides a summary of the updated support in Release 6.5. For more information, see the Cisco UCS Director Compatibility Matrix, Release 6.5.

Cisco Application Centric Infrastructure Support

The following changes were added to Cisco Application Centric Infrastructure support in this release:

  • Cisco Application Centric Infrastructure: Release 3.0

Microsoft Hyper-V Versions

The following changes were added to Microsoft Hyper-V version support in this release:

  • Microsoft System Center Virtual Machine Manager (SCVMM) 2016 Rollup 2

  • Microsoft System Center Virtual Machine Manager (SCVMM) 2016 Rollup 3

VMware vSphere Versions

The following changes were added to VMware vSphere support in this release:

  • Support for VMware vSphere vCenter Server 6.5 Update 1

  • Support for VMware Site Recovery Manager version 6.1.

New and Changed Features in Release 6.5

New Administrative Portal

This release introduces a new and improved HTML-5 based administrative portal that replaces the previously available user interface. When you log in to Cisco UCS Director, by default, the new user interface is displayed. The earlier version of the interface, now referred to as the classic view, is still available, but will be removed in a subsequent release. The following are some of the key features of the new interface:

  • Change in the navigation menu—In earlier releases, you could access pages using the main menu bar. The main menu bar is no longer visible, and is now available as a side bar. You can use your mouse or the cursor to hover over an option on the side navigation bar, and then click any of the menu options.

  • Absence of user interface labels—The user interface no longer includes labels for actions such as Add, Edit, Delete, Export, Filter, and so on. These actions are represented only with icons. If you use your mouse or cursor to hover over the icon, the label displays the action you can perform using that icon.

  • Using Dashboard to Access Detailed Reports—If you have enabled the Dashboard, then it is the first page that you see when you log in to Cisco UCS Director. Typically, you can use this dashboard to add important or frequently accessed report widgets. Now, you can click any of the reports that are displayed on the Dashboard, and immediately access the page in the user interface where more detailed information is displayed

  • Enhancements to reporting capabilities—You can add individual pie charts and bar graph reports to the Dashboard or you can export these reports in PDF, CSV, or KLS formats. In addition, you can search for a report from the Dashboard.

  • Context-sensitive Online Help—If you click the Help icon in the user interface, the online help system displays information on the screen that you currently are accessing.

  • Customized Icons for management—Cisco UCS Director supports customization and management of catalog icons, action-related icons, and status-related icons. Each icon set in the system contains several images that are available by default. You can change the icons that are displayed for either the catalogs, actions or status. You can either upload a new image and set it as the icon, or you can choose a different icon from the set of system-provided icons.

  • ReportMeta data RestAPI URL in HTML-5 is encoded—You can use this URL as is. If you want to decode this URL, then you can use any URL decoder available online.

  • After upgrading from prior versions to Release 6.5, the administrator must update the approval email templates with the HTML-5 URL for approval. If this change is not made, the templates will re-direct to the classic view page. The change in the email template must look like the following:

    out.println("<a href='"+ "https" + "://" + request.getDataObject().getSettings().getCuicIpAddress() + "/app/ux/index.html?filter_entryId_"+ request.getDataObject().getEntryId()+"'>link</a>");


Important

The HTML-5 user interface does not support themes or the topology view. If you select a theme in the HTML-5 user interface, it is applicable for the classic view user interface also.


Documented in the Cisco UCS Director Administration Guide.

Changes in Configuring a Bare Metal Server Provisioning Policy

The following are changes made in this release:

  • The scope of the policy can be set to include either servers or server pools.

  • While using the policy to configure servers, you can allow for the user to select specific servers.

  • You can now select one or more Windows OS images for the server.

  • You can select a static IP pool policy to assign an IP address for the server.

  • You can select a host name validation policy to validate the server host name for the bare metal server.

In addition, after you create a bare metal server provisioning policy, you can validate it from the user interface, and determine if there are any issues with the policy.

Documented in the Cisco UCS Director Administration Guide.

Changes to the Stack View report for a VM

With this release, the Stack View Report for a VM has the following changes:

  • If there are multiple devices in the report, you can use the drop-down list to select a specific device.

  • You can choose to view additional details of a device in the report.

Documented in the Cisco UCS Director Administration Guide.

Enhancements to Managing Users

This release include the following changes to managing users:

  • Introduced the All Users Login History option, using which you can review login-related information for all users in the system.

  • Introduction of session management capability for users—As an administrator, you can configure the maximum number of concurrent sessions for users in the system.

  • While adding a user role, you can enable or disable the availability of roles.

Documented in the Cisco UCS Director Administration Guide.

Database Support on a Non-Root Disk

When you install or upgrade to Cisco UCS Director, Release 6.5, the database is now installed on a secondary, non-root disk in the virtual machine (VM). This secondary disk is automatically created when you install Cisco UCS Director, Release 6.5. When upgrading, you must first create a secondary disk that meets the requirements documented in the Cisco UCS Director Upgrade Guide.

Documented in the Cisco UCS Director Installation on VMware vSphere and Microsoft Hyper-V and the Cisco UCS Director Upgrade Guide.

ASA/ASAv Configuration through APIC Function Profiles and Service Graphs

For systems that include network management through ACI, you can now configure NAT, static route, and IP address parameters in an APIC function profile. You can then add this function profile to an L4-L7 service graph.

Documented in the Cisco UCS Director APIC Management Guide.

Support for NetApp All Flash FAS (AFF)

Cisco UCS Director now provides support for NetApp All Flash FAS (AFF) with ONTAP 9.0 and 9.1. In addition,

Support for EMC Unity

Cisco UCS Director now provides support for orchestration automation, management, monitoring, and reporting for supported EMC Unity storage arrays.

Enhancements to Cisco UCS Manager Support

The following support was added for Cisco UCS Director for Cisco UCS Manager in this release:

  • More than one Cisco UCS Manager account can be added for a pod, such as FlexPod, Vblock, or VSPEX.

Documented in the Cisco UCS Director Management Guide for Cisco UCS Manager.

Server License Tracking for Cisco UCS Central

In previous releases, Cisco UCS Director tracked the number of servers against the available licenses only when they were managed through Cisco UCS Manager . Starting with release 6.5, Cisco UCS Director also tracks the available licenses when the servers are managed through Cisco UCS Central . A warning message informs you when you have exceeded the limit. However, you can continue to manage these servers until the grace period ends.

In addition, now you can Manage and Unmanage the servers directly from Cisco UCS Central account by accessing the Discovered Servers under All UCS Domains. Make sure that you choose the Selected Servers option under server management, while adding a Cisco UCS Central account.

Documented in the Cisco UCS Director Management Guide for Cisco UCS Central.

Enhancements to PowerShell Agent

This release introduces the following support for PowerShell Agent:

  • A new Execute Native PowerShell Command Task. It helps you execute PowerShell scripts locally on the PowerShell Agent server. This task overcomes the limitation where some of the third- party cmdlets are not executable in remote sessions.

  • The Execute PowerShell Command Task now provides an option to choose from various authentication mechanisms other than the default.

Documented in the Cisco UCS Director PowerShell Agent Installation and Configuration Guide.

Enhancements Cisco UCS Director Express for Big Data in Cisco UCS Director

The enhancements to Cisco UCS Director Express for Big Data in Cisco UCS Director include the following:

  • Support for CentOS 7.2 for deploying Big Data clusters

  • Support for Spark services for Cloudera and Hortonworks clusters.

  • Support Splunk 6.4.2, 6.4.3, and 6.5 cluster versions.

  • Introduced an option to enable security for the MapR clusters.

  • Introduced an option for service end users to create Big Data clusters using Advanced Catalog.

  • Support for Kafka services for Cloudera and Hortonworks clusters.

  • Support for IBM Big Insights 4.2 cluster version.

  • Introduced an option to enable high availability support for Hortonworks cluster.

  • Introduced an option to create Hadoop or Splunk cluster with flexible network configuration.

  • Introduced an option to customize the Service Role Entry template for Splunk clusters.

Documented in the Cisco UCS Director Express for Big Data Management Guide.

Enhancements to Bare Metal Agent Installation and Configuration

In this release, the following features and enhancements have been introduced for managing and configuring BMA accounts:

  • An option to upload the OS images to a Bare Metal Agents account and provision the OS images.

  • An option to create a PXE boot request by choosing Administration > Physical Accounts and clicking Bare Metal Agents.

  • Support for Windows Hyper-V 2016 Baremetal OS installation

  • Support for vSphere/ESXi 6.5 Baremetal OS installation

  • Support for multi-Windows version deployment from single BMA—Bare Metal Agent adopts the Microsoft Windows PXE boot process, which maintains a single WinPE for supporting multiple windows versions.

  • Support for viewing network interface details for a Bare Metal Agent account.

  • Additional fields for setting up a PXE boot task for Microsoft Windows. The new fields are Server IP Configuration Type, Server Address, Server Net Mask, and Server Gateway.

  • Support for iPXE-BIOS and iPXE-UEFI network boot firmware.

  • Support for viewing, editing, cloning, and swapping the OS configuration file details.

Documented in the Cisco UCS Director Bare Metal Agent Installation and Configuration Guide.

Enhancements to the End User Portal

In this release, the menu bar is moved from the top of the landing page to the left side.

Documented in the Cisco UCS Director End User Portal Guide.

Enhancements to Custom Tasks

This release introduces the following features:

  • A Java editor for the custom task script, which validates the CloupiaScript code and shows an error message with a solution.

    Documented in the Cisco UCS Director Custom Task Getting Started Guide.

  • A CustomTask Script Analyzer—Analyses the classes and methods of the Cloupiascripts in a custom task, and provides an analysis report that includes custom task status (for example, Executed, Not executed), used methods list, and incompatible methods list.

    Documented in the Cisco UCS Director Upgrade Guide.

Enhancements to Open Automation

This release introduces the following supports:

  • REST API support—The Open Automation compute framework provides REST API support for adaptor- and listener-based APIs

    Documented in the Cisco UCS Director Open Automation Cookbook.

  • Input validation using controllers—Support use of Controller classes to validate input to REST APIs.

    Documented in the Cisco UCS Director Open Automation Cookbook.

  • Icon support— Includes action icons for the UI when you deploy an Open Automation module.

    Documented in the Cisco UCS Director Open Automation Cookbook.

  • Enable new modules without restarting— Activate newly deployed modules without restarting Cisco UCS Director.

    Documented in the Cisco UCS Director Open Automation Cookbook.

  • Troubleshooting solutions—Provides solutions for problems that you may encounter while exposing the REST API support for Open Automation modules in Cisco UCS Director

    Documented in the Cisco UCS Director Open Automation Troubleshooting Guide.

Enhancements to SCVMM and VMware Virtualization

This release introduces the following features:

  • Support for VMware vCenter 6.5

  • Support for SCVMM (Hyper-V) 2016 and Windows 2016 Guest OS

  • VMware Content Library Support—This release introduces support for discovery and viewing reports for VMware content library templates. You can also provision VMs using content library templates.

    Documented in the Cisco UCS Director VMware vSphere Management Guide.

  • VMRC HTML5 Console—This release introduces the ability to launch a VMRC HTML5 console that is web browser and plug-in independent.


    Note

    The HTML5 VMRC SDK is supported with VMware vCenter version 6.0 or later.

    The VMRC HTML5 console will not launch if VNC is enabled on the virtual machine. For information on how to solve this problem, see the Cisco UCS Director Troubleshooting Guide.


    Documented in the Cisco UCS Director VMware vSphere Management Guide.

  • VIX Task Enhancements—The Execute VIX Scripts task supports the option to use Guest Operation APIs instead of VIX APIs.

    Documented in the Cisco UCS Director VM Guest Customization Guide.

  • Guest Operations Task—This release introduces the Guest Operations task that supports existing VIX functionality with the ability to upload and execute files on the guest.

    Documented in the Cisco UCS Director VM Guest Customization Guide.

  • Enhancements to VNC Console Management—This release introduces the Launch VNC Console action, to launch the VNC console independent of the Launch VM Client action. You can also enable a task to automatically unconfigure the VNC console.

    Documented in the Cisco UCS Director Administration Guide.

  • VM name and hostname uniqueness check—This release introduces the ability to disable the VM name and hostname uniqueness validation check.

    Documented in the Cisco UCS Director Administration Guide.

  • Unmount ISO image from CD or DVD drive—This release introduces the ability to unmount an ISO image already attached to a CD or DVD drive on the VM.

    Documented in the Cisco UCS Director Administration Guide.

  • Configure cores per socket during VM provisioning—This release introduces the ability to define cores per socket in the computing policy for use when creating a service request, deploying a VM, cloning a VM, or provisioning a VM using an orchestration workflow.

    Documented in the Cisco UCS Director Administration Guide and the Cisco UCS Director VMware vSphere Management Guide.

  • VMkernel NIC enhancements—This release introduces support for VMware vMotion and traffic options supported by VMware vSphere on a VMkernel NIC.

    Documented in the Cisco UCS Director VMware vSphere Management Guide.

  • VM deployment enhancements—This release introduces the ability to deploy a new VM from a template listed in the images report.

    Documented in the Cisco UCS Director VMware vSphere Management Guide.

  • Credential policy enhancements—This release introduces the ability specify a credential policy to use when adding a VMware cloud.

    Documented in the Cisco UCS Director VMware vSphere Management Guide.

  • VM migration enhancements—This release introduces the ability to migrate a VM between datacenters and modify the VM port group within a VMware vCenter server.

    Documented in the Cisco UCS Director VMware vSphere Management Guide.

Enhancement to Orchestration

This release introduces the following features:

  • Workflow Schedule Management—You can schedule the same workflow to execute multiple times. Previously, only one schedule could exist per workflow.

  • Resource Locking— You can lock and unlock resources in a workflow using special tasks that acquire and release named semaphores.

  • File Upload through Workflow Input—You can upload files to Cisco UCS Director using a workflow task using a special input type, fileUpload.

  • Enhancements to Workflow Designer—The HTML5 Workflow Designer has several new features that ease navigation, such as:

    • Zoom controls to reduce and enlarge your view of the workflow.

    • A Fit to Window action that scales the workflow to your screen with a single click

    • A Navigator to pan the view window within the work area

    The Workflow Designer now also displays counts of conditional, custom, and total tasks.

  • Header-based Search for Workflows—You can search for and launch workflow in the Workflow Designer from anywhere in Cisco UCS Director.

Documented in the Cisco UCS Director Orchestration Guide.

Enhancements to REST API

This release introduces the following features:

  • Requesting JSON API using HTTP/HTTPs POST—Provided instructions on how to pass the JSON API request using the HTTP POST method.

  • REST API support for managing service request—Added the following API: userAPIGetServiceRequestLogEntries

    Documented in the Cisco UCS Director REST API Cookbook.

  • Access XML REST API—Provides a list of APIs to invoke XML REST API to perform basic CRUD operations.

    Documented in the Cisco UCS Director CloupiaScript Cookbook.

  • Role-based access for XML-based version 2 APIs with the URL context of /api/v2.

    Service end users cannot execute the GET Operations with these APIs. Also, service end users can perform the create, update and delete operations using the REST APIs only if they can perform the same operation using the graphical user interface of Cisco UCS Director. If these users cannot perform a create, update or delete operation in the user interface, then they cannot perform these actions using the REST APIs either.

Enhancements to Managing Application Containers

This release introduces the following features:

  • Use Linked Clone in VM—Provides support to deploy linked VMs which are two or more related VMs that share virtual disk storage.

  • Provision a VM using Content Library Template—Provides support to choose a VM template from the content library VM templates for VM provisioning.

Documented in the Cisco UCS Director Application Container Guide.

Enhancements to Working with Custom Tasks

This release introduces the following features:

  • Using API Operations from CloupiaScript—Provides the guidelines for using API operations from CloupiaScript.

  • Java editor for the custom task script—Validates the CloupiaScript code and shows an error message with a solution.

  • Access output of a previous task—Provides two ways to use outputs of a previous tasks in other tasks in a workflow.

  • GitHub integration with custom tasks—Enables you to download custom task code from files in a GitHub repository to custom tasks that you create. Cisco UCS Director supports only GitHub (github.com or an enterprise GitHub instance). It does not support other Git hosting services such as BitBucket, GitLab, Perforce, or Codebase.

Documented in the Cisco UCS Director Custom Task Getting Started Guide.

Enhancements to the Cisco UCS Director Shell Interface

This release introduces the following features:

  • Support for SFTP and SCP protocols for database backup and restore.

  • Introduced an option to enable and disable the HTTPS access.

  • Support for secure options like SFTP and SCP while applying a patch to Cisco UCS Director.

  • Support for resetting MYSQL user password in a Multi-Node setup and Standalone setup.

  • Support for digital signing of software images.

  • Introduced an option to limit the number of concurrent sessions per user by terminating the active GUI sessions.

Documented in the Cisco UCS Director Shell Guide.

Modified Workflow Name

In this release, the Create and Add IBM LUN as NFS Datastore has been modified to Add new NFS datastore to ESXi on V7000.

Updated Support in Release 6.5

This section provides a summary of the updated support in Release 6.5. For more information, see the Cisco UCS Director Compatibility Matrix, Release 6.5.

Cisco Server Support

The following changes were added to Cisco server support in this release:

  • Cisco UCS Manager: 3.1(3*) and 3.2(1)

  • Cisco UCS Central: 2.0(1*)

  • Cisco UCS C-Series Rack Servers (Standalone through Rack accounts): Cisco IMC Supervisor, Release 2.2

  • Cisco UCS E-Series Servers (Standalone through Rack accounts): Cisco IMC Supervisor, Release 2.2

Cisco Application Centric Infrastructure Support

The following changes were added to Cisco Application Centric Infrastructure support in this release:

  • Cisco Application Centric Infrastructure: Release 2.2(2f*)

NetApp Storage Support

The following changes were added to NetApp storage support in this release:

  • NetApp AFF (ALL Flash FAS-ONTAP): 9.0 and 9.1

EMC Storage Support

The following changes were added to EMC storage support in this release:

  • EMC Unity: UnityOS: 4.1.1.91.38882

Hyper-Converged Infrastructure Support

The following support was added for Cisco HyperFlex System in this release:

  • Cisco HX-Series Server: HX220C-M4, HX240C-M4

  • Cisco HX Data Platform: Release 1.8(1c) and Release 2.5(1a)

Deprecation Announcement

Deprecation Announcement for Cisco UCS Invicta

The following Cisco UCS Invicta Series Storage accounts have been deprecated:

  • Cisco UCS Invicta Appliance

  • Cisco UCS Invicta Scaling System

You can no longer create a new Cisco UCS Invicta account. The Cisco UCS Director Invicta Series Management Guide will also no longer be updated.


Note

For End-of-Life milestones and dates, see the End-of-Sale and End-of-Life Announcement for the Cisco UCS Invicta Series.


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 in Release 6.5

You can find detailed information about all open bugs in Release 6.5 through the open bug search for Release 6.5. This search uses the following parameters:

Field

Parameter

Product drop-down list

Choose Series/Model and enter Cisco UCS Director.

Releases drop-down list

Choose Affecting or Fixed in these Releases and enter 6.5(0.0).

Filter

Choose Open from the Status drop-down list.

Open Bugs in Patch Release 6.5(0.1)

There are no open bugs in patch release 6.5(0.1).

Open Bugs in Bare Metal Agent Patch Release 6.5(0.2)

There are no open bugs in the Bare Metal Agent (BMA) patch release 6.5(0.2).

Open Bugs in Patch Release 6.5(0.2)

You can find detailed information about all open bugs in Release 6.5(0.2) through the open bug search for Release 6.5(0.2). This search uses the following parameters:

Field

Parameter

Product drop-down list

Choose Series/Model and enter Cisco UCS Director.

Releases drop-down list

Choose Affecting or Fixed in these Releases and enter 6.5(0.2).

Filter

Choose Open from the Status drop-down list.

Open Bugs in Patch Release 6.5(0.3)

There are no open bugs in patch release 6.5(0.3).

Open Bugs in Release 6.5(0.4)

You can find detailed information about all open bugs in Release 6.5(0.4) through the open bug search for Release 6.5(0.4). This search uses the following parameters:

Field

Parameter

Product drop-down list

Choose Series/Model and enter Cisco UCS Director.

Releases drop-down list

Choose Affecting or Fixed in these Releases and enter 6.5(0.4).

Filter

Choose Open from the Status drop-down list.

Resolved Bugs in Release 6.5

You can find detailed information about all resolved bugs in Release 6.5 through the resolved bug search query for Release 6.5. This search uses the following parameters:

Field

Parameter

Product drop-down list

Choose Series/Model and enter Cisco UCS Director.

Releases drop-down list

Choose Affecting or Fixed in these Releases and enter 6.5(0.0).

Filter

Choose Fixed from the Status drop-down list.

Resolved Bugs in Patch Release 6.5(0.1)

You can find detailed information about all resolved bugs in patch release 6.5(0.1) through the resolved bug search query for Patch Release 6.5(0.1). This search uses the following parameters:

Field

Parameter

Product drop-down list

Choose Series/Model and enter Cisco UCS Director.

Releases drop-down list

Choose Affecting or Fixed in these Releases and enter 6.5(0.1).

Filter

Choose Fixed from the Status drop-down list.

Resolved Bugs in Bare Metal Agent Patch Release 6.5(0.2)

You can find detailed information about all resolved bugs in the Bare Metal Agent (BMA) patch release 6.5(0.2) through the resolved bug search query for Patch Release 6.5(0.2). This search uses the following parameters:

Field

Parameter

Product drop-down list

Choose Series/Model and enter Cisco UCS Director.

Releases drop-down list

Choose Affecting or Fixed in these Releases and enter 6.5(0.2).

Filter

Choose Fixed from the Status drop-down list.

Resolved Bugs in Patch Release 6.5(0.2)

You can find detailed information about all resolved bugs in the Cisco UCS Director patch release 6.5(0.2) through the resolved bug search query for Patch Release 6.5(0.2). This search uses the following parameters:

Field

Description

Product drop-down list

Choose Series/Model and enter Cisco UCS Director.

Releases drop-down list

Choose Affecting or Fixed in these Releases and enter 6.5(0.2)

Filter

Choose Fixed from the Status drop-down list.

Resolved Bugs in Patch Release 6.5(0.3)

You can find detailed information about all resolved bugs in patch release 6.5(0.3) through the resolved bug search query for Patch Release 6.5(0.3). This search uses the following parameters:

Field

Parameter

Product drop-down list

Choose Series/Model and enter Cisco UCS Director.

Releases drop-down list

Choose Affecting or Fixed in these Releases and enter 6.5(0.3).

Filter

Choose Fixed from the Status drop-down list.

Resolved Bugs in Release 6.5(0.4)

You can find detailed information about all resolved bugs in patch release 6.5(0.4) through the resolved bug search for Release 6.5(0.4). This search uses the following parameters:

Field

Parameter

Product drop-down list

Choose Series/Model and enter Cisco UCS Director.

Releases drop-down list

Choose Affecting or Fixed in these Releases and enter 6.5(0.4).

Filter

Choose Fixed from the Status drop-down list.