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.

Installing Cisco UCS Director Powershell Agent and the Powershell Console

Installing a newer version of the PowerShell Agent requires that you uninstall the older version first. To remove the older version of PowerShell Agent, stop the Cisco PSA Service first and then uninstall the agent. For instructions on installing, see Cisco UCS Director PowerShell Agent Installation and Configuration Guide, Release 6.7.

Before installing Cisco UCS Director Powershell Console 6.7, you must uninstall the earlier version of the Powershell Console from the system. To install the latest version, download and double-click the UCSDirector_PSC_6.7.2.0.exe file.

Support for Cisco ACI Multi-Site Controller

This release of Cisco UCS Director introduces a new connector for creating and managing ACI Multi-Site Controller accounts. As an administrator, you can create ACI Multi-Site Controller accounts, and perform actions such as adding, editing and deleting APIC controller accounts, and assigning accounts to a pod. You can manage the user, site, tenant, and schema of these ACI Multi-Site Controller accounts.

Documented in the Cisco UCS Director APIC Management Guide.

Cisco ACI Multi-Site Use Cases on Cisco UCS Director

The basic use cases of implementing Cisco ACI Multi-Site with Cisco UCS Director is documented in the Cisco ACI Multi-Site Use Cases on Cisco UCS Director guide. The guide captures the prerequisites and the configuration of objects on ACI Multi-Site controller and APIC controller to implement the use case.

Dynamic Input for Orchestration Workflows

This release provides greater control of user input to Orchestration Workflows. You can define workflow input processing rules that make display of some user inputs contingent on other input values. This feature is also called "Dynamic Forms" or "Progressive Disclosure."

Documented in the Cisco UCS Director Orchestration Guide.

See sample workflows included in the Examples folder available from the Orchestration > Workflows screen.

Introduction of the Device Connector Tab

The Device Connector tab connects Cisco UCS Director to Cisco Intersight, the cloud-hosted server management system. It enables Cisco UCS Director to be managed and monitored through Cisco Intersight.

To register a device with Cisco Intersight in the cloud, you must do the following:

1. Configure the device connector proxy settings—Required only if you have proxy configuration enabled.

2. Use the device serial number and security code to validate your access to the device from Cisco Intersight and claim the device.

After the device connector is configured and the device is claimed, you can launch the user interface of Cisco UCS Director from Cisco Intersight.

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

Support for Launching Cisco UCS Director From Cisco Intersight

After the device connector is configured and the device is claimed, you can launch the Cisco UCS Director user interface from Cisco Intersight.

Important

If any of the Cisco UCS Director services are down, you cannot launch Cisco UCS Director from Cisco Intersight. A message stating that there is no service is displayed.

Although you can launch Cisco UCS Director from Cisco Intersight, following are some of the restrictions that you need to be aware of:

• You cannot edit a user profile.

• You cannot perform any import and export actions.

• The main menu and the Dashboard are disabled.

• The Device Connector tab is not visible.

• You cannot perform any launch actions.

• You cannot upgrade connector packs.

• You cannot generate any summary reports.

• The user name is displayed as Cisco Intersight user when you launch Cisco UCS Director.

• All service requests and audit log details are logged as Admin user.

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

Introduction of Connector Packs

This release introduces connector packs that are delivered as .zip files that help you perform connector level upgrade in Cisco UCS Director independently, without impacting any other connectors in the system. When a system running Cisco UCS Director is claimed in Cisco Intersight, as a system administrator, you can view a list of recent connector packs versions that are available. You can either upgrade all or specific connector pack versions on the system using the graphical user interface of Cisco UCS Director.

Important

Upgrading connector packs is not available in a multi-node setup.

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

Support for SPICE Console for VMs in KVM Accounts

This release introduces support for launching the Simple Protocol for Independent Computing Environments (SPICE) console for VMs within a Red Hat KVM account.

Documented in the Cisco UCS Director Red Hat Enterprise KVM Management Guide.

