Cisco UCS Director Installation and Upgrade on Microsoft Hyper-V
Manager, Release 5.3
First Published: April 17, 2015
Last Modified: August 19, 2016
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.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: http://
www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership
relationship between Cisco and any other company. (1110R)
© 2015-2016
Cisco Systems, Inc. All rights reserved.
CONTENTS
Preface
Preface vii
Audience vii
Conventions vii
Related Documentation ix
Documentation Feedback ix
Obtaining Documentation and Submitting a Service Request ix
CHAPTER 1
Overview 1
About Cisco UCS Director 1
Features and Benefits 2
Physical and Virtual Management Features 4
Model-Based Orchestration 5
POODLE Vulnerability 5
About Cisco UCS Director for Hyper-V 5
Prerequisites 5
Minimum System Requirements for a Single Node Setup 6
About Licenses 7
Fulfilling the Product Access Key 8
CHAPTER 2
Installing Cisco UCS Director 9
Installing Cisco UCS Director on Microsoft Hyper-V 9
Installing Cisco UCS Director on Microsoft Hyper-V for Windows 2012 R2 11
Configuring the Network Interface using Shelladmin 12
Changing the Default Password 13
Updating the License 14
Changing the Maximum Packet Size 14
Cisco UCS Director Installation and Upgrade on Microsoft Hyper-V Manager, Release 5.3
iii
Contents
CHAPTER 3
Configuring a Multi-Node Setup 17
About the Multi-Node Setup 17
Primary Node 18
Service Nodes 18
Database Nodes 18
Minimum System Requirements for a Multi-Node Setup 19
Minimum System Requirements for a Small Multi-Node Setup 19
Minimum System Requirements for a Medium Multi-Node Setup 21
Minimum System Requirements for a Large Multi-Node Setup 23
Guidelines and Limitations for a Multi-Node Setup 26
Summary of Steps for Configuring a Multi-Node Setup 26
Creating the Inventory Database 27
Creating the Monitoring Database 28
Creating the Primary Node 28
Creating a Service Node 29
Backing Up with a Multi-Node Setup 30
Restoring with a Multi-Node Setup 31
Removing a Service Node 32
Options for Migrating from a Standalone Appliance to a Multi-Node Setup 32
Migrating a Release 4.0 Standalone Appliance to a Multi-Node Setup with a Full Database
Backup 33
Migrating a Release 4.0 Standalone Appliance to a Multi-Node Setup with a Selected
Database Backup 34
Migrating a Release 4.1 Standalone Appliance to a Multi-Node Setup with Selective Database
Table Backup 36
CHAPTER 4
Restarting Cisco UCS Director 39
Restarting Cisco UCS Director 39
CHAPTER 5
Upgrading Cisco UCS Director 41
Supported Upgrade Paths for Cisco UCS Director 41
Upgrading a Single Node Setup to Release 5.3 42
Upgrading a Multi-Node Setup to Release 5.3 43
Cisco UCS Director Installation and Upgrade on Microsoft Hyper-V Manager, Release 5.3
iv
Contents
APPENDIX A
Ports 45
Cisco UCS Director TCP and UDP Port Usage 45
Port List 46
Cisco UCS Director Installation and Upgrade on Microsoft Hyper-V Manager, Release 5.3
v
Contents
Cisco UCS Director Installation and Upgrade on Microsoft Hyper-V Manager, Release 5.3
vi
Preface
This preface contains the following sections:
• Audience, page vii
• Conventions, page vii
• Related Documentation, page ix
• Documentation Feedback, page ix
• Obtaining Documentation and Submitting a Service Request, page ix
Audience
This guide is intended primarily for data center administrators who use Cisco UCS Director 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
Indication
GUI elements
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
Document titles appear in this font.
TUI elements
In a Text-based User Interface, text the system displays appears in this font.
Cisco UCS Director Installation and Upgrade on Microsoft Hyper-V Manager, Release 5.3
vii
Preface
Conventions
Text Type
Indication
System output
Terminal sessions and information that the system displays appear in this
font.
CLI commands
CLI command keywords appear in this font.
Variables in a CLI command appear in this font.
Note
Tip
[]
Elements in square brackets are optional.
{x | y | z}
Required alternative keywords are grouped in braces and separated by vertical
bars.
[x | y | z]
Optional alternative keywords are grouped in brackets and separated by vertical
bars.
string
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.
Means reader take note. Notes contain helpful suggestions or references to material not covered in the
document.
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.
Caution
Means reader be careful. In this situation, you might perform an action that could result in equipment
damage or loss of data.
Timesaver
Means the described action saves time. You can save time by performing the action described in the
paragraph.
Cisco UCS Director Installation and Upgrade on Microsoft Hyper-V Manager, Release 5.3
viii
Preface
Related Documentation
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
Related Documentation
Cisco UCS Director Documentation Roadmap
For a complete list of Cisco UCS Director documentation, see the Cisco UCS Director Documentation
Roadmap available at the following URL: http://www.cisco.com/en/US/docs/unified_computing/ucs/
ucs-director/doc-roadmap/b_UCSDirectorDocRoadmap.html.
Cisco UCS Documentation Roadmaps
For a complete list of all B-Series documentation, see the Cisco UCS B-Series Servers Documentation Roadmap
available at the following URL: http://www.cisco.com/go/unifiedcomputing/b-series-doc.
For a complete list of all C-Series documentation, see the Cisco UCS C-Series Servers Documentation Roadmap
available at the following URL: http://www.cisco.com/go/unifiedcomputing/c-series-doc.
Note
The Cisco UCS B-Series Servers Documentation Roadmap includes links to documentation for Cisco
UCS Manager and Cisco UCS Central. The Cisco UCS C-Series Servers Documentation Roadmap includes
links to documentation for Cisco Integrated Management Controller.
Documentation Feedback
To provide technical feedback on this document, or to report an error or omission, please send your comments
to [email protected]. We appreciate your feedback.
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, using the Cisco Bug Search Tool (BST), submitting a service
request, and gathering additional information, see What's New in Cisco Product Documentation, at: http://
www.cisco.com/c/en/us/td/docs/general/whatsnew/whatsnew.html.
Subscribe to What's New in Cisco Product Documentation, which lists all new and revised Cisco technical
documentation as an RSS feed and delivers content directly to your desktop using a reader application. The
RSS feeds are a free service.
Cisco UCS Director Installation and Upgrade on Microsoft Hyper-V Manager, Release 5.3
ix
Preface
Obtaining Documentation and Submitting a Service Request
Cisco UCS Director Installation and Upgrade on Microsoft Hyper-V Manager, Release 5.3
x
CHAPTER
1
Overview
This chapter contains the following sections:
• About Cisco UCS Director, page 1
• About Cisco UCS Director for Hyper-V, page 5
• Prerequisites, page 5
• Minimum System Requirements for a Single Node Setup, page 6
• About Licenses, page 7
About 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) 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 network 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.
Cisco UCS Director Installation and Upgrade on Microsoft Hyper-V Manager, Release 5.3
1
Overview
Features and Benefits
• 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.
• 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 in an on-demand manner to your users. You can collaborate with other
experts in your company to quickly and easily create policies and 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, as needed, basis.
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
• Baremetal 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 monitor, provision, and
manage the system across physical, virtual, and baremetal 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
following IT-prescribed policies and governance
Cisco UCS Director Installation and Upgrade on Microsoft Hyper-V Manager, Release 5.3
2
Overview
Features and Benefits
Feature
Benefit
Adaptive provisioning
Dynamic capacity
management
• Provides a real-time available capability, internal policies, and application
workload requirements to optimize the availability of your resources
• Provides continuous monitoring that indicates real-time infrastructure
consumption to improve capacity planning and management
• Identifies underutilized and overutilized resources
Multiple hypervisor support
Computing management
• Supports VMware ESX, ESXi, Microsoft Hyper-V, and Red Hat
hypervisors
• Monitors, manages, and provisions physical, virtual, and baremetal
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 trending 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.
Cisco CloudGenie
• Provides mobile management from Apple iPad and iPhone and Android
devices
• Supports mobile self-service provisioning, virtual machine management,
and viewing of administrative dashboards
Cisco UCS Director Installation and Upgrade on Microsoft Hyper-V Manager, Release 5.3
3
Overview
Physical and Virtual Management Features
Physical and Virtual Management Features
Physical Server Management
• Discover and collect configurations and changes
• Monitor and manage physical servers
• Perform policy-based server provisioning
• Manage blade power
• Manage the server life cycle
• Perform server use trending and capacity
analysis
Virtual Computing Management
• Discover, collect, and monitor virtual computing
environments
• Perform policy-based provisioning and dynamic
resource allocation
• Manage the host server load and power
• Manage the VM life cycle and snapshots
• Perform analytics to assess VM capacity,
sprawl, and host utilization
• Perform baremetal provisioning using preboot
execution environment (PXE) boot management
Physical 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
Physical Network Management
• Discover, collect, and monitor physical network
elements
• Provision VLANs across multiple switches
• Configure Access Control Lists (ACLs) on
network devices
• Configure the storage network
• Implement dynamic network topologies
Virtual Storage Management
• 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
Virtual Network Management
• Add networks to VMs
• Perform policy-based provisioning with IP and
DHCP allocation
• Configure and connect Virtual Network
Interface Cards ( vNICs) to VLANs and private
VLANs
• Create port groups and port profiles for VMs
• Monitor organizational use of virtual networks
Cisco UCS Director Installation and Upgrade on Microsoft Hyper-V Manager, Release 5.3
4
Overview
Model-Based Orchestration
Model-Based Orchestration
The turnkey solution in Cisco UCS Director that allows rapid creation of workflows and templates includes
a task library containing many tasks, as well as out-of-the-box workflows.
Model-based orchestration and a workflow designer enable IT administrators to customize and automate
infrastructure administrative and operational tasks. You can extend and customize the system to meet individual
needs.
Included in the task library are Day 1 through Day 3 maintenance and update activities, as shown in the
following table:
Day-1
Day-2
Day-3
• Add tenants
• Monitor performance
• Add/upgrade hardware
• Migrate or add applications
• Start metering and billing
• Repurpose
• Integrate with enterprise
systems
• Manage tenant changes
• Self-service IaaS
• Use self-service portal
POODLE Vulnerability
To avoid POODLE vulnerability, SSL Version 2 and SSL Version 3 are disabled on Cisco UCS Director
north-bound HTTP interface by configuring Apache Tomcat to allow only TLS . Hence, any north-bound
applications accessing Cisco UCS Director through REST API will be connected through TLS. Also, the
browsers will be connected to Cisco UCS Director through TLS. For more information, refer
http://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20141015-poodle.
About Cisco UCS Director for Hyper-V
Cisco UCS Director can be deployed in a Hyper-V environment.
Note
We recommend deploying Cisco UCS Director on the Hyper-V Manager host, rather than the SCVMM
console.
Prerequisites
• Installation of Hyper-V Manager
• Configured system administrator privileges
• Cisco UCS Director installed on Hyper-V host
Cisco UCS Director Installation and Upgrade on Microsoft Hyper-V Manager, Release 5.3
5
Overview
Minimum System Requirements for a Single Node Setup
Minimum System Requirements for a Single Node Setup
The minimum system requirements depend upon how many 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.
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
8 GB
Hard Disk
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
4
Memory
20 GB
Hard Disk
100 GB
Cisco UCS Director Installation and Upgrade on Microsoft Hyper-V Manager, Release 5.3
6
Overview
About Licenses
Table 3: Recommended Memory Configuration for Cisco UCS Director Services
Service
Recommended
Configuration
File Location
Parameter
broker
256 MB
/opt/infra/broker/run.sh
-Xms -Xmx
client
512 MB
/opt/infra/client/run.sh
-Xms -Xmx
controller
256 MB
/opt/infra/controller/run.sh
-Xms -Xmx
eventmgr
512 MB
/opt/infra/eventmgr/run.sh
-Xms -Xmx
idaccessmgr
512 MB
/opt/infra/idaccessmgr/run.sh
-Xms -Xmx
inframgr
8 GB
/opt/infra/inframgr/run.sh
-Xms -Xmx
Tomcat
1 GB
/opt/infra/web_cloudmgr/apache-tomcat JAVA_OPTS="$JAVA_OPTS
-Xmsm -Xmxm"
/bin/catalina.sh
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
4096 MB
max_connect_errors
10000
connect_timeout
20
innodb_read_io_threads
64
innodb_write_io_threads
64
About Licenses
You must obtain a license to use Cisco UCS Director, as follows:
Cisco UCS Director Installation and Upgrade on Microsoft Hyper-V Manager, Release 5.3
7
Overview
Fulfilling the Product Access Key
1 Before you install Cisco UCS Director, generate the Cisco UCS Director 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 8.
3 After you install Cisco UCS Director, update the license in Cisco UCS Director as described in Updating
the License, on page 14.
4 After the license has been validated, you can start to use Cisco UCS Director.
Fulfilling the Product Access Key
Before You Begin
You need the PAK number.
Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
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
Description
Organization Name
The organization name.
Site Contact Name
The site contact name.
Street Address
The street address of the organization.
City/Town
The city or town.
State/Province
The state or province.
Zip/Postal Code
The zip code or postal code.
Country
The country name.
Click Issue Key.
The features for your license appear, and an email with the Digital License Agreement and a zipped license
file is sent to the email address you provided.
Cisco UCS Director Installation and Upgrade on Microsoft Hyper-V Manager, Release 5.3
8
CHAPTER
2
Installing Cisco UCS Director
This chapter contains the following sections:
• Installing Cisco UCS Director on Microsoft Hyper-V, page 9
• Installing Cisco UCS Director on Microsoft Hyper-V for Windows 2012 R2, page 11
• Configuring the Network Interface using Shelladmin, page 12
• Changing the Default Password, page 13
• Updating the License, page 14
• Changing the Maximum Packet Size, page 14
Installing Cisco UCS Director on Microsoft Hyper-V
Before You Begin
System administrator privileges for Hyper-V are required.
Note
If you do not want to use DHCP, you need the following information: IP address, subnet mask, and default
gateway.
Cisco UCS Director Installation and Upgrade on Microsoft Hyper-V Manager, Release 5.3
9
Installing Cisco UCS Director
Installing Cisco UCS Director on Microsoft Hyper-V
Procedure
Step 1
Step 2
Step 3
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.
Step 4
In the Before You Begin pane, choose the custom configuration option, and click Next.
Step 5
In the Name and Location pane, in the Name field, edit the VM name.
Step 6
In the Name and Location pane, check the Store the virtual machine in a different location checkbox and
specify the alternate location.
Step 7 Click Next.
Step 8 In the Assign Memory pane, enter the amount of memory to allocate to this VM (8 GB minimum) and click
Next.
Step 9 In the Configure Networking pane, in the Connection field, accept the default option Not Connected by
clicking Next.
Step 10 In the Connect Virtual Hard Disk pane, accept the default option Attach a virtual disk later by clicking
Next.
Step 11 In the Completing the New Virtual Machine Wizard pane, verify the settings and click Finish.
Step 12 In the Navigation pane, right-click the new VM.
Step 13 In the Navigation pane, choose IDE Controller 0.
Step 14 In the IDE Controller pane, choose Hard Drive and click Add.
Step 15 In the Hard Drive pane, choose the downloaded Cisco UCS Director .vhd file and click OK.
Step 16 Inspect the virtual hard drive properties.
Step 17 In the Navigation pane, choose Memory.
Step 18 In the Memory pane, enter the recommended value (minimum 8 GB).
Step 19 In the Navigation pane, choose Processor.
Step 20 In the Processor pane, enter the recommended value (4 vCPU).
Step 21 Remove the network adapter that was created when you created the new VM.
Step 22 In the Navigation pane, choose Add Hardware.
Step 23 In the Add Hardware pane, choose Legacy Network Adapter and click OK.
Step 24 In the Navigation pane, choose the legacy network adapter.
Step 25 In the Legacy Network Adapter pane, in the Network field, choose your network and click OK.
Step 26 Verify that you have sufficient vCPU and Memory resources allocated. For the minimum resource requirements,
see Minimum System Requirements for a Single Node Setup, on page 6.
Step 27 Power on the VM.
Optionally you can configure network properties from the shelladmin.
Step 28 After the appliance has booted up, copy and paste the Cisco UCS Director IP address that is displayed into a
supported web browser to access the Login page.
Step 29 At the login prompt, enter admin for username and admin for the password to log into Cisco UCS Director.
Note
Change your administrator password after this initial
login.
Cisco UCS Director Installation and Upgrade on Microsoft Hyper-V Manager, Release 5.3
10
Installing Cisco UCS Director
Installing Cisco UCS Director on Microsoft Hyper-V for Windows 2012 R2
What to Do Next
Update your license.
Installing Cisco UCS Director on Microsoft Hyper-V for Windows
2012 R2
Before You Begin
• System administrator privileges for Hyper-V are required.
• Windows 2012 R2 with Hyper-V Manager version 6.3.9
Procedure
Step 1
Step 2
Step 3
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.
Step 4
In the Before You Begin pane, click Next.
Step 5
In the Name and Location pane, in the Name field, edit the VM name.
Step 6
In the Name and Location pane, check the Store the virtual machine in a different location checkbox and
specify the alternate location.
Click Next.
In the Select Generation pane, choose Generation1.
With Generation1, this virtual machine provides the same virtual hardware to the virtual machine as in
previous versions of Hyper-V.
Step 7
Step 8
Cisco UCS Director Installation and Upgrade on Microsoft Hyper-V Manager, Release 5.3
11
Installing Cisco UCS Director
Configuring the Network Interface using Shelladmin
Step 9
In the Assign Memory pane, enter the amount of memory to allocate to this VM (8 GB minimum) and click
Next.
Step 10 In the Configure Networking pane, in the Connection field, accept the default option Not Connected by
clicking Next.
Step 11 In the Connect Virtual Hard Disk pane, choose Attach a virtual disk later and click Next.
Step 12 In the Completing the New Virtual Machine Wizard pane, verify the settings and click Finish.
Step 13 In the Navigation pane, right-click the new VM and choose Settings.
Step 14 In the Navigation pane, choose IDE Controller 0.
Step 15 In the IDE Controller pane, choose Hard Drive and click Add.
Step 16 In the Hard Drive pane, choose the downloaded Cisco UCS Director .vhd file and click OK.
Step 17 Inspect the virtual hard drive properties.
Step 18 In the Navigation pane, choose Memory.
Step 19 In the Memory pane, enter the recommended value (minimum 8 GB).
Step 20 In the Navigation pane, choose Processor.
Step 21 In the Processor pane, enter the recommended value (4 vCPU).
Step 22 Remove the network adapter that was created when you created the new VM.
Step 23 In the Navigation pane, choose Add Hardware.
Step 24 In the Add Hardware pane, choose Legacy Network Adapter and click OK.
Step 25 In the Navigation pane, choose the legacy network adapter.
Step 26 In the Legacy Network Adapter pane, in the Network field, choose your network and click OK.
Step 27 Verify that you have sufficient vCPU and Memory resources allocated. For the minimum resource requirements,
see Minimum System Requirements for a Single Node Setup, on page 6.
Step 28 Power on the VM.
Optionally you can configure network properties from the shelladmin.
By default, this version of Microsoft Hyper-V uses DHCP by default. If you want to use a static IP address
instead of DHCP, you can change this configuration through the shelladmin.
Step 29 After the appliance has booted up, copy and paste the Cisco UCS Director IP address that is displayed into a
supported web browser to access the Login page.
Step 30 At the login prompt, enter admin for username and admin for the password to log into Cisco UCS Director.
Note
Change your administrator password after this initial
login.
What to Do Next
Update your license.
Configuring the Network Interface using Shelladmin
This procedure is optional.
Cisco UCS Director Installation and Upgrade on Microsoft Hyper-V Manager, Release 5.3
12
Installing Cisco UCS Director
Changing the Default Password
Procedure
Step 1
Log into the Cisco UCS Director VM console with the following credentials:
a) User—shelladmin
b) Password—changeme
If you have already logged into the shelladmin and changed the default password, use your new password
instead.
After you have logged in, you can choose Change shelladmin password to change the default
password.
Step 2
Choose Configure Network Interface.
Step 3
At the Do you want to Configure static IP [y/n] 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 or IPV6. This will be 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 Default Password
Procedure
Step 1
Step 2
Click Administration and choose Users and Groups.
On the Login Users pane, right-click on the admin user.
Step 3
In the Change Password dialog box, enter the new password and confirm it.
Step 4
Click Save.
Cisco UCS Director Installation and Upgrade on Microsoft Hyper-V Manager, Release 5.3
13
Installing Cisco UCS Director
Updating the License
Updating the License
Before You Begin
If you received a zipped license file by email, extract and save the .lic file to your local machine.
Procedure
Step 1
Step 2
Step 3
Step 4
Choose Administration > License.
Click on the License Keys tab.
Click Update License.
In the Update License dialog box, do the following:
• To upload a .lic file, click Browse to the base license's .lic file and select the .lic file, then click
Upload.
Step 5
Click Submit.
The license file is processed, and a message appears confirming the successful update.
Changing the Maximum Packet Size
The default maximum packet (query) size for the Cisco UCS Director 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 requires a larger
packet size.
Note
For a multi-node setup, perform this configuration on the inventory database and monitoring database
nodes.
Procedure
Step 1
In the shelladmin, choose Login as Root to log in to Cisco UCS Director.
Step 2
Navigate to the /etc folder.
Step 3
Open the my.cnf file and locate the max_allowed_packet parameter.
Step 4
Change the value of the max_allowed_packet parameter to max_allowed_packet=100M
Step 5
Save the my.cnf file.
Step 6
In the shelladmin, stop and restart the Cisco UCS Director services on the every node, as follows:
a) Choose Stop services.
b) To verify that all services are stopped, choose Display services status.
Cisco UCS Director Installation and Upgrade on Microsoft Hyper-V Manager, Release 5.3
14
Installing Cisco UCS Director
Changing the Maximum Packet Size
c) After all services have stopped on the node, choose Start services.
Cisco UCS Director Installation and Upgrade on Microsoft Hyper-V Manager, Release 5.3
15
Installing Cisco UCS Director
Changing the Maximum Packet Size
Cisco UCS Director Installation and Upgrade on Microsoft Hyper-V Manager, Release 5.3
16
CHAPTER
3
Configuring a Multi-Node Setup
This chapter contains the following sections:
• About the Multi-Node Setup, page 17
• Minimum System Requirements for a Multi-Node Setup, page 19
• Guidelines and Limitations for a Multi-Node Setup, page 26
• Summary of Steps for Configuring a Multi-Node Setup, page 26
• Creating the Inventory Database, page 27
• Creating the Monitoring Database, page 28
• Creating the Primary Node, page 28
• Creating a Service Node, page 29
• Backing Up with a Multi-Node Setup, page 30
• Restoring with a Multi-Node Setup, page 31
• Removing a Service Node, page 32
• Options for Migrating from a Standalone Appliance to a Multi-Node Setup, page 32
About the Multi-Node Setup
The multi-node setup is supported for Cisco UCS Director on a 64-bit operating system only. With a multi-node
setup, you can scale Cisco UCS Director to support a larger number of VMs than is supported by a single
installation of Cisco UCS Director. This setup includes the following nodes:
• One primary node
• One or more service nodes
• One monitoring database
• One inventory database
Cisco UCS Director Installation and Upgrade on Microsoft Hyper-V Manager, Release 5.3
17
Configuring a Multi-Node Setup
Primary Node
For a multi-node setup, you have to install the license on the primary node only.
Note
A multi-node setup improves scalability by offloading the processing of system tasks, such as inventory data
collection, from the primary node to one or more service nodes. You can assign certain system tasks to one
or more service nodes. The number of nodes determines how the processing of system tasks are scaled.
Node pools combine service nodes into groups and enable you to assign system tasks to more than one service
node. This provides you with control over which system task is executed by which service node or group of
service nodes. If you have multiple service nodes in a node pool and one of the service nodes is busy when a
system task needs to be run, Cisco UCS Director uses a round-robin assignment to determine which service
node should process that system task. if all service nodes are busy, you can have the primary node run the
system task.
However, if you do not need that level of control over the system tasks, you can use the default task policy
and add all of the service nodes to the default node pool. All system tasks are already associated with the
default task policy, and the round-robin assignment will be used to determine which service node should
process a system task.
If you want to have some critical tasks processed only by the primary node, you can assign those tasks to a
local-run policy.
For more information about how to configure the primary node and service nodes, and how to assign system
tasks, see the Cisco UCS Director Administration Guide.
Primary Node
A multi-node setup can have only one primary node. This primary node contains the license for Cisco UCS
Director.
The primary node also contains the configuration for the node pools and the service nodes, along with the list
of which system tasks can be offloaded to the service nodes for processing.
Service Nodes
A multi-node setup can have one or more service nodes. The number of service nodes in a multi-node setup
depends upon the number of devices and VMs you plan to configure and manage through Cisco UCS Director.
Database Nodes
The inventory and monitoring databases are created from the Cisco UCS Director MySQL database. The data
that Cisco UCS Director collects is divided between the two databases. The multi-node setup segregates the
data collection which is historically very heavy on the database into a separate database.
Inventory Database
A multi-node setup can have only one inventory database. This database contains the following:
• Physical and virtual accounts and their related inventory data
• Data used in the normal operation of Cisco UCS Director for all supported features
Cisco UCS Director Installation and Upgrade on Microsoft Hyper-V Manager, Release 5.3
18
Configuring a Multi-Node Setup
Minimum System Requirements for a Multi-Node Setup
Monitoring Database
A multi-node setup can have only one monitoring database. This database contains the data that Cisco UCS
Director uses for historical computations, such as aggregations and trend reports.
The parameters of the monitoring database depend upon the number of devices and VMs you plan to configure
and manage through Cisco UCS Director
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
Cisco UCS Director Installation and Upgrade on Microsoft Hyper-V Manager, Release 5.3
19
Configuring a Multi-Node Setup
Minimum System Requirements for a Small Multi-Node Setup
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
broker
512 MB
/opt/infra/broker/run.sh
-Xms -Xmx
client
512 MB
/opt/infra/client/run.sh
-Xms -Xmx
controller
512 MB
/opt/infra/controller/run.sh
-Xms -Xmx
eventmgr
512 MB
/opt/infra/eventmgr/run.sh
-Xms -Xmx
idaccessmgr
512 MB
/opt/infra/idaccessmgr/run.sh
-Xms -Xmx
inframgr
8 GB
/opt/infra/inframgr/run.sh
-Xms -Xmx
Tomcat
2 GB
/opt/infra/web_cloudmgr/apache-tomcat JAVA_OPTS="$JAVA_OPTS
-Xmsm -Xmxm"
/bin/catalina.sh
Minimum Configuration for the Inventory and Monitoring Databases
Component
Minimum Supported Configuration
thread_cache_size
1000
Cisco UCS Director Installation and Upgrade on Microsoft Hyper-V Manager, Release 5.3
20
Configuring a Multi-Node Setup
Minimum System Requirements for a Medium Multi-Node Setup
Component
Minimum Supported Configuration
max_connections
1000
innodb_lock_wait_timeout
100
query_cache_size
128 MB
innodb_buffer_pool_size
24576 MB
max_connect_errors
10,000
connect_timeout
20
innodb_read_io_threads
64
innodb_write_io_threads
64
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
Cisco UCS Director Installation and Upgrade on Microsoft Hyper-V Manager, Release 5.3
21
Configuring a Multi-Node Setup
Minimum System Requirements for a Medium Multi-Node Setup
Minimum Requirements for the Inventory Database
Element
Minimum Supported Requirement
vCPU
8
Memory
60 GB
Hard disk
100 GB (SSD type storage)
Minimum 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
broker
1 GB
/opt/infra/broker/run.sh
-Xms -Xmx
client
1 GB
/opt/infra/client/run.sh
-Xms -Xmx
controller
1 GB
/opt/infra/controller/run.sh
-Xms -Xmx
eventmgr
256 MB
/opt/infra/eventmgr/run.sh
-Xms -Xmx
idaccessmgr
1 GB
/opt/infra/idaccessmgr/run.sh
-Xms -Xmx
inframgr
12 GB
/opt/infra/inframgr/run.sh
-Xms -Xmx
Tomcat
4 GB
/opt/infra/web_cloudmgr/apache-tomcat JAVA_OPTS="$JAVA_OPTS
-Xmsm -Xmxm"
/bin/catalina.sh
Minimum Inventory Database Configuration
Component
Minimum Supported Configuration
thread_cache_size
2000
max_connections
2000
Cisco UCS Director Installation and Upgrade on Microsoft Hyper-V Manager, Release 5.3
22
Configuring a Multi-Node Setup
Minimum System Requirements for a Large Multi-Node Setup
Component
Minimum Supported Configuration
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
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
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
Cisco UCS Director Installation and Upgrade on Microsoft Hyper-V Manager, Release 5.3
23
Configuring a Multi-Node Setup
Minimum System Requirements for a Large Multi-Node Setup
• 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
60 GB
Hard disk
100 GB
Minimum Requirements for the Inventory Database
Element
Minimum Supported Requirement
vCPU
8
Memory
120 GB
Hard disk
200 GB (SSD type storage)
Minimum 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
broker
2 GB
/opt/infra/broker/run.sh
-Xms -Xmx
client
2 GB
/opt/infra/client/run.sh
-Xms -Xmx
controller
2 GB
/opt/infra/controller/run.sh
-Xms -Xmx
Cisco UCS Director Installation and Upgrade on Microsoft Hyper-V Manager, Release 5.3
24
Configuring a Multi-Node Setup
Minimum System Requirements for a Large Multi-Node Setup
Service
Recommended
Configuration
File Location
Parameter
eventmgr
256 MB
/opt/infra/eventmgr/run.sh
-Xms -Xmx
idaccessmgr
2 GB
/opt/infra/idaccessmgr/run.sh
-Xms -Xmx
inframgr
24 GB
/opt/infra/inframgr/run.sh
-Xms -Xmx
Tomcat
8 GB
/opt/infra/web_cloudmgr/apache-tomcat JAVA_OPTS="$JAVA_OPTS
-Xmsm -Xmxm"
/bin/catalina.sh
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
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
Cisco UCS Director Installation and Upgrade on Microsoft Hyper-V Manager, Release 5.3
25
Configuring a Multi-Node Setup
Guidelines and Limitations for a Multi-Node Setup
Component
Minimum Supported Configuration
max_connect_errors
10,000
connect_timeout
20
innodb_read_io_threads
64
innodb_write_io_threads
64
Guidelines and Limitations for a Multi-Node Setup
Before you configure a multi-node setup for Cisco UCS Director, consider the following:
• The multi-node setup is supported for Cisco UCS Director on a 64-bit operating system only.
• Your multi-node setup can have only one primary node.
• You must plan the location and IP addresses of your nodes carefully as you cannot reconfigure the types
of most nodes later. You can only reconfigure a service node as a primary node. You cannot make any
other changes to the type of node. For example, you cannot reconfigure a primary node as a service node
or an inventory database node as a monitoring database node.
• You have to install the license on the primary node only.
• After you configure the nodes, the list of operations available in the shelladmin changes for the service
nodes, the inventory database node, and the monitoring database node.
Summary of Steps for Configuring a Multi-Node Setup
This procedure provides a high-level summary of the steps involved in configuring a multi-node setup.
Note
Plan your multi-node setup carefully. You can only change a service node to a primary node. You cannot
change any other type of node after you configure it. For example, you cannot reconfigure a primary node
as a service node or an inventory database node as a monitoring database node.
Procedure
Step 1
Deploy a Cisco UCS Director VM for each node in the multi-node setup.
For example, if your multi-node setup, includes a primary node, an inventory database, a monitoring database,
and three service nodes, deploy six Cisco UCS Director VMs.
Step 2
In the Cisco UCS Director shelladmin, configure the nodes in the following order:
1 Creating the Inventory Database, on page 27
2 Creating the Monitoring Database, on page 28
Cisco UCS Director Installation and Upgrade on Microsoft Hyper-V Manager, Release 5.3
26
Configuring a Multi-Node Setup
Creating the Inventory Database
3 Creating the Primary Node, on page 28
4 Creating a Service Node, on page 29
You must create and start the inventory database and the monitoring database nodes before you
configure the primary node and any service nodes.
Update the license file in the Cisco UCS Director that will be the primary node.
You do not need to update the license file on any other node.
Note
Step 3
See Updating the License, on page 14.
Step 4
In Cisco UCS Director on the primary node, configure the system tasks as follows:
a) Create one or more node pools if you want to control the assignment of system tasks by service node, or
accept the default node pool.
b) Create one or more system task policies if you want to control the assignment of system tasks by service
node, or accept the default task policy.
c) Configure the service nodes.
d) Configure the primary node.
e) Assign the system tasks to system policies if you want to control the assignment of system tasks by service
node.
See the Cisco UCS Director Administration Guide.
Creating the Inventory Database
Procedure
Step 1
Step 2
Log into the Cisco UCS Director shelladmin on the inventory database node.
From the Cisco UCS Director Shell menu, choose Configure Multi-Node Setup and press Enter.
Step 3
From the menu, choose Configure Multi Node Setup (Advanced Deployment) and press
Enter.
When prompted, press 1 to configure the current node.
When prompted, press y and then select the option to configure the node as the inventory database node.
From the menu, choose Configure Inventory Database and press Enter.
Step 4
Step 5
Step 6
Step 7
Step 8
When prompted, press Enter to continue.
To verify that the services for the inventory database are up and running, choose Display Services
Status and press Enter.
You should see the following lines:
2838 ?
3172 ?
00:00:00 mysqld_safe
3-02:51:38 mysqld
After you return to the shelladmin, the menu options change to those available for an inventory database node.
Cisco UCS Director Installation and Upgrade on Microsoft Hyper-V Manager, Release 5.3
27
Configuring a Multi-Node Setup
Creating the Monitoring Database
Creating the Monitoring Database
Procedure
Step 1
Step 2
Log into the Cisco UCS Director shelladmin on the monitoring database node.
From the Cisco UCS Director Shell menu, choose Configure Multi-Node Setup and press Enter.
Step 3
From the menu, choose Configure Multi Node Setup (Advanced Deployment) and press
Enter.
When prompted, press 1 to configure the current node.
When prompted, press y and then select the option to configure the node as the monitoring database node.
Step 4
Step 5
Step 6
Step 7
Step 8
From the menu, choose Configure Monitoring Database and press Enter.
When prompted, press Enter to continue.
To verify that the services for the monitoring database are up and running, choose Display Services
Status and press Enter.
You should see the following lines:
2838 ?
3172 ?
00:00:00 mysqld_safe
3-02:51:38 mysqld
After you return to the shelladmin, the menu options change to those available for a monitoring database node.
Creating the Primary Node
Before You Begin
The inventory and monitoring databases must be up and running before you create the primary node.
Note
Do not run any daemons on the primary database.
Cisco UCS Director Installation and Upgrade on Microsoft Hyper-V Manager, Release 5.3
28
Configuring a Multi-Node Setup
Creating a Service Node
Procedure
Step 1
Step 2
Log into the Cisco UCS Director shelladmin on the primary node.
From the Cisco UCS Director Shell menu, choose Configure Multi-Node Setup and press Enter.
Step 3
From the menu, choose Configure Multi Node Setup (Advanced Deployment) and press
Enter.
When prompted, press 1 to configure the current node.
When prompted, press y and then select the option to configure the node as the primary node.
From the menu, choose Configure Primary Node and press Enter.
Step 4
Step 5
Step 6
Step 7
At the Provide Inventory DB IP prompt, enter the IP address assigned to the Cisco UCS Director VM for the
inventory database.
This step registers the VM as a primary node with the inventory database.
Step 8
At the Provide Monitoring DB IP prompt, enter the IP address assigned to the Cisco UCS Director VM for
the monitoring database.
This step registers the VM as a primary node with the monitoring database.
Step 9 When prompted, press Enter to continue.
Step 10 To verify that the services for the primary node are up and running, choose Display Services Status
and press Enter.
You should see the following lines:
Service
---------broker
controller
eventmgr
client
idaccessmgr
inframgr
TOMCAT
websock
Status
---------RUNNING
RUNNING
RUNNING
RUNNING
RUNNING
RUNNING
RUNNING
RUNNING
PID
----25677
25715
25749
25808
25854
25911
25967
26009
Node Type : primary
Inventory DB( 172.29.109.135:3306 ) status
Monitor DB( 172.29.109.144:3306 ) status : UP
Press return to continue ...
: UP
After you return to the shelladmin, the menu options change to those available for a primary node.
Creating a Service Node
Before You Begin
The inventory and monitoring databases must be up and running before you create the primary node.
Cisco UCS Director Installation and Upgrade on Microsoft Hyper-V Manager, Release 5.3
29
Configuring a Multi-Node Setup
Backing Up with a Multi-Node Setup
Procedure
Step 1
Step 2
Log into the Cisco UCS Director shelladmin on the service node.
From the Cisco UCS Director Shell menu, choose Configure Multi-Node Setup and press Enter.
Step 3
From the menu, choose Configure Multi Node Setup (Advanced Deployment) and press
Enter.
When prompted, press 1 to configure the current node.
When prompted, press y and then select the option to configure the node as the secondary node.
From the menu, choose Configure Service Node and press Enter.
Step 4
Step 5
Step 6
Step 7
At the Provide Inventory DB IP prompt, enter the IP address assigned to the Cisco UCS Director VM for the
inventory database.
This step registers the VM as a service node with the inventory database.
Step 8
At the Provide Monitoring DB IP prompt, enter the IP address assigned to the Cisco UCS Director VM for
the monitoring database.
This step registers the VM as a service node with the monitoring database.
Step 9 When prompted, press Enter to continue.
Step 10 To verify that the services for the service node are up and running, choose Display Services Status
and press Enter.
You should see the following lines:
Service
---------broker
controller
eventmgr
client
idaccessmgr
inframgr
TOMCAT
websock
Status
---------RUNNING
RUNNING
RUNNING
RUNNING
RUNNING
RUNNING
RUNNING
RUNNING
PID
----25677
25715
25749
25808
25854
25911
25967
26009
Node Type : service
Inventory DB( 172.29.109.135:3306 ) status
Monitor DB( 172.29.109.144:3306 ) status : UP
Press return to continue ...
: UP
After you return to the shelladmin, the menu options change to those available for a service node.
Step 11 Repeat this procedure for every service node.
Backing Up with a Multi-Node Setup
This procedure provides a high-level summary of the steps required to back up a multi-node setup.
Cisco UCS Director Installation and Upgrade on Microsoft Hyper-V Manager, Release 5.3
30
Configuring a Multi-Node Setup
Restoring with a Multi-Node Setup
The backup procedure requires you to first stop the Cisco services. This must be done before you work with
the Monitoring and Inventory databases. Then you back up the databases, after which you re-start the services,
starting with the Primary node.
Before You Begin
To back up the databases, you use an FTP server, for which you will need:
• An FTP server account and the IP address
• The FTP server's login credentials
• Backup file name(s)
Procedure
Step 1
Step 2
Step 3
Step 4
Shut down the services for both the Primary and Service nodes. Use Shell option 3, Stop Services.
Back up the Monitoring database. Use the Shell Backup Database option.
Backup the Inventory database. Use the Shell Backup Database option.
Start the Services (Service nodes first, followed by Primary node). Use Shell option 4, Start Services.
Restoring with a Multi-Node Setup
This procedure provides a high-level summary of the steps required to restore a multi-node setup.
The restore procedure requires you to first stop the Cisco services. This must be done before you work with
the Monitoring and Inventory databases. Then you restore the databases, after which you re-start the services,
starting with the Primary node.
Before You Begin
To restore the databases, you use an FTP server, for which you will need:
• An FTP server account and the IP address
• The FTP server's login credentials
• Backup file name(s)
Procedure
Step 1
Step 2
Step 3
Step 4
Shut down the services for both the Primary and Service nodes. Use Shell option 3, Stop Services.
Restore the Monitoring database. Use the Shell Restore Database option.
Restore the Inventory database. Use the Shell Restore Database option.
Start the Services (Service nodes first, followed by Primary node). Use Shell option 4, Start Services.
Cisco UCS Director Installation and Upgrade on Microsoft Hyper-V Manager, Release 5.3
31
Configuring a Multi-Node Setup
Removing a Service Node
Removing a Service Node
This procedure provides a high-level summary of the steps required to remove a service node from a multi-node
setup.
The removal procedure requires you to first stop the Cisco services. This must be done before you remove a
service node from Monitoring and Inventory databases.
Procedure
Step 1
Step 2
Step 3
Step 4
Shut down the services for both the Primary node and the Service node(s). Use Shell option 3, Stop Services.
Start the services on the Service node(s) that you want to be active and operational. Use Shell option 4, Start
Services.
Start the services on the Primary node. Use Shell option 4, Start Services.
Using the Cisco UCS Director GUI, delete the Service node that you want to remove.
This removes the respective Service node from the database.
Options for Migrating from a Standalone Appliance to a
Multi-Node Setup
All requirements and configuration for a multi-node setup must be completed before you attempt to migrate
from a standalone appliance to a multi-node setup. Please refer to the requirements and instructions pertaining
to the multi-node setup you are planning to implement before proceeding.
Refer to the most recent Release Notes and ReadMe file for up-to-date information about support for migrating
from a previous release of a Cisco UCS Director standalone appliance to a multi-node setup on the current
release. Single to multi-node migration from some earlier releases to the current release may not be supported.
Note
You must upgrade to Cisco UCS Director, Release 4.0 or later, before you can migrate to a multi-node
setup and backup the database.
You can choose between the following options for migrating a Cisco UCS Director standalone appliance to
a multi-node setup:
• You restore a backup of the entire database from Cisco UCS Director, Release 4.0, to the Cisco UCS
Director, Release 4.1 monitoring database and inventory database nodes. This option is similar to the
database backup and restore you can perform through shelladmin.
• You back up the database from Cisco UCS Director, Release 4.0, separately for the inventory database
and monitoring database nodes. If you choose this option, only selected database tables are backed up
and restored to the monitoring and inventory databases. This option requires you to execute custom
scripts from /opt/infra.
• You perform a back up that involves using custom scripts twice, once for the inventory database and
once for the Monitor database. The backed up databases will have tables that are built selectively for
Cisco UCS Director Installation and Upgrade on Microsoft Hyper-V Manager, Release 5.3
32
Configuring a Multi-Node Setup
Migrating a Release 4.0 Standalone Appliance to a Multi-Node Setup with a Full Database Backup
the node type. You then copy the backed up appliance file to the relevant node and execute the custom
script again. But this time you execute the script in each Inventory and Monitor node.
Detailed instructions for these options follow in this section.
Migrating a Release 4.0 Standalone Appliance to a Multi-Node Setup with a
Full Database Backup
This procedure restores all database tables to the inventory database and the monitoring database.
Before You Begin
You must have an FTP server with valid credentials to perform a backup and restore of the database.
Procedure
Step 1
In the shelladmin, upgrade the Cisco UCS Director, Release 4.0, standalone appliance to Cisco UCS Director,
Release 4.1 with the Apply Patch option.
For more information, see the following topics in the installation and upgrade guide for release 4.1:
• Upgrading from Cisco UCS Director, Release 4.0 to Release 4.1
• Upgrading from Cisco Unified Infrastructure Controller 3.x 32-bit to Cisco UCS Director, Release 4.1
64-bit
Step 2
Step 3
In the shelladmin, choose Backup Database to backup the full database of the upgraded Cisco UCS
Director.
Deploy a Cisco UCS Director VM for each node in the multi-node setup.
For example, if your multi-node setup, includes a primary node, an inventory database, a monitoring database,
and three service nodes, deploy six Cisco UCS Director VMs.
Step 4
In the shelladmin, configure the nodes in the following order:
1 Creating the Inventory Database, on page 27
2 Creating the Monitoring Database, on page 28
3 Creating the Primary Node, on page 28
4 Creating a Service Node, on page 29
Step 5
You must create and start the inventory database and the monitoring database nodes before you
configure the primary node and any service nodes.
In the shelladmin, choose Stop services to stop the Cisco UCS Director services.
Step 6
Choose Restore database to import and restore the database backup that you took in Step 2.
Step 7
When prompted, choose Start services to start the Cisco UCS Director services.
After you log in to the primary node, all data from the database in the Cisco UCS Director, Release 4.0,
standalone appliance should be available.
Note
Cisco UCS Director Installation and Upgrade on Microsoft Hyper-V Manager, Release 5.3
33
Configuring a Multi-Node Setup
Migrating a Release 4.0 Standalone Appliance to a Multi-Node Setup with a Selected Database Backup
Migrating a Release 4.0 Standalone Appliance to a Multi-Node Setup with a
Selected Database Backup
This procedure backs up and restores only the selected database tables required for each of the inventory
database and the monitoring database.
Before You Begin
You must have an FTP server with valid credentials to perform a backup and restore of the database.
Procedure
Step 1
In the shelladmin, upgrade the Cisco UCS Director, Release 4.0, standalone appliance to Cisco UCS Director,
Release 4.1 with the Apply Patch option.
For more information, see the following topics in the installation and upgrade guide for release 4.1:
• Upgrading from Cisco UCS Director, Release 4.0 to Release 4.1
• Upgrading from Cisco Unified Infrastructure Controller 3.x 32-bit to Cisco UCS Director, Release 4.1
64-bit
Step 2
In the shelladmin, choose Login as Root to log in to the upgraded Cisco UCS Director.
Step 3
Back up the database tables required for the inventory database, as follows:
a) Navigate to the /opt/infra folder.
cd /opt/infra
b) From Infra, run the dbInfraBackupRestore.sh script.
# ./dbInfraBackupRestore.sh backup
This script takes a database backup with the tables required for the inventory database.
c) After the script has been executed, check for an output file in /tmp folder named
infra_database_backup.tar.gz.
Step 4
Back up the database tables required for the monitoring database, as follows:
a) Navigate to the /opt/infra folder.
cd /opt/infra
b) From Infra, run the dbMonitoringBackupRestore.sh script.
# ./dbMonitoringBackupRestore.sh backup
This script takes a database backup with the tables required for the monitoring database.
c) After the script has been executed, check for an output file in /tmp folder named
monitoring_database_backup.tar.gz.
Step 5
Deploy a Cisco UCS Director VM for each node in the multi-node setup.
Cisco UCS Director Installation and Upgrade on Microsoft Hyper-V Manager, Release 5.3
34
Configuring a Multi-Node Setup
Migrating a Release 4.0 Standalone Appliance to a Multi-Node Setup with a Selected Database Backup
For example, if your multi-node setup, includes a primary node, an inventory database, a monitoring database,
and three service nodes, deploy six Cisco UCS Director VMs.
Step 6
In the shelladmin, configure the nodes in the following order:
1 Creating the Inventory Database, on page 27
2 Creating the Monitoring Database, on page 28
3 Creating the Primary Node, on page 28
4 Creating a Service Node, on page 29
You must create and start the inventory database and the monitoring database nodes before you
configure the primary node and any service nodes.
In the shelladmin, choose Stop services to stop the Cisco UCS Director services on the primary node
and all service nodes.
Restore the database to the inventory database, as follows:
a) Copy the infra_database_backup.tar.gz to the /tmp folder on the node that hosts the inventory
database.
b) On the inventory database node, navigate to the /opt/infra folder.
Note
Step 7
Step 8
cd /opt/infra
c) From Infra, run the dbInfraBackupRestore.sh script.
# ./dbInfraBackupRestore.sh restore
The script restores the database backup from the backup file in the /tmp folder .
Step 9
Restore the database to the monitoring database, as follows:
a) Copy the monitoring_database_backup.tar.gz to the /tmp folder on the node that hosts the
monitoring database.
b) Navigate to the /opt/infra folder.
cd /opt/infra
c) From Infra, run the dbMonitoringBackupRestore.sh script.
# ./dbMonitoringBackupRestore.sh restore
The script restores the database backup from the backup file in the /tmp folder .
Step 10 Choose Start services on the primary node and all service nodes to start the Cisco UCS Director
services.
After you log in to the primary node, all data from the database in the Cisco UCS Director, Release 4.0,
standalone appliance should be available.
Cisco UCS Director Installation and Upgrade on Microsoft Hyper-V Manager, Release 5.3
35
Configuring a Multi-Node Setup
Migrating a Release 4.1 Standalone Appliance to a Multi-Node Setup with Selective Database Table Backup
Migrating a Release 4.1 Standalone Appliance to a Multi-Node Setup with
Selective Database Table Backup
To perform this migration to a multiple node setup, your back up involves using custom scripts twice, once
for the inventory database and once for the Monitor database. The backed up databases have tables that are
built selectively for the node type. To restore to the multi-node setup, you copy the backed up appliance file
to the relevant node and execute the custom script again in each Inventory and Monitor node.
Steps for Backup and Restore for Standalone
Multi node
The DB backup step involves executing custom script which needs to be
executed twice, one for Inventory DB and other for Monitor DB.
The backed up DB will have selective tables that are relevant to the node type.
DB Backup
1st DB Backup for Inventory Node
- Login as root user
cd /opt/infra
From Infra execute the dbInfraBackupRestore.sh as shown below
#. /dbInfraBackupRestore.sh backup
This script will take a backup with necessary tables
for inventory node.
Once the script is executed, check for the output file
in /tmp folder with name as infra_database_backup.tar.gz
- 2nd DB Backup for Monitor Node
- Login as root user
cd /opt/infra
From Infra execute the dbMonitoringBackupRestore.sh as shown below
#. / dbMonitoringBackupRestore.sh backup
This script will take a backup with necessary tables for monitor node.
Once the script is executed, check for the output file in /tmp folder
with name as monitoring_database_backup.tar.gz
DB Restore
Stop services on Primary Node & Service Node. In case of more than
one Services nodes, Stop services on all the nodes.
To restore the DB on Inventory and Monitor node, user needs to
copy the backed up file from backup appliance to the relevant node.
After the files are placed on the nodes, user needs to execute the
custom script again. But this time the script needs to be
executed individually in each node (Inventory and Monitor nodes).
- 1st DB Restore for Inventory Node
- Login as root user
Copy the backup file (infra_database_backup.tar.gz) from the backup
appliance to /tmp folder in the Inventory node appliance.
In the Inventory node appliance
cd /opt/infra
From Infra execute the dbInfraBackupRestore.sh as shown below
#. /dbInfraBackupRestore.sh restore
This script will restore the DB from backup file
(infra_database_backup.tar.gz) placed in /tmp folder.
- 2nd DB Restore for Monitor Node
- Login as root user
Copy the backup file (monitoring_database_backup.tar.gz) from the backup
appliance to /tmp folder in the Monitor node appliance.
In the Monitor node appliance
Cisco UCS Director Installation and Upgrade on Microsoft Hyper-V Manager, Release 5.3
36
Configuring a Multi-Node Setup
Migrating a Release 4.1 Standalone Appliance to a Multi-Node Setup with Selective Database Table Backup
cd /opt/infra
From Infra execute the dbMonitoringBackupRestore.sh as shown below
#. / dbMonitoringBackupRestore.sh restore
This script will restore the DB from backup file
(monitoring_database_backup.tar.gz) placed in /tmp folder.
Before You Begin
Procedure
Step 1
Start the database backup with the Inventory node.
a) Login as root user.
b) cd /opt/infra
c) From infra, execute the dbInfraBackupRestore.sh script as shown below.
#. /dbInfraBackupRestore.sh backup
This script will make a backup with the necessary tables for the Inventory node.
d) After the script has executed, check in the /tmp folder for the output file, which will have a name something
like infra_database_backup.tar.gz.
Although actual file names may vary. This is the given name for the purposes of this explanation.
Step 2
Continue the database backup with the Monitor node.
a) Login as root user.
b) cd /opt/infra
c) From infra, execute the dbMonitoringBackupRestore.sh as shown below.
#. / dbMonitoringBackupRestore.sh backup
This script will make a backup with the necessary tables for the Monitor node.
d) After the script has executed, check in the /tmp folder for the output file, which will have a name something
like monitoring_database_backup.tar.gz.
Troubleshooting Tips
This ends the database backup procedures. Next, you restore the database on each Inventory and Monitor
node. This involves copying each backed up file from the backup appliance to the appropriate node. After the
files are placed on the nodes, execute the script again. This time, however, you execute the script individually
in each node (that is, in each Inventory and Monitor node).
Step 3
Start the database restore process by stopping services.
a) Stop services on the Primary node.
b) Stop services on the Service node(s). If there are multiple Services nodes, stop services on all of them.
Step 4
Restore the database on each Inventory and Monitor node.
a) Copy each backed up file from the backup appliance to the appropriate node.
b) After the files are placed on the nodes, execute the script again. But this time, execute the script individually
in each node (in each Inventory and Monitor node).
Step 5
Start the first database Restore process with the Inventory Node.
a) Login as root user.
b) Copy the backup file, infra_database_backup.tar.gz, from the backup appliance to the /tmp folder in
the Inventory node appliance.
c) In the Inventory node appliance, use cd /opt/infra
d) From infra, execute the dbInfraBackupRestore.sh script as shown below.
#. /dbInfraBackupRestore.sh restore
Cisco UCS Director Installation and Upgrade on Microsoft Hyper-V Manager, Release 5.3
37
Configuring a Multi-Node Setup
Migrating a Release 4.1 Standalone Appliance to a Multi-Node Setup with Selective Database Table Backup
This script will restore the database from the backup file, infra_database_backup.tar.gz, placed in /tmp
folder.
Step 6
Continue the database Restore process with the Monitor Node.
a) Login as root user.
b) Copy the backup file, monitoring_database_backup.tar.gz, from the backup appliance to the /tmp folder
in the Monitor node appliance.
c) In the Monitor node appliance, use cd /opt/infra
d) From infra, execute the dbMonitoringBackupRestore.sh script as shown below.
#. / dbMonitoringBackupRestore.sh restore
This script will restore the database from the backup file, monitoring_database_backup.tar.gz, placed in
/tmp folder.
What to Do Next
Test thoroughly.
Cisco UCS Director Installation and Upgrade on Microsoft Hyper-V Manager, Release 5.3
38
CHAPTER
4
Restarting Cisco UCS Director
This chapter contains the following sections:
• Restarting Cisco UCS Director, page 39
Restarting Cisco UCS Director
If you see errors after installing Cisco UCS Director, log into the Secure Shell (SSH) client and run scripts to
verify whether services are running or not.
Procedure
Step 1
Using the Cisco UCS Director IP address, log in with the following credentials:
a) User—shelladmin
b) Password—changeme
If you have already logged into the shelladmin and changed the default password, use your new password
instead.
After you have logged in, you can choose Change shelladmin password to change the default
password.
Step 2
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.
Step 3
Verify that the following services appear:
1.
2.
3.
4.
5.
6.
7.
8.
9.
Broker
Controller
Eventmgr
Client
Idaccessmgr
Inframgr
Tomcat
Websock
Database (mysqld)
Note
Services that start in the background do not appear in the window.
Cisco UCS Director Installation and Upgrade on Microsoft Hyper-V Manager, Release 5.3
39
Restarting Cisco UCS Director
Restarting Cisco UCS Director
Step 4
Choose Stop services.
Step 5
To verify that all services are stopped, choose Display services status.
Step 6
To restart services, choose Start services.
Cisco UCS Director Installation and Upgrade on Microsoft Hyper-V Manager, Release 5.3
40
CHAPTER
5
Upgrading Cisco UCS Director
This chapter contains the following sections:
• Supported Upgrade Paths for Cisco UCS Director, page 41
• Upgrading a Single Node Setup to Release 5.3, page 42
• Upgrading a Multi-Node Setup to Release 5.3, page 43
Supported Upgrade Paths for Cisco UCS Director
The upgrade path to Cisco UCS Director, Release 5.3 depends upon your current version of Cisco UCS
Director. The following are the supported upgrade paths for Cisco UCS Director, Release 5.3.
Note
From Release 5.3.1.0 and onwards, the upgrade checks for valid target paths and will upgrade only if the
upgrade path from the appliance version and target version is supported.
Upgrade Paths for Release 5.3.x.x
The upgrade paths for Cisco UCS Director, Release 5.3.x.x are as follows:
• From Release 5.3.0.0 to Release 5.3.x.x
• From Release 5.3.0.1, you must first upgrade to Cisco UCS Director, Release 5.3.1.x and then upgrade
to Cisco UCS Director, Release 5.3.2.x.
• From Release 5.3.0.2 to Release 5.3.x.x
• From Release 5.3.1.0 to Release 5.3.x.x
• From Release 5.3.1.1 to Release 5.3.x.x
• From Release 5.3.1.2 to Release 5.3.x.x
Upgrade Paths for Release 5.2.x.x
The upgrade paths for Cisco UCS Director, Release 5.2.x.x are as follows:
Cisco UCS Director Installation and Upgrade on Microsoft Hyper-V Manager, Release 5.3
41
Upgrading Cisco UCS Director
Upgrading a Single Node Setup to Release 5.3
• From Release 5.2.0.0 to Release 5.3.x.x
• From Release 5.2.0.1 to Release 5.3.x.x
• From Release 5.2.0.2 to Release 5.3.x.x.
• From Release 5.2.0.2A to Release 5.3.x.x
• From Release 5.2.0.3 to Release 5.3.1.2 and later
Note
Due to database changes, you cannot upgrade from Release 5.2.0.3 to a release prior to Release 5.3.1.2.
Upgrade Path for Release 5.1.x.x
You can upgrade directly from Cisco UCS Director, Release 5.1.x.x to Cisco UCS Director, Release 5.3.x.x.
Upgrade Paths for Release 5.0.x.x and Earlier Releases
To upgrade from Release 5.0.x.x or an earlier release, you must first upgrade to Cisco UCS Director, Release
5.1.x.x and then upgrade to Cisco UCS Director, Release 5.3.x.x.
For information about how to upgrade to previous releases of Cisco UCS Director, see the installation and
upgrade guide for that release. For example, if you need to upgrade from Release 3.x, you must first upgrade
to Release 4.0 and then follow that upgrade path.
Upgrading a Single Node Setup to Release 5.3
Follow this procedure to upgrade from Cisco UCS Director, Release 5.0, 5.1, or 5.2. If you need to upgrade
from an earlier release, see the "Supported Upgrade Paths for Cisco UCS Director" topic above.
Before You Begin
• Download the Cisco UCS Director, Release 5.3 patch from http://www.cisco.com.
• Place the software in the FTP or HTTP server that you plan to use to install the upgrade.
• If NFS mount is used for application storage, disable it before you apply a patch. If you do not, the
upgrade will fail.
Note
We recommend that you take a snapshot of the VM before you begin the upgrade. If you do this, you do
not need to back up the existing configuration database through an FTP server.
Cisco UCS Director Installation and Upgrade on Microsoft Hyper-V Manager, Release 5.3
42
Upgrading Cisco UCS Director
Upgrading a Multi-Node Setup to Release 5.3
Procedure
Step 1
Step 2
Start your current version of Cisco UCS Director (Release 5.0, Release 5.1, or Release 5.2).
In the ShellAdmin, choose Stop services to stop all services.
Step 3
To verify that all services are stopped, choose Display services status.
Step 4
(Optional) If desired, you can choose Backup database to back up the Cisco UCS Director database.
You do not need to back up the database if you took a snapshot of the VM before you started.
Step 5
To upgrade Cisco UCS Director to Release 5.3, choose Apply patch.
Step 6
When prompted, enter the location of the Release 5.3 patch.
ftp://username:password@hostname|IP_address/software_location_and_name
Step 7
Step 8
Wait for the download and installation to complete.
When prompted, choose Start services to start services and complete the upgrade process.
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 Cisco UCS Director services have started, Cisco
UCS Director is available, the login screen is displayed, and the admin user can log in to Cisco UCS
Director.
All Cisco UCS Director services must be started before you attempt to perform other shelladmin
procedures, such as apply additional patches, take a database backup, or restore a database from a
backup.
Step 9 When the upgrade is complete, choose Show Version in ShellAdmin to verify the current version of Cisco
UCS Director.
Step 10 After upgrading, reboot the Cisco UCS Director VM to update the kernel version.
Upgrading a Multi-Node Setup to Release 5.3
Perform these steps on the primary node and all service nodes. You do not need to upgrade the inventory
database or monitoring database nodes.
Follow this procedure to upgrade from Cisco UCS Director, Release 5.0, 5.1, or 5.2. If you need to upgrade
from an earlier release, see the "Supported Upgrade Paths for Cisco UCS Director" topic above.
Before You Begin
• Download the Cisco UCS Director, Release 5.3 patch from http://www.cisco.com.
• Place the software in the FTP or HTTP server that you plan to use to install the upgrade.
• If NFS mount is used for application storage, disable it before you apply a patch. If you do not, the
upgrade will fail.
Cisco UCS Director Installation and Upgrade on Microsoft Hyper-V Manager, Release 5.3
43
Upgrading Cisco UCS Director
Upgrading a Multi-Node Setup to Release 5.3
Note
We recommend that you take a snapshot of the VM before you begin the upgrade. If you do this, you do
not need to back up the existing configuration database through an FTP server.
Procedure
Step 1
Step 2
Start the primary and service nodes for your current version of Cisco UCS Director (Release 5.0, Release 5.1,
or Release 5.2).
In the ShellAdmin for the primary and all service nodes, choose Stop services to stop all services.
Step 3
To verify that all services are stopped, choose Display services status.
Step 4
(Optional) If desired, you can choose Backup database on the inventory database and monitoring
database nodes to back up the Cisco UCS Director database.
You do not need to back up the database if you took a snapshot of the VM before you started.
Step 5
In the ShellAdmin for the primary node and all service nodes, choose Apply patch to upgrade those nodes
to Release 5.3.
When prompted, enter the location of the Release 5.3 patch.
ftp://username:password@hostname|IP_address/software_location_and_name
Step 6
Step 7
Step 8
Wait for the download and installation to complete.
When prompted, choose Start services to start services on the primary node and all services nodes and
complete the upgrade process.
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 on the primary and secondary service
nodes and complete the patch process. The patch process is not complete or successful until the Cisco
UCS Director services have started, Cisco UCS Director is available, the login screen is displayed,
and the admin user can log in to Cisco UCS Director.
All Cisco UCS Director services must be started before you attempt to perform other ShellAdmin
procedures, such as apply additional patches, take a database backup, or restore a database from a
backup.
Step 9 When the upgrade is complete, choose Show Version in ShellAdmin to verify the current version of Cisco
UCS Director.
Step 10 After upgrading, reboot the Cisco UCS Director VM to update the kernel version.
Cisco UCS Director Installation and Upgrade on Microsoft Hyper-V Manager, Release 5.3
44
APPENDIX
A
Ports
This appendix contains the following sections:
• Cisco UCS Director TCP and UDP Port Usage, page 45
• Port List, page 46
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 following figure shows the network ports used for communication between the Cisco UCS Director
appliance and managed devices, ESX servers, Baremetal Agent, PowerShell Agent, NTP, and Active Directory.
Figure 1: Cisco UCS Director TCP and UDP Port Usage
Cisco UCS Director Installation and Upgrade on Microsoft Hyper-V Manager, Release 5.3
45
Ports
Port List
Port List
Default Port
Protocol
Description
22
TCP
SSH
80
UDP
HTTP
443
UDP
HTTPS
27000/7279/8082 (Mgmt)
TCP
Citrix licensing
2598/1494/2112/2513
TCP
Virtual Desktop Agent for Desktops
67/68
UDP
DHCP
389/636
TCP/UDP
Active Directory
3268/3269
TCP
53
TCP/UDP
DNS
123
TCP/UDP
NTP
3306
TCP/UDP
MySQL
8787/5999
TCP
Cisco UCS Director + VNC Connectivity
3389
TCP/UDP
Cisco UCS Director + RDP Connectivity
80/443/8080
TCP/UDP
Cisco UCS Director + NetApp Connectivity
80/443
UDP
Cisco UCS Director + UCSM Connectivity
80/443
UDP
Cisco UCS Director + vCenter Connectivity
3389
TCP/UDP
RDP
135/445
TCP
SMB/RPC
88
TCP/UDP
Kerberos
137
TCP/UDP
NetBIOS Name (nbname)
138
TCP/UDP
NetBIOS datagram (nbdatagram)
139
TCP
NetBIOS session (nbsession)
Cisco UCS Director Installation and Upgrade on Microsoft Hyper-V Manager, Release 5.3
46
Ports
Port List
Default Port
Protocol
Description
80/443
UDP
Desktop Delivery Controller <--> vCenter
8080 through ICA
TCP
Desktop Delivery Controller <--> Virtual Desktops
1494/2598/2512/2513
TCP
Users (Citrix Recvr) <--> Virtual Desktops
389/636 (LDAP Ports)
TCP/UDP
Desktop Delivery Controller <--> Active Directory
389/636, 3268/3269, 53
TCP/UDP
Virtual Desktops <--> Active Directory + DNS
5985/5986
TCP
PowerShell Agent <-> Xendesktop through WinRM
43891
TCP/UDP
Cisco UCS Director <--> PowerShell Agent
80/8081
TCP
XenApp
Cisco UCS Director Installation and Upgrade on Microsoft Hyper-V Manager, Release 5.3
47
Ports
Port List
Cisco UCS Director Installation and Upgrade on Microsoft Hyper-V Manager, Release 5.3
48