CISCO Release 6.9 UCS Director User Manual

: June 13, 2024
: Cisco

Table of Contents

CISCO Release 6.9 UCS Director
Product Information
FAQs
IMPORTANT SAFETY INSTRUCTIONS
Overview
Installing Cisco UCS Director on VMware vSphere
Installing Cisco UCS Director on Microsoft Hyper-V
Restarting Cisco UCS Director
Post-Installation Configuration
Read User Manual Online (PDF format)
Download This Manual (PDF format)

CISCO Release 6.9 UCS Director

Product Information

Specifications

Product: Cisco UCS Director
Installation Guide: VMware vSphere and Microsoft Hyper-V, Release 6.9
First Published: 2024-05-07
Manufacturer: Cisco Systems, Inc.
Headquarters: 170 West Tasman Drive San Jose, CA 95134-1706 USA
Website: http://www.cisco.com
Contact: Tel: 408 526-4000, 800 553-NETS (6387) Fax: 408 527-0883

Overview

The Cisco UCS Director is a comprehensive management solution for virtualized environments. It offers both physical and virtual management features to streamline operations and enhance efficiency.

Features and Benefits

The Cisco UCS Director provides a range of features including:

Automated provisioning of resources
Performance monitoring and reporting
Multi-hypervisor support for VMware vSphere and Microsoft Hyper-V
Integration with Cisco UCS infrastructure

Benefits of using Cisco UCS Director include improved resource utilization, simplified management tasks, and enhanced visibility into the virtualized environment.

Physical and Virtual Management Features

The product offers a combination of physical and virtual management capabilities, allowing users to manage both their hardware infrastructure and virtualized resources from a single interface.

Cisco UCS Director Installation Guidelines

Before proceeding with the installation, make sure to review the installation guidelines provided in the user manual. These guidelines outline the necessary steps and requirements for a successful installation.

About Licenses

Users are required to fulfill the product access key and verify digitally signed images during the installation process. Ensure compliance with licensing terms to avoid any disruptions in product usage.

Digitally Signed Images

Digitally signed images ensure the authenticity and integrity of the software being installed. Follow the provided requirements for verifying digitally signed images to maintain a secure installation process.

Requirements for Verifying Digitally Signed Images

Prior to installation, ensure that you meet all the specified requirements for verifying digitally signed images. This step is crucial for confirming the software’s authenticity and preventing unauthorized modifications.

Verifying a Digitally Signed Image

Follow the detailed instructions in the user manual to verify digitally signed images before proceeding with the installation.
This verification step adds an extra layer of security to the software deployment process.

FAQs

Q: How can I obtain additional support for Cisco UCS Director?
- A: For additional support or inquiries regarding Cisco UCS Director, you can contact your Cisco representative or visit the Cisco website for relevant resources and documentation.
Q: Is training available for utilizing all features of Cisco UCS Director?
- A: Yes, Cisco offers training programs to help users leverage the full potential of Cisco UCS Director. Visit the Cisco website or contact your representative for more information on available training options.
Q: Can Cisco UCS Director be integrated with other third-party virtualization platforms?
- A: While Cisco UCS Director primarily supports VMware vSphere and Microsoft Hyper-V, it may have integration capabilities with other third-party virtualization platforms. Consult the product documentation or contact support for specific integration details.

Cisco UCS Director Installation Guide for VMware vSphere and Microsoft Hyper-V, Release 6.9
First Published: 2024-05-07
Americas Headquarters
Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000
800 553-NETS (6387) Fax: 408 527-0883

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE- NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
All printed copies and duplicate soft copies of this document are considered uncontrolled. See the current online version for the latest version.
Cisco has more than 200 offices worldwide. Addresses and phone numbers are listed on the Cisco website at www.cisco.com/go/offices.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: https://www.cisco.com/c/en/us/about/legal/trademarks.html. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1721R)
© 2024 Cisco Systems, Inc. All rights reserved.

CONTENTS

PREFACE CHAPTER 1 CHAPTER 2

Preface v Audience v Conventions v Related Documentation vii Documentation Feedback vii Communications, Services, and Additional Information vii
Overview 1 Cisco UCS Director 1 Features and Benefits 2 Physical and Virtual Management Features 3 Cisco UCS Director Installation Guidelines 4 About Licenses 5 Fulfilling the Product Access Key 5 Digitally Signed Images 6 Requirements for Verifying Digitally Signed Images 6 Verifying a Digitally Signed Image 6
Installing Cisco UCS Director on VMware vSphere 9 for VMware vSphere 9 Default Root and Shelladmin Passwords 9 Prerequisites for VMware vSphere 10 Minimum System Requirements for a Single-Node Setup 10 Installing on VMware vSphere 12 Reserving System Resources 14

Cisco UCS Director Installation Guide for VMware vSphere and Microsoft Hyper-V, Release 6.9 iii

Contents

CHAPTER 3 CHAPTER 4 CHAPTER 5 APPENDIX A

Installing Cisco UCS Director on Microsoft Hyper-V 15 for Microsoft Hyper-V 15 Prerequisites 15 Minimum System Requirements for a Single Node Setup on Microsoft Hyper-V 16 Installing on Microsoft Hyper-V 18
Restarting Cisco UCS Director 21 Restarting 21
Post-Installation Configuration 23 Changing the Admin Password 23 Updating the License 23 Configuring the Network Interface in ShellAdmin 24 Changing the Maximum Packet Size 24
Ports 27 Cisco UCS Director TCP and UDP Port Usage 27 Cisco UCS Director TCP and UDP Port Usage on VMware vSphere 27 Cisco UCS Director TCP and UDP Port Usage on Microsoft Hyper-V 28 Port List 29 Multi-Node Port Requirements 30

Cisco UCS Director Installation Guide for VMware vSphere and Microsoft Hyper-V, Release 6.9 iv

