Cisco UCS Director 6-0 Install Config v1 Lab Guide PDF

Cisco dCloud
Cisco UCS Director 6.0 Installation and Configuration Lab v1

Last Updated: 25-APRIL-2017
About This Lab

This lab includes the following scenarios:
• Scenario 1: Deploy and Set Up UCS Director (Optional)
• Scenario 2: Initial System Configuration
• Scenario 3: Creation of Policies
• Scenario 4: Configure User Account & Create a Catalog
• Scenario 5: PXE Boot Using Baremetal Agent
• Scenario 6: Application Container Deployment
• Scenario 7: Deploy a VLAN using Orchestrator
Limitations
This UCS Director demonstration begins with a database restore. This means that when a saved session is restarted, database
changes will be overwritten and lost. To save a customized session, use the procedure in Appendix A to back up and restore the
database.
Requirements
The table below outlines the requirements for this preconfigured demonstration.
Table 1. Requirements
Required Optional
● Laptop ● Cisco AnyConnect
About This 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.
Topology
This content includes preconfigured users and components to illustrate the scripted scenarios and features of the solution. Most
components are fully configurable with predefined administrative user accounts. You can see the IP address and user account
© 2017 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 1 of 63
Cisco dCloud
credentials to use to access a component by clicking the component icon in the Topology menu of your active session and in the
scenario steps that require their use.
Figure 1. Topology
Cisco dCloud
Get Started
BEFORE PRESENTING
Cisco dCloud strongly recommends that you perform the tasks in this document with an active session before presenting in front of
a live audience. This will allow you to become familiar with the structure of the document and content.
It may be necessary to schedule a new session after following this guide in order to reset the environment to its original
configuration.
PREPARATION IS KEY TO A SUCCESSFUL PRESENTATION.
Follow the steps to schedule a session of the content and configure your presentation environment.
1. Initiate your dCloud session. [Show Me How]
NOTE: It may take up to 10 minutes for your session to become active.
2. 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, Username: DCLOUD\demouser, Password: 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.
3. Click Desktop on the Start menu.
Figure 1. Start Menu
Cisco dCloud
Scenario 1. Deploy and Set Up UCS Director (Optional)

The purpose of this scenario is to Deploy UCS Director using an OVF file, which takes approximately five to ten minutes to
complete. An instance of UCS Director is already configured in the environment, so it is not necessary to perform this scenario in
order to perform initial system configuration.
Once you deploy this iteration of UCS Director, use the previously configured UCS Director to follow the script.
Steps
Deploy UCS Director
1. From the demonstration workstation, double-click the VMware vSphere icon to open vSphere. Check Windows Session
Credentials and click Log In.
2. From the top menu, select File > Deploy OVF Template.
3. Page through the Deploy OVF Template as follows:
a. In the Source window, click Browse.
b. Navigate to ftproot > CUCSD_6_0_0_0_60299_VMWARE_GA and double-click CiscoUCSDirector_60299.ovf.
Figure 2. Double-click the OVF Template File
c. Click Next.
d. Click Next through the OVF Template Details window – no changes needed.
e. Click Accept in the End User License Agreement window and click Next.
f. Click Next through the Name and Location window – no changes needed.
g. In the Host/Cluster window, select dCloud-Cluster and click Next.
h. In the Storage window, select DemoDatastore and click Next.
i. Click Next through Disk Format
j. In the Network Mapping window, select n1kv_mgmt_vlan under Destination Networks and click Next.
Cisco dCloud
Figure 3. Map the Network
k. In the Properties window, change the default passwords to C1sco12345.
l. Enter the IP Addresses:
• Management IP Address: 198.18.133.110
• Management IP Subnet Mask: 255.255.192.0
• Gateway IP Address: 198.18.128.1
4. Click Next, then Finish to begin the process of VM deployment. The process will take approximately ten minutes.
Figure 4. Monitor the Deployment Process
5. When the process has completed, the CUCSD-6.0.0 VM will show in the Hosts and Clusters window in vSphere in the
Powered On state.
Figure 5. CUCSD-6.0.0 VM in vSphere
6. Proceed to Initial System Configuration.
Cisco dCloud
Scenario 2. Initial System Configuration

