cisco ucs director 5.2 lab-v.1.5

Cisco UCS Director 5.2 Lab

Cisco UCS Director 5.2

Lab Guide

Version 1.5

Gregg Mills - Juan Montanez – Rudy Slavec - Jean Michaels Solutions Readiness Engineers Americas Partner Organization

3


Contents Introduction .................................................................................................................................... 4 Lab Objectives ................................................................................................................................. 4 Disclaimer ........................................................................................................................................ 5 Build Information ............................................................................................................................ 5 Prerequisite Knowledge .................................................................................................................. 5 Logical Topology.............................................................................................................................. 6 Versions ........................................................................................................................................... 6 Exercise 1: Review the Current Setup ............................................................................................. 7

Section 1.1: Access the lab environment ................................................................................... 7 Section 1.2: Access vCenter Server and review the VMware setup ........................................ 11 Section 1.3: Verify access to Datastores .................................................................................. 17

Exercise 2: Install Cisco UCS Director ............................................................................................ 18 Section 2.1: Deploy the UCSD OVF Template ....................................................................... 18 Section 2.2: Applying CUCSD Patch ...................................................................................... 31 Section 2.3: Deploy VACS Patch ............................................................................................. 38 Section 2.4: Use Internet Explorer to Login to UCSD ............................................................. 48 Section 2.5: UCS Director Initial configuration using Guided Setup ....................................... 50

Exercise 3: UCS Director Basic Information .................................................................................. 58 Section 3.1: Working with User Profiles .................................................................................. 58 Section 3.2 Enable Dashboard: ................................................................................................. 62 Section 3.3: System Parameters ................................................................................................ 66 Section 3.4: Change Login Page Background .......................................................................... 68 Section 3.5: Change Application Logo ..................................................................................... 74 Section 3.6: Change Application Header .................................................................................. 81

Exercise 4: Adding Groups & Users, Configuring LDAP in UCS Director ....................................... 83 Section 4.1 Verification that system is ready............................................................................ 83 Section 4.2: Adding a User Group ............................................................................................ 87 Section 4.3: Setting Resource Limits for a group ..................................................................... 89 Section 4.4: Adding a User to UCS Director ............................................................................ 91 Section 4.5: Configuring LDAP Integration ............................................................................. 94 Section 4.6: Adding User Groups from an AD Server ........................................................... 100

Exercise 5: Pod Configuration, Creating Policies and Virtual Datacenter Configuration ........... 102 Section 5.1: Using guided Setup for FlexPod configuration .................................................. 102 Section 5.2: Adding a second pod ........................................................................................... 119 Section 5.3: Add NetApp Storage Physical Account.............................................................. 137 Section 5.4: Creating Computing Policies .............................................................................. 145 Section 5.5: Creating Network, Storage and System Policies ................................................ 148 Section 5.6: Creating Cost Models ......................................................................................... 161 Section 5.7: Configuring Virtual Data Center (VDC) ............................................................ 164

APPENDIX A: Troubleshooting .................................................................................................... 169 Cisco AnyConnect Secure Mobility Client Installation Instructions:................................. 175 Troubleshooting Cisco AnyConnect Connection issues: .................................................... 179

4


Introduction Cisco UCS Director is the primary component of the Cisco UCS Director Product Suite. This component provides a converged infrastructure management solution with self-service functions that enable end users and administrators to request as well as manage virtual and physical infrastructure components with ease. Cisco UCS Director is a 64-bit appliance that uses standard virtual templates. It can be installed and managed through VMware vCenter or Microsoft Hyper-V manager. In this lab you will act as a network consultant who is executing a statement of work for an enterprise customer. The customer is preparing for a new deployment of Cisco UCS Director in their VMware environment. The customer has asked you to install and set up the software. You will use the Cisco UCS Director 5.2 OVF; along with a UCSD patch; to complete the installation.

Lab Objectives The following tasks will be performed in this lab with Cisco UCS Director Software:

• Installation, patching and initial configuration

• Basic administration using guided setup wizards

• Product customization

• Adding users & groups

• Configuring LDAP integration

• Use of UCS Director Wizards to configure a FlexPod

• Adding Individual Infrastructure Accounts

• Discover and monitor Virtual Resources

• Configure Policies for Virtual Cloud (Compute, Storage, Network and System Policies)

• Create a Cost Model

• Configure a Virtual Data Center (VDC)

5


Disclaimer This Guide is intended to demonstrate one way to configure the network, to meet the specified requirements of this example. There are various ways that this can be accomplished, depending on the situation and the customer’s goals/requirements. Please ensure that you consult all current official Cisco documentation before proceeding with a design or installation. This lab is primarily intended to be a learning tool, and may not necessarily follow best practice recommendation at all times, in order to convey specific information. This guide is not intended to be a deployment guide. It is intended for learning purposes only.

Build Information As of the writing of this document, the current relevant documentation could be found on CCO at the following links:

• Cisco UCS Director Installation and Upgrade on VMware vSphere, Release 5.2 - http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/ucs-director/vsphere-install-guide/5-2/b_Installing_UCSDirector_on_vSphere_5_2.html

• Cisco UCS Director Administration Guide, Release 5.2 – http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/ucs-director/administration-guide/5-2/b_Cisco_UCSD_Admin_Guide_52.html

• Cisco UCS Director FlexPod Management Guide, Release 4.1 - http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/ucs-director/flexpod-mgmt-guide/4-1/b_Cisco_UCSD_FlexPod_MGT_GD.html

• Video: Installing UCS Director – http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/ucs-director/videos/5-2/installing_ucs_director.html

• Video: Cisco UCS Director Device Discovery - http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/ucs-director/videos/5-2/ucs_director_discover.html

• Video: Cisco UCS Director FlexPod Configuration - http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/ucs-director/videos/5-2/ucs_director_flexpod.html

Prerequisite Knowledge A solid understanding of VMware vSphere, NetApp Storage, and Cisco UCS solutions is assumed.

http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/ucs-director/vsphere-install-guide/5-2/b_Installing_UCSDirector_on_vSphere_5_2.html

http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/ucs-director/vsphere-install-guide/5-2/b_Installing_UCSDirector_on_vSphere_5_2.html

http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/ucs-director/administration-guide/5-2/b_Cisco_UCSD_Admin_Guide_52.html

http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/ucs-director/administration-guide/5-2/b_Cisco_UCSD_Admin_Guide_52.html

http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/ucs-director/flexpod-mgmt-guide/4-1/b_Cisco_UCSD_FlexPod_MGT_GD.html

http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/ucs-director/flexpod-mgmt-guide/4-1/b_Cisco_UCSD_FlexPod_MGT_GD.html

http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/ucs-director/videos/5-2/installing_ucs_director.html

http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/ucs-director/videos/5-2/installing_ucs_director.html

http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/ucs-director/videos/5-2/ucs_director_discover.html

http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/ucs-director/videos/5-2/ucs_director_discover.html

http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/ucs-director/videos/5-2/ucs_director_flexpod.html

http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/ucs-director/videos/5-2/ucs_director_flexpod.html

6


Logical Topology The following diagram depicts the logical topology of the lab.

Versions The lab was constructed using the following software versions: Flexpod Architecture: ESXi 5.5.0 VMware vCenter Server 5.5.0 Cisco UCS Director 5.2.0.0 (patched to 5.2.0.1) Cisco UCS Manager Simulator 3.0(1c) Netapp Simulator 8.2.3 (7-Mode)

7


Exercise 1: Review the Current Setup An important first step in any deployment is to review the existing network setup before you install and configure any new equipment. In this exercise, you will take a quick look at the current VMware deployment and verify that the server admin has set up the virtual hosts for use by the Cisco UCS Director.

Section 1.1: Access the lab environment

Step 1: To access the lab, open Cisco AnyConnect from your computer and use the following URL to connect to: 128.107.217.3/ucsd and click Connect.