Preface
· Audience, on page v · Conventions, on page v · Related Documentation, on page vii · Documentation Feedback, on page vii · Communications, Services, and Additional Information, on page vii
Audience
This guide is intended primarily for data center administrators who use and who have responsibilities and expertise in one or more of the following:
· Server administration · Storage administration · Network administration · Network security · Virtualization and virtual machines

Conventions
Text Type GUI elements
Document titles TUI elements System output

Indication GUI elements such as tab titles, area names, and field labels appear in this font. Main titles such as window, dialog box, and wizard titles appear in this font.
Document titles appear in this font.
In a Text-based User Interface, text the system displays appears in this font.
Terminal sessions and information that the system displays appear in this font.

Cisco UCS Director Installation Guide for VMware vSphere and Microsoft Hyper-V, Release 6.9 v

Preface

Text Type CLI commands
[] {x | y | z}
[x | y | z] string

<> [] !, #

Indication CLI command keywords appear in this font. Variables in a CLI command appear in this font.
Elements in square brackets are optional.
Required alternative keywords are grouped in braces and separated by vertical bars.
Optional alternative keywords are grouped in brackets and separated by vertical bars.
A nonquoted set of characters. Do not use quotation marks around the string or the string will include the quotation marks.
Nonprinting characters such as passwords are in angle brackets.
Default responses to system prompts are in square brackets.
An exclamation point (!) or a pound sign (#) at the beginning of a line of code indicates a comment line.

Note Means reader take note. Notes contain helpful suggestions or references to material not covered in the document.
Caution Means reader be careful. In this situation, you might perform an action that could result in equipment damage or loss of data.
Tip Means the following information will help you solve a problem. The tips information might not be troubleshooting or even an action, but could be useful information, similar to a Timesaver.

Timesaver Means the described action saves time. You can save time by performing the action described in the paragraph.

Warning

IMPORTANT SAFETY INSTRUCTIONS

This warning symbol means danger. You are in a situation that could cause bodily injury. Before you work on any equipment, be aware of the hazards involved with electrical circuitry and be familiar with standard practices for preventing accidents. Use the statement number provided at the end of each warning to locate its translation in the translated safety warnings that accompanied this device.
SAVE THESE INSTRUCTIONS

Cisco UCS Director Installation Guide for VMware vSphere and Microsoft Hyper-V, Release 6.9 vi

Preface

Overview

· Cisco UCS Director, on page 1 · Cisco UCS Director Installation Guidelines, on page 4 · About Licenses, on page 5 · Digitally Signed Images, on page 6
Cisco UCS Director
Cisco UCS Director is a complete, highly secure, end-to-end management, orchestration, and automation solution for a wide array of Cisco and non-Cisco data infrastructure components, and for the industry’s leading converged infrastructure solutions based on the Cisco UCS and Cisco Nexus platforms. For a complete list of supported infrastructure components and solutions, see the Cisco UCS Director Compatibility Matrix. Cisco UCS Director is a 64-bit appliance that uses the following standard templates:
· Open Virtualization Format (OVF) and Open Virtual Appliance (OVA) for VMware vSphere · Virtual Hard Disk (VHD) for Microsoft Hyper-V
Management through Cisco UCS Director Cisco UCS Director extends the unification of computing and networking layers through Cisco UCS to provide you with comprehensive visibility and management of your data center infrastructure components. You can use Cisco UCS Director to configure, administer, and monitor supported Cisco and non-Cisco components. The tasks you can perform include the following:
· Create, clone, and deploy service profiles and templates for all Cisco UCS servers and compute applications.
· Monitor organizational usage, trends, and capacity across a converged infrastructure on a continuous basis. For example, you can view heat maps that show virtual machine (VM) utilization across all your data centers.
· Deploy and add capacity to converged infrastructures in a consistent, repeatable manner. · Manage, monitor, and report on data center components, such as Cisco UCS domains or Cisco Nexus
network devices. · Extend virtual service catalogs to include services for your physical infrastructure.
Cisco UCS Director Installation Guide for VMware vSphere and Microsoft Hyper-V, Release 6.9 1

Features and Benefits

Overview

· Manage secure multi-tenant environments to accommodate virtualized workloads that run with non-virtualized workloads.
Automation and Orchestration with Cisco UCS Director
Cisco UCS Director enables you to build workflows that provide automation services, and to publish the workflows and extend their services to your users on demand. You can collaborate with other experts in your company to quickly and easily create policies. You can build Cisco UCS Director workflows to automate simple or complex provisioning and configuration processes. Once built and validated, these workflows perform the same way every time, no matter who runs the workflows. An experienced data center administrator can run them, or you can implement role-based access control to enable your users and customers to run the workflows on a self-service basis, as needed. With Cisco UCS Director, you can automate a wide array of tasks and use cases across a wide variety of supported Cisco and non-Cisco hardware and software data center components. A few examples of the use cases that you can automate include, but are not limited to:
· VM provisioning and lifecycle management
· Network resource configuration and lifecycle management
· Storage resource configuration and lifecycle management
· Tenant onboarding and infrastructure configuration
· Application infrastructure provisioning
· Self-service catalogs and VM provisioning
· Bare metal server provisioning, including installation of an operating system

Features and Benefits

The features and benefits of Cisco UCS Director are as follows:

Feature Central management

Benefit
· Provides a single interface for administrators to provision, monitor, and manage the system across physical, virtual, and bare metal environments
· Provides unified dashboards, reports, and heat maps, which reduce troubleshooting and performance bottlenecks

Self-service catalog

· Allows end users to order and deploy new infrastructure instances conforming to IT-prescribed policies and governance

Adaptive provisioning

· Provides a real-time available capability, internal policies, and application workload requirements to optimize the availability of your resources

Dynamic capacity management

· Provides continuous monitoring of infrastructure resources to improve capacity planning, utilization, and management
· Identifies underutilized and overutilized resources

Cisco UCS Director Installation Guide for VMware vSphere and Microsoft Hyper-V, Release 6.9 2

Overview

Physical and Virtual Management Features

Feature

Benefit

Multiple hypervisor support

· Supports VMware ESX, ESXi, Microsoft Hyper-V, and Red Hat hypervisors

Computing management

· Provisions, monitors, and manages physical, virtual, and bare metal servers, as well as blades
· Allows end users to implement virtual machine life-cycle management and business continuance through snapshots
· Allows administrators to access server utilization trend analysis

Network management

· Provides policy-based provisioning of physical and virtual switches and dynamic network topologies
· Allows administrators to configure VLANs, virtual network interface cards (vNICs), port groups and port profiles, IP and Dynamic Host Control Protocol (DHCP) allocation, and access control lists (ACLs) across network devices

Storage management

· Provides policy-based provisioning and management of filers, virtual filers (vFilers), logical unit numbers (LUNs), and volumes
· Provides unified dashboards that allow administrators comprehensive visibility into organizational usage, trends, and capacity analysis details.

Physical and Virtual Management Features

Physical Server Management

Virtual Computing Management

· Discover and collect configurations and changes · Monitor and manage physical servers · Perform policy-based server provisioning · Manage blade power · Manage server life cycle · Perform server use trending and capacity analysis · Perform bare metal provisioning using preboot
execution environment (PXE) boot management

· Discover, collect, and monitor virtual computing environments
· Perform policy-based provisioning and dynamic resource allocation
· Manage the host server load and power
· Manage VM life cycle and snapshots
· Perform analysis to assess VM capacity, sprawl, and host utilization

Cisco UCS Director Installation Guide for VMware vSphere and Microsoft Hyper-V, Release 6.9 3

Cisco UCS Director Installation Guidelines

Overview

Physical Storage Management

Virtual Storage Management

· Discover, collect, and monitor storage filers
· Perform policy-based provisioning of vFilers
· Provision and map volumes
· Create and map Logical Unit Number (LUN) and iGroup instances
· Perform SAN zone management
· Monitor and manage network-attached storage (NAS) and SAN-based storage
· Implement storage best practices and recommendation

· Discover, collect, and monitor storage of vFilers and storage pools
· Perform policy-based storage provisioning for thick and thin clients
· Create new datastores and map them to virtual device contexts (VDCs)
· Add and resize disks to VMs
· Monitor and manage organizational storage use
· Perform virtual storage trend and capacity analysis

Physical Network Management

Virtual Network Management

· Discover, collect, and monitor physical network elements
· Provision VLANs across multiple switches

· Add networks to VMs
· Perform policy-based provisioning with IP and DHCP allocation

· Configure Access Control Lists (ACLs) on network devices

· Configure and connect Virtual Network Interface Cards ( vNICs) to VLANs and private VLANs

· Configure storage network s

· Create port groups and port profiles for VMs

· Implement dynamic network topologies

· Monitor organizational use of virtual networks

Cisco UCS Director Installation Guidelines
Before you install Cisco UCS Director, be aware of the following:
Cisco UCS Director VM Disks During Cisco UCS Director installation, on either VMware vSphere or Microsoft Hyper-V, the installer creates two hard disks.
· Primary disk–Contains the Cisco UCS Director appliance and operating system. Post-installation, the primary disk is named Hard Disk 1.
· Secondary disk–Contains the Cisco UCS Director database. Post-installation, the secondary disk is named Hard Disk 2.
Both disks are automatically created during the installation with the same disk format and parameters.

Cisco UCS Director Installation Guide for VMware vSphere and Microsoft Hyper-V, Release 6.9 4

Overview

About Licenses

Cisco UCS Director OVF and VHD Zip Files

Note Cisco UCS Director OVF and VHD zip files are created using zip 3.x in AlmaLinux9.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 and Windows Server or with the latest versions of archiving tools such as 7-Zip or WinRAR.

About Licenses
You must obtain a license to use , as follows: 1. Before you install , generate the license key and claim a certificate (Product Access Key). 2. Register the Product Access Key (PAK) on the Cisco software license site, as described in Fulfilling the
Product Access Key, on page 5. 3. After you install , update the license in as described in Updating the License, on page 23. 4. After the license has been validated, you can start to use .

Fulfilling the Product Access Key
Before you begin You need the PAK number.

Step 1 Step 2
Step 3 Step 4 Step 5 Step 6

Navigate to the Cisco Software License website. If you are directed to the Product License Registration page, you can take the training or click Continue to Product License Registration. On the Product License Registration page, click Get New Licenses from a PAK or Token. In the Enter a Single PAK or TOKEN to Fulfill field, enter the PAK number. Click Fulfill Single PAK/TOKEN. Complete the additional fields in License Information to register your PAK:

Name Organization Name

Description The organization name.

Site Contact Name

The site contact name.

Street Address

The street address of the organization.

City or Town

The city or town.

State or Province

The state or province.

Zip or Postal Code

The zip code or postal code.

Cisco UCS Director Installation Guide for VMware vSphere and Microsoft Hyper-V, Release 6.9 5

Digitally Signed Images

Overview

Step 7

Name Country

Description The country name.

Click Issue Key.
The features for your license appear, and you receive an email with the Digital License Agreement and a zipped license file.

Digitally Signed Images
images are delivered in digitally signed zip files. These signed zip files are wrapped in a container zip file that includes the following:
· Digitally signed zip file–Contains the installation image · Verification program–Verifies the certificate chain and signature. During certificate chain validation,
the program verifies the authenticity of the end-entity certificate using Cisco’s SubCA and root CA certificates. Then, the authenticated end-entity certificate is used to verify the signature. · Digital signature file–Contains the signature that you can verify before installation. · Certificate file–Enables you to verify the digital signature. This Cisco-signed x.509 end- entity certificate contains a public key that can be used to verify the signature. This certificate is chained to the Cisco root posted on http://www.cisco.com/security/pki/certs/crcam2.cer. · ReadMe file–Provides the information and instructions required to verify the digitally signed zip file.
Verify the image offline. Once the image is verified, you can begin the installation of .
Requirements for Verifying Digitally Signed Images
Before you verify a digitally signed image, ensure that you have the following on your local machine: · Connectivity to https://www.cisco.com during the verification process · Python 3.4.0 or later · OpenSSL

Verifying a Digitally Signed Image
Before you begin Download the image from Cisco.com.

Step 1

Unzip the file you downloaded from Cisco.com and verify that it contains the following files: · ReadMe file

Cisco UCS Director Installation Guide for VMware vSphere and Microsoft Hyper-V, Release 6.9 6

Overview

Verifying a Digitally Signed Image

Step 2 Step 3 Step 4

· Digitally signed zip file, for example CUCSD_6_9_0_0_69115_VMWARE_GA.zip or CUCSD_6_9_0_0_69115_HYPERV_GA.zip
· Certificate file, for example UCS_GENERIC_IMAGE_SIGNING-CCO_RELEASE.cer
· Digital signature generated for the image, for example CUCSD_6_9_0_0_69115_VMWARE_GA.zip.signature or CUCSD_6_9_0_0_69115_HYPERV_GA.zip.signature
· Signature verification program, for example cisco_x509_verify_release.py3

Review the instructions in the ReadMe file.

Note

If there are any differences between these instructions and those in the ReadMe, follow the ones in the

ReadMe.

Run the signature verification program from the directory where you have unzipped the downloaded content.
Example: Signature Verification for VMware OVA Installation
python3 cisco_x509_verify_release.py3 -e UCS_GENERIC_IMAGE_SIGNING- CCO_RELEASE.cer -i CUCSD_6_9_0_0_69115_VMWARE_GA.zip -s CUCSD_6_9_0_0_69115_VMWARE_GA.zip.signature -v dgst -sha512
Example: Signature Verification for Hyper-V VHD Installation
Review the output and ensure that the verification has succeeded.
Example: Expected Output for VMware OVA Installation
Retrieving CA certificate from http://www.cisco.com/security/pki/certs/crcam2.cer … Successfully retrieved and verified crcam2.cer. Retrieving SubCA certificate from http://www.cisco.com/security/pki/certs/innerspace.cer … Successfully retrieved and verified innerspace.cer. Successfully verified root, subca and end-entity certificate chain. Successfully fetched a public key from UCS_GENERIC_IMAGE_SIGNING-CCO_RELEASE.cer. Successfully verified the signature of CUCSD_6_9_0_0_69115_VMWARE_GA.zip using UCS_GENERIC_IMAGE_SIGNING- CCO_RELEASE.cer
Example: Expected Output for Hyper-V VHD Installation
Retrieving CA certificate from http://www.cisco.com/security/pki/certs/crcam2.cer … Successfully retrieved and verified crcam2.cer. Retrieving SubCA certificate from http://www.cisco.com/security/pki/certs/innerspace.cer … Successfully retrieved and verified innerspace.cer. Successfully verified root, subca and end-entity certificate chain. Successfully fetched a public key from UCS_GENERIC_IMAGE_SIGNING-CCO_RELEASE.cer. Successfully verified the signature of CUCSD_6_9_0_0_69115_HYPERV_GA.zip using UCS_GENERIC_IMAGE_SIGNING- CCO_RELEASE.cer

What to do next Install or upgrade .

Cisco UCS Director Installation Guide for VMware vSphere and Microsoft Hyper-V, Release 6.9 7

Verifying a Digitally Signed Image

Overview

Cisco UCS Director Installation Guide for VMware vSphere and Microsoft Hyper-V, Release 6.9 8

2 C H A P T E R

Installing Cisco UCS Director on VMware vSphere

· for VMware vSphere, on page 9 · Default Root and Shelladmin Passwords, on page 9 · Prerequisites for VMware vSphere, on page 10 · Minimum System Requirements for a Single-Node Setup, on page 10 · Installing on VMware vSphere, on page 12 · Reserving System Resources, on page 14
for VMware vSphere
Note The appliance and boot-up logs are located in the /var/log/ucsd directory. · install.log contains the one time appliance installation logs. · bootup.log contains the appliance boot-up sequence information, such as startup messages for the database and infrastructure services.
Default Root and Shelladmin Passwords
During installation, Cisco UCS Director uses default passwords for the following accounts: · Root user for the Almalinux operating system of the Cisco UCS Director VM. The default password is cisco123. · Shelladmin user for the Cisco UCS Director Shell menu. The default password is changeme.
Once the installation is completed ,the first time you log in to Cisco UCS Director, you are prompted to reset the default root and Shelladmin passwords. The new root and Shelladmin password must meet the password requirements. It cannot be a dictionary word or be all lowercase.
Cisco UCS Director Installation Guide for VMware vSphere and Microsoft Hyper-V, Release 6.9 9

Prerequisites for VMware vSphere

Installing Cisco UCS Director on VMware vSphere

Prerequisites for VMware vSphere
Before you install Cisco UCS Director for VMware vSphere, complete the following steps:
· Install VMware vSphere or vCenter.
· Configure a VMware vSphere or vCenter user account with system administrator privileges for Cisco UCS Director.
You need administrator privileges to connect to and install Cisco UCS Director on VMware vCenter. Cisco UCS Director requires a user account with system administrator privileges to discover, manage and automate VMware vCenter configuration from Cisco UCS Director. These operations include creating, deleting and modifying VMs, ESXi hosts and clusters, datastores and datastore clusters, standard and DV switches, and virtual network port groups.
· Download the Cisco UCS Director software from the Download Software area on Cisco.com.
· Extract the Cisco UCS Director OVF file from the digitally signed zip file to your local disk. See Digitally Signed Images, on page 6.

Minimum System Requirements for a Single-Node Setup

The following tables detail the minimum resource requirements for a single- node setup of . Cisco recommends a single-node setup for installations of up to 5000 VMs.
For optimal performance, the entire memory and CPU allocations specified in the table below should be reserved. Failure to follow these specifications could affect performance. For example, 4 vCPU cores with 3000 MHz and 16G of memory must be reserved for the VM.
The minimum memory required for the inframgr service is automatically set during deployment. To enable the inframgr service to use more than the minimum required memory, edit the inframgr.env file available in the following location:
/opt/infra/bin/
In this file, update the MEMORY_MAX parameter to the value you want. To activate the changes, restart the inframgr service.
The default memory settings are MEMORY_MIN=8192m and MEMORY_MAX=8192m.
For information about minimum system requirements for a multi-node setup, see the Cisco UCS Director Multi-Node Installation and Configuration Guide.
Table 1: Minimum system requirements for a single-node installation (up to 5,000 VMs)

Element vCPU Allocated Memory Reserved Memory Disk Space

Minimum Supported Requirement 4 16 GB 16 GB 100 GB

Cisco UCS Director Installation Guide for VMware vSphere and Microsoft Hyper-V, Release 6.9 10

Installing Cisco UCS Director on VMware vSphere

Minimum System Requirements for a Single-Node Setup

Element Disk Write I/O Bandwidth Disk Read I/O Bandwidth Memory Allocated for inframgr

Minimum Supported Requirement 4 MBps 4 MBps 8 GB

Restart the database and all services after making these changes to the /etc/my.cnf.

Up to 2,000 VMs If you plan to manage up to 2,000 VMs, the environment must meet at least the minimum system requirements in the following table.
Table 2: Minimum System Requirements for up to 2,000 VMs

Element vCPU Memory Primary Disk (Hard Disk 1) Secondary Disk (Hard Disk 2) Disk Read I/O Bandwidth Disk Write I/O Bandwidth

Minimum Supported Requirement 4 16 GB 100 GB 100 GB 4 MBps 4 MBps

Up to 5,000 VMs If you plan to manage no more than 5,000 VMs, the environment must meet at least the minimum system requirements and recommended configurations in the following tables.
Table 3: Minimum System Requirements for up to 5,000 VMs

Element vCPU Memory Primary Disk (Hard Disk 1) Secondary Disk (Hard Disk 2) Disk Write I/O Bandwidth Disk Read I/O Bandwidth

Minimum Supported Requirement 8 20 GB 100 GB 100 GB 4 MBps 4 MBps

You must also edit the MEMORY_MIN and MEMORY_MAX settings in /opt/infra/bin/inframgr.env as follows:
MEMORY_MIN=8192m

Cisco UCS Director Installation Guide for VMware vSphere and Microsoft Hyper-V, Release 6.9 11

Installing on VMware vSphere

Installing Cisco UCS Director on VMware vSphere

MEMORY_MAX=8192m Restart the inframgr service after making the memory size changes. Edit the following parameters in the /etc/my.cnf file.
Table 4: Minimum Database Configuration

Element thread_cache_size max_connections innodb_lock_wait_timeout query_cache_size innodb_buffer_pool_size max_connect_errors connect_timeout innodb_read_io_threads innodb_write_io_threads

Minimum Supported Configuration 100 1000 100 128 MB 2048 MB 10000 20 64 64

Restart the database and all services after making these changes to the /etc/my.cnf.

Installing on VMware vSphere

Note We recommend that you use VMware vCenter for OVF deployment. VMware vCenter versions ESXi 8.0 U1 and ESXi 8.0 U2 are supported. OVF deployment wizards support only IPv4 addresses.
Before you begin
You need administrator privileges to connect to VMware vCenter. Cisco UCS Director requires a user account with system administrator privileges to discover, manage and automate VMware vCenter configuration from Cisco UCS Director. These operations include creating, deleting and modifying VMs, ESXi hosts and clusters, datastores and datastore clusters, standard and DV switches, and virtual network port groups.

Note If you do not want to use DHCP, you need the following information: IPv4 address, subnet mask, and default gateway.

Step 1 Step 2

In the Navigation pane, choose the Data Center where you want to deploy Cisco UCS Director. Choose Datacenter > Deploy OVF Template.

Cisco UCS Director Installation Guide for VMware vSphere and Microsoft Hyper-V, Release 6.9 12

Installing Cisco UCS Director on VMware vSphere

Installing on VMware vSphere

Step 3 Step 4
Step 5 Step 6 Step 7 Step 8
Step 9 Step 10
Step 11 Step 12 Step 13

In the Source pane, do one of the following to choose your OVA source location:
· Choose files , navigate to the location where you downloaded the OVF, choose the OVA file, and click Open. · Replace FQDN (Fully Qualified Domain Name) with the path to the URL on your local area network where the
OVA file is stored, including the IP address or domain name, and click Next.

In the Name and Location pane, do the following: a) In the Name field, edit the VM name. b) From the Inventory Location area, choose the inventory location where is being deployed, and click Next.