The purpose of this section is to perform Guided Setup in UCSD, to configure the Mail, DNS, and NTP servers as well as the
Administrative Email Address. Following Guided Setup, the scenario walks through policy setups as follows:
• Network
• Storage resource allocation
• Computing
• Service delivery
• Virtual Data Center
• Cost Model
• End User Self-Service
Steps
Guided Setup
1. From the workstation desktop, open a Chrome browser.
2. Click the UCSD Login shortcut on the bookmarks tab and log in (admin/C1sco12345).
NOTE : The browser shortcut opens the default Lab iteration of UCS Director. If you have deployed your own UCS Director in
Section 1 and wish to run this scenario in that iteration, open Chrome and go to 198.18.133.110 (admin/C1sco12345).
3. From the top UCS Director menu, click Administration > Guided Setup.
4. Click Launch Guided Setup.
Figure 6. Launch Guided Setup
5. Check the Initial System Configuration checkbox and click Submit.
Cisco dCloud
Figure 7. Select Initial System Configuration
NOTE: There may be a pop-up that asks whether to work from a saved session or start a new one. Always click Start A New
Session.
6. All of the tasks are selected. Click Submit.
Figure 8. All Tasks Selected
7. In the Initial System Configuration dialog, perform the following functions:
a. Click Next through the Overview window.
b. Click Skip through the Licensing window, as the license has already been updated.
c. Click Next through the Locale window, which is already set to English.
d. It is not necessary to modify the DNS Server, which is configured to 198.18.133.1. If desired, check the Modify DNS
Servers checkbox to see where a different DNS IP could be entered. Uncheck the box and click Next.
Cisco dCloud
Figure 9. Configure DNS Servers
e. In the Mail Server window, enter the parameters shown below. The Password is C1sco12345.
Figure 10. Configure Mail Server
f. Click Next.
g. In the Email Address window, no changes are necessary as the email address is configured. If desired, click the
Modify Email Address checkbox to see the fields that are used to configure an email address.
Figure 11. Configure Email Address
h. Uncheck Modify Email Address and click Next.
i. Click Next through the NTP Server window, no changes are necessary.
j. Verify the details in the Summary window and click Next. Note that the License will show a status of Skipped,
because license configuration is not a part of this lab.
Cisco dCloud
Figure 12. Verify Summary
8. In the Recommended Next Steps window, click the Launch button under FlexPod Wizard.
Figure 13. Launch FlexPod Wizard
9. In the FlexPod Configuration window, perform the following operations. The purpose of the FlexPod configuration is to allow
UCS Director to communicate with UCSM, NetApp, Nexus Virtual devices and VMware.
a. Click Next through the Overview.
b. Click to add a POD.
c. In the Add POD window, enter dCloud Datacenter in the Name field.
d. Click to add a site.
e. In the Add Site dialog box, enter dCloud-Site in the Site Name field.
f. Enter administrator in the Contact Name field and click Submit, then OK to close the Add Site dialog box.
Cisco dCloud
Figure 14. Configure the Site
g. In the Site field, select dCloud-Site from the drop-down.
h. Enter RTP in the Address field.
i. Click Add, then OK to close the Add POD dialog box.
Figure 15. Add POD Dialog Box
j. Select dCloud Datacenter from the Pod drop-down and click Next to proceed to Cisco UCS Manager configuration.
k. Enter the UCS Manager configuration parameters as shown in the following figure. The Password is C1sco12345.
Cisco dCloud
Figure 16. UCS Manager Configuration Parameters
l. Click Next to proceed to the NetApp window, and add a NetApp account to the POD.
m. Enter the NetApp account parameters as shown in the following figure. The Password is C1sco12345.
Figure 17. NetApp Configuration Parameters
n. Click Next to proceed to Nexus Physical Devices.
o. Click Skip to proceed to Nexus Virtual Device configuration – Nexus Physical Devices are outside the scope of this
lab.
p. Enter the Nexus Virtual Device parameters as shown in the following figure. The Password is C1sco12345.
Cisco dCloud
Figure 18. Nexus Virtual Device Configuration
q. Click Next to proceed to VMware, and add a VMware account to the POD.
r. Enter the VMware account parameters as shown in the figure below. The Password is C1sco12345.
Figure 19. VMware Parameters
s. Click Next to review the Summary. The Nexus Physical Device will show as Skipped, because the configuration of
physical devices is not within the scope of this lab.
Figure 20. Summary
Cisco dCloud
10. Click Next to accept the configuration.
11. Click Close. Device Discovery and the vDC Creation Wizard are outside the scope of this lab.
12. Verify the FlexPod configuration as follows:
a. Click Converged on the top UCS Director menu.
b. Click the dCloud Datacenter icon.
c. Verify that all of the Components are present.
Figure 21. dCloud Datacenter Components
Cisco dCloud
Scenario 3. Creation of Policies