HyperFlex Replication Support Using Cisco UCS Director

In Cisco UCS Director, you can protect VMs for disaster recovery by scheduling periodic snapshots between two HyperFlex (HX) clusters. You can protect individual VMs and you can create protection groups with schedules and policies that apply to every VM in the group.

Documented in the Cisco UCS Director HyperFlex Systems Management Guide.

Resource Limits Support for Hyper-V Provisioning

This release of Cisco UCS Director introduces support for configuring resource limits for provisioning Hyper-V systems.

Documented in the Cisco UCS Director Administration Guide.

Enhanced Scheduling Capabilities for System Tasks

This release of Cisco UCS Director introduces an option to schedule a system task with a Fixed Delay option. This option enables a fixed time delay between consecutive executions of a system task.

By default, most system tasks are configured with the Fixed Delay option. However, there are a few tasks that are configured with the Fixed Rate option.

This release also introduces the capability to configure a customized frequency for the system tasks.

Documented in the Cisco UCS Director Administration Guide.

Pre-Provisioning and Post-Provisioning Workflow Support for Standard Catalogs

This release of Cisco UCS Director introduces support for configuring standard catalogs to execute a pre-provisioning workflow in addition to the post-provisioning workflow. With this support, you can run tasks to determine if all prerequisites have been met to provision a VM, such as availability of IP addresses, or creating VLAN on external switch. After provisioning a VM, you can run tasks to perform additional procedures such as set user permissions, add VM directories or configure vNICs.

With the introduction of pre-provisioning support, the input type for tasks "Create Standard Catalog" and "Modify Standard Catalog" has changed from Workflow to Compound Workflow. If you configured workflows with these tasks in earlier releases of Cisco UCS Director with the task input configured as Workflow, then after upgrading to Release 6.6, the workflow validation fails. You must manually edit the user input for the workflows, and change the Task Input type to Compound Workflow. To determine the workflows that are impacted, run the following command:

/opt/infra/sysmgr/getStandardCatalogTaskWorkflows.sh

This command lists the workflow name, the version, and the name of the folder that contains the workflow.

This input type change does not impact existing Catalogs or new Catalogs. It only affects workflows that use the two tasks mentioned above.

Documented in the Cisco UCS Director Administration Guide and the Cisco UCS Director Orchestration Guide.

Introduction of the Global Dashlet Option

In this release of Cisco UCS Director, the Global Dashlet option has been introduced. Administrators can use this option to configure the number of dashlets that users within all groups can view when they login to the End User Portal.

Documented in the Cisco UCS Director Administration Guide.

Support for Selecting User Groups as Approvers for VDC Actions

From this release onwards, while adding, editing or cloning a virtual data center, you can either choose user groups or individual users as the first and second level approvers. If you choose User Groups as approvers, you can also specify if the task requires approval from all users of the groups.

Documented in the Cisco UCS Director Administration Guide.

Support for Manually Adding Search-based Organizational Units (OUs)

This release of Cisco UCS Director introduces a new option to provide OUs manually to the system and to synchronize user records with the LDAP server. In addition, you can enable or disable the manual search based OU integration at any point in time.

Documented in the Cisco UCS Director Administration Guide.

Deprecated Support for Verisign Identity Protection (VIP) Authentication

From this release onwards, configuring an authentication preference using the Verisign Identity Protection (VIP) Authentication Service is no longer supported. This option is currently displayed in the user interface of the administrative portal, and will be removed in a subsequent release.

Classic View No Longer Available

From this release onwards, the Classic view of the user interface is no longer available. In release 6.5, administrators could set the system to launch the Classic View user interface for subsequent login sessions. Also, administrators could specify this setting for login sessions of other users as well. These options have now been removed.

Documented in the Cisco UCS Director Administration Guide.

Support for Fabric Extender (FEX)

This release supports creating FEX profiles to configure FEX interfaces and to define policies for host-facing ports.