Note

If you chose a Data Center in Step 2, option b might not be available.

c) Click Next.
In the Compute Resource pane, choose the required host, and click Next. TheReview Details pane, will display template details ,verify and click Next. On the Select Storage , choose the storage location for the VM. In the Disk Format pane, choose one of the following options and click Next:
· Thick Provisioned (Lazy Zeroed) format–To allocate storage immediately in thick format. This is the recommended format. All performance data is verified with this format.
· Thick Provisioned (Eager Zeroed) format–To allocate storage in thick format. It might take longer to create disks using this option.
· Thin Provisioned format–To allocate storage on demand as data is written to disk.
Important We recommend that you do not choose the Thin Provisioned format.

In the NetworkMapping pane, choose the network and click Next In the Properties pane, enter the following information and click Next:
· Management IP Address–The management IP address to be used for ens192. If your network uses DHCP, leave the default value of 0.0.0.0.
· Management IP Subnet Mask–The management IP subnet mask to be used for ens192. If your network uses DHCP, leave the default value of 0.0.0.0.
· Gateway IP Address–The Gateway IP Address to be used for ens192. If your network uses DHCP, leave the default value of 0.0.0.0.
· Ucsd Root Password
· ShellAdmin Password

Note

While deploying the OVA in a Customise template window,if no default passwords are populated for