Cisco UCS Director provides a self-service portal where virtual machines (VMs) are provisioned from a pool of assigned resources
using predefined policies set by administrators.
A policy is a group of rules that determine where and how a new VM is provisioned within the infrastructure based on the
availability of system resources.
Cisco UCS Director requires that you set up the following policies to provision VMs:
• Computing
• Storage
• Network
• System
Steps
Network Policy Configuration
The purpose of this section is to configure a Network Policy, which includes resources such as network settings, DHCP or static IP,
and the option to add multiple vNICs for VMs provisioned using this policy
1. From the top UCS Director menu select Policies > Virtual/Hypervisor Policies > Network.
2. On the VMware Network Policy tab, click .
Figure 22. Add VMware Network Policy
3. In the Network Policy Information dialog box, perform the following steps:
a. Enter Sales Network Policy in the Policy Name field.
b. Select dCloud-Cluster from the Cloud Name drop-down.
c. Click to add a VM Network.
Cisco dCloud
Figure 23. Add VM Network to the Network Policy
4. In the Add Entry to VM Networks dialog box, enter eth0 in the NIC Alias field.
5. Select E1000 from the Adapter Type drop-down.
6. click to add a Portgroup
7. Click Select to select a Portgroup.
8. Select demo_vlan from the Portgroups list and click Select.
Figure 24. Select Portgroup
9. Click Submit to close the Add Entry to Port Groups dialog box, then click OK.
10. Click Submit to close the Add Entry dialog box, then click OK.
11. Click Submit to create the Sales Network Policy, then click OK.
12. Verify the presence of the Sales Network Policy in the VMware Network Policy list.
Figure 25. Sales Network Policy
Cisco dCloud
Storage Resource Allocation Policy
The purpose of this section is to configure the Sales Bronze Storage Policy.
A storage policy defines resources such as the datastore scope, type of storage to use, minimum conditions for capacity, latency,
and so on.
1. From the main UCSD menu click Policies > Virtual/Hypervisor Policies > Storage.
2. Click the VMware Storage Policy tab.
3. Click .
Figure 26. Add VMware Storage Policy
4. In the Add Storage Resource Allocation Policy dialog box, configure the following parameters:
a. Enter Sales Bronze Storage Policy in the Policy Name field.
b. Enter Sales Bronze Storage Policy in the Policy Description field.
c. Select dCloud-Cluster from the Cloud Name drop-down.
d. Uncheck Use Local Storage and Use SAN.
e. Click Next.
Figure 27. Add Storage Resource Allocation Policy
13. Click Next through the Additional Disk Policies window – no changes are required.
Cisco dCloud
14. Click Submit, then OK to create the Storage Policy.
15. Verify the presence of the Sales Bronze Storage Policy in the VMware Storage Policy list.
Figure 28. VMware Storage Policy List
Computing Policy
The purpose of this section is to create the Computing policy.
The purpose of this section is to create the computing policies that determine the compute resources that can be used during
provisioning that satisfy group or workload requirements.
Administrators can define advanced policies by mixing and matching various conditions in the computing policy.
1. From the top menu, select Policies > Virtual/Hypervisor Policies > Computing.
2. On the VMware Computing Policy tab, click .
3. In the Add Computing Policy dialog box, perform the following steps:
a. Enter Sales Bronze Compute Policy in the Policy Name field.
b. Select dCloud-Cluster from the Cloud Name drop-down.
c. Click Submit, then OK to create the Compute policy.
Figure 29. Create Compute Policy
Cisco dCloud
4. Verify the presence of the newly created Compute Policy in the list.
Figure 30. Newly Created Compute Policy
System Policies
The purpose of this section is to deploy the Service Delivery policy – including the System policy, Cost Model, and End User Self-
Service policy.
A system policy defines the system-specific information such as the template to use, time zone, OS specific information, and so on.
1. From the main UCSD menu, select Policies > Virtual/Hypervisor Policies > Service Delivery.
2. On the VMware System Policy tab, click .
3. In the System Policy Information dialog box, perform the following steps:
a. Enter Sales System Policy in the Policy Name field.
b. Enter dcloud.cisco.com in the DNS Domain field.
c. Enter dcloud.cisco.com in the DNS Suffix List field.
d. Enter 198.18.133.1 in the DNS Server List.
e. Select Windows and Linux from the VM Image Type drop-down, which enables Windows-only parameters.
Figure 31. System Policy Information
Cisco dCloud
f. Scroll down and enter dCloud in the License Owner Name field.
g. Enter Cisco Systems in the Organization field.
h. Enter C1sco12345 in the Administrator Password field.
i. Enter 198.18.133.1 in the Domain field.
j. Enter administrator in the Domain Username field.
k. Enter C1sco12345 in the Domain Password field.
Figure 32. Windows Parameters
l. Click Submit, then OK.
m. Verify the presence of the Service Delivery Policy in the VMware System Policy list.
Figure 33. Service Delivery Policy
Cost Model
A cost model is used to define the unit level costs of virtual resources such as CPU, RAM, and storage. These costs are used for
chargeback calculations of VMs within the virtual infrastructure.
Cisco dCloud
1. From the top UCSD menu, click Policies > Virtual/Hypervisor > Service Delivery.
2. Click the Cost Model tab.
3. Click . .
4. Configure the Cost Model by changing the values as shown in the following figure, and click Add, then OK.
Figure 34. Add Cost Model
5. Verify the presence of the Sales Bronze Cost Model in the Cost Model list.
Figure 35. Sales Bronze Cost Model
End User Self-Service Policy
The purpose of this section is to set up the End User Self-Service policy. This policy governs which actions will be allowed on VMs
that are created as a result of self-service workflows.
1. Still in the Service Delivery window, scroll over to the End User Self-Service Policy tab and click .
2. In the Add End User Policy pop-up, select VMware from the Account Type drop-down.
Cisco dCloud
3. Click Submit.
4. Enter End User Self Service in the Policy Name field.
5. Click the VM Power Management checkbox. Scroll down to see what other options are available,
6. Click Submit, then OK.
Figure 36. Self-Service Policy Parameters
Edit Virtual Data Center
The purpose of this section is to create a Virtual Data Center.
A Virtual Data Center (vDC) is a logical grouping that combines virtual resources, operational details, rules, and policies to manage
specific group requirements.
A group or organization can manage multiple vDCs. images, templates, and policies. Organizations can allocate quotas and assign
resource limits for individual groups at the vDC level.
You can also define approvers specific to a vDC. The approvers assigned to a particular vDC must approve all service requests
from users for VM provisioning.
A VM that is provisioned using a service request can be associated with a specific vDC. When you create a service request, you
can choose the vDC on which this VM is provisioned. You can view a list of the vDCs that are available for a particular group and
choose the required vDC when provisioning VMs. You will see vDC selection in later when ordering a VM.
1. From the main UCS Director menu, select Policies > Virtual/Hypervisor Policies > Virtual Data Centers.
2. On the vDC tab, click .
3. Select VMware from the Account Type drop-down and click Submit.
4. In the Add vDC dialog box, perform the following steps:
a. Enter Sales Bronze vDC in the vDC Name field.
Cisco dCloud
b. Click in the Group field to add a group.
c. Configure the Group as follows in the Add Group dialog box and click Add, then OK.
Figure 37. Add Group Parameters
d. Click Select and select the newly created Sales group from the Group list. Click Select.
e. Under Approvers and Contacts, click Select to see the dialog box where approvers can be added to this vDC.
Figure 38. Click Select
f. Select admin and click Select.
NOTE: If you do not select an approver, any service request for a VM in the vDC will be completed without approval being
required.
g. Scroll down to the Policies section and select policies from the drop-downs as follows:
Cisco dCloud
Figure 39. Select Policies
h. Click Add, then OK to create the vDC.
i. Verify the presence of the vDC in the vDC list.
Figure 40. Newly Created Sales Bronze vDC
Cisco dCloud
Scenario 4. Configure User Account & Create A Catalog

