September 2016 SL10295 Version 1.0.0
1 Introduction to FlexPod Automation This lab demonstrates how to use FlexPod Automation to automate the configuration of a FlexPod (UCS Mini, Nexus Switches, Clustered Data ONTAP and ESXi). The lab showcases the automation of a real world use case based on the Deployment Guide (FlexPod Datacenter with Cisco UCS Mini and VMware vsphere 6.0 with IP-Based Storage). The lab is designed to provide you with the knowledge to deploy and configure a FlexPod configuration. The following list identifies some key benefits of deploying FlexPod Automation: Streamlines the deployment process, reducing it from weeks to minutes. Replaces varied command-line interfaces with a single GUI. Automatically applies best practices when configuring components. 1 Overview You will gain hands-on experience with interactive provisioning and configuration of FlexPod resources. FlexPod with Infrastructure Automation is a predesigned, best practice data center architecture that is built on the Cisco Unified Computing System (UCS), the Cisco Nexus 9000 family of switches, and NetApp FAS2552 and operated from a GUI to provide a simplified user experience. 1 Prerequisites This is an intermediate lab, and requires a basic knowledge of clustered ONTAP, as well as familiarity with the different components in the FlexPod stack. 2
2 Lab Environment Figure 2-1: Lab Diagram Table 1: Table of Systems Host Name Operating System IP Address Username / Password UCSD simulator 192.168.10.110 root / cisco123 admin / Netapp1! 3 UCSPE simulator 192.168.10.105 ucspe / ucspe UCSD-BMA simulator 192.168.10.120 root / pxeboot NIS VM Appliance 192.168.10.99 root / Netapp1! vnx-os-1 simulator 192.168.10.106 admin / admin vnx-os-2 simulator 192.168.10.107 admin / admin
4 Host Name Operating System IP Address Username / Password DC1 Windows Server 2012 R2 192.168.0.253 DEMO\administrator / Netapp1! JUMPHOST Windows Server 2012 R2 192.168.0.5 DEMO\administrator / Netapp1! VC1 Windows Server 2012 R2 192.168.0.31 DEMO\administrator / Netapp1! ESX1 vsphere ESX 6.0 192.168.10.51 root / Netapp1! ESX2 vsphere ESX 6.0 192.168.10.52 root / Netapp1! ESX3 vsphere ESX 6.0 192.168.10.53 root / Netapp1! ESX4 vsphere ESX 6.0 192.168.10.54 root / Netapp1!
3 Getting Started In a real customer environment, you would connect your web client computer and all of the FlexPod network cables (12) to your network switch. The lab handles this network connection and client computer and starts once you have successfully powered up everything. You can access Cisco UCS Director by browsing to http://192.168.10.110 from your client computer. 3 Log into Cisco UCS Director 1. Double-click the Chrome shortcut on your desktop. Figure 3-1: 2. Using Google Chrome, navigate to http://192.168.10.110. 3. Enter the user name admin and password Netapp1! for Cisco s UCS Director, click Login. Note: If you are presented with a screen with clouds on it, and a message that the system is starting up, please wait 30 seconds. If that does not resolve the issue, you need to restart UCS Director (it is not crash consistent, and will struggle to start from a LOD snapshot at times). To restart UCS Director, you need to use the PuTTy session UCSD, and login with username root, and password cisco123. Issue the shutdown -r 0 command, and wait 10 minutes. At that time, go back to http://192.168.10.110 and you should be presented with a login screen. 3 Figure 3-2: 3 Launch the Automation Wizard 1. In the Guided setup window, select the FlexPod with Infrastructure Automation checkbox. 2. Click Submit. 5
1 2 Figure 3-3: 3. Keep the default settings in the next Guided setup window, and click Submit. This will open the FlexPod with Infrastructure Automation wizard. 3 Figure 3-4: 6
4 Lab Activities This lab contains the following lab activities: Introduction to FlexPod Automation on page 2 Getting Started on page 5 Launch Automation Wizard on page 7 My New FlexPod Preview Configuration Hypervisor Software Review Installation (Optional) on page 23 4.1 Launch Automation Wizard 4.1 Overview 1. Scroll down and review the Overview. 2. Press Next. 1 2 Figure 4-1: 4.1 Apply USCD License The first step in the procedure is to provide your license for Cisco UCS Director (UCSD). 1. In the Apply UCSD License page of the wizard, click Upload. 7
1 Figure 4-2: 2. Click the Click and select a file from your computer option. This will prompt you to locate the license file from your local client computer. 8
2 Figure 4-3: 3. From the Desktop, select CCUIC201510271237342190.lic file. 4. Click Open. 9
3 4 Figure 4-4: 5. When the file is uploaded, click Submit to add the license. 10
5 Figure 4-5: 6. Click Next. 11
6 Figure 4-6: 4.1 My New FlexPod 1. Due to networking limitations within the lab infrastructure, the inputs allowed for this lab are more restrictive than they would be in an end user s environment. Because of these limitations, you must use the following inputs when completing the wizard. FlexPod Name and Password FlexPod Name Insight2016 Password Netapp1! Management Network Starting IP 192.168.0.200 Subnet Mask 255.255.255.0 Gateway 192.168.0.1 Server Provisioning 12 Number of Hosts 4
1 Figure 4-7: Management Network Services NTP Server 192.168.0.253 DNS Servers 192.168.0.253 DNS Domain Name flexpod.com DNS Search Domains flexpod.com, netapp.com, cisco.com Network Proxy Services Leave blank 2. After you enter the inputs, click Next. 13
2 Figure 4-8: 4.1 Preview Configuration 1. Review the auto generated values by scrolling down, and click Next. Note: Because of networking limitations within the lab infrastructure, do not change any of the values presented in the Preview Configuration window. 14
1 Figure 4-9: 4.1 Hypervisor Software FlexPod with Infrastructure Automation will automatically install and configure hypervisor software on your Cisco UCS servers. Due to licensing and distribution limitations, end-users must provide their own ESXi ISO image. The image should be readily available to your client computer. 1. On the Hypervisor Software page of the wizard, click Upload. 15
1 Figure 4-10: 2. Click the option Click and select a file from your computer. This will prompt you to locate the ISO image from your local client computer. 16
2 Figure 4-11: 3. Select your ESXi v6.0 installation ISO image (VMware-VMvisor-Installer-6.0.0-2494585.x86_64.iso) from the Desktop. 4. To select the file click Open. 17
3 4 Figure 4-12: 5. When the file is uploaded, click Submit. 18
5 Figure 4-13: 6. Click Next. 19
6 Figure 4-14: 7. Review the configuration in teh Final Review, and click Submit. 20
7 Figure 4-15: 8. Clicking the Submit button launches a series of automation scripts. As each step in the process completes, you will see it change from blue to green. 21
Figure 4-16: 9. When all steps are complete, your new FlexPod will be successfully provisioned! Note: This process may take up to 30 minutes to complete. While you wait you may want to review the References section of this document. 22
9 Figure 4-17: 4.2 Review Installation (Optional) FlexPod with Infrastructure Automation creates a number of clustered ONTAP objects that you can view in System Manager. To review the configuration please log into System Manager. 4.2 Login to System Manager 1. From Chrome, enter the Cluster management address: https://192.168.0.208 2. Click ADVANCED. 3. Click Proceed to 192.168.0.208... 23
1 2 Figure 4-18: 4. Enter credentials Username admin Password Netapp1! 5. Click Sign In. 24
4 5 Figure 4-19: 6. Expand the Cluster tab then select Storage > Aggregates. From this pane, you can determine that the automation created four aggregates (2 Data, and 2 Root). 6 Figure 4-20: 7. Under the Cluster tab, expand Configuration, then select Network. 8. Select the Network Interfaces tab. In this pane you can review the network interfaces created by the automation using the range provided in the UCSD Wizard. The NFS data LIFs were used to mount two volumes on each of the ESXi hosts. 25
8 7 Figure 4-21: 9. Expand the Storage Virtual Machines tab, then the NFS SVM (Insight2016-nfs). 10. Select Storage > Volumes. FlexPod with Infrastructure Automation created two volumes to be used as datastores in vcenter. 9 10 Figure 4-22: 4.2 Final Step The final configuration step is to associate the ESXi hosts to a vcenter. Each host contains two datastores that were created by. 26
1. Log into vcenter from Chrome, enter https://192.168.10.31/vsphere-client. 2. Select ADVANCED. 3. Select Proceed to vc1... 3 Figure 4-23: 4. Enter DEMO\Administrator as the user name, and Netapp1! as the password. 5. Click Login. 4 5 Figure 4-24: 27
4.2 Create a new Datacenter 1. Select the Hosts and Clusters icon. 1 Figure 4-25: 2. Right click VC1, and select New Datacenter. 2 Figure 4-26: 3. Enter a name for the new datacenter. 4. Click OK. 28
3 4 Figure 4-27: 4.2 Add ESXi Hosts to vcenter 1. Right click the newly created Datacenter, and select Add Host. 1 Figure 4-28: 2. Enter 192.168.0.214 for the IP address, then select Next. 29
2 Figure 4-29: 3. Enter root for the user name, and Netapp1! for the password, click Next. 3 Figure 4-30: 4. Click Yes. 30
4 Figure 4-31: 5. Select Next at the Host summary screen. 5 Figure 4-32: 6. Select any license from the panel, then click Next. 31
6 Figure 4-33: 7. Select Next at the Lockdown mode screen. 7 Figure 4-34: 8. Select Next at the VM location screen. 32
8 Figure 4-35: 9. Review the details, and select Finish. 9 Figure 4-36: 10. Repeat the process for the other ESXi hosts: 33
192.168.0.215 192.168.0.216 192.168.0.217 11. Review the ESXi details by selecting one of the newly added hosts, then clicking the Related Objects tab. 12. Select the Datastore tab. 13. From this screen you can verify that the automation successfully created two datastores using <PODNAME>_fas_01_vmStorage and <PODNAME>_fas_02_vmStorage. 11 12 13 Figure 4-37: Your setup is now complete, and ready for VMs to be created on your FlexPod datastores. 34
5 Lab Limitations This lab uses a completely virtualized environment (as listed in the next section). Regardless of the limits imposed by the virtualized environment, this lab provides a good approximation of the end-user experience with FlexPod with Infrastructure Automation (FPIA). One major benefit of virtualization is that the automation runs in about half of the time required by real hardware. 5 Software 35 Clustered Data ONTAP 8.3.2 NetApp Integration Software (NIS) 1.02 Cisco UCS platform emulator (UCSPE) 3.1 Cisco UCS Director 5.4.0.0 appliance Cisco Bare Metal Agent X.X vcenter and ESXi 6.0
6 References The following sources were used as reference for this lab guide: 36 Demo Videohttps://www.youtube.com/watch?v=50l0QxI-tG0 Installation Guidehttp://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/UCS_CVDs/ flexpod_automation_ucsmini.html Cisco CSPhttp://www.cisco.com/c/en/us/td/docs/switches/datacenter/csp_2100/quick_start/ b_cisco_csp_2100_quick_start_1_0.htmlhttp://www.cisco.com/c/en/us/support/switches/cloudservices-platform-2100/tsd-products-support-install-and-upgrade.html Cisco UCS Director:http://www.cisco.com/c/en/us/support/servers-unified-computing/ucs-director/ products-installation-and-configuration-guides-list.html FlexPod Automation Based CVD:http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/ UCS_CVDs/flexpod_ucsmini_esxi55_ip.html
7 Version History 37 Version Date Document Version History 1.4.0 May 2015 Initial Release
Refer to the Interoperability Matrix Tool (IMT) on the NetApp Support site to validate that the exact product and feature versions described in this document are supported for your specific environment. The NetApp IMT defines the product components and versions that can be used to construct configurations that are supported by NetApp. Specific results depend on each customer's installation in accordance with published specifications. NetApp provides no representations or warranties regarding the accuracy, reliability, or serviceability of any information or recommendations provided in this publication, or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS, and the use of this information or the implementation of any recommendations or techniques herein is a customer s responsibility and depends on the customer s ability to evaluate and integrate them into the customer s operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document. Go further, faster 2016NetApp, Inc. All rights reserved. No portions of this document may be reproduced without prior written consent of NetApp, Inc. Specifications are subject to change without notice. NetApp, the NetApp logo, Data ONTAP, ONTAP, OnCommand, SANtricity, FlexPod, SnapCenter, and SolidFire are trademarks or registered trademarks of NetApp, Inc. in the United States and/or other countries. All other brands or products are trademarks or registered trademarks of their respective holders and should be treated as such.