root and shelladmin, please enter the default password cisco123 for root and changeme for shelladmin.

In the Ready to Complete pane, do the following: a) Verify the options that you chose in the previous panes. b) Click Finishto start the deployment process.
After the appliance has booted up, copy and paste the management IP address (from the IP address that is shown) into a supported web browser to access the Login page. On the Login page, enter admin as the username and admin for the login password.

Cisco UCS Director Installation Guide for VMware vSphere and Microsoft Hyper-V, Release 6.9 13

Reserving System Resources

Installing Cisco UCS Director on VMware vSphere

Step 14 Step 15
Step 16

Agree to the License Agreement and click the submit button. Generate a Self- Signed Certificate by entering the Local domain, day, and password.

Note

It will take 30 seconds to restart the Tomcat service.

On the Login page, enter admin as the username and admin for the login password to change the password for the admin user.
For information about upgrading from Cisco UCSD 6.7.4.3/6.8.x.x to Cisco UCSD 6.9, follow the migration process under the Cisco UCS Director Upgrade Guide.

Reserving System Resources
For optimal performance, we recommend reserving extra system resources for beyond the minimum system requirements listed in Minimum System Requirements for a Single-Node Setup, on page 10.

Note For more information about how to reserve system resources, see the VMWare documentation.

Step 1 Step 2 Step 3 Step 4 Step 5 Step 6

