Cisco UCS Director 5-4 VMware v1 Demo Guide

Cisco dCloud
Cisco UCS Director 5.4 with VMware v1

Last Updated: 08-JAN-2016
About This Cisco Solution

Cisco UCS Director (UCSD) improves business agility and increases efficiency by improving infrastructure management and
services delivery. It provides unified infrastructure provisioning and automation across computing, networking, and storage
resources to drastically reduce complexity for IT operators and administrators.
Learn more about Cisco UCS Director at http://www.cisco.com/go/ucsdirector.
About
This preconfigured Cisco UCS Director demonstration includes:
Scenario 1: Unified Dashboard Overview
Scenario 2: Add ESXi Host and Enable vSAN Workflows & HyperConverged Infrastructure
Scenario 3: Self-Service Catalog for Predefined Workflow
Scenario 4: Application Container Deployment
Scenario 5: Bare Metal Provisioning using Bare Metal Agent Server
Scenario 6: CloudSense Analytics and Reports
Scenario 7: Executing Predefined Workflows
Scenario 8: Rebranding the UCS Director User Interface
Requirements
Table 1. Demonstration Requirements
Required Optional
Laptop None
Cisco AnyConnect
Topology
This demonstration contains preconfigured users and components to illustrate the scripted scenarios and features of this solution.
All information needed to access the demonstration components, is located in the Topology and Servers menus of your active
demonstration.
Topology Menu. Click on any server in the topology and a popup window will appear with available server options.
Servers Menu. Click on or next to any server name to display the available server options and credentials.
2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 1 of 66
Cisco dCloud
Figure 1. Demonstration Topology
Cisco dCloud
Get Started
BEFORE DEMONSTRATING
We strongly recommend that you go through this process at least once, before presenting in front of a live audience. This will allow
you to become familiar with the structure of the document and the demonstration.
PREPARATION IS KEY TO A SUCCESSFUL CUSTOMER PRESENTATION.
IMPORTANT: If you experience any issues with UCS Director, refer to Troubleshooting section.
Follow the steps to schedule a session of the content and configure your presentation environment.
1. Browse to dcloud.cisco.com, select the location closest to you, and log in with your Cisco.com credentials.
2. Schedule a session. [Show Me How]
3. Register and configure your router if this is the first time you will use the router with dCloud. [Show Me How]
4. Test your connection. [Show Me How]
5. Verify that the status of your session is Active in My Dashboard > My Sessions.
NOTE: It may take up to 20 minutes for your session to become active.
6. Click View to open the active session.
7. For best performance, connect to the workstation with Cisco AnyConnect VPN [Show Me How] and the local RDP client on
your laptop [Show Me How]
Workstation 1: 198.18.133.36, (dcloud\demouser/C1sco12345)
NOTE: You can also connect to the workstation using the Cisco dCloud Remote Desktop client [Show Me How]. The dCloud
Remote Desktop client works best for accessing an active session with minimal interaction. Many users experience connection and
performance issues with this method.
8. From the demonstration workstation, launch VMware vSphere Client [ ].
At the bottom of the login window, check Use Windows session credentials, if not already checked, and then click Login.
9. From the demonstration workstation, launch Chrome and login to UCS Director (admin/C1sco12345).
10. From the demonstration workstation, launch Internet Explorer (IE) and login to UCS Director (demouser/C1sco12345).
Proceed through any security warnings.
Configure an Email Client
1. Set up your external email to receive notifications based on requests submitted and completed during the demo.
a. From the demonstration workstation, open the Scripts folder , and double-click Cisco UCS Director Email Setup.
b. A console window will open and then close, which indicates the script is working in the background.
Cisco dCloud
c. In the External Email Address popup window, enter the email address you want emails related to the demo sent. Click
OK.
NOTE: The predefined workflow used during the demonstration will send notifications based on the request and the user role. For
example, the admin user would receive requests requiring approval. Setting up external email allows you to receive email in your
external account.
Check your Spam or Junk folder if you do not receive an email notification as documented in the demonstration steps below.
Cisco dCloud
Scenario 1. Unified Dashboard Overview