Users can self-provision virtual machines (VMs) using predefined catalog items. A catalog is created by the system administrator
or the end user. It defines parameters such as the cloud name and the group name to which the VM is bound.
To aid in managing catalogs, Cisco UCS Director allows you to group similar catalogs within a folder.
The purpose of this scenario is to:
• Add the demouser account
• Create a Standard catalog of self-service workflows that can be accessed by that account
• Place a workflow in the catalog that creates a virtual Ubuntu 12 Server
Steps
Create a User Account
The purpose of this section is to create the demouser user in UCS Director.
1. From the top UCS Director menu select Administration > Users and Groups.
2. Click the Users tab.
3. Click .
4. in the Add User dialog box, perform the following steps:
a. Select Service End-User from the User Role drop-down.
b. Select Sales Group from the User Group drop-down.
c. Enter demouser in the Login Name field.
d. Enter C1sco12345 in the Password and Confirm Password fields.
e. Enter demouser@dcloud.cisco.com in the User Contact Email field.
f. Enter demo in the First Name field.
g. Enter user in the Last Name field.
h. Click Add, then OK to complete the creation of the user account.
Cisco dCloud
Figure 41. Add User Parameters
Create a Catalog
The purpose of this section is to create a catalog of self-service operations that are available to the recently created demouser.
1. From the top UCS Director menu select Policies > Catalogs.
2. Click .
3. In the Add Catalog pop-up, select Standard from the Catalog Type drop-down and click Submit.
4. In the Add Catalog dialog box, perform the following steps:
a. Enter Unbuntu 12 Server in the Catalog Name field.
b. Select VM: Linux from the Catalog Icon drop-down.
c. Next to Selected Groups, click the Select button and check the Sales Group checkbox in the resulting list. Click
Select.
d. Next to Image, click Select and select the ubuntu12srv image from the list. Click Select.
Figure 42. Select ubuntu12srv Image
e. Verify the Basic Information parameters and click Next to proceed to Application Details.
Cisco dCloud
Figure 43. Verify Basic Information
f. Click Next through the Application Details window, without making any changes.
g. Click Next through the User Credentials window, without making any changes.
h. Click Next through the Customization window, without making any changes.
i. Click Next through the VM Access window, without making any changes.
j. Click Submit, then OK to create the catalog.
Figure 44. Standard Catalog is Created
Configure an Email Client
Set up external email to receive notifications based on requests submitted and completed during the demo.
1. From the demonstration workstation, open the Scripts folder and double-click Cisco UCS Director Email Setup.
4. A console window will open and then close, which indicates that the script is working in the background.
5. In the External Email Address popup window, enter the email address you want emails related to the demo sent. Click OK.
Cisco dCloud
Using Self-Service Provisioning
1. Open a Firefox browser window. Click the Cisco UCS Director shortcut and log into UCS Director (demouser/C1sco12345).
2. Click anywhere in the Catalogs section to view the user catalog.
Figure 45. Click Catalogs
3. Double-click the recently created Unbuntu 12 Server workflow.
Figure 46. Unbuntu 12 Server Workflow in Standard Demouser Catalog
4. In the Create Service Request dialog box, perform the following steps:
a. Click Next through the Catalog Selection window, without making any changes.
b. Click Next through the Deployment Configuration window, without making any changes.
c. Click Next through the Custom Specification window, without making any changes.
d. Click Next through the Custom Workflow window, without making any changes.
e. Review the Summary and click Submit, then OK.
Cisco dCloud
Figure 47. Review the Summary
5. Monitor the service request as follows:
a. Click the menu icon .
b. Click Services in the top menu.
Figure 48. Menu > Services
c. Click the service request and click the View Details icon.
Figure 49. Double-click the New Service Request
Cisco dCloud
6. 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.
Figure 50. 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.
• Select Organizations > My Approvals in the top menu.
• Click the service request and click Approve.
Cisco dCloud
Figure 51. Service Approval Request Example
NOTE: The entire process to create and customize the VM may take up to 15 minutes to complete. The Complete status may
display within 5-6 minutes, but wait until you receive notification that the request is complete.
• Click Approve on the resulting screen.
Figure 52. Click Approve
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.
Cisco dCloud
Figure 53. My Approvals
• In the Service Request window, you may enter an optional Comment and then click Approve.
Figure 54. Service Request
7. Click OK.
8. Return to the demouser UCS Director window. Click the View Details button to show that 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 the VM may take up to 15 minutes to complete. You may see a status of
Complete within 5-6 minutes, but the scenario has not completed until the email is received. Continue with the rest of the scenario
while waiting for completion.
Cisco dCloud
Figure 55. Workflow Status Example
9. From the demonstration workstation, go to VMware vSphere Client
a. Show and explain how the VMware Recent Tasks and Summary windows correlate with the request submitted via
UCS Director.
10. Return to the Cisco UCS Director window for admin.
a. You should still be on the My Approvals page. If not, click Organizations > My Approvals.
b. Click Refresh to see the Status of the request.
11. Continue to monitor the status of the service request in all three windows until it is completed.
Cisco dCloud
Figure 56. Simultaneous Monitoring of VM Provisioning Request
12. Go to the email client configured for the demo.
• The account will receive an email with the subject Service Request for provisioning of VM(s) has been completed,
when the request is complete.
Figure 57. Example Service Request for Provisioning VM(s) Completed Email
13. Close all windows except the UCS Director admin window in preparation for Scenario 5.
Cisco dCloud
Scenario 5. PXE Boot Using Baremetal Agent