Log in to VMware vCenter. Choose the VM for . Shut down the VM. In VMware vCenter, click the Resource Allocation tab to view the current resource allocations, and click Edit. In the Virtual Machine Properties pane, edit resource allocations by choosing a resource and entering the new values. Verify that the new resource allocations have been made.

Cisco UCS Director Installation Guide for VMware vSphere and Microsoft Hyper-V, Release 6.9 14

3 C H A P T E R

Installing Cisco UCS Director on Microsoft Hyper-V

· for Microsoft Hyper-V, on page 15 · Prerequisites, on page 15 · Minimum System Requirements for a Single Node Setup on Microsoft Hyper-V, on page 16 · Installing on Microsoft Hyper-V, on page 18
for Microsoft Hyper-V
can be deployed in a Hyper-V environment.

Note

· We recommend to deploy on the Hyper-V managed host, rather than the SCVMM console.

· The appliance and bootup logs are located in the /var/log/ucsd directory. install.log contains the one time appliance installation logs. bootup.log contains the appliance boot-up sequence information, such as startup messages for the database and infrastructure services.

Prerequisites
Before you install Cisco UCS Director for Microsoft Hyper-V, complete the following steps: · Install Microsoft System Center Virtual Machine Manager (SCVMM). If you only have a Hyper-V environment, must be deployed on a Hyper-V host. · Configure an SCVMM user account with administrator privileges for Cisco UCS Director. · Download the Cisco UCS Director software from the Download Software area on Cisco.com. · Extract the Cisco UCS Director VHD and db files from the digitally signed zip file to your local disk. See Digitally Signed Images, on page 6.