Documented in the Cisco UCS Director APIC Management Guide.

Write and Execute CloupiaScript Permissions

This release of Cisco UCS Director introduces the Write CloupiaScript and Execute CloupiaScript permissions to control user access to CloupiaScript. By default, the user will have permission to write and execute custom tasks using CloupiaScript.

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

Execute Generic API task

This release of Cisco UCS Director provides the Execute Generic API task that helps you to define parameters to interact with REST API based systems easily. This task handles any JSON/XML interactions automatically and generates task output as needed. This approach helps you to extend the functionality of Cisco UCS Director.

Documented in the Cisco UCS Director Fundamentals Guide.

You can find instructions on working with the Generic API task in the Working with Generic API Task of Cisco UCS Director guide.

Custom Input Validation

This release of Cisco UCS Director provides an option to validate any input at runtime using a customer-provided script. This customer-provided script (written in bash, javascript. python, or perl) can validate user inputs and flag errors before submitting the service request.

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

See sample workflows included in the Examples folder available from the Orchestration > Workflows screen.

REST API support for managing import and export of artifacts

This release of Cisco UCS Director provides REST API support for managing import and export of artifacts. You can export and import workflows, custom tasks, script modules, and activities in Cisco UCS Director.

Documented in the Cisco UCS Director REST API Cookbook.

Support for adding Windows license for virtual machine (VM)

This release of Cisco UCS Director provides support to add Windows licenses that you want to use for VM while creating an application container template for fenced virtual container, adding an application profile, and adding VMs.

Documented in the Cisco UCS Director Application Container Guide.

Summary Screen Enhancements for Create Service Request Action

While creating a service request using an advanced catalog, the Summary screen displays information on all the values that you entered while creating the service request.

While provisioning a VM using an advanced catalog, the Summary screen displays the approximate service request cost estimate.

Documented in the Cisco UCS Director Administration Guide.

Auto-Populate Input Values from a Previous Service Request

When re-executing an Orchestration Workflow, you can optionally copy the workflow input values from a previous service request. You choose from a list of previous service requests running the same workflow.

Documented in the Cisco UCS Director Orchestration Guide.

Support for Virtual SAN Cluster Configuration through Cisco UCS Central

This release of Cisco UCS Director introduces support for VSAN cluster configuration on servers managed through Cisco UCS Central accounts. You can use a workflow to configure servers managed through the Cisco UCS Central account, install ESXi on an SD on these servers, add them to the vCenter and create a VSAN cluster with these hosts.

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

Introduction of Scoped Inventory Tasks for Cisco UCS Central Accounts

This release of Cisco UCS Director introduces the following workflow tasks for Cisco UCS Central accounts:

• Request Inventory Collection by DN

• Request Inventory Collection by Resource

These tasks support running an inventory process on a specific resource type, such as service profile, or on a specific object running as part of the workflow. With the addition of these tasks, the inventory process does not affect the parallel execution of other service requests for the same Cisco UCS Central account.

Documented in the Cisco UCS Director UCS Central Management Guide.

Support for Firmware Upgrade for Standalone C-Series Server

This release of Cisco UCS Director introduces the ability to automate the firmware upgrade of the Standalone C-series server using a workflow task.

Documented in the Cisco UCS Director UCS Central Management Guide.

Support for External DHCP Servers with Cisco Bare Metal Agent

This release of Cisco UCS Director and Cisco Bare Metal Agent have been qualified with using external DHCP server for OS deployments.

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

Support for Encrypting the Root Password in the Kickstart File

This release of Cisco UCS Director introduces support for encrypting the root password in the ks.cfg file.

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

Support for Big Data Cluster Versions

This release introduces support for Cloudera 5.13.1 and 5.14.0, MapR 5.2.2 and 6.0.0, Hortonworks 2.6.3 and 2.6.4, and Splunk 7.

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

Support for Customizing the Port Number

This release introduces support for specifying a custom port number while adding a Hadoop or Splunk derived account.

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