Cisco UCS Director Baremetal Agent (Baremetal Agent) automates the process of using a Preboot Execution Environment (PXE)
to install operating systems on Baremetal servers or virtual machines. Baremetal Agent provides the following services that are
required for a functional PXE install environment:
• Dynamic Host Control Protocol (DHCP)
• Hypertext Transfer Protocol (HTTP)
• Trivial File Transfer Protocol (TFTP)
We have already deployed Baremetal Agent VM in this lab.
NOTE: Perform this scenario in a FireFox browser.
Steps
Configuring the Baremetal Agent Network
The purpose of this section is to configure the Baremetal Agent on UCS Director. It is performed in the administrator window.
1. From the top menu of UCS Director, click Administration > Physical Accounts.
2. Click the Bare Metal Agents tab, and click .
Figure 58. Add Baremetal Agent
3. In the Add Bare Metal Agent Appliance dialog box, perform the following steps:
a. Enter ucsd-bma in the Account Name field.
b. Check the Baremetal Agent Uses Different Interfaces for Management and PXE Traffic checkbox.
c. Enter 198.18.133.111 in the Management Address field.
d. Enter 198.18.6.111 in the PXE Interface Address field.
e. Enter root in the Login ID field.
f. Enter C1sco12345 in the Password field.
g. Verify all fields and click Submit, then OK.
Cisco dCloud
Figure 59. Verify All Fields
4. In the Baremetal Agents window, verify that the newly created ucsd-bma agent is Reachable. Click ucsd-bma.
NOTE: It may be necessary to click the ancillary menu drop-down to see the Configure DHCP option.
5. Click Configure DHCP.
Figure 60. Agent is Reachable
6. Verify that the IP addresses are the same as those shown in the figure below, and click Submit, then OK.
Figure 61. DHCP Addresses for Baremetal
Cisco dCloud
7. Click ucsd-bma again. Click the button when it becomes live.
8. Verify that eth1 is configured, and click Close.
Figure 62. eth1 is Configured
9. Click
10. Click Start in the Start Bare Metal Agent Appliance dialog box. This starts the Enabled Services – DHCP, TFTP, and HTTP.
It may take a minute or two before the confirmation dialog box appears. Click OK.
11. Back in the Bare Metal Agents window, verify that the Enabled Services show as Running.
Figure 63. Enabled Services Are Running
Provisioning a Non-Windows Operating System Image
This procedure provisions an OS image for installation by Baremetal Agent. You must provision the OS image before you can
request a PXE boot for the OS image.
1. From the Windows Start button on the lab workstation, open WinSCP.
Cisco dCloud
Figure 64. Open WinSCP
2. In the WinSCP Login dialog box, enter the login parameters to login to the recently configured Baremetal Agent:
• Host Name: 198.18.133.111
• User name: root
• Password: C1sco12345
3. Click Login.
Figure 65. Login to WinSCP
4. In the resulting window, navigate to the ftproot directory on the local side.
Cisco dCloud
Figure 66. Navigate to ftproot
5. On the Baremetal Agent side, navigate to / <root>/opt.
6. Right-click the VMware-VMvisor-Installer… file on the local side and click Rename on the menu. Ctrl-C to copy the filename
to the clipboard for future use. Do not change the file name.
7. Drag the VMware-VMvisor-Installer-6.0.0.update02.iso file to the Baremetal Agent side and click Copy in the resulting
dialog box.
Figure 67. Drag the VMware File to the Baremetal Agent Side
8. Wait until the file has been completely copied.
9. Open PuTTY from the lab workstation Task Bar.
10. Double-click ucsd-bma in the Saved Sessions window, and log in to the console window (root/C1sco12345).
Cisco dCloud
Figure 68. ucsd-bma Saved Session
11. Type the command cd /opt/infra at the command prompt.
12. Type the command ./isoExtractor.sh at the command prompt.
Figure 69. Output of the ./isoExtractor.sh command
13. Enter 5 <Enter> to install ESXi 6.0.
14. At the Image path prompt, enter /opt/VMware-VMvisor-Installer-6.0.0.update02.iso.
NOTE: The filename may be different from the filename in the above command. If so, Ctrl+V to paste the filename into the
command.
15. At the OS catalog name prompt, enter ESXI-6.
Cisco dCloud
Figure 70. Command Sequence
16. Return to the WinSCP window. On the Baremetal Agent side, navigate to the /opt/cnsaroot/templates directory, and verify
the presence of the newly created ESXI-6 template.
Figure 71. ESXI-6 Template
17. Return to the UCS Director admin window, which is still open to the Physical Accounts > Baremetal Agents page.
18. Click the ucsd-bma agent and click View Details.
19. Click Refresh to see the new ESXI-6 image in the BMA OS List. This may take a few minutes.
Figure 72. ESXI-6 Image in BMA OS List
Cisco dCloud
20. From the top UCS Director menu, select Physical > Compute.
21. Click dCloud Datacenter, then click the PXE Boot Requests tab.
22. Click Add PXE Request.
Figure 73. Add PXE Request
23. The first field in the PXE Boot Request Add dialog box requires the MAC Address of the server. Obtain it as follows:
a. Return to the vSphere window.
b. Right-click vesx4 and click Edit Settings.
Figure 74. Edit Settings
c. Click Network adapter 1 to obtain the MAC Address.
Figure 75. MAC Address
24. Return to UCS Director and complete the PXE Boot Request Add as follows:
Cisco dCloud
a. Copy/Paste the MAC Address in the Server MAC Address field.
b. Enter esxi4 in the Host Name field.
c. Enter C1sco12345 in the Root Password and Confirm Password fields.
d. Enter 0 in the Management VLAN field.
e. Enter 198.18.133.134 in the Server Address field.
f. Enter 255.255.192.0 in the Network Mask field.
g. Enter 198.18.128.1 in the Gateway field.
h. Enter 198.18.133.1 in the Name Server field.
i. Choose the appropriate time zone from the Timezone drop-down.
j. Select ucsd-bma from the Target BMA drop-down.
k. Select ESXI-6 from the OS-Type drop-down.
Figure 76. PXE Boot Request Add
l. Click Submit, then OK to add the PXE Boot Request.
25. Click the new PXE Boot Request, then click Setup PXE Environment to make sure the PXE request is executed with the
correct boot options.
Cisco dCloud
Figure 77. Click Setup PXE Environment
26. Click Submit, then OK through the pop-up.
Enable VMRC and Load ESXi Installer
VMware vSphere and vCloud Director contain the VMRC browser plug-in that can be loaded in supported web browsers. Web
applications running in the browser can use the VMRC browser plug-in to access virtual machine console functions by using the
VMRC JavaScript API. With a web application that uses VMRC browser plug-in and the VMRC API, users can remotely access,
and interact with, a virtual machine from any system with the appropriate web browser and operating system.
NOTE: This portion of the lab must be performed in Firefox.
1. From the top UCS Director menu select Virtual > Compute.
2. Click the VMs tab and select vesx4.
Figure 78. Select vesx4
3. Scroll all the way to the right and click .
4. Scroll all the way to the bottom of the list and click Enable/Disable VMRC.
5. In the resulting pop-up, click the Enable VMRC Console checkbox and click Submit, then OK.
6. Select vesx4 again. Click and select Power ON from the menu.
7. Click Proceed in the VM Task dialog box.
8. Wait for the Completed pop-up – click OK.
9. Select vesx4 again and click Launch VM Client.
10. Select VMRC Console (Browser Plugin) from the Access Scheme drop-down and click Proceed, then OK.
11. The VMRC Console tab opens in Chrome and shows the ESXI-6 image loading. This can take 10-15 minutes.
NOTE: Proceed with the rest of the scenario and check back on the VMRC Console tab later to confirm the successful boot.
Cisco dCloud
Scenario 6. 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 section is to create a workflow that can be used to deploy the three-tier application container from the template
created in the previous section, by cloning an existing workflow and modifying it.
Steps
Clone and Edit an Existing Workflow
1. From the top UCS Director menu select Policies > Orchestration.
2. On the Workflows tab, expand the Default > Containers folder and review the existing workflows. A Fenced Container Setup
workflow already exists.
3. Select the Fenced Container Setup workflow and click Clone.
Figure 79. Fenced Container Workflow
4. Enter dCloud Fenced Container in the Workflow Name field.
5. Scroll down to Save Options and check Place in New Folder. Enter dCloud in the Folder Name field.
6. Under Notifications, select Send e-mail to User Group and Admin from the Email Policy drop-down.
Cisco dCloud
Figure 80. Save Options & Notifications
7. Click Next.
8. Click Next through the Add User Inputs screen – no changes are necessary.
9. Click Submit without making any changes in the Add User Outputs screen, then click OK.
10. Verify that the dCloud folder now exists, with the newly created dCloud Fenced Container workflow in it.
NOTE: The dCloud Fenced Container workflow is currently an exact copy of the original Fenced Container workflow. The next few
steps edit the workflow to work in this lab environment.
Figure 81. dCloud Fenced Container Workflow
11. Double-click the workflow.
12. Double-click Allocate Container VM Resources to edit this task.
Figure 82. Allocate Container VM Resources
13. In the Edit Task dialog box, click Next through Task Information and User Input Mapping.
Cisco dCloud
14. In the Task Input screen, perform the following steps:
a. Select Distributed Virtual Portgroup N1K from the Virtual Network Type drop-down.
b. Enter VSM in the Primary DVSwitch field.
c. Click Next.
16. Click Validate Workflow.
17. Close the workflow.
Deploy an Application Container
Application containers are a templatized approach to provisioning applications for end users. Each application container is a
collection of VMware virtual machines (VMs) and/or Baremetal servers (BMs) with an internal private network that is based on
rules specified by the administrator. An application container can have one or more VMs and BMs and can be secured by a fencing
gateway (for example, a Virtual Secure Gateway) to the external or public cloud.
Creating an Application Container involves the following tasks:
• Creating application policies, including a gateway policy and a virtual infrastructure policy.
• Creating a container template:
o Add networks (one network per application tier)
o Add virtual machines and Baremetal servers
o (Optional) Add load balancing and firewall services
o Add deployment policies
• Creating a container based on the container template
1. In the UCS Director admin window, click Policies > Application Containers from the top menu.
2. Click the Virtual Infrastructure Policies tab, and click Add Policy.
Figure 83. Add Policy
3. In the Add Virtual Infrastructure Policy dialog box, perform the following steps:
a. Enter Sales_3Tier_APP in the Policy Name field and click Next to advance to the Gateway screen.
b. Click Next through the following three screens without making any other changes.
c. Review the Summary and click Submit, then OK.
Cisco dCloud
Figure 84. Summary
4. Click the Application Container Templates tab and click Add Template.
Figure 85. Add Template
5. In the Add Application Container Template dialog box, perform the following steps:
a. In the Template Specification window, enter Sales_3Tier_Template in the Template Name field.
b. Click Next.
c. In the Virtual Infrastructure Policy window, the recently created Sales_3Tier_APP policy is selected by default.
Click Next.
d. In the Networks window, click to add a network.
e. Change the defaults to match the figure below and click Submit, then OK.
Figure 86. Network Parameters
f. Click Next.
Cisco dCloud
g. In the Virtual Machines window, click to add a VM.
h. Add three VMs – db-server, web-server, and app-server – with the following parameters:
PARAMETER db-server app-server web-server
VM Name db-server app-server web-server
VM Image db-server app-server web-server
Use Network Uncheck Uncheck Uncheck