Cisco UCS Director Installation Guide for VMware vSphere and Microsoft Hyper-V, Release 6.9 15

Minimum System Requirements for a Single Node Setup on Microsoft Hyper-V

Installing Cisco UCS Director on Microsoft Hyper-V

Minimum System Requirements for a Single Node Setup on Microsoft Hyper-V
The minimum system requirements depend upon how many VMs you plan to manage. We recommend deploying a 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 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 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 environment must meet at least the minimum system requirements in the following table.
Table 5: Minimum System Requirements for up to 2,000 VMs

Element vCPU Memory Primary Disk (Hard Disk 1) Secondary Disk (Hard Disk 2) Disk Read I/O Bandwidth Disk Write I/O Bandwidth

Minimum Supported Requirement 4 16 GB 100 GB 100 GB 4 MBps 4 MBps

Cisco UCS Director Installation Guide for VMware vSphere and Microsoft Hyper-V, Release 6.9 16

Installing Cisco UCS Director on Microsoft Hyper-V

Minimum System Requirements for a Single Node Setup on Microsoft Hyper-V

Up to 5,000 VMs If you plan to manage no more than 5,000 VMs, the environment must meet at least the minimum system requirements and recommended configurations in the following tables.
Table 6: Minimum System Requirements for up to 5,000 VMs

Element vCPU Memory Primary Disk (Hard Disk 1) Secondary Disk (Hard Disk 2) Disk Read I/O Bandwidth Disk Write I/O Bandwidth

Minimum Supported Requirement 8 20 GB 100 GB 100 GB 4 MBps 4 MBps

You must also edit the MEMORY_MIN and MEMORY_MAX setting in /opt/infra/bin/inframgr.env as follows: MEMORY_MIN=8192m MEMORY_MAX=8192m Edit the following parameters in the /etc/my.cnf file.
Table 7: Minimum Database Configuration

Element thread_cache_size max_connections innodb_lock_wait_timeout query_cache_size innodb_buffer_pool_size max_connect_errors connect_timeout innodb_read_io_threads innodb_write_io_threads

Minimum Supported Configuration 100 1000 100 128 MB 2 GB 10000 20 64 64

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

Cisco UCS Director Installation Guide for VMware vSphere and Microsoft Hyper-V, Release 6.9 17

Installing on Microsoft Hyper-V

Installing Cisco UCS Director on Microsoft Hyper-V

Installing on Microsoft Hyper-V
Before you begin · System administrator privileges for Hyper-V are required. · Microsoft Windows 2019 with Hyper-V Role or Windows 2022 with Hyper-V Role are required to deploy this release of Cisco UCS Director.