Cisco UCS Director is a multi-hypervisor and multi-cloud management solution that provides virtual infrastructure control,
management, and monitoring from a unified dashboard. The unified dashboard gives administrators complete visibility into
organizational use, trends, capacity analysis details, and much more.
Steps
This section highlights a few of the many options available to the administrator.
Dashboard Menu
The dashboard is completely customizable.
Show the different preconfigured widgets available on the dashboard and how easy it is to:
o Adjust the size of the reports displayed on the Dashboard by using the slide bar ( )
o Move the widgets around
o See and change different options for widgets
o Mouse over graph element to display popup tooltip
Figure 2. Dashboard Admin View
Converged Menu
1. On the menu bar, choose Converged.
2. Click the dCloud Datacenter icon.
Cisco dCloud
Figure 3. dCloud Datacenter
3. Show the available components in dCloud Datacenter.
Figure 4. dCloud Datacenter Stack
NOTE: The features of the Map Reports are discussed more in Scenario 6: Analytics and Reports.
4. From the dCloud Datacenter stack, go to the Virtual section and double-click the component VMware.
Show how to drill-down into virtual administration.
Click the back button [ ] to go back to the dCloud Datacenter stack.
Cisco dCloud
5. From the dCloud Datacenter stack, go to the Compute section and double-click the component Demo_UCSM.
Show how to drill-down into the physical UCS chassis management.
Click the back button to go back to the dCloud Datacenter stack.
6. From the dCloud Datacenter stack, go to the Network section and double-click the component VSM.
Show how to drill-down into the device administration.
Click the back button to go back to the dCloud Datacenter stack.
7. From the dCloud Datacenter stack, go to the Storage component and double-click the component NetApp_EDGE.
Show how to drill-down into the storage device.
HyperConverged Menu
The HyperConverged menu will be explored once VSAN is enabled in Scenario 2.
Virtual Menu
From the top menu, click Virtual to display the Virtual menu.
Figure 5. Virtual Menu
The Virtual Menu has four submenus: Compute, Storage, Network, and VDI. Click through the submenus and discuss the
available options and features. Suggested talking points:
VM lifecycle operations
Detailed components of an active VM
Typical lifecycle operations and infrastructure components
Snapshot summary of VMs that have been snapshotted and operations you can perform on them
Storage utilization map
Cisco dCloud
Figure 6. Virtual Menu > Compute
Physical Menu
The Physical Menu has three submenus: Compute, Storage, and Network. Click through the submenus and discuss the
available options and features based on customer interest. Suggested talking points:
Physical infrastructure monitoring
Chassis and server details
Detailed information for storage
Physical network details: VTP, Private VLANs, Port profiles, VSANs, VLANs
SAN Zonesets, SAN Zones, QOS Policy Maps, and QOS Class Maps
1. From the top menu, select Physical > Compute.
2. In the side navigation bar, expand dCloud-Site and click dCloud Datacenter.
Cisco dCloud
Figure 7. Physical Summary for dCloud Datacenter
Organizations Menu
The Organizations Menu has six submenus: Service Requests, My Approvals, Summary, Virtual Resources, Physical
Resources, and Chargeback. Click through the submenus and discuss the available options and features based on customer
interest. Suggested talking points:
Workflow status, log, and created or modified objects of a completed service request
Rollback service request feature for a successfully completed request
Resubmit service request features for a failed service request
1. From the top menu, click Organizations > Service Requests.
2. Double-click a Service Request to see the workflow.
Figure 8. Organizations Menu Service Request for All User Groups
Cisco dCloud
Policies Menu
The Policies Menu has seven main submenus: Catalogs, Applications Containers, Virtual/Hypervisor Policies, Physical
Infrastructure Policies, Tag Library, Resource Groups, and Orchestration. Click through the submenus and discuss the
available options and features based on customer interest. Suggested talking points:
Import and export functions and the ability to import more preconfigured workflows
Task Library
Alter orchestration flow by dragging a task
Admin control of parameters the user can enter
Hover over the on success and on failure actions of a task to show how to rewire
Edit a trigger by picking a VM and parameter, and then build a rule
Figure 9. Orchestration > Workflow Tab > VMProvisioning > VMProvisioning Setup
Administration Menu
The Administration Menu has 11 submenus: Guided Setup, License, System, Users and Groups, Virtual Accounts, Physical
Accounts, Integration, Mobile Access, User Interface Settings, Open Automation, and Support Information. Click through
the submenus and discuss the available options and features based on customer interest.
NOTE: We will demonstrate User Interface Settings in Scenario 8: Rebranding the Interface.
Cisco dCloud
Figure 10. Administration > Users and Groups > Users
CloudSense Menu
The CloudSense menu has three submenus: Reports, Assessments, and Report Builder.
Features from this menu are part of Scenario 6: Analytics and Reports.
This concludes the activities in this scenario.
Cisco dCloud
Scenario 2. Add ESXi Host and Enable vSAN Workflows & HyperConverged
Infrastructure
The purpose of this scenario is to use UCS Director workflows to add an additional ESXi host to a cluster, then enable vSAN.
Steps
1. Open Internet Explorer (IE) and login to UCS Director (demouser/C1sco12345) if you have not already done so. Ignore any
security warnings.
2. Click the vSphere shortcut on the taskbar and login to vSphere (no credentials are required.)
3. Position the windows so that you can look back and forth between UCS Director and vSphere without resizing them.
Figure 11. Resize vSphere and UCS Director Windows
4. In UCS Director, click Catalog.
5. Click the vSphere Infrastructure folder to view the available workflows, then double-click Add ESXi Host.
Figure 12. Choose a Workflow
Cisco dCloud
6. Click Next in the resulting Catalog Selection window, without making any changes.
7. Select vesx3.dcloud.cisco.com from the Host Name drop-down.
Figure 13. Select the Host
8. Click Next, then Submit.
9. Click OK.
10. Click Services to view a list of service requests, then double-click the Add ESXi Host service request to view progress.
Figure 14. View the Service Request
11. Bring the vSphere window to the front, and watch as UCS Director adds the new ESXi host and configures it. This will take
three or four minutes to run.
12. From the home page, select Hosts and Clusters.
Figure 15. Hosts and Clusters
13. Wait approximately three minutes until the vesx3.dcloud.cisco.com host is created. Click the hostname.
Cisco dCloud
Figure 16. VM Configured in vSphere
14. When the Create NAS datastore tasks appear in Recent Tasks, click the Configuration tab and select Storage to show the
datastores being added.
Figure 17. Datastores in vSphere
15. Now there are three ESXi hosts in the vSphere cluster, and vSAN storage can be enabled. In UCS Director, click Catalog >
vSphere Infrastructure to view the available workflows, then double-click Enable vSAN.
Cisco dCloud
Figure 18. Click Enable vSAN
a. Click Next through all the screens, no updates are needed. Click Submit.
16. Click Services to view a list of service requests, then double-click the Enable vSAN service request to view it.
Figure 19. View the Service Request
17. Bring the vSphere window to the front, and watch the tasks complete in the Recent Tasks area.
18. Click vesx1.dcloud.cisco.com and click the Configuration tab, then Storage to see the vSAN datastore come online.
Figure 20. View Configuration to See vSAN
Cisco dCloud
19. View the system from a different browser to show the new storage configuration.
a. Open a Chrome browser window if one is not already open, and login to UCS Director (admin/C1sco12345).
b. On the Dashboard, mouse over the Total Capacity per Storage table to show that it now shows vSAN storage.
c. Click Virtual > Storage and the Datastore Capacity Report tab to show that the new datastore is available in
the UCS Director inventory.
Figure 21. vSAN Storage
20. Configure the dCloud-Datacenter compute Pod with the new vSAN storage in UCS Director.
a. From the Chrome browser, select Converged.
b. Select the dCloud-Datacenter icon, and click Edit.
Figure 22. Configure Converged Infrastructure with vSAN
c. Select Virtual SAN Pod from the Type drop down menu and select Save.
d. Click OK to clear the confirmation.
Cisco dCloud
Figure 23. Edit POD
21. Review the Hyperconverged infrastructure.
a. On the menu bar, choose HyperConverged > Virtual SAN.
b. Click the Pods tab.
c. Choose the dCloud Datacenter Virtual SAN pod and then click View Details.
All the Virtual SAN clusters, Virtual SAN qualification policies, and related system tasks for the pod are displayed on the Virtual
SAN Clusters tab, the Qualification Policies tab, and the System Tasks tab. Alternately you can also view the Virtual SAN pod
report by choosing the Virtual SAN pod on the Converged tab of the menu bar.
22. Select Assign Cluster(s) to POD
Figure 24. Hyperconverged Assigned Cluster to POD
23. Select the dCloud-Cluster and Submit.
Cisco dCloud
Figure 25. Assign Cluster to POD
24. Double click the dCloud-Cluster
Figure 26. View Hyperconverged Cluster
25. By default, the Summary tab appears. You can also view related service request, datastore capacity, host, disk group, disk,
license, and topology details in the Service Request, Datastore Capacity Report, Hosts, Disk Groups, Disks, License, and
Topology tabs.
Cisco dCloud
Figure 27. Review Hyperconverged Configuration
Cisco dCloud
Scenario 3. Self-Service Catalog for Predefined Workflow