Support for Splunk Multi-Site Cluster Management

This release introduces an option to create a new multi-site Splunk cluster or migrate an existing Splunk cluster to a multi-site Splunk cluster.

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

Support for NFS Datastore Creation for all Storage Connectors

This release of Cisco UCS Director introduces support for creating and managing the NFS datastore. You can create and delete NAS client networks, allocate IP addresses to a NAS client network, and deallocate IP addresses from a NAS client network.

Documented in the Cisco UCS Director Management Guide for IBM Storwize.

Enhancements to the Cisco UCS Director Shell Interface

This release of Cisco UCS Director introduces support for regenerating device connector REST API access key, granting or denying client access to MySQL port, and cleaning up patch files or directories. This release also introduces an option to limit the number of days the self-signed certificate will be valid.

Documented in the Cisco UCS Director Shell Guide.

Orchestrate VM Provisioning Without VDC

The Orchestration Task Library contains tasks to generically provision VMware or HyperV virtual machines without a virtual data center (VDC) and its associated policies.

The new orchestration tasks are:

• VMware - Provision a VM without VDC

• VMware - Provision a Blank VM

• VMware - Guest Customization

• VMware - Get Snapshots

Documented in the Cisco UCS Director Task Library.

New, Modified, and Removed Workflows and Tasks

Following are the new workflows introduced in this release:

VMware-related workflows

• Create Virtual SAN Cluster from Baremetal using UCSC

• Install ESXI on SD Card for Virtual SAN using UCSC

• Install ESXI on SD Card using UCSC

Following are the new tasks introduced in this release:

Cisco UCS-related tasks

• Create UCS Disk Group Policy

• Delete UCS Disk Group Policy

• Create UCS Scrub Policy

• Delete UCS Scrub Policy

• Add UCS Service Profile Template

• Configure UCS Server Port

Rack Server-related tasks

• Add Firmware Image Profile

• Run Rack Server Firmware Upgrade

• Monitor Rack Server Firmware Upgrade

• Delete Firmware Image Profile

The following task has been enhanced in this release:

• Create UCS Boot Policy

The following obsoleted task has been removed from this release:

• VM Provision

Deprecated Support for Workflow Templates

Workflow templates have been deprecated in this release of Cisco UCS Director. These templates will be removed from the product in a subsequent release.

Standalone Task Library Reference

The Orchestration Task Library can be viewed in PDF form on cisco.com and in HTML form on Cisco DevNet. Previously to view the reference you had to log into Cisco UCS Director and click the Task Library action on the Workflows page.

Documented in the Cisco UCS Director Orchestration Task Library Reference and on Cisco DevNet.

Restriction on Including Special Characters for Credential Policies

In prior versions of Cisco UCS Director, while adding a credential policy, you could not include special characters in the policy name field. But, while cloning a credential policy, you were allowed to include special characters in the policy name. Starting with release 6.6, you cannot include special characters in the name field while cloning a credential policy.

User Password Expiry Related Enhancements

This release introduces the following user password expiry-related enhancements:

• The Users screen displays the password expiry date and time for each user. This information is derived from the Password policy that is configured in the system.

  The Users screen also graphically represents the password expiry status for each user. A new column titled Password Expiry Status displays a green icon for passwords that have not yet expired, and a red icon for passwords that have expired. To view information on user passwords that have expired, choose Administration > Integration > Change Records.

• All users will receive an email notification when their passwords are reset or modified by the administrator. Users will receive this notification only if SMTP is configured in Cisco UCS Director.

For more information, see the Cisco UCS Director Administration Guide, Release 6.6.

Support for Japanese User Interface

This release includes support for the Japanese user interface. If you are an administrator, and want to change the language preference for your account, then mouse over your login name in the user interface and choose Edit My Profile. In the subsequent screen, choose the Japanese language from the Language drop-down list.