Note: If you do not have AnyConnect installed, please refer to Appendix A: Troubleshooting

Step 2: If you see a security warning, click Connect Anyway to continue.

8


Step 3: A Cisco AnyConnect login box will appear. Your password will be assigned by the lab Proctor. The username is formatted as stu7xx where the xx is your assigned pod number. Enter your username and password that was assigned, and click OK

Username stu7xx Password assigned by instructor

Note: If you receive an error message regarding the VPN connection being blocked due to it being an untrusted VPN server please see the Appendix A for steps to resolve this issue.

Step 4: Click Accept in the Cisco AnyConnect banner popup.

Step 5: Once you have successfully made a connection to the lab via Anyconnect VPN, open Microsoft Remote Desktop (RDP) on your computer.

Generally, Microsoft Remote Desktop can be found by navigating to the Start > All Programs > Accessories > Remote Desktop Connection. If the Start menu on your system includes the Run… box, you can also try navigating to Start > Run… and typing mstsc.exe into the run box and then clicking OK to run the program.

9


Step 6: Click the arrow next to Show options to expand the window.

Step 7: Connect to your pod’s workstation. The IP address of your workstation depends on your pod number. The IP address is 172.20.x.11 where x is your pod number. For example, if you were assigned Pod 0, you would connect to 172.20.0.11.

Pod Workstation: 172.20.x.11 User name: administrator

Step 8: When prompted enter the username and leave the password field blank.

Username: administrator Password: no password (leave blank)

10


Step 9: Click yes for the remote verification warning.

Step 10: You should now see the Pod Workstation desktop.

11


Section 1.2: Access vCenter Server and review the VMware setup Let’s review the configurations that are present within vCenter before getting started with deploying UCSD.

Step 11: Locate and open the VMware vSphere Client icon on the Pod Workstation desktop.

12


Step 12: Your client should already be configured with the proper credentials to connect to vCenter and will connect automatically. However, if necessary, use the following credentials to log in to vCenter.

vCenter address: 10.1.7.10

Username: [email protected] Password: Cisc0123!

If you had to manually set or change the credentials, click the Login button

Note: Connecting to vCenter may take two to three minutes. Step 13: If you see a security warning, click Ignore.

Step 14: Once you access vCenter, if you are presented with the Home screen as shown below, click the Hosts and Clusters icon in the Inventory list.

13


Step 15: Click the + symbols in the left navigation pane as many times as necessary to fully expand the Hosts and Clusters view as shown below. You will notice that there is one Data Center (N1KV-DC), one cluster (N1KV-Cluster), two hosts (The red alarm symbols on the two hosts can be ignored) and four virtual machines.

14


Step 16: Select the first host in the list - 10.1.7.101 and then click the Configuration tab.

Step 17: In the Hardware window on the configuration page, select Networking.

Step 18: Under Networking there is one Standard Switch listed - vSwitch0. Verify that the Physical Adapter is vmnic0 and that the switch is connected to the VM Network and the Management Network.

15


Step 19: Take a moment to look at the properties for the vSwitch0. Select Properties above the physical Adapters listed.

Step 20: Verify the number of ports for vSwitch0 is set to 120.

Step 21: Select VM Network from the configuration list and verify the VM Network VLAN ID is set to None(0) - this is by default.

16


Step 22: Next, select Management Network to verify its settings. This VLAN ID should also be set to None (0), by default. When done, click Close.

17


Section 1.3: Verify access to Datastores In this lab, the datastores have already been created. The lab is configured using nested ESXi hosts, with two NetApp Simulators. Each host will have access to datastore1 and datastore2.

Step 23: Visually verify the host can access both datastores. While still under the Configuration tab for the first host (10.1.7.101), select Storage from the hardware list.

Step 24: Ensure that the view is set to Datastores and verify there are two NetApp datastores listed under the device column.

Step 25: Repeat the above nine steps for the second ESXi host – 10.1.7.102 – to verify that host’s networking and datastores are configured as shown in the steps.

In this exercise you verified that the VMware setup is ready for the rest of this lab. You have verified that the two ESXi hosts are configured. Do not close the vSphere client. You will continue to use it in the following sections.

18


Exercise 2: Install Cisco UCS Director

Section 2.1: Deploy the UCSD OVF Template

Step 26: If the vSphere client was closed in the previous section, log back in with the following credentials:

vCenter address: 10.1.7.10 Username [email protected] Password Cisc0123!

Step 27: Once logged back in, expand the server list to show the N1KV-Cluster under the N1KV-DC data center.

Step 28: Click on the N1Kv-Cluster to select it.

19


Step 29: From the menu list, click File and then Deploy OVF Template.

Step 30: The Deploy OVF Template dialog box appears. The OVF file has been saved to the E: drive of the administrator PC for you. To navigate to the source OVF file in on the workstation, click Browse

20


Step 31: Ensure that the E: Drive is selected, and then double click the CUCSD_5_2_0_0_VMWARE_GA folder.

Step 32: Select the cucsd_5_2_0_0.ovf file and click Open

21


Step 33: After clicking open, the Deploy OVF Template box appears again with the OVF file listed. Click Next>

Step 34: Review the OVF Template details and click Next>

22


Step 35: Click Accept to accept the End User License Agreement

Step 36: After accepting the EULA, the Next> button is no longer grayed out, click Next>

23


Step 37: Change the name to CUCSD-PODx (x = your pod number) and click Next>

Step 38: Click vacs_datastore1 (scroll and adjust the columns to ensure selection) and click Next>

24


Step 39: Choose the “Thin Provision” radio button and click Next >.

Step 40: First click on Destination Networks drop-down menu and then change the destination network to “VM Network”.

25


Step 41: Ensure VM Network appears in the Destination Networks list and then click Next>

Step 42: Leave DHCP for the IP address allocation scheme set. You’ll modify this setting later – after the VM has been deployed. To proceed click Next >

26


Step 43: Make sure that your Deployment settings match the screenshot and then click Finish

27


Step 44: A box will appear stating that the CUCSD OVF is deploying and it will also appear in the list under N1KV-Cluster. The deployment will take 40-60 minutes to complete.

Note In your own, production environment, you would continue to monitor the deployment until it has successfully completed – as shown by the example dialog box below. To save time in the lab, a new UCSD image has already been deployed for you. As such, you’ll cancel the deployment that you started and will switch over to the already-deployed image to continue the lab. The already-deployed image shows as CUCSD-Fresh_Deploy in vCenter.

Step 45: Click the Cancel button to cancel the deployment. Then, click Yes to confirm to abort the deployment.

Step 46: Wait two or three minutes until the deployment has backed out and the CUCSD-PODx VM no longer appears in vCenter under the N1KV-Cluster.

28


Step 47: Before starting the new UCSD VM (CUCSD-Fresh_Deploy), you need to change the VM’s resource reservations. Right-click the VM named CUSCD-Fresh_Deploy in the N1KV-Cluster and then click Edit Settings.

Step 48: Click on the Resources tab

Step 49: Select CPU and enter or verify the value of 4000 MHZ in the CPU Reservation field

29


Step 50: Next, select Memory from the Settings list and enter or verify the value 4096 MB for the Memory Reservation

Step 51: After changing the amount of CPU and memory reservation, click OK at the bottom right of the dialog box to save your changes.

Step 52: With the CUCSD-Fresh_Deploy VM still selected, click the power on button to start the image.

30


Step 53: While the VM is starting, click the console button to open the console window to view the power up cycle.

Step 54: Wait approximately 5-10 minutes for the CUCSD to finish booting. (NOTE: The following are screen captures taken throughout the boot cycle… They do not show the entire process.) When the boot process is complete, a blue screen will appear in the console window. The Failed messages are ok; they simply appear because it is not fully configured yet.

31


Section 2.2: Applying CUCSD Patch After the UCSD VM is deployed and booted, the next step is to install the UCSD patch.