This scenario features the self-service capabilities of Cisco UCS Director using predefined workflows and preconfigured virtual
datacenters.
The predefined workflow will send an email notification as defined in the workflow, for example, when the administrator
needs to approve a request.
Virtual datacenters have been preconfigured with different authorization requirements. Service requests for Sales Gold vDCs
require authorization. Service requests for Sales Bronze and Sales vSAN vDCs do not. Refer to the table below for details.
Table 2. Preconfigured Virtual Datacenters
Sales Bronze vDC Sales Gold vDC Sales vSAN vDC
No authorization required in order for service Authorization is required for service request to be No authorization required in order for Service
request to be completed completed Request to be completed
Storage efficiency is enabled, using NetApp Ability to customize the size of the VM Nested ESXi, with no SSD, therefore vSAN
Up to 15 minutes to complete service requests performance not representative.
Rapid Cloning, for faster deployment
(cloning) VM deployment performed using a full clone
Up to 5 minutes to complete service requests
Only attempt one deployment at a time; attempting (approx 5 mins).
(cloning)
more than one will slow down the deployment of
all
The purpose of this scenario is to demonstrate
submitting a service request that does not require authorization on from the UCSD UI and
submitting a service request that does require authorization from the UCSD UI
NOTE: Before beginning this scenario, make sure that you have configured an email client.
Steps
Submit Service Request Using UCSD UI No Authorization Required
1. Go to the IE browser window that where demouser is still logged in to Cisco UCS Director.
2. From the toolbar, click Catalog.
3. Double-click the Standard folder.
Figure 28. Standard Folder
Cisco dCloud
4. From the Standard folder, double-click Ubuntu 12 Server dCloud-Cluster.
Figure 29. Standard Folder
5. In the Create Service Request wizard, complete the following.
a. In the Catalog Selection pane, no updates needed. Click Next.
b. In the Deployment Configuration pane, choose Sales Bronze vDC from the Select VDC drop-down list.
Optionally, you may enter a comment, but no other updates needed. Click Next.
NOTE: To use vSAN rather than NFS, select the Sales vSAN vDC in the Deployment Configuration pane. Performance will be
slower because the system will do a full clone, rather than use the NetAPP Rapid Clone mechanism,
c. In the Custom Specification pane, no updates needed. Click Next.
d. In the Custom Workflow pane, no updates needed. Click Next.
e. In the Summary pane, review your inputs and click Submit. Click OK.
6. Click Services to see the status of your submitted request.
Figure 30. Service Request
7. Go to the email client that you configured for the demo.
You will have an email with the subject Technical Information: Resource allocation successful.
8. From the demonstration workstation, go to VMware vSphere Client
Show and explain how the Recent Tasks window, and the Summary tab in the VMware window, correlate with the
request submitted via UCS Director.
Cisco dCloud
Figure 31. VMware Summary of Completed Request
9. Return to the Chrome window, showing the Cisco UCS Director window for the user admin.
10. From the menu bar, choose Organizations > Service Requests.
11. Double-click the Create VM service request submitted earlier as the user demouser to see the Workflow Status of the
request.
Figure 32. Double-click Create VM Service Request
Cisco dCloud
12. Wait for the request to complete, which may take five or ten minutes.
Figure 33. Workflow Status
13. Go to the email client configured for the demo.
You will have an email with the subject Service Request for provisioning of VM(s) has been completed, when the
request is complete.
NOTE: The admin email may go to the Junk/Spam folder, even if the demouser email did not.
Submit Service Request Using UCSD UI Authorization Required
1. Go to the IE browser window, where demouser is logged in to Cisco UCS Director.
2. From the Catalog, double-click the Standard folder.
3. From the Standard folder, double-click Windows 7 dCloud-Cluster.
Figure 34. Catalog
Cisco dCloud
4. In the Create Service Request wizard, complete the following.
a. In the Catalog Selection pane, no updates needed. Click Next.
b. In the Deployment Configuration pane, choose Sales Gold vDC from the Select VDC drop-down list.
Optionally, you may enter a comment, but no other updates needed. Click Next.
c. In the Custom Specification pane, you can change the configuration or accept the default values. Click Next.
d. In the Custom Workflow pane, no updates needed. Click Next.
e. In the Summary pane, review your inputs and click Submit. Click OK.
You will have an email with the subject Approval Required.
6. Go to the Cisco UCS Director window for the user demouser and click Services to see the status of your submitted request.
Figure 35. Services
7. Double-click the service request to see the individual steps. The process will stop at Step 6: Approval By admin.
8. The Admin must approve the service request in order for it to be processed. Use option a (if you are connected to the
demonstration using Cisco AnyConnect) or option b (if you are connected to the demonstration using the Cisco dCloud
Remote Desktop Client) to approve the service request.
a. If you are connected to the demonstration using Cisco AnyConnect, follow the bulleted steps below:
Go to the email client that you configured for the demo and open the email with the subject Approval Required.
Click link to go to launch Cisco UCS Director.
NOTE: If you receive a warning, click Advanced and proceed to the IP address to continue.
Cisco dCloud
Figure 36. Example Approval Needed Email
The Cisco UCS Director log in window will open in a web browser on your laptop. Log in with the following
credentials: Username: admin, Password: C1sco12345.
You will go directly to the Service Approval page.
On the bottom of the window, you will see Approve is preselected. You may enter a comment and then click
Submit. Click OK.
Cisco dCloud
Figure 37. Service Approval Request Example
NOTE: The entire process to create and customize your VM may take up to 15 minutes to complete. You may see a status of
Complete within 5-6 minutes, but wait until you receive notification that the request is complete.
Close the web browser window on your laptop.
b. If you are connected to the demonstration using the Cisco dCloud Remote Desktop Client with HTML5,
follow the bulleted steps below:
From the demonstration workstation, go to the Cisco UCS Director window for the user admin.
From the menu bar, choose Organizations > My Approvals.
Either click the service request that needs approval and click or right-click on the service request
and choose Approve from the drop-down list.
Figure 38. My Approvals
In the Service Request window, you may enter an optional Comment and then click Approve.
Cisco dCloud
9. Click OK.
10. Return to the demouser UCS Director window, where the workflow has progressed through Step 7: Approval and proceeded
to Step 8: VMware VM Provision.
You may need to click Refresh to get the latest status.
NOTE: The entire process to create and customize your VM may take up to 15 minutes to complete. You may see a status of
Complete within 5-6 minutes, but wait until you receive notification that the request is complete.
Cisco dCloud
Figure 40. Workflow Status Example
11. From the demonstration workstation, go to VMware vSphere Client
Show and explain how the VMware Recent Tasks and Summary windows correlate with the request submitted via UCS
Director.
12. Go to the Cisco UCS Director window for admin.
You should still be on the My Approvals page. If not, click Organizations > My Approvals.
13. Click Refresh to see the Status of the request.
14. Continue to monitor the status of the service request in all three windows until it is completed.
Cisco dCloud
Figure 41. Simultaneous Monitoring of VM Provisioning Request
You will have an email with the subject Service Request for provisioning of VM(s) has been completed, when the
request is complete.
Figure 42. Example Service Request for Provisioning VM(s) Completed Email
Cisco dCloud
Scenario 4. Application Container Deployment