Step 1 Step 2 Step 3 Step 4 Step 5
Step 6
Step 7 Step 8
Step 9 Step 10 Step 11 Step 12 Step 13 Step 14
Step 15 Step 16 Step 17 Step 18 Step 19 Step 20 Step 21 Step 22

Log into the Hyper-V host. Choose Start > Administrative Tools to open Hyper-V Manager. In the Hyper-V Manager dialog box, choose Action > New Virtual Machine. In the Before You Begin pane, click Next. In the Name and Location pane, do the following: a) In the Name field, edit the default VM name. b) Check the Store the virtual machine in a different location checkbox and specify the alternate location. c) Click Next.
In the Select Generation pane, choose Generation2.
With Generation2, this virtual machine provides the same virtual hardware to the virtual machine as in previous versions of Hyper-V.

In the Assign Memory pane, enter the amount of memory to allocate to this VM (16 GB minimum) and click Next. In the Configure Networking pane, click Next to accept the default option in the Connection field. The default option is Not Connected.

In the Connect Virtual Hard Disk pane, choose Attach a virtual disk later and click Next. In the Completing the New Virtual Machine Wizard pane, verify the settings and click Finish. In the Navigation pane, right-click the new VM and choose Settings. In the Security pane, deselect the Enable Secure Boot checkbox. In the Navigation pane, choose IDE Controller 0. In the IDE Controller pane, choose Hard Drive and click Add.

Note

You need to add two hard drives since we have two VHD files separately for OS and application, and for

database.

In the Hard Drive pane, choose the downloaded .vhd file and click OK. Inspect the virtual hard drive properties. In the Navigation pane, choose Memory. In the Memory pane, enter the recommended value (minimum 16 GB). In the Navigation pane, choose Processor. In the Processor pane, enter the recommended value (4 vCPU). Remove the network adapter that was created when you created the new VM. In the Navigation pane, choose Add Hardware.

Cisco UCS Director Installation Guide for VMware vSphere and Microsoft Hyper-V, Release 6.9 18

Installing Cisco UCS Director on Microsoft Hyper-V

Installing on Microsoft Hyper-V

Step 23 Step 24 Step 25 Step 26 Step 27
Step 28 Step 29

In the Add Hardware pane, choose Network Adapter and click OK. In the Navigation pane, choose the network adapter. In the Network Adapter pane, in the Network field, choose your network and click OK. Verify that you have allocated sufficient vCPU and Memory resources. For the minimum resource requirements, see Minimum System Requirements for a Single Node Setup on Microsoft Hyper-V, on page 16. Power on the VM.
Optionally you can configure network properties from the shelladmin.
By default, this version of Microsoft Hyper-V uses DHCP for address allocation. If you want to use a static IP address instead of DHCP, you can change this configuration through ShellAdmin.

After the appliance has booted up, copy and paste the IP address that is displayed into a supported web browser to access the Login page.
At the login prompt, enter admin for username and admin for the password to log into .

Note

We recommend that you change the default admin password after this initial login.

What to do next Update your license.

Cisco UCS Director Installation Guide for VMware vSphere and Microsoft Hyper-V, Release 6.9 19

Installing on Microsoft Hyper-V

Installing Cisco UCS Director on Microsoft Hyper-V

Cisco UCS Director Installation Guide for VMware vSphere and Microsoft Hyper-V, Release 6.9 20

4 C H A P T E R

Restarting Cisco UCS Director

This chapter contains the following sections: · Restarting , on page 21
Restarting
If you see errors after installing , log in to the Secure Shell (SSH) client and verify whether services are running or not.

Step 1 Step 2 Step 3
Step 4 Step 5 Step 6

Log in to the VM console with the shelladmin user credentials: If this is the first time you have logged into the ShellAdmin after deployment, you will be prompted to change the default password.
To display the status of all services, choose Display services status. If this option is not available, you can use SSH to restart the services.
Verify that the following services appear:

1. broker 2. controller 3. eventmgr 4. idaccessmgr 5. inframgr 6. websock 7. connectormgr 8. tomcat 9. flashpolicy 10. mariadbd

Note

Services that start in the background do not appear in the window.

Choose Stop services. To verify that all services are stopped, choose Display services status. To restart services, choose Start services.

Cisco UCS Director Installation Guide for VMware vSphere and Microsoft Hyper-V, Release 6.9 21

Restarting

Restarting Cisco UCS Director

Cisco UCS Director Installation Guide for VMware vSphere and Microsoft Hyper-V, Release 6.9 22

5 C H A P T E R

Post-Installation Configuration

· Changing the Admin Password, on page 23 · Updating the License, on page 23 · Configuring the Network Interface in ShellAdmin, on page 24 · Changing the Maximum Packet Size, on page 24
Changing the Admin Password
You are prompted to change the default admin user password after you log into for the first time. On subsequent login, you can follow these steps to change the admin user password.

Step 1 Step 2 Step 3 Step 4 Step 5 Step 6

Choose Administration > Users and Groups. On the Users and Groups page, click Users. Click the row with the administration user for which you want to change the default password. From the More Actions drop-down list, choose Change Password. On the Change Password screen, enter the old password and then the new password and confirm it. Click Save.

Updating the License
Before you begin If you received a zipped license file by an email, extract and save the license (.lic) file to your local machine.

Step 1 Step 2 Step 3 Step 4

Choose Administration > License. On the License page, click License Keys. Click Update License. On the Update License screen, do the following:

Cisco UCS Director Installation Guide for VMware vSphere and Microsoft Hyper-V, Release 6.9 23

Configuring the Network Interface in ShellAdmin

Post-Installation Configuration

a) Drop the .lic file from your local system or click Select a File and navigate to the location where you stored the .lic file.
To enter license text instead of file upload, check the Enter License Text checkbox and enter the license text in the License Text field.
b) Click Submit.
The license file is processed, and a message appears confirming the successful update.

Configuring the Network Interface in ShellAdmin
This procedure is optional.

Step 1
Step 2 Step 3