Step 55: Filezilla FTP server has already been started on your student desktop. Navigate to the system tray on your student desktop and right-click on the Filezilla Server icon.

Step 56: From the context menu that appears, click on Restore.

NOTE: Keep the FileZilla Server window open and visible in the background so you can monitor the status of the connection and transfer.

32


Step 57: On the bottom task bar return to the CUCSD- Fresh_Deploy console window.

Step 58: Using your keyboard arrows keys, select the Login option if it is not already selected. Press <Enter> to login

Step 59: At the localhost login: prompt, use the following credentials:

Username = shelladmin Password = changeme (Note: The password will not be displayed when typed.)

33


When the menu loads, part of it will scroll by quickly. The screenshot below has been manually edited to show all of the menu options for your reference.

Step 60: Option 1 is used to change the shelladmin password. Type “1” and press Enter to be prompted to change the password for shelladmin. Set the New UNIX password to “Cisc0123!” (Without the quotes). Enter the password twice. Then, press Enter to continue

34


Step 61: After changing the password, the next step is to apply the CUCSD patch. Option 19 from the menu is used to apply a patch. Enter “19” and press Enter to start the process to apply patch.

Step 62: Enter “y” for yes to respond to the message that appears stating that the services need to be stopped before the patch can be applied. Do you want to stop the services [y/n]: y

Step 63: Enter “n” for no when prompted to back up the database(this is a new install so there is no need to back up the database)

Do you want to take database backup before applying patch[y/n]? n

35


Step 64: You are now prompted for the Patch URL. Enter the following: Patch URL: ftp://admin:[email protected]/cucsd_patch_5_2_0_1.zip

Step 65: Enter “y” to install the patch when prompted and hit Enter

Note In your own, production environment, you would continue to monitor the patch installation until it has successfully completed. The patch install will take between 60 and 90 minutes on average. When the patch is successfully installed, the UCSD console will return to the menu display. At that point, you would use menu option 21) Reboot Appliance to reboot the UCSD and have it reload with the new patch applied. To save time in the lab, an already-patched UCSD image has been created for you. As such, you’ll shut down the VM with the patch install that you started and will switch over to the already-patched UCSD image to continue the lab. The already-patched image shows as CUCSD-Post_Patch in vCenter.

36


Step 66: Use Ctl + Alt to release the mouse from the console window. On the console screen for the UCSD VM, navigate to VM > Power, and click Power Off (optionally, you can use the keyboard shortcut of Ctrl+E).

Step 67: Click Yes to confirm the power off command for the CUCSD-Fresh_Deploy VM. Click the red X to close the console window.

37


Step 68: Return to the vSphere Client and start the VM that already has the patch fully installed. In the vSphere Center navigation pane, locate and click the CUCSD-Post_Patch VM to select it, and then click Power On button to start the image.

Step 69: While the VM is starting, click the console button to open the console window to view the power up cycle.

38


Step 70: When the blue login screen appears (takes roughly 5 minutes), note the version number of the system on the first display line – the 5.2.0.1 indicates that the patch has been installed. Also, note the URL on the screen. You will use this URL to manage the UCSD VM from the web. At this time, you can close this console window. For this lab, all other configuration on the UCSD will be performed through SSH or the web interface.

Section 2.3: Deploy VACS Patch (Skip to Section 2.4 if you are not implementing the Cisco VACS Lab today)

If you intend to implement Cisco Virtual Application Container Services (VACS), the next step in deploying the CUCSD VM is to apply the VACS Patch. You can install the VACS patch through the console – in much the same way you installed the UCSD patch. However, you can also install the patch via an SSH session into the UCSD system. For this lab, you’ll use PuTTY to SSH into the UCSD to install the VACS patch.

39


Step 71: Open PuTTY from the desktop.

Step 72: Click UCS Director in the Saved Sessions area and then click Load to set the connection details for the UCSD.

40


Step 73: After Putty loads the connection details for UCSD, Click Open.

Step 74: If a Putty Security Alert is displayed, click Yes

41


Step 75: When prompted in the Putty window use the following credentials to login:

Username: shelladmin [email protected]’s password: Cisc0123! Press Enter

The menu loads very quickly after logging in. We are going to apply another patch, but this time it will be a VACS patch. (Note: The PuTTY settings for this connection have been modified so that you can see the entire menu in the output window.)

Step 76: Type “19” and press Enter

42


As you saw with the earlier patch, the system will need to stop the appliance services before the patch can be applied.

Step 77: Type “y” and press Enter to stop the services

Step 78: When prompted to make a backup of the database, enter “n” and press <Enter> to continue.

Step 79: When prompted for the Patch URL type, ftp://admin:[email protected]/VACS-5_2_STV_1_1a.zip and press <Enter> Step 80: Confirm that the system is applying the correct patch. Type “y” and press <Enter>

43


The patch will now download and install.

NOTE: When the patch has completed (takes about 5 to 8 minutes), you will be prompted to press return to continue.

Step 81: Press <Enter> to continue.

44


Step 82: Now that the patch is installed, the appliance will need to be rebooted. Type “21” to reboot the appliance and press <Enter>

Step 83: The prompt will ask if you want to reboot the appliance, type “y” and press <Enter>.

Step 84: The message Rebooting successful appears after the reboot.

45


Step 85: The putty window will notify you that the connection has been lost. Click OK

Step 86: Return to vCenter and select the CUCSD-Post_Patch VM. Then click the console window button to reopen the console window if it was close before.

46


Step 87: When the window opens, watch as the CUCSD reboots.

Step 88: The CUCD VM window will turn blue when it’s done rebooting.

47


Step 89: Open Internet Explorer from your management PC using the icon on the task bar.

Step 90: The homepage is set to https://10.1.7.220:443 and will load the Cisco UCS Director Login page. It may take a minute or two but accept any security messages that appear.

The display will show the system starting up message. NOTE: The message may take a minute or two to appear if the UCSD VM console has just returned to its blue window state.

https://10.1.7.220/

48


Step 91: Watch the Internet Explorer window for the system to finish starting up. The login screen should appear when the system is completely restarted. When the login prompt reappears move on to the next section.

Section 2.4: Use Internet Explorer to Login to UCSD

Step 92: If you do not already have a browser opens to the UCSD (skipped installing the VACS patch), return to your management PC and open Microsoft Internet Explorer from the taskbar.

The homepage is set to https://10.1.7.220:443 and will load the Cisco UCS Director login page. If you are prompted about a problem with the website’s certificate, click Continue to this website (not recommended) to continue to the login page.

https://10.1.7.220/

49


Note: It can take 5-10 min for the login screen to appear after the services are restarted. If the login screen fails to appear after 10 minutes, all of the services may not be running. If the login screen does not appear, use the troubleshooting steps in Appendix A to restart the UCSD services, and then continue with the following steps.

Step 93: When the login screen appears, enter the following username and password:

Username: admin Password: admin

Click Login

Note: If an authentication error appears upon trying to log in, please follow the UCSD services reset in the Appendix A and then try logging in again.

50


Step 94: If prompted to save the password info, click Not for this site.

Step 95: If prompted to enable AutoComplete for this website, click No.

Section 2.5: UCS Director Initial configuration using Guided Setup The Guided Setup is a tool available within UCS Director that will walk through the configuration process of certain functions. The Guided setup will be used to do some initial configuration within the UCS Director Web interface. Upon loading the page, the Guided Setup dialog will be displayed. You will use this dialog for the initial configuration.

51


Step 96: Click the check box for Initial System Configuration and then click Submit

Step 97: Here you can choose the tasks that you want the wizard to complete. From the Select Tasks list, uncheck the boxes for the tasks Select Locale, Mail Setup, and Configured Email

NOTE: You should have checkmarks in the checkboxes for Apply License, DNS Server, and NTP Server only.

Step 98: When you are sure of your choices, click Submit

52


Step 99: Read through the Prerequisites and Sequence of Steps sections and then click Next