An application container is a collection of virtual machines (VMs) with an internal private network controlled by rules specified by
the administrator. The application container can have one or more VMs that are guarded by a fencing gateway (for example, a
Virtual Secure Gateway) to the external/public cloud. Cisco UCS Director provides support for application containers and enables
you to define container templates with one or more fenced networks and VMs. When an application container is created from a
template, Cisco UCS Director automatically deploys VMs and configures networks and the firewall. Cisco UCS Director also
automatically configures virtual and physical switches for Layer 2 changes.
The purpose of this scenario is to submit a service request to deploy three VMs using an application container, and review the
UCSD application templates associated with the deployment.
Steps
Deploy an Application
1. Go to the IE window, showing Cisco UCS Director for the user demouser (demouser/C1sco12345).
2. From the tool bar, click Catalog and then double-click the Service Container folder.
3. From the Service Container folder, double-click Sales 3-Tier App dCloud-Cluster.
4. In the Create Service Request wizard, complete the following:
a. In the Catalog Selection pane, no updated needed. Click Next.
b. In the Deployment Configuration pane, enter Contain1 as the Service Container Name. Click Next.
NOTE: The Service Container Name must be less than eight characters.
c. In the Summary pane, review the inputs and click Submit.
Figure 43. Service Request Summary
5. Click OK.
This request will deploy three VMs, provision a port-profile on the Cisco Nexus 1000V, and create a working application.
NOTE: Although no authorization is required, the entire process may take up to 15 minutes to complete. The status of the request
may be Complete within 5-6 minutes, but wait until for the email notification that the request is complete.
Cisco dCloud
6. While the application is being deployed, review the templates used to create the application container:
a. Go to the vSphere Client window, or open it if one is not already open.
b. From the menu bar, choose Home > Inventory > VMs and Templates.
c. In the Navigation pane, expand vc1.dcloud.cisco.com > dCloud-DC > Templates.
The three templates that have been mapped to the Sales_3Tier_App_Template in UCS Director are app-server, db-
server, and web-server.
Figure 44. vSphere Client VMs and Templates
7. Review the newly created application in vSphere:
a. From the menu bar, choose Home > Inventory > Networking.
b. In the Navigation pane, expand vc1.dcloud.cisco.com > dCloud-DC > VSM > VSM.
The name includes the service container name and the actual network name defined in the application container
template.
c. Click through the tabs in the work pane to review the ports, virtual machines, and hosts that were created with the
application.
Figure 45. Application
Cisco dCloud
8. From the menu bar, choose Home > Inventory > VMs and Templates.
9. In the Navigation pane, expand vc1.dcloud.cisco.com > dCloud-DC > FencedContainers > Contain1.
10. Click any server to see the assigned static IP address based on the policy set from the application container. This scenario will
examine those settings further.
Figure 46. Servers in Application Container
View or Modify an Existing Template
The purpose of this section is to walk through an existing template without making any changes to it. At the end of the steps,
clicking Close ends the process without saving.
1. Go to the Cisco UCS Director window for the user admin.
2. From the menu bar, choose Policies > Application Containers.
3. Click the Application Containers tab to see deployed application containers. Note that this may be empty if the earlier
request is still in progress.
Figure 47. Application Containers
4. Click the Application Container Template tab to see existing templates or to create a new one.
Cisco dCloud
Figure 48. Application Container Templates
5. Double-click the existing template named Sales_3Tier_App_Template.
6. Walk through the Modify Application Container Template dialog box:
a. The Template Specification pane allows the user to add an optional Template Description. Click Next without
adding a description.
Figure 49. Template Specification
b. The Virtual Infrastructure Policy pane allows users to verify or select the Virtual Infrastructure Policy. For this
template, the Virtual Infrastructure Policy is set to Sales_3Tier_V1_Policy. Click Next.
Figure 50. Virtual Infrastructure Policy
Cisco dCloud
c. The Networks pane allows users to review or select the internal networks where the VMs will be added,
including selecting VLAN ID ranges, IP addresses, Network Masks and Gateway IPs. Click the to see the
Network dialog box, then click Close. Click Next.
Figure 51. Networks
d. The Virtual Machines pane shows the three VMs that will be deployed. This deployment contains app, web, and
DB servers. Click to show the dialog box that would be used to add new VMs to the deployment, then click
Close. Click Next.
Figure 52. Virtual Machines
e. The Policies pane shows the policies that have been set for the template. The policies that have been set for
this template are Gold level. Click Next.
Cisco dCloud
Figure 53. Policies
f. The Options pane shows the options for the application container. Click Next.
Figure 54. Options
g. The Workflows pane shows the UCS Director workflows that can be used to deploy the application container.
Click the Select button to see a complete list of all available workflows. Click Cancel to close the list.
h. Click Next.
Cisco dCloud
Figure 55. Workflows
i. In the Summary pane, review the network settings that have been configured for the application container.
j. Click Close to end the walkthrough without saving.
Figure 56. Summary Pane
Verify Application Creation
1. Go to the vSphere Client window.
2. From the menu bar, choose Home > Inventory > Hosts and Clusters.
3. In the Navigation pane, expand vc1.dcloud.cisco.com > dCloud-DC > dCloud-Cluster and review the new VMs created for
the Contain1 application.
Cisco dCloud
Figure 57. Created VMs in vSphere Client
4. Click each VM and verify that they are all in Powered On state before continuing.
Figure 58. VM in Powered On State
5. Go to the Google Chrome window and open a new tab.
6. From the Google Chrome bookmarks bar, click the Demo Webserver shortcut . The Welcome to dCloud
page confirms that the deployed application is running.
Figure 59. Deployed Application Welcome Page
Cisco dCloud
Review the Server Configuration of the Application
2. From the toolbar, choose Home > Inventory > VMs and Templates.
3. In the Navigation pane, expand vc1.dcloud.cisco.com > dCloud-DC > FencedContainers > Contain1.
4. Right-click Contain1-web-server1 and choose Open Console from the drop-down list. Log in to the console window
(root/C1sco12345).
Figure 60. Open Console
5. At the command prompt, type ifconfig.
6. Review the output TCP/IP addressing has been configured as defined in the Application Container Template.
Figure 61. ifconfig Output
7. Close the console window.
Cisco dCloud
Scenario 5. Bare Metal Provisioning Using Bare Metal Agent Server