Log in to the VM console with the shelladmin user credentials: If this is the first time you have logged into the ShellAdmin after deployment, you will be prompted to change the default password.
Choose Configure Network Interface. At the Do you want to Configure DHCP/STATIC IP [D/S] prompt, enter one of the following choices:
· If DHCP is enabled, enter D (IP addresses are assigned automatically) · To configure static IP, enter S, and then choose the interface you want to configure at the next prompt followed by
the option to select IPv4. This is followed by the confirmation of the interface selected and the version of IP for which you select Y to continue. Then enter the following details:
· IP address
· Netmask
· Gateway
· DNS Server 1
· DNS Server 2

Step 4 Confirm when prompted.

Changing the Maximum Packet Size
The default maximum packet (query) size for the database queries is 4 MB. If one or more of your pods requires a larger size, we recommend that you increase the configuration of the maximum packet size to 100 MB. For example, the import of large open automation modules typically require a larger packet size.

Cisco UCS Director Installation Guide for VMware vSphere and Microsoft Hyper-V, Release 6.9 24

Post-Installation Configuration

Changing the Maximum Packet Size

Note For a multi-node setup, perform this configuration on the inventory database and monitoring database nodes.

Step 1 Step 2 Step 3 Step 4 Step 5 Step 6

In the shelladmin, choose Login as Root to log in to . Navigate to the /etc folder. Open the my.cnf file and locate the max_allowed_packet parameter. Change the value of the max_allowed_packet parameter to max_allowed_packet=100M Save the my.cnf file. In the shelladmin, stop and restart the services on every node, as follows: a) Choose Stop services. b) To verify that all services are stopped, choose Display services status. c) After all services have stopped on the node, choose Start services.

Cisco UCS Director Installation Guide for VMware vSphere and Microsoft Hyper-V, Release 6.9 25

Changing the Maximum Packet Size

Post-Installation Configuration

Cisco UCS Director Installation Guide for VMware vSphere and Microsoft Hyper-V, Release 6.9 26

A A P P E N D I X
Ports
This appendix contains the following sections: · Cisco UCS Director TCP and UDP Port Usage, on page 27 · Port List, on page 29 · Multi-Node Port Requirements, on page 30
Cisco UCS Director TCP and UDP Port Usage
This section provides a list of the TCP and UDP ports that Cisco UCS Director uses for connections and communications with external applications or devices. The port usage depends upon whether you have deployed Cisco UCS Director on VMware vSphere or Microsoft Hyper-V.
Cisco UCS Director TCP and UDP Port Usage on VMware vSphere
The following figure shows the network ports used for communication between the Cisco UCS Director appliance and managed devices, ESX servers, Bare Metal Agent, PowerShell Agent, NTP, and Active Directory for an installation on VMware vSphere.
Cisco UCS Director Installation Guide for VMware vSphere and Microsoft Hyper-V, Release 6.9 27

Cisco UCS Director TCP and UDP Port Usage on Microsoft Hyper-V Figure 1: Cisco UCS Director TCP and UDP Port Usage

Ports

Cisco UCS Director TCP and UDP Port Usage on Microsoft Hyper-V
The following figure shows the network ports used for communication between the Cisco UCS Director appliance and managed devices, ESX servers, Bare Metal Agent, PowerShell Agent, NTP, and Active Directory for an installation on Microsoft Hyper-V.
Figure 2: Cisco UCS Director TCP and UDP Port Usage

Cisco UCS Director Installation Guide for VMware vSphere and Microsoft Hyper-V, Release 6.9 28

Ports

Port List

Default Port 22 80 69 443 27000/7279/8082 (Mgmt) 2598/1494/2112/2513 67/68 389/636 3268/3269 53 123 3306 8787/5900-5964 3389 80/443/8080 80/443 80/443 3389 135/445 88 137 138 139 80/443 8080 through ICA 1494/2598/2512/2513

Protocol TCP TCP/UDP TFTP UDP TCP TCP UDP TCP/UDP TCP TCP/UDP TCP/UDP TCP/UDP TCP TCP/UDP TCP/UDP UDP UDP TCP/UDP TCP TCP/UDP TCP/UDP TCP/UDP TCP UDP TCP TCP

Description SSH HTTP TFTP for Cisco UCS Director Bare Metal Agent HTTPS Citrix licensing Virtual Desktop Agent for Desktops DHCP Active Directory
DNS NTP MariaDB + VNC Connectivity + RDP Connectivity + NetApp Connectivity + Cisco UCS Manager Connectivity + vCenter Connectivity RDP SMB/RPC Kerberos NetBIOS Name (nbname) NetBIOS datagram (nbdatagram) NetBIOS session (nbsession) Desktop Delivery Controller <–> vCenter Desktop Delivery Controller <–> Virtual Desktops Users (Citrix Recvr) <–> Virtual Desktops

Cisco UCS Director Installation Guide for VMware vSphere and Microsoft Hyper-V, Release 6.9 29

Multi-Node Port Requirements

Ports

Default Port 389/636 (LDAP Ports) 389/636, 3268/3269, 53 5985/5986 43891 80/8081 902
903

Protocol TCP/UDP TCP/UDP TCP TCP/UDP TCP TCP
TCP

9002

TCP

Description Desktop Delivery Controller <–> Active Directory
Virtual Desktops <–> Active Directory + DNS
PowerShell Agent <-> Xendesktop through WinRM
<–> PowerShell Agent
XenApp
VMwareESXi host management and VM customization and to execute VIX tasks
VMwareESXi host management and VM customization and to execute VIX tasks (for Vmware vCenter releases prior to 5.0)
VMRC Connectivity

Multi-Node Port Requirements
The ports listed in Cisco UCS Director TCP and UDP Port Usage, on page 27 are applicable for both single and multi-node setups. For a multi-node setup, the following port must be opened between the nodes:
· From the primary nodes to database nodes: port 3306

Cisco UCS Director Installation Guide for VMware vSphere and Microsoft Hyper-V, Release 6.9 30