Step 100: The next step in the custom wizard is to upload a license. The required valid license file has been saved on the E: drive of your student PC. To locate the license click Browse

53


Step 101: The license file is located in the UCS License folder on the New Volume (E:) drive. Browse to E:/UCS License folder and click Open

Step 102: Then choose the license file CCUIC201309102115438650 and click Open

Step 103: The license file appears in the upload field. Click Upload to upload the file.

54


Step 104: A box appears stating that the File Upload is completed, click OK

Step 105: Click the Next button at the bottom right of the page to move to the next step in the wizard.

Step 106: The DNS Server information shown is incorrect. Click the checkbox next to Modify DNS Servers. After clicking the checkbox, a DNS Servers list appears. Delete the current DNS Server entry by highlighting it and pressing <Delete> on your keyboard.

55


Step 107: Type 10.1.7.5 in the box and then click Next.

Step 108: The NTP Server information will also need to be corrected. Click the checkbox next to Modify NTP Servers. After clicking the checkbox, a NTP Servers list appears. Delete the current NTP Server entries by highlighting them and pressing <Delete> on your keyboard.

56


Step 109: Set the NTP Server to 10.1.7.5 and click Next

Step 110: On the summary page the status of Apply License, DNS Server, and NTP server should be green. If so, click finish. Note: If green checks missing go back and verify the correct information has been configured in the wizard following the previous steps.

57


Step 111: The submit result box appears indicating everything was successful. Click OK

Step 112: The wizard closes and you are returned to the UCS Director interface. Notice the differences in the menu. If the VACS patch was not installed the “Converged” option is the first in the list and if VACS was installed the “Solutions” options will appear first.

…or…

58


Exercise 3: UCS Director Basic Information In this exercise you will be working with user profiles, enabling the Dashboard within UCSD, adjusting the system parameters and making changes to the user interface settings.

Section 3.1: Working with User Profiles

Step 113: Before working with the User Profile, review the Converged information currently configured. If you installed the VACS patch and are at the Solutions menu option, click on the Converged option from the menu bar.

Step 114: The default pod is displayed.

59


Step 115: Navigate to Administration > Users and Groups

Step 116: Notice the set of tabs such as ‘User Groups’, ‘Login Users’, ‘Current Online Users’, etc, available under the Users and Groups Option.

Step 117: On the Users Groups tab we see the Default Group. Select the Default Group and watch the options change above the list. This is the called the context menu. The context menu allows configuration changes dependent upon the current selection.

60


Step 118: Select the Login Users tab

Step 119: Select the admin user in the list and click Edit

Step 120: When the Edit user box appears, enter the information in the corresponding fields to update the profile:

User Contact Email: [email protected] First Name: Admin Last Name: User

Click Save

mailto:[email protected]

61


Step 121: The Submit Result box appears indicating the User information was modified. Click OK

Step 122: You can now see updated profile admin information appear in the fields.

62


Section 3.2 Enable Dashboard: The Dashboard is the first window that you will see when you login to UCS Director. It’s not automatically available when UCSD is first deployed, but it can be enabled so you can display report widgets from the dashboard.

Step 123: Notice that Dashboard is currently not a menu option. To enable the Dashboard for the admin user, click on the admin option at the top right corner.

Step 124: Click on the Dashboard tab

Step 125: To enable the dashboard, check the Enable Dashboard check box and then click on Apply.

63


Step 126: There is no message that will appear after clicking to apply. Click the “x” to close the User Information window.

Step 127: Verify that the Dashboard tab is now available for admin user.

Step 128: Click on Dashboard and enable the Automatic Refresh by on the button that currently shows the word OFF.

64


Step 129: The dashboard contents are now set to be refreshed based on the Interval time selected. Currently it is set to refresh every 5 minutes. Change the Interval value to 10 minutes by sliding the dot to the right

Now that the Dashboard is enabled, summary reports can now be added, allowing the user to immediately view those reports upon logging into the UCSD web interface.

Step 130: To add a summary report of active VMs vs. inactive VMs to the Dashboard, navigate to Virtual > Compute.

Step 131: Multiple summary reports related to VMs are shown on the summary tab, let’s add one to the dashboard. Click on the drop-down arrow at the top right of the report titled VMs Active vs Inactive. Then, click on Add to Dashboard.

65


Step 132: Click OK to close the information box telling you that the report has been added to the Dashboard.

Step 133: Navigate back to the Dashboard. The VMs Active vs Inactive report is now shown on the Dashboard.

Step 134: (Optional) Log out and back in to the UCSD web interface to verify that the Dashboard is the first screen shown when logging in.

66


Section 3.3: System Parameters In this section you will configure some of the UCSD System parameters.

Step 135: Navigate to Administration > System from the menu.

Step 136: To change the system parameters start by clicking on System Parameters tab.

Step 137: Modify the following system parameters:

Number of Days to keep Deleted VMs Data: 90 Number of Days to keep Trend Data: 90

67


Step 138: Use the drop down menu to change the Number of Days to keep Metering Data to 120.

Step 139: Change the Currency to your local currency by selecting it from the drop down menu.

Step 140: Click Save

68


Step 141: Click OK to close the Submit Results window.

Section 3.4: Change Login Page Background There are a few features that are customizable within the UCS Director interface. One of those features is the ability to change the background of the login page that users see.

Step 142: To start, click on Administration > User Interface Settings

69


Step 143: Select the checkbox Use customizable Login page. The Options appear to change the Logo Images and Background Images.(May have to scroll to see both)

Step 144: Click the green plus button to the right of Background Images (Scroll the window if needed).

Step 145: Enter the following:

Image label: My_Background Description: My Login Page Background

70


Step 146: There are images preloaded on the E: Drive to choose from. To locate them, click Browse.

Step 147: Browse to E:/UCS Backgrounds and double click on the folder to open

Step 148: Choose your preferred background from the folder and then click Open

71


Step 149: The mage is now listed in the field click Upload.

Step 150: The File Upload completed box will appear after the file is loaded. Click OK.

Step 151: Next, click Submit

Step 152: The Submit Result box will appear after the configuration change is added. Click OK.

72


Step 153: Select the My_Background image and click the button for Set selected image as currently used to use the new image as the login background.

Step 154: A message appears for confirmation of the use of My_Background for the login page. Click Submit.

Step 155: The Submit Result box will appear after the image is updated. Click OK.

73


Step 156: My_Background is now indicated as the Currently Used image. To finalize the change, click Submit.

Step 157: The Submit Result box will appear after the configuration change is saved. Click OK.

Step 158: Let’s view the changes. Click Log Out in the upper right menu.

When logged out, the login page should show the newly configured background image. If it doesn’t, log back in and make sure you followed all of the steps and clicked on all of the Submit buttons to add, apply, and save the changes before you logged out. (NOTE: Your screen may differ from the screenshot depending on the image you chose.)

74


Section 3.5: Change Application Logo In addition to changing the login screen, you can also change the application logo within the UCS Director interface.

Step 159: Log back in to UCSD with credentials:

Username: admin Password: admin

Click Login

75


Step 160: The Guided setup window appears again. Scroll to the bottom of the Guided Setup window and check the “Don’t show this page again” box. Then click Submit

Click Ok

The application logo is what appears in the upper left of the UCS Director header. Currently the application logo is the Cisco logo. It can be changed to a different image that has been saved on the E: Drive.

76


Step 161: The Application logo settings are located under the User Interface settings. Navigate to those settings by clicking on Administration > User Interface Settings.

Step 162: Select the Application Logo tab.

The Application Logo listed as the Default Image and Currently Used is the Cisco logo.

77


Step 163: To add another image, Click green plus button to the right of Images.

Step 164: The Add Entry to Images dialog box appears. Enter the Image Label as New_Application_Logo

Step 165: Locate the image file that has already been saved to the E: drive by clicking Browse. Take a moment to note the information below the file upload box that states the image specifications.

78