Cisco UCS Director Bare Metal Agent (BMA), in conjunction with Cisco UCS Director, automates the process of Pre-Boot
Execution Environment (PXE) installing operating systems on Bare Metal servers or virtual machines.
In this scenario, we will show use a VM (in place of a physical server) to provision or stream operating system (OS) files on to a
target host by using the BMA along with the UCSD server.
NOTE: Use Google Chrome for this scenario.
Steps
Enable VMRC Console
The purpose of this section is to enable the VMRC console, which allows a Virtual Machine console session to be initiated directly
from UCS Director. A VM then has an VMware ESXi deployed to it via the Bare Metal Agent.
1. Go to the Google Chrome window displaying Cisco UCS Director for the user admin.
2. From the menu bar, choose Virtual > Compute.
3. Click the VMs tab, and click the vesx4 deployed VM dCloud-Cluster.
Figure 62. VMs
4. From the tool bar, click the drop-down and scroll down the menu to choose Enable/Disable VMRC Console.
Figure 63. Drop-down list with Enable/Disable VMRC Console selected
5. On the Enable VMRC Console Access window, check the checkbox, and then click Submit.
Cisco dCloud
Figure 64. Enable VMRC Console Access
6. Click OK to return to the VMs list.
7. Select the vesx4 from the VMs list and then click Launch VM Client from the tool bar.
8. On the Launch Client window, choose VMRC Console.
NOTE: This will launch the VMware Remote Console session to the dCloud-Cluster VM. If you receive the message Remote
Console plugin is not properly installed, then please restart this section using the Chrome browser.
Figure 65. Launch Client
9. Click Proceed. Continue through any security warnings.
A blank browser tab opens. The window is blank because the VM is powered off.
Figure 66. VMRC Console for vexs3
10. Return to the UCS Director Chrome tab for the user admin.
11. Select the dCloud-Cluster VM vesx4 and then click Power ON from the tool bar.
12. On the VM Task window, verify Execute Now is selected and then click Proceed.
Cisco dCloud
Figure 67. VM Task
13. Click OK.
14. Go to the VMRC Console window.
15. When the VM powers up, the BMA automatically deploys ESXi on to the VM.
It will take approximately 15 minutes to deploy ESXi to the server.
The BMA server, in conjunction with the UCSD server, streams the OS files to the host over the dedicated PXE network.
After the deployment completes, the VM will shut down automatically.
Normally, the host will now be moved from the PXE VLAN to the production VLAN.
Figure 68. Loading VMware ESXI
16. Open the vSphere Client window and login if you have not already done so.
17. From the toolbar, choose Home > Inventory > Hosts and Clusters.
18. In the Navigation pane, expand vc1.dcloud.cisco.com > dCloud-DC > dCloud-Cluster and then click vesx4.
The network is pxe_vlan. One of the sections in this scenario will change the attached network to n1kv_mgmt_vlan.
Cisco dCloud
Figure 69. Show vesx4 VLAN
View BMA Settings
While the previous section is running, walk through the setup of the BMA PXE Request, which configures the integration between
UCS Director and the Bare Metal Agent.
1. Go to the UCS Director window for the user admin.
2. From the menu bar, choose Administration > Physical Accounts.
3. Click the Bare Metal Agents tab to configure the BMA server.
Figure 70. Bare Metal Agents
4. Select the ucsd-bma Bare Metal Agent from the list and click Edit.
5. In the Modify Bare Metal Agent Appliance window:
The BMA Management Address field contains the IP Address of the BMA.
The Login ID and Password fields contain the user name and password.
The BMA PXE Interface Address field contains the PXE network interface IP Address.
o This interface will stream the OS to the target host.
o This is a different subnet than the BMA Management Address. This environment has a dual network
configuration so that one network interface is dedicated to the management network and another is dedicated to
the PXE network. This allows the deployment of hosts in a segregated environment.
The BMA is connecting back to the UCSD server using the UCSD IP address in the UCSD Database Address field.
Cisco dCloud
Figure 71. Modify Bare Metal Agent Appliance
6. Click Close.
Learn to Configure BMA Settings
The purpose of this section is to learn how to configure some of the BMA settings directly within UCS Director instead of having to
ssh to the VM to make the changes. This demonstration does not support making configuration changes.
1. Click the button to show the hidden menu, then click Configure DHCP.
Figure 72. Click Configure DHCP
The Configure DHCP window shows the DHCP Subnet, DHCP Netmask, and more.
Cisco dCloud
Figure 73. Configure DHCP
2. Click Close.
3. Select the ucsd-bma, and select Edit from the menu bar.
4. Note that the UCS Director BMA has two interfaces, one for management, and another to service PXE requests to deploy
Operating Systems to clients. The Database Address is the reference to the UCS Director.
Figure 74. Bare Metal Agent Registration
5. Click Close.
Learn How to Submit a PXE Request
The purpose of this section is to walk through the process of submitting a PXE request, to build a physical server and deploy an
OS. This demonstration does not support submitting an actual PXE request.
Cisco dCloud
1. From the main UCS Director menu, choose Physical > Compute.
Figure 75. Physical Compute
2. In the Navigation pane, choose dCloud Datacenter.
3. Click the PXE Boot Requests tab.
4. Click Add PXE Request.
5. In the PXE Boot Request Add window,
The Server MAC Address field is for the MAC address of the physical host being requested.
The Host Name field is for the host name.
The Root Password and Confirm Password fields are for the root password of the prospective host, and password
confirmation.
In the Server Address field, you would add the management address of the server once it has been deployed and
moved to the production VLAN. The temporary IP Address used for the PXE image deployment will be configured
automatically.
The Network Mask and Gateway fields are configured based on the value in the Server Address field.
The Timezone field is for the desired time zone.
The Target BMA field allows users to select which BMA will be used to deploy the server. UCSD supports a many-to-one
configuration of BMA servers to UCSD.
The OS Type field allows users select which image to stream on to the target server.
6. Click Close.
7. Choose the available PXE boot request and then click Edit PXE Request.
You can see the settings that have been used for the PXE configured for this demonstration.
Cisco dCloud
Figure 76. PXE Boot Request Modify
8. Click Close.
Change BMA Network
Wait until the vesx4 shows as Powered On in vSphere before continuing with this section. The purpose of this section is to change
the BMA network from pxe_vlan to n1kv_mgmt_vlan.
1. Still in the Google Chrome window, where admin is logged into UCS Director, choose Policies > Orchestration from the
menu bar.
2. Expand the dCloud folder.
Cisco dCloud
Figure 77. Orchestration with the BMA Network Change Workflow selected
3. Double-click the BMA Network Change workflow
4. From the tool bar, click Execute Now.
Figure 78. Execute Now
5. In the Executing Workflow: BMA Network Change window, click Select.
Figure 79. Submit Workflow
6. Check the check box next to dCloud-Cluster for vesx4 and click Select. DO NOT click Submit.
Cisco dCloud
Figure 80. Select
You should still be at Home > Inventory > Hosts and Clusters and have vesx4 selected in the Navigation pane.
8. In the Summary, you can see that the Network is named pxe_vlan.
Figure 81. vesx4 Summary
9. Go back to the UCS Director window.
10. Click Submit.
Cisco dCloud
11. On the Service Request Submit Status window, click Show Detail Status.
Figure 83. Service Request Submit Status
12. Review the status of the workflow.
13. Go to the vSphere Client window, which still shows Home > Inventory > Hosts and Clusters and has vesx4 selected in the
Navigation pane.
14. In the Summary, the Network has been migrated to n1kv_mgmt_vlan.
Cisco dCloud
Figure 85. vesx4 Summary
15. Power on the VM.
NOTE: The VM may show as Powered On already if it is still deploying to the ESXi. Wait for the VM to show as Powered Off,
and then power it on.
Figure 86. Power On Button
16. Go to the UCSD VMRC Console window to see the VMware ESXi version along with the static IP address.
Figure 87. vesx4 VMRC Console
Cisco dCloud
17. To verify the ESXi host is fully accessible, launch a second VMware vSphere Client [ ] from the wkst1 desktop.
18. Log in with the following credentials: IP address / Name: 198.18.133.34, User name: root, Password: C1sco12345.
Verify Use Windows session credentials is unchecked
19. In the Security Warning window, check the check box and then click Ignore.
Figure 88. Security Warning
20. You will then connect to the VM we just deployed in VMware vSphere Client.
This concludes the activities in this scenarios.
Cisco dCloud
Scenario 6. Analytics and Reports