To change the language setting for other users, choose Administration > Users and Groups and choose a user from the list. Click Edit to modify the language preference from the Locale drop-down list.

Proxy Configuration Changes

You can enable proxy configuration on the system. It is a system-wide configuration. To enable proxy, choose Administration > System > Proxy Configuration.

The proxy setting that you configure from the Administration menu does not have any impact on the proxy setting that you configure to use the Device Connector tab.

For more information, see the Cisco UCS Director Administration Guide, Release 6.6.

Enhancements to Host Image Mapping on Cisco UCS E-series Servers

Host Image Mapping allows you to download a firmware file to Cisco UCS Director, and upgrade the firmware on Cisco UCS E-series servers. Using Cisco UCS Director, you can create a host image mapping profile to download and upgrade either one of the following:

• ISO firmware image

• CIMC image or

• BIOS image

Using Cisco UCS Director, you can download the firmware image on Cisco IMC in one of the following methods:

• Provide a location on the network (an FTP, FTPS, HTTP or HTTPS server) where the firmware file is currently available.

• Choose the firmware file from a location on your system.

• Download the firmware image from www.cisco.com.

Important

To perform these tasks, Cisco IMC version 3.2.4 must be installed on the E-series servers. This feature does not work with prior versions of Cisco IMC. Host image mapping profiles created in prior versions of Cisco UCS Director will no longer work after you upgrade to the Cisco UCS Director release 6.6(1.0). You must delete these profiles and create it again after upgrading to this version.

For more information, see the Cisco UCS Director Management Guide for Rack Servers, Release 6.6.

Introduction of Power Restore Policy for E-series Servers

This release introduces a Power Restore policy that allows you to change the value set for the power restore policy on an E-series server without logging into the Cisco IMC of that server.

For more information, see the Cisco UCS Director Management Guide for Rack Servers, Release 6.6.

Support for Configuring Graceful Timeout on UCS C-series Servers

This release introduces support for configuring a timeout for host systems to shut down before a firmware upgrade process is initiated.

While uploading a firmware image from a local server, or while uploading a firmware image from a network server, you can now specify a timeout period, in minutes, within which the host system must gracefully shut down. You can also enable the host system to forcibly shutdown before the firmware upgrade process is initiated. The new fields introduced to enable configuring graceful timeout and force shut down are available on the Add Firmware Image - Local screen and Add Firmware Image - Network screen.

Note	You can configure graceful timeout for systems running Cisco IMC version 3.1(3a) or higher.

For more information, see the Cisco UCS Director Management Guide for Rack Servers, Release 6.6.

Support for Policy-Based Redirect (PBR) in APIC and Multi-Site Controller (MSC)

Cisco Application Centric Infrastructure (ACI) policy-based redirect (PBR) enables provisioning service appliances, such as firewalls or load balancers, as unmanaged nodes without needing a Layer 4 to Layer 7 package. From this release, Cisco UCS Director has the provision to create the following objects that are necessary to get PBR support:

• Layer 4-Layer 7 PBR

• Layer 4-Layer 7 redirect health group

• Destination of redirect traffic

For more information, see the Configuring Policy Based Redirect chapter in Cisco UCS Director APIC Management Guide, Release 6.6.

The use case on how to deploy PBR in intra-VRF design is documented in the Cisco ACI Policy-Based Redirect Use Case on Cisco UCS Director guide.

Enhancements to existing APIC tasks to support PBR

The following actions are enhanced to extend the PBR feature support in an APIC account:

• Adding a Bridge Domain to VRF— Introduced the Endpoint Dataplane Learning field to enable or disable data-plane IP learning on remote and local leaf switches, and Limit IP Learning to Subnet field to enable the fabric learn only IP addresses for subnets configured on the bridge domain.

• Adding a Managed Device Cluster—Introduced three fields to select device package model, enable promiscuous mode, and to choose APIC to device management connectivity.

• Creating a Service Graph Template—Introduced Route Redirect drop-down list to enable policy-based route redirect on the ADC or Firewall Routed mode.