Configuration From
Image
VM Network Interface Add Add Add
VM Network Interface eth0 eth0 eth0

Name
Select the Network l3vlan2 l3vlan2 l3vlan2
Adapter Type E 1000 E 1000 E 1000
IP Address 198.18.2.10 198.18.2.20 198.18.2.30
i. Review the resulting table of Virtual Machines and click Next.
Figure 87. Table of Virtual Machines
j. In the Policies window, select policies as shown in the figure below and click Next.
Figure 88. Policies
k. In the Options window, select End User Self Service from the drop-down and check both checkboxes.
Cisco dCloud
Figure 89. Options
l. Click Next.
m. In the Workflows window, click Select.
n. Type dcloud in the Search bar to locate the dCloud Fenced Container workflow.
Figure 90. Search for the dCloud Fenced Container Workflow
o. Click Select, then click Next.
p. Review the Summary and click Submit, then OK.
Figure 91. Summary
Add the Template to the Catalog
The purpose of this section is to add the application container template to the catalog. This will allow users to deploy a three-tier
application from the Sales_3Tier_Template, using the dCloud Fenced Container workflow.
1. From the top UCS Director menu, click Policies > Catalogs.
Cisco dCloud
2. Click .
3. Select Service Container from the Catalog Type drop-down and click Submit.
4. Enter Sales_3TierAPP in the Catalog Name field.
5. Click the Select button next to Group and select Sales Group.
6. Click Next.
Figure 92. Service Container Folder Appears In Catalog
8. Double-click the Service Container folder to see the Sales_3TierAPP dCloud-Cluster workflow, which can be deployed by a
user.
9. Return to the IE browser window, where demouser is already logged into UCS Director. If the window is not open, open an IE
browser and log into UCS Director as demouser (demouser/C1sco12345).
10. Click the Menu icon, and click Catalogs.
11. Run the Sales_3TierAPP workflow as follows:
a. Double-click the Sales_3TierAPP dCloud-Cluster workflow or click Create Request to create a service request.
b. Click Next through Catalog Selection.
c. In the Deployment Configuration screen, enter contain in the Service Container Name field and click Next.
Figure 93. Deployment Configuration
d. Click Submit.
12. Monitor the request as follows:
Cisco dCloud
a. Click the Menu icon and click Services in the top UCS Director menu.
b. Double-click the most recent request, or click it and click View Details.
Figure 94. Monitor the Service Request
c. Click Refresh until the workflow completes successfully, which will take approximately ten minutes.
Figure 95. Successful Completion
13. Return to the vSphere window, where the three VMs (app-server, db-server, and web-server) have been created.
Figure 96. Three New VMs in vSphere
Cisco dCloud
14. Navigate to VMs and Templates to see the Fenced Container with the three VMs.
Figure 97. Fenced Container
15. Click any VM, then click the Summary tab to see its IP Address.
Figure 98. IP Address of the app-server VM
16. Verify that the newly deployed application is reachable as follows:
a. Open a browser tab and type webserver.dcloud.cisco.com in the Location bar.
Cisco dCloud
Figure 99. Web Server Connected to Application and Database Servers
Cisco dCloud
Scenario 7. Create and Deploy a VLAN using Orchestrator