UCS Director provides real-time reporting of resource health and utilization capabilities. It provides visibility into real-time physical
and virtual infrastructure resource consumption, which leads to efficient capacity planning. The solution's unified management of
compute, network, and storage access elements speeds discovery and eliminates the tedious and error-prone process of manually
correlating information about disparate system components. Administrators can quickly detect and remedy bottlenecks or outages
affecting application performance and availability.
The purpose of this scenario is to demonstrate CloudSense Analytics and other available UCS Director reports using the web
browser for the admin user.
Steps
Map Report Using Laptop Web Browser
1. From the demonstration workstation, go to the Cisco UCS Director window for the user admin.
The Map Reports display is dependent upon having a number of VMs running on the platform, and some key UCS
Director system tasks having been executed since they were deployed. This enables inventory and performance data to
be collected and analysed for display. These system tasks can be triggered manually via the following process:
a. Click Administration > System and click the System Tasks tab.
b. Expand VMware Standard Tasks and select VMware Inventory Collector dCloud-Cluster. Select Run Now. Click
Submit, then OK.
c. Expand Virtualization Tasks and select Performance Data Collector dCloud-Cluster. Select Run Now. Click
Submit, then OK.
d. Expand General and select HeatMap Data Aggregator Task. Select Run Now. Click Submit, then OK.
2. From the top menu bar, choose Converged.
3. Select dCloud Datacenter.
4. Double-click the virtual component VMware.
5. Scroll the tab bar to the right and click the Map Reports tab, below the dCloud-Cluster header.
You may have to click and choose Map Reports from drop-down list depending on your screen resolution.
Cisco dCloud
Figure 89. Drop-down List with Map Reports Selected
6. The CPU Utilization Map report is selected by default from the Report drop-down list.
7. Under Display Controls in the lower right corner, check Show Labels.
8. Hover over or click on a VM to show the CPU utilization of the host. The output will be similar to the output shown below.
Figure 90. CPU Utilization Map Report Example
NOTE: This view does not display well in this small demo environment. Its value is realized in production environments with
larger number of hosts and virtual machines.
VM Stack View Report
2. From the menu bar, choose Virtual > Compute.
3. Click the VMs tab and then select one of the available VMs.
4. Click .
Cisco dCloud
Figure 91. Click Stack View
5. Review the Stack View, which provides an illustration of the underlying infrastructure which supports the VM (Guest OS,
Virtual Hardware, Hypervisor and Physical Infrastructure) and broken into Compute, Network and Storage resources
Figure 92. Stack View
Cisco dCloud
Scenario 7. Executing Predefined Workflows