Step 166: Navigate to the E:\UCS Logos folder to select a new logo image. Then click Open

Step 167: Click Upload

Step 168: The File Upload completed box will appear after the file is loaded. Click OK.

79


Step 169: Click Submit

Step 170: The Submit Result box will appear after the image is added. Click OK.

Step 171: Select the newly added application logo called New Application Logo and mark

it as Currently Used by clicking the relevant action button .

80


Step 172: Confirmation of the change appears, click Submit

Step 173: The Submit Result box will appear after the image is updated. Click OK.

New Application Logo now shows as Currently Used.

Step 174: Re-load the web page or log out and log back in to UCSD. The new application logo appears in the upper left corner.

81


Section 3.6: Change Application Header The last item you will be modifying is the application header. This is located to the right of the application logo that you just changed. Currently, Cisco UCS Director is displayed along the header.

Step 175: Start by navigating to Administration > User Interface Settings

Step 176: Select the Application Header tab.

82


Step 177: To change the Application header, enter the following text:

Product Name: Cisco UCS Director Partner Labs Product Name 2nd Line: DataCenter Management The Enable About Dialog box should be checked

Click Save Note: If the Save option is not visible, maximize the browser window.

Step 178: The Submit Result box will appear after the configuration change is saved. Click OK.

Step 179: Re-load the web page or log out and log back in to UCSD. The new application header appears in upper left portion of the screen. (Note: You may have wait a minute and to reload the page more than once to see the change appear .)

You’ve taken a look at modifying user profiles, enabling the dashboard, adjusting system parameters and making changes to the login page background, application log and header within this section.

83


Exercise 4: Adding Groups & Users, Configuring LDAP in UCS Director For this next exercise you will add user groups and individual users in UCS Director. You will also work to configure LDAP. This will be done within the UCS Director Web interface.

Section 4.1 Verification that system is ready Before adding groups and users; or configuring LDAP, you’ll need to ensure that the UCS Manager VM that has been created in advance for this lab is powered on. You will also want to verify that you can ping UCS Manager from the desktop of your pod PC.

Step 180: Return to the vSphere Client, which may already be open and can be located on the task bar of the administrator PC. Click the N1KV-VC.n1kvlab.cisco.com- vSphere Client icon on the taskbar.

Step 181: If the icon does not appear there, double click the icon on the desktop and log back in.

vCenter address: 10.1.7.10

Username: [email protected] Password: Cisc0123!

84


Step 182: If the UCS Manager VM is not already powered up, select UCS Manager and click the Power On button to start it.

Step 183: With the UCS Manager VM still selected, open a console window to watch it power on. Click the console window button.

You will see the powered on button appear next to the vm name and the boot-up scripts running in the console window.

85


Step 184: After the UCS Manager has completed loading, it will present a login prompt on the console.

Step 185: Return to your management PC, open a command prompt window by clicking Start and then type CMD in the search window.

86


Step 186: In the command prompt window ping the UCS Manager VM. Type ping 10.1.7.227 and press <Enter>.

Step 187: Once you’ve verified that you can reach UCS Manager via ping, close the Command window and the UCS Manager console window. You can also close the vSphere Client.

87


Section 4.2: Adding a User Group Returning to Internet Explorer, log back into the UCS Director Web interface if previously closed. From here a user group can be manually added.

Step 188: To add a user, select Administration > Users & Groups.

Step 189: Ensure that the User Groups tab is selected and click the Add button to add a group.

88


Step 190: The Add Group box appears. Enter the following:

Name: Lansters Description: Network Team Code: ITX (X is your pod number) Contact Email = [email protected] First Name = Lanster Last Name = Cisco

Click Add

Step 191: Click OK to close the confirmation box.

89


The new Lansters group is now listed below the default group. The group code, contact email and other details that were used when the group was created are also shown in the list.

Section 4.3: Setting Resource Limits for a group There are options within UCS Director that allow resources to be limited for individual groups. In this next section, you will modify the Resource limits for the Lansters group.

Step 192: While still on the User Groups tab within the Users and groups page, select the Lansters entry and then click Edit Resource Limits action button.

Step 193: Check Enable Resource Limits box. The Resource Limit window expands allowing configuration of Resource Limits.

Enter Maximum Active VM Count: 20 Enter Maximum Total VM Count: 30

Click Save to save the Group Resource Limits.

90



Step 195: The User Groups list now indicates that resource limits have been set for the Lansters Group.

91


Section 4.4: Adding a User to UCS Director UCS Director also allows management of login users from within the web interface. In this next section you will add a new user to the Lansters group created in the previous section.

Step 196: From the menu section, select Administration > Users and Groups (You may already be there as a result of the previous steps.)

Step 197: Click the Login Users tab

Step 198: Two default users - admin and infraUser are listed. Click the Add button to start the process to add a new user.

92


Step 199: The Add user dialog box appears. From the drop-down select the User Role: to be Service End-User

Step 200: The Add User form automatically updates to allow selection of the User Group. Select User Group: Lansters

Step 201: Continue completing the form with the remaining information:

Login Name: jouser Password: cisco

Confirm Password: cisco User Contact Email: [email protected] First Name: Joe Last Name: User

Click Add

93



Verify that the jouser shows below the infraUser in the list.

94


Section 4.5: Configuring LDAP Integration You can use LDAP integration to synchronize the LDAP server’s groups and users with Cisco UCS Director. LDAP authentication enables synchronized users to authenticate with the LDAP server. You can synchronize LDAP users and groups automatically or manually. In addition, LDAP synchronization is also available as a system task.

Step 203: From the Main Menu, navigate to Administration > Users and Groups (You may already be there because of the previous steps.)

Step 204: Authentication options are configured under another tab located in the Users and Groups page. Click on the Authentication Preferences tab.

Step 205: Select Local first, fallback to LDAP from the drop down menu. With this selection, authentication is attempted first within the Cisco UCS Director’s user database. If the user is unavailable in the local database, the LDAP server is then checked.

95


Step 206: Verify that Local First, fallback to LDAP is listed in the field and then click Save.

Step 207: A message appears stating the authentication preferences were saved and also instructs us to move to another page to configure Directory settings. Click OK

Step 208: Locate and click the LDAP Integration tab

Step 209: There are currently no LDAP Accounts listed on the page. Click Add button

96


Step 210: The LDAP Server Configuration window appears. Use the following information to fill the LDAP Configurations:

Account Name: UCSD Lab AD Server Type: Microsoft Active Directory Server: 10.1.7.5 Port: 389 Domain name: n1kvlab.cisco.com User name: administrator Password: Cisc0123!

Click Next

Step 211: The next step in the configuration is the LDAP Search Base settings. Next to Search Base, click Select.

97


Step 212: The Select window appears. Click the check box at the left to select OU=UCSD_Users@DC=n1kvlab@DC=cisco@DC=com Note: Be sure this box is checked before moving onto the next step.

Click Select

Step 213: The DN you just selected is now listed for the LDAP Search Base. Click Next

98


Step 214: You will not be creating any LDAP User Role Filters so click Submit

Step 215: Click Ok to close the confirmation box.

Step 216: Select the UCSD Lab AD account from the list and click on Test Connection to verify there is connectivity.

Step 217: Click Close to close the box indicating that the test was successful.

99


Step 218: Click on Search BaseDN

Step 219: The LDAP Search Base window appears. Click Submit

Step 220: Click OK on the LDAP search base entries saved message

Step 221: Click the Login Users tab to verify that the LDAP Users are being shown in the list. You may need to click the Refresh button to update the user list. After refreshing the page you can see login information for janeuser and jayuser in the list.

100


Section 4.6: Adding User Groups from an AD Server

Step 222: From the Administration > Users and Groups page, select the User Groups tab

Step 223: Click the Refresh button to refresh the page.

Note: As a common practice, use the ‘Refresh’ button to ensure the page information is current (especially, after adding new accounts, infrastructure etc.), as the Inventory Collection process is asynchronous and usually takes a few minutes to update the inventory data tables, tabular reports and graphical reports etc.