Orchestrator works by executing a series of scripted actions called tasks. Each task performs one action. By connecting tasks so
that the input of one task is the output of a previous task, you build up a workflow to automate administrative processes such as
creating VMs, provisioning Baremetal servers, setting up storage, compute, and network resources, and many others.
The purpose of this scenario is to add a workflow to the catalog that allows users to create a VLAN, and then to demonstrate
deploying that workflow.
Steps
1. Login to UCS Manager (admin/C1sco12345). Click LAN in the left menu and review the existing VLANs.
Figure 100. Default VLAN in UCS Manager
2. In the admin window of UCS Director, click Policies > Orchestration to display the workflows.
3. Click .
4. In the Add Workflow dialog box, perform the following steps:
a. Enter Add VLAN to UCSM in the Workflow Name field.
Cisco dCloud
b. In the Save Options section, select dCloud from the Select Folder drop-down.
c. In the Notifications section, select Send e-mail to User Group and Admin from the Email Policy drop-down.
d. Click Next.
e. Click to add a User Input.
f. Enter VLAN_ID in the Input Label field.
g. Click Select and select VLAN ID from the list of inputs. Click Select.
h. Click Submit, then OK.
i. Click to add another User Input.
j. Enter VLAN_Name in the Input Label field.
k. Click Select and select Generic Text Input from the list of inputs. Click Select.
l. Click Submit, then OK.
Figure 101. User Inputs for VLAN Creation
m. Click Next.
n. Click Submit, then OK.
5. Review the workflow as it appears in the Workflow Designer. The shell of the workflow is there, but no tasks are associated to
it.
Figure 102. Create VLAN in UCSM Workflow – No Tasks
6. In the Available Tasks list, expand Physical Compute Tasks > Cisco UCS Tasks.
7. Drag Add VLAN onto the work window.
Cisco dCloud
Figure 103. Drag & Drop Add VLAN
8. In the Add Task dialog box, perform the following steps:
a. Click Next through Task Information.
b. In the User Input Mapping window, scroll to the VLAN Name section and click the Map to User Input checkbox.
c. Select VLAN_NAME from the User Input drop-down.
d. Scroll to the VLAN ID section.
e. Check the Map to User Input checkbox.
f. Select VLAN_ID from the User Input drop-down.
Figure 104. User Inputs
g. Click Next through Task Inputs, where the UCSM mapping is pre-selected.
Cisco dCloud
h. Click Submit, then OK.
9. Review the new task in the Workflow Designer.
Figure 105. New Create VLAN Task
10. Click Validate Workflow.
11. Click OK when the workflow is validated.
12. Click Execute Now to execute the workflow – the User Inputs box pops up, requesting the VLAN name and ID -
13. Enter 10 in the VLAN_ID field.
14. Enter usingUCSD in the VLAN_NAME field.
Figure 106. User Inputs for VLAN Creation
15. Click Submit.
16. Click Show Detail Status to monitor the workflow, clicking Refresh until it completes.
17. Return to UCSM and check the VLANs – the newly created VLAN exists in UCSM.
Cisco dCloud
Figure 107. VLAN in UCSM
Cisco dCloud
Appendix A. Save Customized Demo