In this scenario, we will demonstrate how you can use a predefined workflow to add a VLAN to three different systems and how to
remove the VLAN from all or some of the systems.
NOTE: To receive notification emails during this scenario, make sure the email client is configured.
Steps
The purpose of this scenario is to demonstrate executing two example workflows:
create a VLAN across three different systems and
create a UCS Service Profile from a template, assign a server from a server pool, then power it on
Create VLAN Using Predefined Workflow
2. From the menu bar, choose Policies > Orchestration.
3. Expand the dCloud folder and then double-click the workflow named Create vLan in dCloud to display the predefined
workflow.
4. Click Execute Now button at the top of Workflow Designer.
Figure 93. Workflow Designer Create vLan in dCloud
5. In the Submit Workflow popup, enter an ID and Name for the VLAN.
IMPORTANT: The vLAN ID must be a number between 10 and 500.The vLAN Name cannot contain spaces; however, you can
use underscores.
6. Click Submit.
Cisco dCloud
You will receive a confirmation that the request was submitted successfully, along with the assigned service request (SR) ID.
7. Click Show Detail Status.
Figure 95. Service Request Submit Status
Figure 96. Service Request Current Status
Cisco dCloud
8. Verify the creation of the VLAN you created in three systems.
a. VMware vSphere Client
o Login to the VMware vSphere Client window with Windows login credentials, if it is not already open.
o Choose Home > Inventory > Networking to display existing VLANs in the left-pane.
Figure 97. VMware vSphere Client
b. Nexus 1000v
o From the demonstration workstation, launch PuTTY [ ] and double-click Nexus 1000v to access the Nexus
1000v (admin/C1sco12345).
o Type show vlan at the command prompt, which will display all existing VLANs.
Figure 98. Command show vlan
o Type show port-profile brief at the command prompt, which will also display existing port profiles.
Cisco dCloud
Figure 99. Command show port-profile brief
c. UCS Manager
o From the demonstration workstation, launch Cisco UCS Manager [ ] and login (admin/C1sco12345)
o In the Navigation pane, click the LAN tab and then expand LAN Cloud > VLANs to display existing VLANs.
Figure 100. UCS Manager VLANs
NOTE: This section demonstrated how a single workflow created a VLAN in UCS Manager, VMware vSphere Client, and the
Nexus 1000. Demonstrate other defined workflows, or create your own based on customer interests.
9. Optionally, when your request has a status of Complete, you may choose to rollback all or part of your original service
request.
Cisco dCloud
a. Go to the Cisco UCS Director window for admin.
b. Choose Organizations > Service Requests to display all service requests.
c. Select your submitted request.
d. From the toolbar, click Rollback Request [ ]. (Rollback Request will not appear on the toolbar until a
Service Request is selected.)
NOTE: By default, all completed tasks related to the workflow are selected and you can de-select the items you do not want to
rollback.
e. Click Submit.
Create Service Profile Using Predefined Workflow
2. From the menu bar, choose Policies > Orchestration.
3. Expand the dCloud folder and then double-click the workflow named Create SP and Power On to display the predefined
workflow.
4. Click Execute Now.
Figure 101. Workflow Designer Create SP and Power On
5. In the Executing Workflow: Create SP and Power On popup, enter Demo_Service_Profile in the Name field.
6. Click Submit.
Cisco dCloud
You will receive an email confirmation that the request was submitted successfully, along with the assigned service request (SR)
ID.
7. Click Show Status Details and monitor the status until the service request has a status of Complete.
8. Verify the creation of the SP you created in UCS Manager as follows:
a. In the UCS Manager console, click the Servers tab and then expand the Servers > Service Profiles > root
hierarchy.
b. Verify that the recently created Demo_Service_Profile1 appears in the directory.
Figure 103. UCS Manager
NOTE: You may demonstrate other defined workflows or create your own based on customer interests.
9. Optionally, when your request has a status of Complete, you may choose to rollback all or part of your original service
request.
a. Choose Organizations > Service Requests to display all service requests and highlight your submitted request.
b. From the toolbar, click Rollback Request.
NOTE: By default, all completed tasks related to the workflow are selected and you can de-select the items you do not want to
rollback.
Cisco dCloud
Scenario 8. Rebranding Interface