Step 224: Verify that a new group has been imported from LDAP. Note that the source shows as External.

101


At this point, you have completed the following tasks in configuring UCS Director:

• Installation, Patching and Configuration

• Basic Administration, Guided Setup using Wizards

• Product Customization

• Adding Users & Groups

• Configuration LDAP Integration

102


Exercise 5: Pod Configuration, Creating Policies and Virtual Datacenter Configuration In this exercise you will perform FlexPod configuration using a guided setup wizard, then adding a second pod and NetApp Storage physical account; creating Computing, Network, Storage and System Policies; and lastly configuring a Virtual DataCenter (VDC).

Section 5.1: Using guided Setup for FlexPod configuration

Step 225: Begin by using the Guided setup to do some configuration on for FlexPod. Navigate to Administration > Guided Setup

Step 226: From the Setup tab guided setup can be accessed. Click Launch Guided Setup

103


The Guided Setup box appears which allows you to check the boxes of the wizard you want to use to complete the FlexPod configuration.

Step 227: Click the check box for FlexPod Configuration and click Submit

Step 228: On the next screen, ensure FlexPod Configuration is selected and click Submit

104


Step 229: The Custom Wizard section for creating a FlexPod account appears. Read the Overview information and click Next.

Step 230: You will need to create a new pod for the account. Click the ‘Add’ action button to add a new Pod.

105


Step 231: The Add POD dialog box appears. Name the new pod Pod1. You will also need to add a site name. Click the add symbol next to the site list drop down.

Step 232: The Add Site box appears. Complete the fields with the following info:

Site: San Jose Description: SJC Office Contact Name: Joe User

Click Submit

106


Step 233: The Submit result window appears indicating the change was added. Click OK

Step 234: Now the site will be listed in the drop down menu. Click the drop down arrow for the Site list and select San Jose.

Step 235: Complete the rest of the form to add the pod:

Type: Flexpod (the Default option) Description: San Jose Pod Address: 150 Tasman Drive

Click Add

107



Step 237: Ensure that Pod1 is selected in the Pod selection and click Next

Step 238: The Custom Wizard advances to the Cisco UCS Manager Account step. Enter the following information:

Account Name: UCSM-1 Server Address: 10.1.7.227 User ID: administrator Password: Cisc0123! Transport Type: http Port: 80

108


Click Next

Step 239: If the wizard is able to connect to the UCS Manager, it will advance to the next section - to add the NetApp account information. In the NetApp Common options section make sure that the radio button for NetApp 7 Mode is selected.

109


Step 240: Complete the remaining fields with the following information: Account Name: NetApp-1 Server Address: 10.1.7.230 User ID: root Password: Cisc0123! Transport Type: https Port: 443 Select the checkbox for No HA Configuration

Click Next

110


Step 241: You will not be configuring any Nexus Physical Devices so click Skip.

Step 242: The next page asks for configuration details for Nexus Virtual Device. For this lab you will not configure this page either. Click Skip

111


Step 243: You also will not be adding a VMware account to the pod at this time. Click Skip for a third time.

Step 244: Ensure that you have completed all the steps in the Summary screen, except for Nexus Physical Devices, Nexus Virtual Device and VMware - those steps will show yellow exclamation points for their status. You can scroll down to see the configurations for each section before moving on. Click Finish.


112


Step 246: Click Launch Guided Setup again.

Step 247: Check the box of the wizard to complete Device Discovery and click Submit. This will begin the wizard that allows us to discover and assign accounts to pods.

Note: Although you could have run the FlexPod Configuration wizard and the Device Discovery wizard at the same time, we wanted to be sure that Pod1 was created first (as part of the Flexpod configuration) before we discovered devices - so that the device that we discover can be easily added to Pod1.

113


Step 248: On the next screen, ensure Device Discovery is selected and click Submit.

Step 249: Read through the Prerequisites and the Sequence of Steps and click Next

Step 250: In the IP Address(es) box, enter the IP address range 10.1.7.1 – 10.1.7.50

114


Step 251: Click the Add button under Credential Policy. The credential policies are used to authenticate against the range of IP Addresses.

Step 252: The Add Credential Policy window appears. You will use the search field in this window. As you start to type the word VMWare in the search field the account types are filtered.

Step 253: Choose VMware as the account type by selecting the checkbox.

115


Step 254: After selecting the VMWare option, the Add Credential Policy window appears: Fill in the following information:

Policy Name: VMWare Timeout: 15 Server User ID: [email protected]

Server Password: Cisc0123! Server Access Port: 443 Server Access URL: /sdk

Click Submit


116


Step 256: The newly created VMWare policy now appears in the list. Select the checkbox for VMware policy under the Credential Policy list and click Next

Step 257: On the next page, select Pod1 from the drop-down box. Then click Discover

Wait for the discovery to finish. You will see the screen refresh and a validating message and progress bar at the bottom of the window.

117


Step 258: After the discovery completes a list of discovered VMware accounts will appear. In our lab, the vCenter Server at 10.1.7.10 was discovered. Ensure that Pod1 is selected; and then check the checkbox next to the discovered vCenter server. Then click the Add button to add the device to the pod.

Step 259: A message appears that the IP was successfully assigned to Pod1. Click Close to end the device discovery wizard.

Step 260: The Wizard will close. To verify what was configured, click Converged in the top menu.

118


Step 261: Pod1 is listed on the Converged page for the San Jose site. Click Pod1 one time to select it.

Step 262: Ensure all the three accounts were added.

At this point, you have completed a FlexPod configuration through the use of the FlexPod Configuration and Device Discovery Wizards

119


Section 5.2: Adding a second pod

In the last section, you created Pod1 via the guided setup. In this section you will be adding a second pod manually.

Step 263: Navigate to Administration > Physical Accounts

Step 264: Click on the Pods Tab

Step 265: Pod1 – the pod created during the guided setup – is shown in the list. Start to add Pod2 by clicking the Add action button to add a new Pod

120


Step 266: The Add POD window appears. Fill in the fields with the following information:

Name: Pod2 Type: FlexPod Site: San Jose Description: SJC Pod2 Address: 220 Tasman Drive

Click Add

Step 267: Click OK to close the confirmation window.

Step 268: Verify that Pod2 is now shown in the list below Pod1.

121


Step 269: Click on the Converged option from the menu.

The visual representations of both pods are shown.

Step 270: Complete the configuration of Pod2 with the respective accounts for Virtual, Compute, Network and Storage layers. Navigate to Administration > Virtual Accounts

Step 271: On the Virtual Accounts tab click the Add button to add a Virtual Account.

122


Step 272: From the drop down menu select the Cloud Type of VMware.

Step 273: After Selecting VMware from the drop down list, the Add Cloud dialog box immediately opens. Enter the following information:

Cloud Type: VMware Cloud Name: VCenter-2 Server Address: 10.1.7.10 Server User ID: [email protected] Server Password: Cisc0123! Server Access Port: 443 Server Access URL: /sdk Description: Pod2 vCenter Contact Email: [email protected] Pod: Pod2 (from drop down)

Click Add



123


Step 274: A duplicate VMware server warning is displayed at the bottom of the window. Check the Ignore Warnings checkbox and click Add again. This warning is showing up because you are adding the same vCenter account to 2 different PODs.

Step 275: Click OK to close the successful addition notification box.

Step 276: Verify that the newly created Vcenter-2 account is now shown in the list.

Step 277: Select Vcenter-2 and click Test Connectivity

124


Step 278: Click Close to close the Test results notification box.

Note: When an infrastructure account is added, relevant discovery and inventory collection processes get initiated to capture the current state of the new account. This process is referred to as ‘Inventory Collection’. Every account is associated to one or more inventory collection processes or tasks.

Step 279: Navigate to Administration > System.

Step 280: When the page loads, click the System Tasks tab.