• Applying a Service Graph Template—In the Node One Consumer and Provider Connector area, the status of the policy-based routing is displayed. Also, added a provision to choose consumer and provider layer 3 destination virtual IP (VIP) addresses.

• Adding a Logical Device Context—Introduced a new field to add the context name.

• Adding a Logical Interface Context—Introduced fields to select Layer 3 network, to choose Layer 3 destination (VIP), to select policy-based redirect when L3 destination is set as false, to select custom QoS policy that need to be associated to the interface context, and to enable permit logging for logical interface context.

For more information, see the Cisco UCS Director APIC Management Guide, Release 6.6.

Extension of support for Multi-Site Controller (MSC) account

Using Cisco UCS Director, users can perform the following tasks in an MSC account:

• Add or update an external EPG of MSC with multiple sites.

• Add or update an ACI multi-site service graph.

• Add or update a service graph to a contract.

For more information, see the Cisco UCS Director APIC Management Guide, Release 6.6.

Support for custom QoS in APIC

This release of Cisco UCS Director introduces support for custom QoS. While configuring layer 4 to layer 7 service, you can perform the following actions to introduce custom QoS in your environment:

• Add or update a custom QOS policy.

• Add or update a DSCP to a priority map.

• Add or update a Dot1P classifier.

For more information, see the Cisco UCS Director APIC Management Guide, Release 6.6.

Enhancements to Logical Interface Context in APIC

To extend the IP address support in logical interface context, Cisco UCS Director has introduced actions to add virtual IP address to logical interface and to add a subnet to a logical device context while configuring layer 4 to layer 7 service.

For more information, see the Cisco UCS Director APIC Management Guide, Release 6.6.

Support for Migrating LUNs

This release provides an option to move a LUN from one volume to another within the same Storage Virtual Machine (SVM) without causing any disruption in data.

Support for Enabling and Disabling Data Compression

This release provides an option to enable and disable data compression within a volume to reduce storage capacity. By checking the Enable Background Compression and Enable Inline Compression check boxes, you can enable background and inline compression of data respectively.

Support for FlexGroup Volumes

This release introduces support for creating FlexGroup volumes. A FlexGroup volume is a scale-out Network Attached Storage (NAS) container that provides high performance along with automatic load distribution and scalability. A FlexGroup volume contains several constituents that automatically and transparently share the traffic.

Support for User and Group Quotas

This release introduces support for creating user quotas and group quotas on a volume or a QTree. A quota limits the amount of disk space and the number of files that a particular user or group can consume.

Support for Upgrading Server Firmware Versions for Cisco UCS Manager Accounts

This release introduces support for upgrading BIOS, CIMC, PCI adapters, RAID controllers, and other firmware component versions on Cisco UCS Manager accounts. You can download updated versions of these firmware components from a remote server on the network. This remote server can either be an FTP, TFTP, SCP or SFTP server on the network. After downloading a new version, you can upgrade the firmware on the Cisco UCS Manager account. At a later point in time, you can choose to delete all the firmware packages from the remote location.

Support for Modifying Existing UCS Server Profile Pools and Policies

This release introduces support for modifying existing UCS server profile pools and policies using the Modify UCS Service Profile workflow task. Following is a list of service profile pools and policies that you can edit using this workflow task:

• Server Power State

• UUID Pool

• In-band Management IP Pool (IPv4)

• Out-band Management IP Pool (IPv4)

• In-band Management IP Pool (IPv6)

• Management VLAN

• IQN pool

• LAN Adapter policy

• SAN Adapter policy

• Local Disk Configuration policy

• Maintenance policy

• Host Firmware package

• BIOS policy

• Boot policy

• Scrub policy

• Power control policy

• IPMI Access profile

• Serial over LAN policy

• Statistics threshold policy

• vMedia policy

• Storage profile

Support for Big Data Cluster Version

This release introduces support for Cloudera 5.15.

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