Organizations can customize self-service portals. The logo, login page, home page, and so on can be customized for branding and
user interface-related changes.
The purpose of this scenario is to re-skin the interface to a different brand as admin and show the customized interface as demo
user.
Steps
1. Logout of any open IE window where Cisco UCS Director is logged in as demouser, or open an IE browser and accept the
security warnings.
2. Show how the login window looks.
Figure 104. Login Before Rebranding
3. Go to the Google Chrome Cisco UCS Director window for the user admin.
4. From the menu bar, choose Administration > User Interface Settings.
5. On the Login Page tab, check Use customizable Login page.
6. Choose the available Logo Image.
7. Choose the available Background Image and click Submit. Click OK.
8. Go to the Cisco UCS Director window for the user demouser and refresh the browser window.
9. Show how the login window has changed.
Cisco dCloud
Figure 105. Login After Rebranding
10. Login to UCS Director (demouser/C1sco12345) in this window.
11. Show the color scheme of the user interface.
Figure 106. Page Header Before Rebranding
12. Go to the Cisco UCS Director window for the user admin.
13. On the User Interface Settings window, click the Color Theme tab.
14. Change the Theme Style from Default Style to another style available from the drop-down list (for example, Red Style).
15. Click Save.
16. Click OK.
17. Go to the Cisco UCS Director window for the user demouser and reload the webpage [ ]. It may be necessary to wait as
long as 30 seconds for the change to take effect.
18. Show how the color theme of the interface has changed.
Figure 107. Page Header After Rebranding
Cisco dCloud
Cisco dCloud
Appendix A. Release Notes

5.3 v1 Release Notes
New features in Cisco UCS Director 5.3 release:
Upgraded UCS Director to 5.3.0.2
Upgraded UCS Bare Metal Agent to 5.3
Added new Virtual SAN demo scenario
Back To Top
Cisco dCloud
Appendix B. Troubleshooting and Saving Content
Troubleshooting
If you encounter any performance or access issues for UCS Director, including seeing the message Cisco UCS Director is starting
up. Please wait until the system is ready., for more than 10 minutes, follow the steps below to stop and then restart the services.
1. From the demonstration workstation desktop, open the Scripts folder.
2. Double-click Restart Cisco UCS Director to start the UCSD services.
3. A command window will open to execute the script and will close when the script has completed.
NOTE: It will take approximately five minutes for UCS Director to restart.
4. You may now continue with your demonstration.
Back To Top
Save Customized Demo

To save a customized version of this demonstration, follow the steps below, after you have completed all of your customizations.
Customizations made to the demo may not load correctly when attempting to run the custom demo if the steps below are not
followed.
1. Complete all customizations to your demonstration before continuing.
2. From the demonstration workstation desktop, open the Scripts folder.
3. Double-click Demo Save Shutdown.
A command window will open to execute the script and will close when the script has completed.
The demonstration workstation will shutdown.
This script will save any customizations to UCS Director and prepare the demo environment for a clean save.
Do not run the Demo Save Shutdown script until after you have completed all customizations.
4. After the Demo Save Shutdown script has completed, go to the Cisco dCloud UI. Go to My Dashboard > My
Demonstrations and save your customized UCS Director demonstration.
Back To Top
Cisco dCloud

Cisco UCS Director 5-4 VMware v1 Demo Guide

Enviado por

Dados do documento

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Cisco UCS Director 5-4 VMware v1 Demo Guide

Enviado por

Direitos autorais:

Formatos disponíveis

Cisco dCloud

Cisco UCS Director 5.4 with VMware v1

About This Cisco Solution

Learn more about Cisco UCS Director at http://www.cisco.com/go/ucsdirector.

Scenario 1: Unified Dashboard Overview

Scenario 3: Self-Service Catalog for Predefined Workflow

Scenario 4: Application Container Deployment

Scenario 5: Bare Metal Provisioning using Bare Metal Agent Server

Scenario 6: CloudSense Analytics and Reports

Scenario 7: Executing Predefined Workflows

Scenario 8: Rebranding the UCS Director User Interface

Figure 1. Demonstration Topology

PREPARATION IS KEY TO A SUCCESSFUL CUSTOMER PRESENTATION.

2. Schedule a session. [Show Me How]

4. Test your connection. [Show Me How]

NOTE: It may take up to 20 minutes for your session to become active.

6. Click View to open the active session.

Workstation 1: 198.18.133.36, (dcloud\demouser/C1sco12345)

8. From the demonstration workstation, launch VMware vSphere Client [ ].

Configure an Email Client

Scenario 1. Unified Dashboard Overview

The dashboard is completely customizable.

o Move the widgets around

o See and change different options for widgets

o Mouse over graph element to display popup tooltip

Figure 2. Dashboard Admin View

1. On the menu bar, choose Converged.

2. Click the dCloud Datacenter icon.

Figure 3. dCloud Datacenter

3. Show the available components in dCloud Datacenter.

Figure 4. dCloud Datacenter Stack

Show how to drill-down into virtual administration.

Click the back button [ ] to go back to the dCloud Datacenter stack.

Show how to drill-down into the physical UCS chassis management.

Click the back button to go back to the dCloud Datacenter stack.

Show how to drill-down into the device administration.

Click the back button to go back to the dCloud Datacenter stack.

Show how to drill-down into the storage device.

The HyperConverged menu will be explored once VSAN is enabled in Scenario 2.

Figure 5. Virtual Menu

Detailed components of an active VM

Typical lifecycle operations and infrastructure components

Storage utilization map

Figure 6. Virtual Menu > Compute

Physical infrastructure monitoring

Chassis and server details

Detailed information for storage

1. From the top menu, select Physical > Compute.

Figure 7. Physical Summary for dCloud Datacenter

Rollback service request feature for a successfully completed request

Resubmit service request features for a failed service request

1. From the top menu, click Organizations > Service Requests.

2. Double-click a Service Request to see the workflow.

Figure 8. Organizations Menu Service Request for All User Groups

Alter orchestration flow by dragging a task

Admin control of parameters the user can enter

Edit a trigger by picking a VM and parameter, and then build a rule

Figure 10. Administration > Users and Groups > Users

This concludes the activities in this scenario.

Figure 11. Resize vSphere and UCS Director Windows

4. In UCS Director, click Catalog.

Figure 12. Choose a Workflow

7. Select vesx3.dcloud.cisco.com from the Host Name drop-down.

Figure 13. Select the Host