125


Step 281: System tasks are listed in the first column. Expand some of the folders to see the tasks under each.

Step 282: To review the result of Inventory collection process from adding the Virtual Account, select Virtual > Compute

126


A summary view of the different Virtual Machine information that was collected is in the screenshot below. You can use the chart slider to increase/decrease the size of the graphs

Step 283: Click on VCenter-2 (Cloud Name) on the left pane to see data relevant to a specific Virtual Account.

Step 284: Click the Polling tab

127


Step 285: Click on Request Inventory Collection. This action will force the inventory collection process. Inventory collection is an asynchronous process and will take a few minutes to complete.

Step 286: Click Submit to submit the request for inventory collection on VCenter-2.


Step 288: Click the refresh option several times until the status changes to complete.

128



Step 290: Click the Physical Accounts tab

Step 291: Click the Add action button to add a new Physical Account

129


Step 292: The Add Account window appears. From the drop down menu of each field select the following:

Pod Type: Pod2 Category: Computing Account Type: UCSM

Click Submit

Step 293: The detailed Add Account window appears. Use the details from the list below to configure a UCS Manager Account:

Authentication Type: Locally Authenticated Server Management: All Servers Account Name: UCSM-2 Server Address: 10.1.7.227 User ID: administrator Password: Cisc0123! Transport Type: http Port: 80

Click Add

130



Step 295: Select the UCSM-2 account and click on Test Connection

131


Step 296: Click Close to close the test confirmation box.

Step 297: Review the Inventory Collection process by going to Administration > System

Step 298: Click the System Tasks tab.

Step 299: Search for UCS Inventory Collector to filter the task list. As you type the system task filter automatically.

132


Step 300: Select the UCS Task for UCS Inventory Collector UCSM-2 (You may have to expand column to see the correct label.) Click the Run Now action button to force the Inventory Collection process to run immediately.

Step 301: Click Submit to confirm that you want to run the task.

Step 302: A message indicating the task is scheduled to run appears, click OK

133


Step 303: Click on the Refresh button to update the Inventory status. Continue to click refresh while the Inventory status changes. Verify that the last row in the Execution Status column will change through these status indicators - OK, In Queue, In Progress, OK

Step 304: Navigate to Physical > Compute to review the Inventory Collection results

134


Step 305: Click the arrow next to the Pod2 account to expand the list.

Step 306: Under Pod2, select the listing for UCSM-2

135


Step 307: Wait a few seconds for the screen to refresh. Review the UCS Chassis and UCS server information collected by UCS Director

Step 308: Expand the dropdown list icon on the right-side corner to see additional list of options available

136


Step 309: Select UCS Servers option to see the full list of UCS Servers available.

Step 310: You may select one of the entries to see the additional actions available for each blade server selected. Notice the ‘Power ON’, ‘Associate’ etc buttons across the top when the server types are selected.

137


Section 5.3: Add NetApp Storage Physical Account Next, you will go through the steps to manually configure a NetApp Physical Account as part of Pod2.


Step 312: Select the Physical Accounts tab

Step 313: Click the Add action button to add a new Physical Account

138


Step 314: The Add Account window appears. Select the following from the drop down menu: Pod: Pod2 Category: Storage Account Type: NetApp ONTAP

Choose Submit

Step 315: The detailed Add Account Window Appears. Use the information below to complete the form:

Account Name: Netapp-2 Server Address: 10.1.7.230 User ID: root Password: Cisc0123! Transport Type: https Port: 443

Click Add

139


Step 316: You will not be able to add this manually because this lab is using a Netapp Simulator, this however would work in production. Click Close.

Note: For the remainder of this section, you’ll review the NetApp Physical Account that was automatically created by the FlexPod wizard on Pod1. You would use the same steps to verify the NetApp account on Pod2 if you had been successful in manually creating it.

Step 317: Navigate to Administration > System

140


Step 318: Click the System Tasks tab to initiate an inventory process.

Step 319: In the search pane, enter the keyword NetApp to filter the data

Step 320: Select NetApp Inventory Collector and click on Run Now action button.

Step 321: Click Submit to confirm the task to run now.

141



Step 323: Use the Refresh button to update the Execution status. Check the Inventory Collection process is complete (keep clicking refresh until the status shows “OK”)

Step 324: Once the task completes, navigate to Physical > Storage

142


Step 325: Click the arrow next to Pod1

Step 326: Select the NetApp-1 account

Step 327: Double-click the NetApp-1 account to drill-down into additional details

143


Step 328: Click the Volumes tab to view the Volumes

Step 329: Review the column information for Volumes

Step 330: Click the LUNS tab to view the LUNs

Step 331: Review the info.

144


Step 332: Select one of the LUNs in the list to see the actions available above the table Note: Please do not perform any actions on the LUNs for the purpose of this lab

Step 333: Navigate to the Converged menu option.

Step 334: View the logical representation of the POD1 and POD2 that you have been working on - to ensure all the accounts are added and represented well.

145


Step 335: Select Pod1 to see the Converged Stack Builder visual representation of each of the layers as shown below.

Section 5.4: Creating Computing 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

In this section you will create a computing policy. Computing policies determine the computing resources used during provisioning that satisfy group or workload requirements.

146


Step 336: Select Policies > Virtual/Hypersivor Policies > Computing

Step 337: Click the Add button under VMware Computing Policy

Step 338: When the Add Computing Policy window appears, complete the form with the following information:

Policy Name: Lab Compute Policy CloudName: Vcenter-2 Host/Node: All

Click the Select button

147


Step 339: In the Select Items window, check the box for Resources@N1KvCluster and click Select.

Step 340: Back at the Add Computing Policy window, finish the form:

ESXi Type: Any ESX/ESKi ESX Version: Any Filter Conditions: Leave Blank Allow Resizing of VM: checked Click Submit

148



Step 342: The Lab Compute Policy now appears in the VMware Computing Policy list.

Section 5.5: Creating Network, Storage and System Policies In this section you will be creating Network, Storage and System Policies. Network Policy - A network policy includes resources such as network settings, DHCP, or static IP, and the option to add multiple vNICs for VMs provisioned using the policy.

Step 343: Navigate to Policies > Virtual/Hypervisor Policies > Network

149


Step 344: From VMWare Network Policy tab, click Add to add a new network policy

Step 345: The Network Policy Information window appears. Enter the following to start configuring the policy:

Policy Name: Lab Network Policy Policy Description: Lab Network Policy

Cloud Name: Vcenter-2

Click Add next to VMnetwork

Step 346: The Add Entry to VM Networks box appears. Use the following to complete the fields:

NIC Alias: NIC 1 Adapter Type: E1000

Next click the Add Button next to Port Groups table

150


Step 347: The Add Entry to Port Groups window appears. Select the Port Group Name by clicking the Select button

Step 348: A Select box appears. Click the check box next to the Host Node with IP 10.1.7.101, with Port Group Name VM Network. Click Select

151


Step 349: The Add Entry Window reappears. Select IP Address Type and Source by using the drop down menu (as you do this the fields will update below the drop down boxes.)

Select IP Address Type: Static Select IP Address Source: Inline IP Pool

Static IP Pool: 10.1.7.70-10.1.7.80 Subnet Mask: 255.255.255.0 Gateway IP Address: 10.1.7.1

Click Submit


152


Step 351: You are returned to the Add Entry window. Notice the Port group now listed for Vcenter-2. This form is complete now. Click Submit


Step 353: You are returned to the Network Policy Information window. Notice that now there is a NIC Alias, NIC 1, listed in the VM Networks list. Click Submit

153



Step 355: The Lab Network Policy is now listed with the Cloud Name, Policy description and a status of OK.

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. The storage policy also provides options to configure additional disk policies for multiple disks and to provide datastore choices for use during a service request creation.

Step 356: To add a VMWare Storage Policy navigate to Policies > Virtual/Hypervisor Policies > Storage.