To save a customized version of this demonstration, complete all customizations and follow the steps below. Customizations made
to the demo may not load correctly when attempting to run the custom demo if the steps below are not followed.
Back up UCS Director Database
Complete all desired customizations, and then use this procedure to back up the UCS Director database.
1. Complete all customizations to your demonstration before continuing.
2. From the demonstration workstation desktop, open a PuTTY window.
3. Double-click ucsd.dcloud.cisco.com in the Saved Sessions window.
4. Log in to ucsd.dcloud.cisco.com (shelladmin/C1sco12345) to bring up a list of Actions.
5. Type 7 <Enter> to select Backup Database.
Cisco dCloud
6. Enter y <Enter> at the Services will be stopped before Database Backup. Do you want to continue? [y/n] prompt.
7. Enter the required credentials as follows:
• FTP Server IP Address: 198.18.133.1
• FTP Server Login: demouser
• FTP Server Password: C1sco12345
8. Wait for the process to complete, which will take a few minutes, and note the name of the remote backup file.
Cisco dCloud
9. Open a Windows Explorer window, and navigate to the ftproot drive. Verify that the backup file exists.
10. Return to the PuTTY window. Hit <Enter> at the Press return to continue… prompt to return to the list of actions.
11. Close the PuTTY window. Click OK in the confirmation window.
12. Go to the Cisco dCloud UI. Click Dashboard and save the customized UCS Director demonstration.
Restore the UCS Director Database
Perform this procedure at the start of a Saved Session.
1. On the workstation desktop, open Windows Explorer and navigate to the Z: drive.
2. Single-click the backup file twice, and copy the filename to the clipboard.
3. Open a PuTTY window, and double-click ucsd.dcloud.cisco.com to open a PuTTY session.
4. Log in (shelladmin/C1sco12345) to display the list of Actions.
5. Enter 8 <Enter> to restore the database.
6. Enter y <Enter> at the Services will be stopped before Database Restore. Do you want to continue? [y/n] prompt.
7. Enter the FTP server credentials as follows:
• FTP Server IP Address: 198.18.133.1
• FTP Server Login: demouser
• FTP Server Password: C1sco12345
• Remote Backup File (Absolute Path to File): <paste backup file name>
8. Enter y <Enter> at the Do you want to restore from file <filename> [y/n] ? prompt.
NOTE: The filename listed in the above prompt will be a temporary filename that mirrors the saved backup filename.
Cisco dCloud
9. Wait until the process has finished, which will take a few minutes, and the Press return to continue… prompt appears.
10. Hit <Enter> to return to the list of Actions.
11. Enter 4 <Enter> to restart services.
12. Hit <Enter> to return to the list of Actions.
13. Enter 2 <Enter> to display the list of services.
14. If any services are still down, hit <Enter> to return to the list of Actions. Keep displaying the list of services until all services
are up.
15. Double-click the UCS Director shortcut on the wkst1 desktop, and make sure UCS Director is reachable.
16. Go to the Cisco dCloud UI. Click Dashboard and save the customized UCS Director demonstration.
Cisco dCloud

Cisco UCS Director 6-0 Install Config v1 Lab Guide PDF

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Cisco UCS Director 6-0 Install Config v1 Lab Guide PDF

Hochgeladen von

Copyright:

Verfügbare Formate

Cisco dCloud

Cisco UCS Director 6.0 Installation and Configuration Lab v1

About This Lab

• Scenario 1: Deploy and Set Up UCS Director (Optional)

• Scenario 2: Initial System Configuration

• Scenario 3: Creation of Policies

• Scenario 4: Configure User Account & Create a Catalog

• Scenario 5: PXE Boot Using Baremetal Agent

• Scenario 6: Application Container Deployment

• Scenario 7: Deploy a VLAN using Orchestrator

● Laptop ● Cisco AnyConnect

About This Solution

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

PREPARATION IS KEY TO A SUCCESSFUL PRESENTATION.

1. Initiate your dCloud session. [Show Me How]

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

• Workstation 1: 198.18.133.36, Username: DCLOUD\demouser, Password: C1sco12345

3. Click Desktop on the Start menu.

Figure 1. Start Menu

Scenario 1. Deploy and Set Up UCS Director (Optional)

Deploy UCS Director

3. Page through the Deploy OVF Template as follows:

a. In the Source window, click Browse.

b. Navigate to ftproot > CUCSD_6_0_0_0_60299_VMWARE_GA and double-click CiscoUCSDirector_60299.ovf.

Figure 2. Double-click the OVF Template File

g. In the Host/Cluster window, select dCloud-Cluster and click Next.

h. In the Storage window, select DemoDatastore and click Next.

i. Click Next through Disk Format

Figure 3. Map the Network

k. In the Properties window, change the default passwords to C1sco12345.

l. Enter the IP Addresses:

• Management IP Address: 198.18.133.110

• Management IP Subnet Mask: 255.255.192.0

• Gateway IP Address: 198.18.128.1

Figure 4. Monitor the Deployment Process

Figure 5. CUCSD-6.0.0 VM in vSphere

6. Proceed to Initial System Configuration.

Scenario 2. Initial System Configuration

• Storage resource allocation

• Virtual Data Center

• End User Self-Service

1. From the workstation desktop, open a Chrome browser.

4. Click Launch Guided Setup.

Figure 6. Launch Guided Setup

5. Check the Initial System Configuration checkbox and click Submit.

Figure 7. Select Initial System Configuration

6. All of the tasks are selected. Click Submit.

Figure 8. All Tasks Selected

7. In the Initial System Configuration dialog, perform the following functions:

a. Click Next through the Overview window.

Figure 9. Configure DNS Servers

Figure 10. Configure Mail Server

Figure 11. Configure Email Address

h. Uncheck Modify Email Address and click Next.

Figure 12. Verify Summary

Figure 13. Launch FlexPod Wizard

a. Click Next through the Overview.

b. Click to add a POD.

d. Click to add a site.

Figure 14. Configure the Site

g. In the Site field, select dCloud-Site from the drop-down.

h. Enter RTP in the Address field.

i. Click Add, then OK to close the Add POD dialog box.