Support for NVMe Disks

This release introduces an option to support NVMe disks in Splunk clusters.

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

Support for RHEL 7.5

This release introduces support RHEL 7.5 for deploying Cloudera 5.15 clusters.

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

Support for Update BMA Appliance Task system task

This release introduces a new system task (Update BMA Appliance Task).

Navigate to the Big Data Tasks folder here: Administration > System > System Tasks. The system scheduler connects to all Bare Metal Agents that are currently managed, performs a version check, stops services, pushes the required updates, and starts the services. This task is performed when

• the Cisco Big Data Express connector pack is upgraded.

• a BMA is added.

Note	If any of the BMA goes down and update fails, you should add the BMA to kickstart the process again. You can use the system task history to check for any failures and add the BMA again to trigger the process.

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

Assign a HyperFlex ReadyClone VM to a VDC in Orchestration

This release adds the ability in orchestration to assign a VM created using ReadyClone to a virtual data center (VDC). The orchestration task Create HyperFlex ReadyClones of a VM has a new output, VMware Account Identity. Map this output to the Select VM input of the Assign VMs to VDC task to assign a ReadyClone to a VDC.

Mapping passwords to Generic Text is invalid

As of this release, the mapping of password-type input fields to a generic text type is not allowed. Generic text input is no longer presented as an option when mapping password inputs.

If you run a workflow that was previously created (in an earlier release of Cisco UCS Director) with a password mapped to generic text, the workflow can run and complete successfully (assuming that no other tasks fail in the service request). However, validation fails for such a workflow.

To avoid exposing passwords to unauthorized users, Cisco recommends that you remap passwords to masked input types in existing workflows, then revalidate the workflows.

Create a ReadyClone VM from an Image in Orchestration

This release adds the ability in orchestration to create a ReadyClone VM from an image. The VMware Image Selector type now maps to the VM Template Name input in the Create a HyperFlex ReadyClone VM task. Pass the VMware Image Selector as a task input to the VM Template Name input property to use the image as a template for the ReadyClones.

New and Modified NetApp Workflow Tasks

The following workflow tasks have been introduced in this release:

• Create NetApp Cluster FlexGroup Volume

• Destroy NetApp Cluster FlexGroup Volume

• Modify NetApp Cluster Flexible Volume Compression Status

• Migrate NetApp Cluster LUN

The following workflow tasks have been enhanced in this release:

• Add NetApp Cluster Quota

• Delete NetApp Cluster Quota

• Modify NetApp Cluster Quota

New and Modified Workflow Tasks for Cisco UCS Manager

Following are the workflow tasks introduced in this release:

• Download UCS Firmware

• Install UCS Server Firmware

• Delete UCS Firmware

• Modify UCS Service Profile

Following is the workflow task enhanced in this release:

• Create UCS Boot Policy

Note

To view descriptions of these workflow tasks, see the Task Library that you can launch in the following ways: Choose Orchestration > Workflows in the user interface and click the Task Library action. Go to http://IP_address/app/cloudmgr/onlinedocs/cloupiaTaskLib.html where IP_address is the IP address of Cisco UCS Director.

Change in Support for Multi-node Configuration in a Subsequent Release

An upcoming release of Cisco UCS Director will feature updates to improve the efficiency of the system’s multi-node capability. All multi-node configurations will be reconfigured automatically in an upcoming release of Cisco UCS Director.

Special Characters Not Allowed in Task Names

Certain special characters are disallowed in task names. You cannot use a disallowed character in the name of a new instance of a task, nor can you change an existing name to contain such a character.

Existing workflows might contain instances of tasks whose names contain disallowed characters. This might occur if you import a workflow from a previous version of Cisco UCS Director, for example. Such workflows can still be run, despite having tasks with "illegal" names.

If you modify a task instance that has a name containing a disallowed character, you have the option of renaming the task. To rename the task, check the Edit the task name box, overwrite the task name, and submit the form.