154


Step 357: Select the VMware Storage Policy tab

Step 358: Click Add to start configuring theVMware Storage Policy

Step 359: The Add Storage Resource Allocation Policy window appears. Use the following details to configure the storage policy:

Policy Name: Lab Storage Policy Policy Description: Lab Storage Policy Cloud Name: Vcenter-2 Data Stores/Datastore Clusters Scope: Include Selected Datastores

155


Step 360: After selecting “Include Selected Datastores” from the drop down, the Select button appears. Click Select

Step 361: The Select dialog box appears. Select VACS-datastore2 and click Select

156


Step 362: Complete the rest of the fields in the Add Storage Resource Allocation Policy window:

Use Shared Data Stores Only: Leave unchecked Use Local Storage: Checked Use NFS: Checked Use SAN: Checked

Step 363: Leave the other options with defaults and click Next for additional disk Policies

157


Step 364: Leave the defaults for Disk Policies and click Submit to add the storage policy to UCS Director.


Step 366: The Storage Policy now appears in the list with an OK status

158


System Policy - A system policy defines the system specific information such as the template to use, time zone, OS specific information, and so on.

Step 367: Select Policies > Virtual/Hypervisor Policies > Service Delivery from the menu

Step 368: From VMWare System Policy tab, click Add to add a system policy

159


Step 369: The System Policy Information window appears. Enter the following details to configure system policy:

Policy Name: Lab System Policy Policy Description: Lab System Policy VM Name Template: (Your First Name) -SR${SR_ID} Time Zone: Pacific DNS Domain: n1kvlab.cisco.com

Step 370: At the bottom of the window use the drop down menu to select, VM Image Type: Windows and Linux

160


Step 371: Scroll down to complete the form.

Product ID: Leave Blank for Now License Owner Name: Cisco Organization: APO License Mode: Per-Seat Number of License User: 1 Auto Logon: checked Administrator password: Cisc0123! Domain/Workgroup: Workgroup Work Group: workgroup

Click Submit to add the system policy

161



Step 373: The newly created System Policy appears in the list.

Section 5.6: Creating Cost Models 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. Cost models offer a definition of costs in a linear model, Costs can be defined at the unit level. The cost of a particular resource for a VM is calculated based on how many units are assigned to that VM. For example, the cost of 1 GB of RAM is defined within the cost model and this unit cost is used to determine the cost of RAM for a particular VM. You can define one-time provisioning costs, active or inactive VM costs, and provisioned, reserved, or used costs for resources such as CPU, memory and so on. These costs are used to calculate the VM costs based on usage.

162


Step 374: Select the Cost Model tab.

Step 375: Click Add to add a Standard Cost Model. Note: There is an ‘Advanced Cost Model’ which will not be discussed as part of this lab

Step 376: The Add Cost Model dialog box appears. Enter the following details to configure the Standard Cost Model

Cost Model Name: Lab Standard Model Cost Model Description: leave blank Cost Model Type: Standard Charge Duration: Hourly One Time Cost: 20 Active VM Cost: 0.5 CPU Charge Unit: GHz Provisioned CPU Cost: 0.1 Reserved CPU Cost: 0.05 Used CPU Cost: 0.1 Provisioned Memory Cost: 0.01 Reserve Memory Cost: 0.1 Used Memory Cost: 0.1 Received Network Data Cost: 0 Transmitted Network Data Cost: 0 Committed Storage: 0.1 Uncommitted Storage Cost: 0

163


Verify the settings and then Click Add to add the cost model.


164


Step 378: The Cost Model now appears in the list.

Section 5.7: Configuring Virtual Data Center (VDC) In this section you will be configuring a Virtual Data Center (VDC). A Virtual Data Center serves as a container that combines virtual resources, operational details, rules, and policies to meet 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 approver for a particular VDC must approve requests from users for VM provisioning. Note: There is a default VDC in Cisco UCS Director and all discovered VMs are part of this default VDC. Discovered VMs are VMs that are created outside of Cisco UCS Director or were already created on vCenter before Cisco UCS Director was installed. Cisco UCS Director automatically discovers such VMs and adds them to the default VDC.

Step 379: Navigate to Policies > Virtual/Hypervisor Policies > Virtual Data Centers

165


Step 380: Within the Virtual Data Centers for All User Groups, make sure the vDC tab is selected and click Add to create a Virtual Data Center

Step 381: The Add vDC box appears using the drop down menu for the Account Type choose VMware.

Step 382: Then click Submit.

166


Step 383: The detailed Add vDC window appears. Enter the following details:

VDC Name: Lab vDC vDC Description: Lab vDC

For the Group, click the Select button

Step 384: Click the check box for the Group Name: Lansters and click Select

167


Step 385: Returning to the Add vDC form, verify that the Cloud Name is vCenter-2.

Step 386: Scroll down to finish up with the Policies settings:

System Policy: Lab System Policy Computing Policy: Lab Compute Policy Network Policy: Lab Network Policy Storage Policy: Lab Storage Policy Cost Mode: Lab Standard Model

Click Add to add Virtual Data Center to UCS Director

168



Step 388: The vDC now shows in the list.

Congratulations! You have completed the lab.

169


APPENDIX A: Troubleshooting Login Prompt Troubleshooting:

1. Check the services status by logging back onto the console of the CUCSD-Post_Patch

VM. Press Enter to return to the login prompt.

2. Use the following credentials to log back into the system. Username: shelladmin Password: Cisc0123!

Press Enter

170


3. Check the services status by typing “2” and pressing <Enter>.

4. All of the service statuses should be running, if they are not the services need to be restarted. Press Enter to continue.

171


5. Type “3” and press <Enter> to stop the services.

6. When asked if you want to stop the services, type “y” and press enter.

172


7. Check to see that all the services have stopped by typing “2” and pressing enter.

8. Verify that the services have stopped and press enter to continue.

173


9. To restart the services type “4” and press enter. Press enter again when prompted to continue.

10. At the menu prompt type “2” and press enter. Continue to check the status until all the services show as running.

174


11. Return to the Internet Explorer browser and refresh the page if necessary. The services have restarted completely when the Cisco UCS Director Login screen appears. (return to section 2.5)

175


Cisco AnyConnect Secure Mobility Client Installation Instructions: Open a browser window from your computer and access the following URL : https://128.107.217.3/ucsd When the page loads, click on the Advanced link

The page will expand to display a link. Click on the Proceed to 128.107.217.3(unsafe) link

https://128.107.217.3/ucsd

176


The SSL VPN Service login page will appear

Use the login credentials provided by the lab proctor and click Login (Note: Username is stuXXX where the “XXX” is your pod number)

The lab welcome screen appears, click Continue

177


The AnyConnect Secure Mobility Client WebLaunch wizard will appear. It should install AnyConnect automatically. After installation is complete return to the beginning of the document to log into the lab.

If for some reason it fails. Use the manual installation process. Click the Windows Desktop link to start the download.

A download will begin at the bottom of the browser window

178


When the download is complete, click the triangle to show the menu and select show in folder.

Locate the file in the downloads folder and double click the file to start the installation

Click Run on the security warning

179


The Anyconnect Secure Mobility Client Setup Wizard will walk you through the steps. After installation is complete return to the beginning of the document to log into the lab.

Troubleshooting Cisco AnyConnect Connection issues: From the Cisco AnyConnect Secure Mobility Client window click the blue gear in the lower left corner to access the VPN settings.

180


Navigate to the Preferences tab if not already there when the window opens.

Depending on the client version there may be more options listed on the Preferences Tab. Be sure to Uncheck the “Block Connections to untrusted servers” box.

181


Click the red X to close the window.

Return to Section 1.1 to reattempt connecting to the lab.

cisco ucs director 5.2 lab-v.1.5

Documents

lab cisco ucs director

ucs director basic information

lab environment

lab objectives

lab guide version

lab contents introduction

guided setup

vmware setup