Cisco UCS Director Vblock Management Guide, Release 5.0

Transcription

1 First Published: July 31, 2014 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA USA Tel: NETS (6387) Fax: Text Part Number: OL

2 THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS. THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY. The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB's public domain version of the UNIX operating system. All rights reserved. Copyright 1981, Regents of the University of California. NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED AS IS" WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE. IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental. Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R) 2014 Cisco Systems, Inc. All rights reserved.

3 CONTENTS CHAPTER 1 New and Changed Information for this Release 1 New and Changed Information for this Release 1 CHAPTER 2 Overview 3 About Vblock 3 Vblock Support 4 EMC VNX Block, File, and Unified Account Support 5 PowerPath Virtual Environment Support 5 About EMC Isilon 6 Cisco UCS Director Support for EMC Isilon 6 About EMC VPLEX 6 Pod Support for EMC VPLEX 6 About EMC RecoverPoint 7 System Requirements 8 Vblock Implementation Overview 9 CHAPTER 3 Initial Vblock Configuration 11 Adding a Pod 11 Cisco UCS Manager Accounts 12 Adding a Cisco UCS Manager Account 13 Testing the Connection to a Physical Account 15 Verifying the Discovery of a Cisco UCS Manager Account 15 Viewing the Topology and Connectivity of Devices in a Cisco UCS Domain 16 Exporting the Configuration of a Cisco UCS Manager Account 17 Importing the Configuration of a Cisco UCS Manager Account 17 Adding a Vblock Account 18 Verifying Vblock Account Discovery 19 Configuring VNX 20 OL iii

4 Contents Adding a VNX Block Account 21 Adding a VNX File Account 23 Adding a VNX Unified Account 24 Configuring VMAX 27 Installing the EMC Solutions Enabler 27 Adding a Solutions Enabler Account 28 Initial VPLEX Configuration 29 Creating a VPLEX Account 30 Assigning a Pod to a Cluster 31 Initial EMC Isilon Configuration 31 Creating an EMC Isilon Account 32 Initial EMC RecoverPoint Configuration 33 Creating an EMC RecoverPoint Account 33 Network Configuration 35 Adding a Network Device to a Pod 35 Verifying Network Device Details in a Pod Environment 36 CHAPTER 4 Network Configuration for Cisco UCS Director Baremetal Agent 37 About the Network Configuration Options 37 Single Network for Management and PXE 37 Prerequisites and Assumptions for a Single Network Configuration 38 Separate Networks for Management and PXE 38 Prerequisites and Assumptions for a Separate Network Configuration 39 Configuring the Baremetal Agent Appliance through the Cisco UCS Director GUI 40 Configuring the DHCP Server for a Baremetal Agent Appliance in Cisco UCS Director GUI 42 CHAPTER 5 Vblock Operations 45 Configuration Guidelines for Vblock Operations 45 Creating an Organization 48 Configuring the Chassis/FEX Discovery Policy 48 Creating a UUID Pool 49 Creating a MAC Pool 50 Creating a WWNN Pool 50 Creating a WWPN Pool 51 iv OL

5 Contents Creating a Network Control Policy 51 Creating a vnic Template 53 Creating a VSAN 57 Creating a vhba Template 58 Creating a LAN Boot Policy 60 Creating a SAN Boot Policy 61 Creating a vnic 64 Creating a vhba 64 Creating a Network Policy 65 Creating a Storage Policy 67 CHAPTER 6 Orchestration Workflow Operations 69 Cisco UCS Manager Orchestration Tasks 69 Accessing Task Documentation 70 Navigating to a Predefined Orchestration Workflow 70 Provisioning Vblock Orchestration Workflows 71 Provisioning a Stateless Blade Server Orchestration Workflow Overview 71 Modifying the Workflow Priority 73 Creating the UCS Service Profile Task 74 Choosing the Cisco UCS Server 75 Associating the Cisco UCS Service Profile 76 Powering Off the Cisco UCS Server 77 Setting Up PXE Boot 78 Creating a VNX LUN 80 Creating a VNX Storage Group 81 Adding a VNX Host Initiator Entry 82 Configuring Generic Storage Area Network Zoning 83 Adding Hosts to a VNX Storage Group 85 Adding a LUN to a VNX Storage Group 86 Modifying the Cisco UCS Service Profile Boot Policy 87 Modifying the Cisco UCS Boot Policy LUN ID 88 Resetting the UCS Server 89 Monitoring PXE Boot 90 Adding a VLAN to a Service Profile 91 Disassociating the Cisco UCS Service Profile 92 OL v

6 Contents Configuring the Waiting for Specific Duration Task 93 Provisioning a File System Mounting Orchestration Workflow 94 File System Mounting Orchestration Workflow Overview 94 Creating a VNX File System 95 Adding a VNX NFS Export Task 96 Mounting the NFS Datastore 97 Validating and Executing an Orchestration Workflow 98 CHAPTER 7 Troubleshooting 99 Troubleshooting Cisco UCS Director Connectivity 99 Troubleshooting Cisco UCS Director Baremetal Agent Connectivity 100 vi OL

7 Preface This preface contains the following sections: Audience, page vii Conventions, page vii Related Documentation, page ix Documentation Feedback, page ix Obtaining Documentation and Submitting a Service Request, page ix Audience This guide is intended primarily for data center administrators who use Cisco UCS Director and who have responsibilities and expertise in one or more of the following: Server administration Storage administration Network administration Network security Virtualization and virtual machines Conventions Text Type Indication GUI elements GUI elements such as tab titles, area names, and field labels appear in this font. Main titles such as window, dialog box, and wizard titles appear in this font. Document titles Document titles appear in this font. TUI elements In a Text-based User Interface, text the system displays appears in this font. OL vii

8 Conventions Preface Text Type System output CLI commands [ ] {x y z} [x y z] string < > [ ]!, # Indication Terminal sessions and information that the system displays appear in this font. CLI command keywords appear in this font. Variables in a CLI command appear in this font. Elements in square brackets are optional. Required alternative keywords are grouped in braces and separated by vertical bars. Optional alternative keywords are grouped in brackets and separated by vertical bars. A nonquoted set of characters. Do not use quotation marks around the string or the string will include the quotation marks. Nonprinting characters such as passwords are in angle brackets. Default responses to system prompts are in square brackets. An exclamation point (!) or a pound sign (#) at the beginning of a line of code indicates a comment line. Note Means reader take note. Notes contain helpful suggestions or references to material not covered in the document. Tip Means the following information will help you solve a problem. The tips information might not be troubleshooting or even an action, but could be useful information, similar to a Timesaver. Caution Means reader be careful. In this situation, you might perform an action that could result in equipment damage or loss of data. Timesaver Means the described action saves time. You can save time by performing the action described in the paragraph. viii OL

9 Preface Related Documentation Warning IMPORTANT SAFETY INSTRUCTIONS This warning symbol means danger. You are in a situation that could cause bodily injury. Before you work on any equipment, be aware of the hazards involved with electrical circuitry and be familiar with standard practices for preventing accidents. Use the statement number provided at the end of each warning to locate its translation in the translated safety warnings that accompanied this device. SAVE THESE INSTRUCTIONS Related Documentation Cisco UCS Director Documentation Roadmap For a complete list of Cisco UCS Director documentation, see the Cisco UCS Director Documentation Roadmap available at the following URL: ucs-director/doc-roadmap/b_ucsdirectordocroadmap.html. Cisco UCS Documentation Roadmaps For a complete list of all B-Series documentation, see the Cisco UCS B-Series Servers Documentation Roadmap available at the following URL: For a complete list of all C-Series documentation, see the Cisco UCS C-Series Servers Documentation Roadmap available at the following URL: Note The Cisco UCS B-Series Servers Documentation Roadmap includes links to documentation for Cisco UCS Manager and Cisco UCS Central. The Cisco UCS C-Series Servers Documentation Roadmap includes links to documentation for Cisco Integrated Management Controller. Documentation Feedback To provide technical feedback on this document, or to report an error or omission, please send your comments to ucs-director-docfeedback@cisco.com. We appreciate your feedback. Obtaining Documentation and Submitting a Service Request For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation. Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0. OL ix

10 Obtaining Documentation and Submitting a Service Request Preface x OL

11 CHAPTER 1 New and Changed Information for this Release This chapter contains the following section: New and Changed Information for this Release, page 1 New and Changed Information for this Release The following table provides an overview of the significant changes to this guide for this current release. The table does not provide an exhaustive list of all changes made to this guide or of all new features in this release. Table 1: New Features and Changed Behavior in Vblock, Release 5.0 Feature Where Documented EMC Symmetrix VMAX 10K and Provides EMC Symmetrix VMAX 10K See the Configuring VMAX 20K and 20K storage support. for Vblock section in this guide. See the Vblock Support for EMC VNX Block, File, and Unified Accounts section in this guide. EMC VNX Block, File, and Unified Accounts Supports EMC VNX Block, File, and Unified accounts for the Vblock integrated hardware and software environment. EMC Isilon The EMC Isilon storage system allows See the Vblock Support for you to manage, monitor, and configure EMC VNX Block, File, and reporting. Unified Accounts section in this guide. EMC VPLEX Provides a virtual storage system and access to data in the private cloud. See the About EMC Isilon section in this guide. OL

12 New and Changed Information for this Release New and Changed Information for this Release Feature EMC RecoverPoint Provides continuous data protection for operational and disaster recovery by enabling any-point-in-time recovery for diversified storage environments both within and across pods. Where Documented See the About EMC RecoverPoint section in this guide. 2 OL

13 CHAPTER 2 Overview This chapter contains the following sections: About Vblock, page 3 EMC VNX Block, File, and Unified Account Support, page 5 PowerPath Virtual Environment Support, page 5 About EMC Isilon, page 6 About EMC VPLEX, page 6 About EMC RecoverPoint, page 7 System Requirements, page 8 Vblock Implementation Overview, page 9 About Vblock Vblock is an integrated hardware and software environment that you can use for virtualized and nonvirtualized converged computing, networking, and storage solutions. You can use Vblock for the following: Data centers that need high availability and scalable Vblock storage solutions to reduce operating costs and converge the infrastructure so that it supports hybrid cloud computing. Interface to private cloud services that provides computing resources for end users and virtualized applications. Note The hardware deployed for the Vbock environment is highly modular and varies depending on the specific Vblock rack-mount scheme needed for each customer deployment. For more information, see Cisco Validated Designs on the web. The Vblock environment has the following components: Cisco UCS Director and Cisco UCS Director Baremetal Agent that are installed and configured on either a VMware vcenter host or Hyper-V host to standardize and simplify the configuration of networking, OL

14 Vblock Support Overview storage, and security settings for multiple hosts and to monitor the host compliance. See the Cisco UCS Director Installation Guide and Cisco UCS Director Baremetal Agent Setup Guide for more information. The Vblock virtualization software, computing, and the following Vblock components that are located in one rack to provide scalable storage: Vblock System 200 Series with EMC VNX storage. Vblock System 300 Series with EMC VNX storage. Vblock System 720 Series with EMC Symmetrix VMAX 10K and 20K storage. Cisco Nexus components that provide routing and switching functionality. Cisco UCS Manager that provides unified, embedded management of all software and hardware components in Cisco UCS Director including virtual machines (VMs). The following figure shows the Vblock hardware and software components. Figure 1: Vblock System Series Hardware and Software Component with EMC VNX Storage Vblock Support Cisco UCS Director helps support the unified storage systems in the following ways: 4 OL

15 Overview EMC VNX Block, File, and Unified Account Support Auto-discovery Monitoring Visibly manage all the VNX components RAID groups, storage pools, logical unit numbers (LUNs), storage groups, initiators, file systems, volumes, Network File System (NFS) and Common Internet File System (CIFS). Note Make sure that you create a pod before you add a Vblock account. For more information, see Adding a Pod. EMC VNX Block, File, and Unified Account Support EMC VNX Block, File, and Unified accounts for the VNX versions 5100, 5200, 5300, 5400, 5500, 5600, 5700, and 7500 is now supported. In Cisco UCS Director, you can add three different types of VNX accounts: VNX File account X-Blade enclosure, two to eight blades, configurable failover options, and flexible I/O connectivity. There is one data mover per license. VNX Block account Storage or data processor enclosure, dual active storage processors, automatic failover, and flexible I/O connectivity. There are two service providers per license. VNX Unified account Single platform for VNX File and VNX Block. There are two service providers per license. Note The scope of this guide discusses the configuration of EMC VNX Block, File, and Unified accounts. See the Cisco UCS Director EMC VNX Management Guide for more information about these VNX accounts and how they are managed. PowerPath Virtual Environment Support PowerPath Virtual Environment (VE) is an EMC feature that is enabled between the EMC storage component and VMware host. EMC PowerPath VE automates and optimizes data path pools in virtual environments by automating failover and recovery operations, optimizing load balancing, and standardizing path management. The PowerPath VE software is installed on the VMware host. Once the PowerPath VE feature is enabled, a host can discover the EMC storage component. From within Cisco UCS Director, the storage can be discovered and associated as a datastore. Note Configuring PowerPath VE on the VMware host and EMC storage component is outside the scope of this document. OL

16 About EMC Isilon Overview About EMC Isilon The EMC Isilon storage system consists of three or more nodes that make a cluster. Each node is a self-contained, rack-mountable device that contains industry standard hardware, such as disk drives, CPU, memory, and network interfaces. Each EMS Isilon system is integrated with the OneFS operating system (OS) that is based on FreeBSD. OneFS unifies a cluster of nodes into a single shared resource. OneFS also has file-striping functionality across each node in a cluster, a fully distributed lock manager, caching, fully distributed metadata, and a remote block manager to maintain global coherency and synchronization across the Isilon cluster. The Isilon cluster is a single storage pool with a global namespace. This cluster enables you to support multiple volumes and file systems. Cisco UCS Director Support for EMC Isilon Cisco UCS Director manages, monitors, and does reporting for the EMC Isilon system. Data is collected through the Isilon cluster platform and namespace REST API, which is connected to Cisco UCS Director through HTTP or HTTPS. This data is parsed and bound to the output as Plain Old Java Objects (POJOs), and these objects are distributed throughout the pod. About EMC VPLEX VPLEX is an EMC technology that provides a virtual storage system and access to data in the private cloud. A VPLEX can be implemented on UCS Director through a POD deployment such as Vblock, or as a standalone device. VPLEX has the following capabilities: Uses a single interface for multi-vendor high-availability storage and compute infrastructure to dynamically move applications and data across different compute and storage locations in real time, with no outage required. VPLEX combines scaled clustering with distributed cache coherence intelligence within the same data center, across a campus, or within a specific geographical region. Cache coherency manages the cache so that data is not lost, corrupted, or overwritten. Dynamically and flexibly makes data available for organizations. For example, a business can be sustained through a failure that would have traditionally required outages or manual restore procedures. Presents and maintains the same data consistently within and between sites, and enables distributed data collaboration. Establishes itself between ESX hosts that act as servers for virtual machines (VMs) and storage in a storage area network (SAN) where data can be extended within, between, and across pods. Pod Support for EMC VPLEX The VPLEX virtual storage system technology for accessing data in the private cloud is associated with and supported by this pod. Cisco UCS Director collects data through the VPLEX Element Manager API and connects to the VPLEX server through HTTPS. Once a VPLEX account is established and a pod is associated with a VPLEX cluster, VPLEX provides the following management and monitoring capabilities: 6 OL

17 Overview About EMC RecoverPoint Cluster inventory of ESX hosts and reports for two or more VPLEX directors that form a single fault-tolerant cluster, deployed as one to four engines. VPLEX engine inventory and reports for an engine that contains two directors, management modules, and redundant power. Director inventory and reports for the CPU module(s) that run GeoSynchrony, the core VPLEX software. Two directors are in each engine. Each has dedicated resources and can function independently. Port inventory and reports for Fast Ethernet ports and initiator ports. VPLEX (local or global) data cache report for the temporary storage for recent writes and recently accessed data. Storage volume inventory and reports for a logical unit number (LUN) exported from an array. Extent management (create, delete, and report) for a slice (range of blocks) of a storage volume. Device management (create, delete, attach/detach mirror, and report) for a RAID 1 device whose mirrors are in geographically separate locations. Virtual volume management (create, modify, delete, and report) for a virtual volume that can be distributed over two or more storage volumes that are presented to ESX hosts. Storage views management (create, modify, delete, and report) for a combination of registered initiators (hosts), front-end ports, and virtual volumes that are used to control host access to storage. Recovery point for determining the amount of data that can be lost before a failure event. For more information about VPLEX use cases, see the EMC VPLEX Metro Functional Overview section of the Cisco Virtualized Workload Mobility Design Considerations chapter. This chapter is in the Data Center Interconnect Design Guide for Virtualized Workload Mobility with Cisco, EMC, and VMware. About EMC RecoverPoint EMC RecoverPoint provides continuous data protection for operational and disaster recovery by enabling any-point-in-time recovery for diversified storage environments both within and across pods. RecoverPoint is an IP-based continuous backup solution that secures data by making data loss reversible by providing asynchronousreplication across heterogeneous arrays for block-based storage protocols. If data becomes compromised or lost, it is possible to look at data back in time and recover it in a consistent state by extending the VMware Site Recovery Manager (SRM) functionality with any point-in-time recovery capabilities. In Cisco UCS Director, the following EMC RecoverPoint reports can be accessed for Vblock clusters: Consistency groups that ensure that there is application-dependent write consistency of application data on VPLEX distributed virtual volumes within the VPLEX system in the event of a disaster. Consistency group copies of the initial consistency groups. Replication sets that consist of a production source volume and its local or local and remote replica volumes. One or more replication sets makes up a consistency group. Note See Viewing EMC RecoverPoint Reports section for more information on accessing these reports. OL

18 System Requirements Overview System Requirements Component Vblock Hardware Connectivity Networking Computing Storage Management and Software Cisco UCS Director Cisco UCS Director Baremetal Agent Cisco UCS Director resource reservation Cisco UCS Director Baremetal Agent resource reservation VMware (vcenter Server/ESXI/ESXi/vSphere, or Microsoft Hyper-V Manager) server Requirement For more information, see the VCE Vblock Series 300 Technical Specifications, and VCE Vblock Series 700 Technical Specifications. Two Cisco Nexus 5000/5500 Series switches Two Cisco UCS 6100 or 6200 Series Fabric Interconnects Cisco Nexus 1000V switch One or multiple Cisco UCS chassis with modules that have two Fabric Extenders per chassis EMC VNX or VMAX 10K or 20K storage system Cisco UCS Manager, VCE Vision Intelligent Operations software (Vblock System 300 and 700). See the Compatibility Matrix for all supported versions. See the Compatibility Matrix for all supported versions. 2 GB memory and minimum 3000-GHz CPU 2 GB memory and minimum 2000-GHz CPU See the Compatibility Matrix for all supported versions. 8 OL

19 Overview Vblock Implementation Overview Vblock Implementation Overview There are a variety of ways in which Vblock can be implemented. This section describes the basic tasks involved in a typical Vblock implementation. Step 4 Step 5 Step 6 Step 7 Step 8 Step Research and plan the configuration design that works best for your Vblock network. For more information on Vblock solutions, services, and support, see the Cisco Vblock Systems page on the web. See also the VCE Management and Orchestration Workflow Automation for Vblock Infrastructure Platforms whitepaper. Use the VCE Vblock Series 700 Technical Specifications and VCE Vblock Series 300 Technical Specifications to determine what hardware connectivity requirements that you need for your Vblock design. Use the EMC VNX Series Technical Specifications or EMC Symmetrix VMAX 10K and 20K specifications to determine what network connectivity requirements that you need for your Vblock design for VNX or VMAX (whichever one that you choose). Obtain licensing information for Vblock or the individual devices or software in your implementation. For more information, see the Cisco UCS Director Install and Upgrade Guides. Install Cisco UCS Director and the Cisco UCS Director Baremetal Agent on your VMware (vcenter Server/ESXI/ESXi, vsphere, or Microsoft Hyper-V Manager) server. See the Cisco UCS Director Install and Upgrade Guides web page, for more information. Add the Vblock account using the task in the Initial Vblock Configuration chapter. Connect devices to Cisco UCS Director to the network using the following tasks in the Initial Vblock Configuration chapter: a) Connect Cisco UCS Manager by adding an account. b) Connect EMC VNX unified storage system(s) or EMC Symmetrix VMAX 10K and 20K storage system(s). c) Connect Cisco Nexus series switches. Note For more information on configuring UCS Manager, see Cisco UCS Director Management Guide for Cisco UCS Manager on the web. Use the Network Configuration for Cisco UCS Director Baremetal Agent chapter to connect Cisco UCS Director Baremetal Agent to Cisco UCS Director, and configure the DHCP server parameters for single or separate networks for management and the Preboot execution Environment (PXE). Verify that Cisco UCS Director Baremetal Agent connects to Cisco UCS Director and that baremetal provisioning is on the same network as Cisco UCS Director Baremetal Agent. Use the Vblock Operations chapter to create a top-level root organization, policies, pools, vnic templates and so on. Use the Orchestration Workflow Operations chapter to navigate to a predifined orchestration workflow, learn how a predefined orchestration workflow can be configured, and how to validate a workflow once it has been configured. Go to the Cisco Developed Integrations page for Cisco UCS Director workflows, which are added on a regular basis. OL

20 Vblock Implementation Overview Overview 10 OL

21 CHAPTER 3 Initial Vblock Configuration This chapter contains the following sections: Note The procedures in this chapter assume you are logged into Cisco UCS Director. Adding a Pod, page 11 Cisco UCS Manager Accounts, page 12 Adding a Vblock Account, page 18 Configuring VNX, page 20 Configuring VMAX, page 27 Initial VPLEX Configuration, page 29 Initial EMC Isilon Configuration, page 31 Initial EMC RecoverPoint Configuration, page 33 Network Configuration, page 35 Adding a Pod Step 4 On the menu bar, choose Administration > Physical Accounts. Click the Pods tab. Click Add. In the Add Pod dialog box, complete the following fields: field A descriptive name for the pod. OL

22 Cisco UCS Manager Accounts Initial Vblock Configuration Site drop-down list Type drop-down list Choose the site where you want to add the pod. If your environment does not include sites, you can omit this step. Choose the type of pod that you want to add. This can be one of the following supported types: Generic VSPEX Vblock If you choose any type of pod except the generic type, you must have a license for that pod type. In addition, the nongeneric pod types accommodate only specific physical and virtual components. A generic pod does not require a specific pod license. You can add any type of physical or virtual component to a generic pod. For more information about pod licenses, see Cisco UCS Director Install and Upgrade Guides. field Address field Hide Pod check box (Optional) A description of the pod. The physical location of the pod. For example, this field could include the city or other internal identification used for the pod. Check this check box to hide the pod if you do not want it to show in the Converged Check View. You can continue to add or delete accounts from the pod. For example, you can use this check box to ensure that a pod that does not have any physical or virtual elements is not displayed in the Converged View. Step 5 Click Add. What to Do Next Add one or more accounts to the pod. Cisco UCS Manager Accounts Each Cisco UCS Manager account represents a single Cisco UCS domain that you want to have managed by Cisco UCS Director. For an environment that does not include Cisco UCS Central, you create Cisco UCS Manager accounts in a pod. 12 OL

23 Initial Vblock Configuration Adding a Cisco UCS Manager Account For an environment that includes Cisco UCS Central, you must create a Cisco UCS Central account under multi-domain managers. All Cisco UCS domains that are registered with that Cisco UCS Central, and their related Cisco UCS Manager accounts are brought into Cisco UCS Director when the Cisco UCS Central account is created. You can assign one or more of those Cisco UCS Manager accounts from the Cisco UCS Central account to a pod if needed. You can also register a Cisco UCS Manager account with a Cisco UCS Central account. Adding a Cisco UCS Manager Account Before You Begin Add the pod to which this Cisco UCS Manager account belongs. Step 4 On the menu bar, choose Administration > Physical Accounts. Click the Physical Accounts tab. Click Add. In the Add Account dialog box, complete the following fields: Pod drop-down list Category Type drop-down list Account Type drop-down list Authentication Type drop-down list Choose the pod to which this account belongs. Choose the category type. You must choose Computing. This is the type of infrastructure for the account. Choose the account type. You must choose UCSM. Choose the type of authentication to be used for this account. This can be one of the following: Locally Authenticated A locally authenticated user account is authenticated directly through the fabric interconnect and can be enabled or disabled by anyone with admin or AAA privileges. Remotely Authenticated A remotely authenticated user account is any user account that is authenticated through LDAP, RADIUS, or TACACS+. Server Management drop-down list Choose how you want to have the servers in this account managed. This can be one of the following: All Servers All servers are managed. This option is the default. If you choose this option, all servers are added in the Managed state. Selected Servers Only selected servers are managed. You can add and remove servers from the managed server list as needed. If you choose this option, all servers are added in the Unmanaged state. Account field A unique name that you assign to this account. OL

24 Adding a Cisco UCS Manager Account Initial Vblock Configuration Server Address field User ID field Password field UCS Authentication Domain field Transport Type drop-down list The IP address of Cisco UCS Manager. For a cluster configuration, this is the virtual IP address. The username that this account will use to access Cisco UCS Manager. This username must be a valid account in Cisco UCS Manager. The password associated with the username. The authentication domain for the remotely authenticated account. This field is not displayed if you are using a locally authenticated account. Choose the transport type that you want to use for this account. This can be one of the following: http https Port field field Contact field Location field Service Provider field The port used to access Cisco UCS Manager. (Optional) A description of this account. The address that you can use to contact the administrator or other person responsible for this account. The location of this account. (Optional) The name of the service provider associated with this account, if any. Step 5 Click Add. Cisco UCS Director tests the connection to Cisco UCS Manager. If that test is successful, it adds the Cisco UCS Manager account and discovers all infrastructure elements in Cisco UCS Manager that are associated with that account, including chassis, servers, fabric interconnects, service profiles, and pools. This discovery process and inventory collection cycle takes approximately five minutes to complete. The polling interval configured on the Administration > System > System Tasks tab specifies the frequency of inventory collection. 14 OL

25 Initial Vblock Configuration Testing the Connection to a Physical Account Testing the Connection to a Physical Account You can test the connection at any time after you add an account to a pod. Step 4 Step 5 On the menu bar, choose Administration > Physical Accounts. Click the tab for the type of account that you want to test. For example, click the Physical Accounts tab or the Multi-Domain Managers tab. In the table, click the row of the account for which you want to test the connection. Click Test Connection. When the connection test has completed, click Close. What to Do Next If the connection fails, verify the configuration of the account, including the username and password. If the username and password are correct, determine whether there is a network connectivity problem. Verifying the Discovery of a Cisco UCS Manager Account Step 4 Step 5 Step 6 On the menu bar, choose Physical > Compute. In the left column, choose the pod that includes the Cisco UCS Manager account that you want to verify. Note The left column tree structure lists nodes for Sites, Unassigned Pods, and Multi-Domain Managers. When a Sites node is expanded, all the pods for that site node are displayed. When you expand an Unassigned Pods node, all the pods that are not assigned to any site are displayed. When you expand the Multi-Domain Managers list, all multi-domain manager account types that you added to Cisco UCS Director are displayed. Click the Compute Accounts tab. In the table, click the row of the account that you want to verify. Click View Details. Cisco UCS Director displays a set of tabs that contain information about the components of that account that it has discovered. Click Back to return to the Compute Accounts tab. OL

26 Viewing the Topology and Connectivity of Devices in a Cisco UCS Domain Initial Vblock Configuration Viewing the Topology and Connectivity of Devices in a Cisco UCS Domain Step 4 Step 5 Step 6 On the menu bar, choose Physical > Compute. In the left column, choose the pod that includes the Cisco UCS Manager account for which you want to view the topology. Click the Compute Accounts tab. In the table, click the row of the account. Click View Connectivity. The Topology View - UCS Device Connectivity dialog box is displayed with a view of the topology and connectivity of the devices in the Cisco UCS Domain. If desired, you can modify the following view options: View Mode drop-down list Adjusts the spacing and positioning of the devices. The mode determines which options are available for you to customize the topology view. You can choose between the following view modes: Hierarchical Concentric Circular Force Directed Show Link Labels check box Shows or hides labels on the links between devices. These labels might not display on some view modes. Allow Item Spacing check box Increases the distance between devices for the Hierarchical view mode. Distance control Adjusts the distance between devices for the Concentric view mode. Radius control Changes the radius of the circle and therefore adjusts the distance between devices for the Circular view mode. Rigidity control Adjusts the rigidity for the Force Directed view. Force Distance control Adjusts the distance between devices for the Force Directed view. Step 7 Click Close to return to the Compute Accounts tab. 16 OL

27 Initial Vblock Configuration Exporting the Configuration of a Cisco UCS Manager Account Exporting the Configuration of a Cisco UCS Manager Account Cisco UCS Director exports a file named Ucs-Timestamp-configuration.zip to the location configured for downloads in your browser. Step 4 Step 5 Step 6 Step 7 On the menu bar, choose Physical > Compute. In the left pane, choose the pod that includes the Cisco UCS Manager account for which you want to export the configuration. In the right pane, click the Compute Accounts tab. In the table, click the row for the account. Click Export Configuration. In the Export UCS Configuration dialog box, click Submit. When the configuration export is complete, click Close. Importing the Configuration of a Cisco UCS Manager Account You can import a configuration that has been exported from a Cisco UCS Manager account in Cisco UCS Director or from Cisco UCS Manager. Note When you import a configuration into a Cisco UCS Manager account, you overwrite any existing configuration in that account. Step 4 Step 5 Step 6 Step 7 On the menu bar, choose Physical > Compute. In the left column, choose the pod that includes the Cisco UCS Manager account for which you want to import the configuration. Click the Compute Accounts tab. In the table, click the row of the account for which you want to import the configuration. Click Import Configuration. On the Upload Configuration screen of the Import UCS Configuration wizard, do the following: a) Click Browse and navigate to the configuration file that you want to import. b) Click Upload. c) When the file upload is complete, click OK. d) Click Next. On the Select Configuration screen of the Import UCS Configuration wizard, check one of the following check boxes: Option Import All Configuration Imports all configuration settings in the file. OL

28 Adding a Vblock Account Initial Vblock Configuration Option Customize Import Imports only the configuration settings that you choose. Step 8 Step 9 Click Submit. When the configuration import is complete, click Close. Adding a Vblock Account Before You Begin Make sure that you create a pod before you add a Vblock account. For more information, see Adding a Pod. On the menu bar, choose Administration > Physical Accounts. In the Physical Acccounts tab, click Add. In the Add Account dialog box, complete the following fields: Pod drop-down list Category drop-down list Account Type drop-down list Account Sub Type drop-down list Choose Vblock for this account. Choose Storage. The account type EMC VNX is selected for you when Storage is selected as the category. Choose from the following VNX account subtypes: VNX File X-Blade enclosure, two to eight blades, configurable failover options, and flexible I/O connectivity. There is one data mover per license. VNX Block Storage or data processor enclosure, dual active storage processors, automatic failover, and flexible I/O connectivity. There are two service providers per license. VNX Unified Single platform for VNX File and VNX Block. There are two service providers per license. Authentication Type drop-down list Account field Server Address field User ID field Choose the Authentication Type for this account. The account name. The IP address of the Vblock server. The user ID of the Vblock server. 18 OL

29 Initial Vblock Configuration Verifying Vblock Account Discovery Password field Transport Type drop-down list The password for the Vblock server. Choose the protocol transport type that you want to use for the account. This can be one of the following: http (Hypertext Transfer Protocol) https (Hypertext Transfer Protocol Secure) Note The default transport type protocol for this account is HTTPS. Port field field Contact field Location field Service Provider field The port (80 is the default). The account description. The contact's . The site location for this account. The service provider name, if any. Step 4 Step 5 Step 6 Click Add. Cisco UCS Director automatically discovers all storage elements in the Vblock account, including aggregates, disks, volumes, LUNs, and Qtree. In the Physical Accounts pane, click the account. Click Test Connection. What to Do Next Verify that the account has been discovered. The discovery process typically takes a few minutes. Verifying Vblock Account Discovery After you add a Cisco UCS Manager to a Cisco UCS Director Vblock environment, all discovered components of this environment are displayed at the account level. On the menu bar, choose Physical > Storage. In the Storage pane, click the Vblock account. Click the System Summary tab. The Summary reports for this account appear. OL

30 Configuring VNX Initial Vblock Configuration Configuring VNX Cisco UCS Director supports EMC VNX Block, File, and Unified accounts for the VNX versions 5100, 5200, 5300, 5400, 5500, 5600, 5700, and For a VNX Block account, you create the following: Storage pools Storage groups RAID groups Initiators Logical Unit Numbers (LUNs) The reports available for VNX Block accounts include details on all of these items, as well as on storage processors, ports, data movers, and disk devices. You can also view tabular reports for RAID groups or hosts, and instant reports for file system allocation, the top five storage capacity file systems, the top five file systems file count, and the top five storage capacity volumes. For a VNX File account, you create use either Common Internet File Servers (CIFS) or Network File System (NFS) Export. For CIFS, you create the CIFS servers and shares, and the Domain System (DNS) domains. For NFS Export, you create the following: Storage pools for files File systems Interfaces Volumes Mounts The reports available for VNX File accounts include details on these items, as well as system overview summaries. For a VNX Unified account, which combines VNX Block and VNX File, you perform all the steps needed for both VNX block and VNX file accounts. You can view any of the reports available for VNX block or VNX file accounts. After an account is established, you can configure, manage and monitor EMC VNX features in Cisco UCS Director. For more information about configuring EMC VNX management and monitoring features for this pod, see the Cisco UCS Director EMC VNX Management Guide. 20 OL

31 Initial Vblock Configuration Adding a VNX Block Account Adding a VNX Block Account Because some Navisphere features are now only supported with an SSH CLI, the new secure CLI called NaviSec CLI is required. As a consequence of this Navisphere requirement, you must replace the legacy CLI, navicli, with the Secure CLI called NaviSec CLI. Before You Begin Create a data center for the account of the type Generic or vblock. Configure a VM and install the NavisecCli package on it. Create a set of User credentials for the NavisecCli package with enough privileges to run NavisecCli commands to manage and configure VNX Storage. On the menu bar, choose Administration > Physical Accounts. In the Physical Accounts pane, click Add. In the Add Account dialog box, complete the following fields, then click Submit: Table 2: Add Account Pod drop-down list Category drop-down list Account Type drop-down list Choose the pod (data center) for this account. Choose Storage. Choose EMC VNX Block. Step 4 Another Add Account dialog box appears to collect data. In this Add Account dialog box, complete the following fields: Pod drop-down list Account Type drop-down list Account field field Storage Processor A IP Address field Storage Processor B IP Address field The pre-selected pod (data center) for this account appears. The pre-selected type for this account appears. The account name. Describe this account so that others can distinguish it from similar accounts. The IP address for Storage Processor A. The IP address for Storage Processor B. OL

32 Adding a VNX Block Account Initial Vblock Configuration Use Credential Policy checkbox Credential Policy drop-down list and Add Credential Policy form icon Checkmark this box to apply a new or existing credential policy to the VNX. See the description of your options below. Note If you click this option and apply a policy, the Block Access and Password fields described below will not appear in this form. You have these two options if you check the Use Credential Policy checkbox. From a drop-down list, select a pre-defined policy for this type of account and apply that policy data to this account Click the icon to open the Add Credential Policy form, and use it to define a policy for this type of account. You can use a defined Credential Policy in future sessions; it will appear in the drop-down list. Block Access User field Block Access Password field Protocol drop-down list NaviSecCLI Host IP Addressfield Use Credential Policy checkbox NaviSecCLI Host User field NaviSecCLI Host User Passwordfield Block Access Port field Scope drop-down list Contact field Location field The username for block access. Note If you apply a policy, the Block Access and Password fields described here do not appear in this form. The password for block access. Choose the protocol to be used. The address for the secure Navisphere CLI host. Checkmark this box to apply a new or existing credential policy. See the description of your options above. Note If you apply a policy, the NaviSecCLI Host User and Password fields described below do not appear in this form. The user name for the specified secure Navisphere CLI host. Password for the specified secure Navisphere CLI host. The port to be used. Choose the scope. The contact . The contact's location (user defined). Step 5 Step 6 Step 7 Click Submit. In the Physical Accounts pane, choose the account. Click Test Connection. 22 OL

33 Initial Vblock Configuration Adding a VNX File Account Adding a VNX File Account Before You Begin You must create a data center for the account. On the menu bar, choose Administration > Physical Accounts. In the Physical Acccounts pane, click Add. In the Add Account dialog box, complete the following fields, then click Submit: Table 3: Add Account Pod drop-down list Category drop-down list Account Type drop-down list Choose the pod (data center) for this account. Choose Storage. Choose EMC VNX File. Step 4 Another Add Account dialog box appears to collect data. In the longer Add Account dialog box, complete the following fields: Pod drop-down list Account Type drop-down list Account field field Control Station IP Address field Use Credential Policy checkbox The pre-selected pod (data center) for this account appears. The pre-selected type for this account appears. The account name. Describe this account so that others can distinguish it from similar accounts. The Control Station IP address of the VNX device. Checkmark this box to apply a new or existing policy to the VNX. See the description of your options below. Note If you click this option and apply a policy, the Control Station and Password, and the Protocol/Transport type and Port fields described below will not appear in this form. They are administered by the policy. OL

34 Adding a VNX Unified Account Initial Vblock Configuration Credential Policy drop-down list and Add Credential Policy form icon You have these two options if you check the Use Credential Policy checkbox. From a drop-down list, select a pre-defined policy for this type of account and apply that policy data to this account Click the icon to open the Add Credential Policy form, and use it to define a policy for this type of account. You can use a defined Credential Policy in future sessions; it will appear in the drop-down list. Password field Transport Type drop-down list Port field Contact field Location field The password associated with the specified Control Station address. Choose the transport type. The port. The contact's . The contact's location (user defined). Step 5 Step 6 Step 7 Click Submit. In the Physical Accounts pane, choose the account. Click Test Connection. What to Do Next To change information in a VNX account, click Edit. Adding a VNX Unified Account Because some Navisphere features are now only supported with an SSH CLI, the new secure CLI called NaviSec CLI is required. As a consequence of this Navisphere requirement, you must replace the legacy CLI, navicli, with the Secure CLI called NaviSec CLI. Before You Begin Create a data center for the account of the type Generic or vblock. On the menu bar, choose Administration > Physical Accounts. In the Physical Accounts pane, click Add. In the Add Account dialog box, complete the following fields, then click Submit: 24 OL

35 Initial Vblock Configuration Adding a VNX Unified Account Table 4: Add Account Pod drop-down list Category drop-down list Account Type drop-down list Choose the pod (data center) for this account. Choose Storage. Choose EMC VNX Unified. Step 4 Another Add Account dialog box appears to collect data. In the longer Add Account dialog box, complete the following fields: Pod drop-down list Account Type drop-down list Account field field The Control Station IP Address field Use Credential Policy checkbox Credential Policy drop-down list and Add Credential Policy form icon The pre-selected pod (data center) for this account appears. The pre-selected type for this account appears. The account name. Describe this account so that others can distinguish it from similar accounts. The Control Station IP address of the VNX device. Checkmark this box to apply a new or existing policy to the VNX. See the description of your options below. Note If you click this option and apply a policy, the Control Station and Password, and the file Access Protocol and Port fields described below will not appear in this form. They are administered by the policy. You have these two options if you check the Use Credential Policy checkbox. From a drop-down list, select a pre-defined policy for this type of account and apply that policy data to this account Click the icon to open the Add Credential Policy form, and use it to define a policy for this type of account. You can use a defined Credential Policy in future sessions; it will appear in the drop-down list. Control Station User field Password field File Access Protocol drop-down list File Access Port field The user name associated with the specified Control Station address. The password associated with the Control Station IP address and user name. Choose the protocol to be used. Choose the port to be used. OL

36 Adding a VNX Unified Account Initial Vblock Configuration Storage Processor A IP Address field Storage Processor B IP Address field Use Credential Policy checkbox Block Access User field Block Access Password field NaviSecCLI Host IP Addressfield Use Credential Policy checkbox NaviSecCLI Host User field NaviSecCLI Host User Passwordfield Block Access Port field Scope drop-down list Contact field Location field The IP address for Storage Processor A. The IP address for Storage Processor B. Checkmark this box to apply a new or existing credential policy to the VNX. See the description of the Credential Policy options, above. Note If you click this option and apply a policy, the and Password fields described below will not appear in this form. The username for block access. The associated password for block access. The address for the secure Navisphere CLI host. Checkmark this box to apply a new or existing credential policy. See the description of your options above. Note If you apply a policy, the NaviSecCLI Host User and Password fields described below do not appear in this form. The user name for the specified secure Navisphere CLI host. Password for the specified secure Navisphere CLI host. The port to be used. Choose the scope. The contact . The contact's location (user defined). Step 5 Step 6 Step 7 Click Submit. In the Physical Accounts pane, choose the account. Click Test Connection. What to Do Next To change information in a VNX account, click Edit. 26 OL

37 Initial Vblock Configuration Configuring VMAX Configuring VMAX Cisco UCS Director supports EMC Symmetrix VMAX 10K and 20K. A VMAX license supports one engine (two directors). Cisco UCS Director connects to EMC VMAX using the EMC Solutions Enabler. To manage VMAX in Cisco UCS Director, you use a Linux-based Symmetrix Performance Analyzer (SMC) or Symmetrix Management Console (SPA) server. We recommend Linux version After building the Linux image and installing the EMC Solutions Enabler, you create an EMC VMAX Solutions Enabler account. Note The scope of this guide discusses how to configure the EMC Solutions Enabler and the EMC VMAX Solutions account only. After an account is established, you can configure, manage and monitor EMC VMAX features in Cisco UCS Director. For more information about configuring EMC VMAX management and monitoring features for this pod, see the Cisco UCS Director EMC Symmetrix VMAX Management Guide. Installing the EMC Solutions Enabler Before You Begin To communicate with VMAX, Cisco UCS Director now supports a Windows-based EMC Solutions Enabler (SE). Before using this SE, you must establish a Secure Shell (SSH). To set up an SSH, Cisco recommends that you install Cygwin version , and use the SSH daemon on the host. Cygwin provides a Linux-like environment on Microsoft Windows. See for the download. After you install the SSH server on the Windows-based SE, modify the path in the profile to include the Solutions Enabler bin folder so that whoever uses SSH to get into the Windows SE can immediately run VMAX commands. You should set up new default paths to enable the user-installed software to override the system software. The following sample provides an generic example of code used to modify the path: VMAXHOME="/cygdrive/c/Program Files/EMC/SYMCLI/bin" PATH="/usr/local/bin:/usr/bin:${VMAXHOME}:${PATH}" Note You can add libraries and legacy libraries, such as glibc, to the VM. You will need gatekeepers to serve as Raw Device Mappings (RDMs). Allow 6-8K mappings for each RDM. Create the base Linux image for the VM you will use. For the base Linux image, you can use an SMC or SPA servers that run CentOS, version 5.7 x86 or x86_64. For an SMC server, allow 20 GB of space. For an SPA server, allow at least 120 GB. OL

38 Adding a Solutions Enabler Account Initial Vblock Configuration Step 4 Step 5 Step 6 Step 7 Step 8 Step 9 Assign a few gatekeepers as RDMs. Reboot the Linux VM. From the EMC Powerlink site, download the EMC Solutions Enabler package for Linux, and the SMAS package se7310-linux-i386-ni.tar.gz. Note Refer to the Cisco UCS Director Compatibility Matrix to identify which version to download and install. Use MD5 Checksum 9809ac14ed8bfcc19789d7d5671d6015. Using SCP, transfer the tar file to your VM. At a command prompt, enter the following command to decompress the tar file: [root@smc ~]# tar xzvf se7310-linux-i386-ni.tar.gz Install the EMC Solutions Enabler by entering the following command: [root@smc ~]#./se7310_install.sh -install] Verify that the emc/symcli bin folder is in the Linux path, with this directory structure: <symcli path>/bin. Here is an example: /opt/emc/symcli/bin. To connect to the VMAX device from UCSD, you must update the PATH variable with the SYMCLI binary dir by updating the.bashrc file for the user that logs in to VMAX. a) Log in to the Solutions Enabler machine with the credentials that Cisco UCS Director will use. b) Edit.bashrc using your editor of choice; for example vi.bashrc c) Add the following line to the.bashrc file: PATH=$PATH:$HOME/bin:<symcli binary path>/bin d) Save the file and exit. Adding a Solutions Enabler Account Before You Begin An EMC VMAX Solutions Enabler must be installed on a Linux VM. Step 4 Log into Cisco UCS Director. Choose Administration > Physical Accounts. In the Physical Acccounts pane, click Add. In the Add Account dialog box, complete the following fields: Data Center drop-down list Choose a data center for this account. Category drop-down list Account Type drop-down list Authentication Type drop-down list Choose Storage. Choose EMC VMAX Solutions Enabler. Choose Locally or Remotely. If you chose to authenticate remotely, continue to Step OL

39 Initial Vblock Configuration Initial VPLEX Configuration Account field Server Address field User ID field Password field Transport Type drop-down list Port field field Contact field Location field Service Provider field The account name. The control station IP address for the VMAX device. The user ID for this account. The password for this account. Choose ssh. The port. The account description. The contact's . The location for this account. The service provider for this account. Step 5 Step 6 Step 7 Step 8 For remote authentication, complete the additional field for UCS Authentication Domain. Click Add. In the Physical Acccounts pane, choose the account. Click Test Connection. Initial VPLEX Configuration Note The scope of this guide discusses how to configure a VPLEX account and assign this pod to a VPLEX cluster (plex) only. After a VPLEX account is established and a pod is associated with a VPLEX cluster, you can configure, manage and monitor VPLEX features in Cisco UCS Director. For more information about configuring VPLEX management and monitoring features for this pod, see the Cisco UCS Director EMC VPLEX Management Guide. OL

40 Creating a VPLEX Account Initial Vblock Configuration Creating a VPLEX Account Step 4 Step 5 Step 6 On the menu bar, choose Administration > Physical Accounts. Click the Multi-domain Managers tab. Click New. In the Add Account dialog box, choose EMC VPLEX from the Account Type drop-down list. Click Submit. In the Add Account dialog box, complete the following fields: Account field A unique name that you assign to this account. Server IP field Use Credential check box Username field Password field Protocol drop-down list Port field Contact field Location field The IP address of the VPLEX server. Check the check box if you want to use a policy to give the credentials. The username that this account uses to access the VPLEX server. This username must be a valid account in the VPLEX server. The password associated with the username. The https parameter is pre-selected for the transport type protocol. Note http is not supported for VPLEX. The port used to access the VPLEX server. Port 443 is the default secure HTTPS port. The address that you use to contact the administrator or other person responsible for this account. The location of the contact. Step 7 Step 8 Step 9 Click Submit. In the Multi-Domain Managers tab, choose the EMC VSPEX account that you just created. Click Test Connection. The Test Connectivity dialog box displays and confirms if the connection was successful. 30 OL

41 Initial Vblock Configuration Assigning a Pod to a Cluster Assigning a Pod to a Cluster You must also create a pod with each VPLEX cluster (1 and 2). Step 4 Step 5 Step 6 On the menu bar, choose Physical > Storage. On the Storage pane, click the Multi-Domain Managers icon to expand the list of connected multi-domain managers. Choose EMC VPLEX to expand the connected VPLEX device(s) and click the VPLEX device you want. Click the Clusters tab and click the cluster you want to assign to the pod. Click Assign to Pod. In the Assign Pod to Cluster dialog box, complete the following field: Select Pod drop-down list Choose a pod type. This can be one of the following: Default Pod VSPEX Generic Vblock Step 7 Step 8 Click Submit. Repeat the previous steps to assign a pod to the other cluster. Initial EMC Isilon Configuration Note The scope of this guide discusses how to configure an EMC Isilon account only. After an account is established, you can configure, manage and monitor EMC Isilon features in Cisco UCS Director. For more information about configuring EMC Isilon management and monitoring features for this pod, see the Cisco UCS Director EMC Isilon Management Guide. OL

42 Creating an EMC Isilon Account Initial Vblock Configuration Creating an EMC Isilon Account Step 4 On the menu bar, choose Administration > Physical Accounts. Click the Physical Accounts tab. Click New. In the Add Account dialog box, complete the following fields: Pod drop-down list Choose from the following pod types: Default Pod Generic VSPEX Vblock Category drop-down list Account Type drop-down list Choose Storage. Choose EMC Isilon Cluster. Step 5 Step 6 Click Submit. In the next Add Account dialog box, complete the following fields: Account field Server IP field field Use Credential check box Username field Password field The name of this Isilon account. For example, isilon-1. The IP address of the Isilon storage system. The description of the Isilon storage system. Check the check box if you want to use a policy to give the credentials. The username that this account uses to access the Isilon storage system. This username must be a valid account in the Isilon storage system. The password associated with the username. 32 OL

43 Initial Vblock Configuration Initial EMC RecoverPoint Configuration Protocol drop-down list Choose the protocol transport type that you want to use for the account. This can be one of the following: http (Hypertext Transfer Protocol) https (Hypertext Transfer Protocol Secure) Note The default transport type protocol for this account is HTTPS. Port field Contact field Location field The port used to access Isilon server. Port 443 is the default secure HTTPS port. Note Port 8080 is used for both HTTP and HTTPS. The address that you use to contact the administrator or other person responsible for this account. The location of the contact. Step 7 Step 8 In the Physical Accounts tab, choose the EMC Isilon account that you just created. Click Test Connection. Initial EMC RecoverPoint Configuration Note The scope of this guide discusses how to configure an EMC RecoverPoint account only. After an account is established, you can configure, manage and monitor EMC RecoverPoint features in Cisco UCS Director. For more information about configuring EMC RecoverPoint management and monitoring features for this pod, see the Cisco UCS Director EMC RecoverPoint Management Guide. Creating an EMC RecoverPoint Account Step 4 On the menu bar, choose Administration > Physical Accounts. Click the Multi-Domain Managers tab. Click Add. In the Add Account dialog box, complete the following field: OL

44 Creating an EMC RecoverPoint Account Initial Vblock Configuration Account Type drop-down list Choose EMC RecoverPoint. Step 5 Step 6 Click Submit. In the next Add Account dialog box, complete the following fields: Account field The name of this RecoverPoint account. For example, RP-1. Server IP field field Use Credential check box Username field Password field Protocol drop-down list The IP address of the RecoverPoint system. The description of the RecoverPoint system. Check the check box if you want to use a policy to give the credentials. The username that this account uses to access the RecoveryPoint storage system. This username must be a valid account in the Isilon storage system. The password associated with the username. Choose the protocol transport type that you want to use for the account. This can be one of the following: http (Hypertext Transfer Protocol) https (Hypertext Transfer Protocol Secure) Note The default transport type protocol for this account is HTTPS. Port field Contact field Location field The port used to access Isilon server. Port 443 is the default secure HTTPS port. Note Port 8080 is used for both HTTP and HTTPS. The address that you use to contact the administrator or other person responsible for this account. The location of the contact. Step 7 Step 8 In the Multi-Domain Managers tab, choose the EMC RecoverPoint account that you just created. Click Test Connection. What to Do Next Verify that the account has been discovered. The discovery process typically takes a few minutes. 34 OL

45 Initial Vblock Configuration Network Configuration Network Configuration Cisco UCS Director enables you to manage, orchestrate, and monitor multiple network devices and fabric platforms from Cisco and select vendors: Cisco network and fabric support for Cisco Nexus switches. Brocade network and fabric support. Cisco UCS fabric interconnects that operate in the N-Port Virtualization (NPV) mode in which the server Fibre Channel traffic is either manually or automatically pinned to a specific Fibre Channel over Ethernet (FCoE) uplink. Note See Compatibility Matrix for Cisco UCS Director for more specific network support information. Adding a Network Device to a Pod On the menu bar, choose Administration > Physical Accounts. In the Managed Network Elements tab, click the Add Network Element icon. In the Add Network Element dialog box, complete the following fields: Pod drop-down list Device Category drop-down list Choose a pod. Choose one of the following network device options: Brocade Fabric OS Brocade Network OS Force10 (FTOS) Cisco IOS Cisco Nexus OS Cisco ASA Device IP field Protocol drop-down list The IP address of the device. Choose the protocol to use to communicate with the device. This can be one of the following: telnet ssh OL

46 Verifying Network Device Details in a Pod Environment Initial Vblock Configuration Port field Login field Password field Enable Password field The port number for the device. The default is port 23. The login username. The login password for the device. The enable password for the device. Step 4 Step 5 Click Submit. In the Converged pane, click the pod. What to Do Next Verify that the managed network devices are configured properly. Verifying Network Device Details in a Pod Environment After the network device is added to the pod, all discovered components of the pod environment are displayed at the account level. Step 4 On the menu bar, choose Physical > Network. In the Network pane, click the pod. Click the Managed Network Elements tab. Click the network device, and click View Details. All information about the device appears in the Summary tab. You can choose other tabs to see specific details, such as interfaces, modules, VLANs, port profiles, and so on, depending on the network device. 36 OL

47 CHAPTER 4 Network Configuration for Cisco UCS Director Baremetal Agent This chapter contains the following sections: About the Network Configuration Options, page 37 Single Network for Management and PXE, page 37 Separate Networks for Management and PXE, page 38 Configuring the Baremetal Agent Appliance through the Cisco UCS Director GUI, page 40 Configuring the DHCP Server for a Baremetal Agent Appliance in Cisco UCS Director GUI, page 42 About the Network Configuration Options You can choose between the following network configuration options for Cisco UCS Director Baremetal Agent: Single network for management and PXE (Preboot Execution Environment) Separate networks for management and PXE Choose the network configuration option that best meets the requirements of your environment. For advice on this decision, refer to the high-level discussions in this chapter. Single Network for Management and PXE We recommend that you choose this network configuration option if your environment permits the following to be hosted on the same network interface and Layer 2 network (see the following figure): Services provided by Cisco UCS Director Baremetal Agent, such as DHCP, TFTP, and HTTP OL

48 Prerequisites and Assumptions for a Single Network Configuration Network Configuration for Cisco UCS Director Baremetal Agent Management traffic between Cisco UCS Director Baremetal Agent and Cisco UCS Director or other devices and appliances Figure 2: Sample Topology for a Single Network Prerequisites and Assumptions for a Single Network Configuration If you plan to configure Cisco UCS Director Baremetal Agent with a single network configuration, ensure that your environment meets the following prerequisites and assumptions: Cisco UCS Director has been installed and the network interface configured, as described in the appropriate Cisco UCS Director installation guide. Cisco UCS Director is reachable through a web browser and you can log in. Cisco UCS Director Baremetal Agent has been installed, as described in the Cisco UCS Director Baremetal Agent Installation and Configuration Guide, and no additional configuration has been performed. The required single Management and PXE VLAN is provisioned and available as a virtual port group or port profile that virtual machines (VMs) can be attached to or leverage. Separate Networks for Management and PXE We recommend that you choose this network configuration option if your environment does not permit the following to be hosted on the same network interface and layer 2 network: On the PXE network, services provided by Cisco UCS Director Baremetal Agent, such as DHCP, TFTP, and HTTP 38 OL

49 Network Configuration for Cisco UCS Director Baremetal Agent Prerequisites and Assumptions for a Separate Network Configuration On the Management network, traffic between Cisco UCS Director Baremetal Agent and Cisco UCS Director or other devices and appliances Figure 3: Sample Topology for Separate PXE and Management Networks Prerequisites and Assumptions for a Separate Network Configuration If you plan to configure Cisco UCS Director Baremetal Agent with a separate network configuration, ensure that your environment meets the following prerequisites and assumptions: Cisco UCS Director has been installed and the network interface configured, as described in the appropriate Cisco UCS Director installation guide. Cisco UCS Director is reachable through a web browser and you can log in. Cisco UCS Director Baremetal Agent has been installed, as described in the Cisco UCS Director Baremetal Agent Installation and Configuration Guide and no additional configuration has been performed. The following networks are provisioned and available as a virtual port group or port profile that VMs can be attached to or leverage: Management (MGMT) network Used for traffic between Cisco UCS Director Baremetal Agent and Cisco UCS Director PXE network Used for PXE services traffic, such as DHCP, HTTP, and TFTP OL

50 Configuring the Baremetal Agent Appliance through the Cisco UCS Director GUI Network Configuration for Cisco UCS Director Baremetal Agent Note The PXE network/vlan must be configured as the native, or default, VLAN on the server. For example, for a Cisco UCS Director server, edit the vnic template associated with the server and choose the PXE network/vlan as the native VLAN. You can perform this configuration in Cisco UCS Manager or Cisco UCS Director. Configuring the Baremetal Agent Appliance through the Cisco UCS Director GUI At this point, you have two options when you create a new Baremetal Agent: Use a single network for both management and PXE traffic. Use separate networks: one for management and another for PXE traffic. Before You Begin The BMA 5.0 ovf must be deployed and its network must be configured. Cisco UCS Director 5.0 Multi-Node configuration must be completed. You must have created VMs in the VMware vsphere hypervisor. The network must be configured, the Baremetal Agent VM must be completely booted up, and the VMware vsphere VM Console must be closed. You have the IP address of the Baremetal Agent VM. You must have an environment that supports the network configuration you intend to use: either the single network or the separate network configuration. Refer as necessary to the topics in this documentation set that explain these different configurations. To provide required DHCP services, locate one DHCP server in the same PXE VLAN as Cisco UCS Director Baremetal Agent and configure that DHCP server with an appropriate IP address range. To use Cisco UCS Director Baremetal Agent to PXE boot a given operating system, you must first provision that operating system image. Step 4 On the Menu bar, chooseadministration > Physical Accounts Click the Baremetal Agents tab. Click Add. In the Add Baremetal Agent Appliance dialog box, complete the appropriate fields as described in the following table: To configure Cisco UCS Director Baremetal Agent for multi-node capabilities, set the UCSD Database Address to use the InventoryNode IP address. See the entry in the table below. 40 OL

51 Network Configuration for Cisco UCS Director Baremetal Agent Configuring the Baremetal Agent Appliance through the Cisco UCS Director GUI BMA field BMA Management /PXE Address field Login ID field Password field The name you assign to the Bare Metal Agent for a given purpose. As a best practice, apply a naming convention that includes the names of the managed system components. This will enable you to recognize the constraints and capabilities of the agent. The IP address of the BMA manager. If you are using a single network for both BMA manager and the PXE, then this same address will automatically be assigned as the PXE address. Important This address must be reachable from the UCSD appliance. The Login ID for the Baremetal Agent administrator. The Password for the same Baremetal Agent administrator. BMA uses Different Interfaces for Management and PXE Traffic checkbox BMA PXE Interface Address field field Location field UCSD Database Address drop-down list Check this box if you want the network hosting the PXE server to be separate from the network hosting the traffic manager. Note If you check this box, a different set of fields will appear in this form below the checkbox. The IP address for the BMA PXE server, if different from the address of the BMA manager. Note This field appears only if the BMA uses Different Interfaces... checkbox above has been selected. Additional useful information about this Baremetal agent. Optional. Location of this Baremetal agent. A physical location name, for example. Optional. Choose the IP address associated with the UCSD database that this BMA is going to use. Attention If you are configuring BMA for multi-node capabilities, select the InventoryNode IP address. Step 5 Click Submit. Troubleshooting Tips Be aware that the first BMA defined in Cisco UCS Director Baremetal Agent is automatically labeled as the Default BMA. OL

52 Network Configuration for Cisco UCS Director Baremetal Agent Configuring the DHCP Server for a Baremetal Agent Appliance in Cisco UCS Director GUI Step 6 A new row appears in the Baremetal Agents tab, showing current information for this agent. Initiate BMA services by clicking Start Services. If the DHCP sever is not correctly configured, the status displayed in the Enabled Services column will indicate that services are not enabled. BMA status will become "active" once the network services are started correctly. The first BMA created with Release 5.0 or later will be designated as the "Default" BMA. By default, the Default BMA will be used as the target BMA for the Setup PXE Boot task, if you use this task in a Workflow. To designate a different BMA as the Default, select it in the Baremetal Agents tab and click Set Default BMA. What to Do Next Check the service status by clicking Service Status. To see the SSH-based test connection status with the BMA, check the Baremetal Agents table column labeled Reachable. By default, a test Connection request is triggered every 15 minutes. This frequency can be adjusted by using the "BMA Heartbeat Task". To check the BMA log, click View BMA logs. To check for Cisco UCS Director Baremetal Agent database updates by BMA, check the Baremetal Agents table column labeled Status. If there is no update in the database then the status will be "Inactive" To configure a PXE interface IP address, click Configure Interface. Optional: Test by using the agent to perform a PXE boot in a controlled test environment. For details about setting up the PXE Boot request, see the documentation about "Adding and Configuring PXE Boot Requests". Configuring the DHCP Server for a Baremetal Agent Appliance in Cisco UCS Director GUI The DHCP server and the TFTP server are the crucial components of a PXE server. This configuration feature reads the DHCP configuration from the BMA appliance and enables you to edit the configuration. You use the BMA option titled Configure DHCP to edit configuration data that applies to the DHCP subnet, netmask, bootp, router, and PXE server. Note If you are configuring the DHCP service for the first time, or you have made a change in the DHCP configuration, be aware you must click Start Services to start or re-start the DHCP. The current status of the services appears in the Enabled Services column in Baremetal Agents tab. Restriction For a multi-home DHCP configuration, you can use the Configure DHCP option to edit only the first subnet information. For the remaining subnets, you must manually edit the DHCP configuration file (/etc/dhcpd.conf). 42 OL

53 Network Configuration for Cisco UCS Director Baremetal Agent Configuring the DHCP Server for a Baremetal Agent Appliance in Cisco UCS Director GUI Before You Begin The BMA 5.0 ovf must be deployed and its network must be configured. Cisco UCS Director 5.0 Multi-Node configuration must be completed. You must have one DHCP server in the same PXE VLAN as thecisco UCS Director Baremetal Agent, and this DHCP server must be configured with an appropriate IP address range. Step 4 Step 5 On the Menu bar, choose Administration > Physical Accounts > Baremetal Agents Select a Baremetal Agent and click Configure DHCP. The Configure DHCP dialog box appears. This form contains the default DHCP configuration available in the BMA. Tip The PXE Server IP address should be the same PXE interface address that you specify when adding the BMA account. Update or otherwise modify the DHCP configuration data, as appropriate, and click Submit. All the DHCP IP address assignments shown in the dialog box will be updated in the BMA DHCP configuration and the DHCP service will be restarted. Select the BMA account just added and click Start Services. After the services have started, verify that the status of the account is set to Active, and that the Enable Services column indicates that all expected services are running. What to Do Next At this point, if you have a Baremetal agent defined to use the PXE server that you have just configured, click Start Services to start the services that comprise your PXE server. This results in a change in the protocol status. Details are displayed in the Enabled Services column. To edit or delete configuration data, click Stop Services first. OL

54 Network Configuration for Cisco UCS Director Baremetal Agent Configuring the DHCP Server for a Baremetal Agent Appliance in Cisco UCS Director GUI 44 OL

55 CHAPTER 5 Vblock Operations This chapter contains the following sections: Tip For more information about the Vblock operations described in this chapter, see the Cisco UCS Director Management Guide for Cisco UCS Manager. Configuration Guidelines for Vblock Operations, page 45 Configuration Guidelines for Vblock Operations The following table provides Cisco UCS Director guidelines for implementing Vblock operations. The configuration notes explain important configuration details related to each task in this chapter. Tip For more information related to the tasks in this chapter, see the Cisco UCS Director Management Guide for Cisco UCS Manager. Task Configuration Notes Creating an Organization, on page 48 Create a top-level organization which is the root. The policies and pools created in this root are system-wide and are available to all organizations in the system. Configuring the Chassis/FEX Discovery Policy, on page 48 A chassis policy is configured to specify how the system reacts when a new chassis is added. Ensure that the 2-link option is selected from the Action drop-down list. Creating a UUID Pool, on page 49 Create a universally unique identifier (UUID) suffix pool with a name that is less than 16 characters. The default settings can be used. The UUID suffix pool ensures that UUID suffix variable values are unique for each server associated with a service profile. The service profile uses the UUID suffix pool to avoid conflicts. OL

56 Configuration Guidelines for Vblock Operations Vblock Operations Task Creating a MAC Pool, on page 50 Creating a WWNN Pool, on page 50 Creating a WWPN Pool, on page 51 Creating a Network Control Policy, on page 51 Creating a vnic Template, on page 53 Configuration Notes Create two MAC pools for each fabric interconnect. For example, fabric interconnect A and B. Specify 2 in the Size field (recommended). Create two worldwide node name (WWNN) pools for each fabric interconnect. Specify 2 in the Size field (recommended). Create two worldwide port name (WWPN) pools for each fabric interconnect. Specify 2 in the Size field (recommended). Create the network control policy with the Cisco Discovery Protocol (CDP) enabled. Create two vnic templates for each fabric interconnect. For example, fabric interconnect A and B. Follow the instructions in the task and use the following configuration guidelines: For the Target check boxes, choose both the Adapter and VM parameters. From the Template Type drop-down list, choose the Initial Template. In the MTU field, we recommend that you enter Note If the PXE server and the Cisco UCS server are in separate VLANs, you must create separate vnic templates for both servers in each fabric interconnect. Creating a VSAN, on page 57 Associating the VSANs to the Fabric Interconnects Creating a vhba Template, on page 58 Create a virtual storage area network (VSAN) for each fabric interconnect. For example, fabric interconnect A and B. Associate each VSAN with each fabric interconnect. Create a vhba template for each fabric interconnect. Follow the instructions in the task and use the following configuration guidelines: From the Template Type drop-down list, choose the Initial Template. In the Max Data Field Size field, enter Creating a LAN Boot Policy, on page 60 Creating a SAN Boot Policy, on page 61 Create a LAN boot policy for each fabric interconnect. Create a SAN boot policy for each fabric interconnect. 46 OL

57 Vblock Operations Configuration Guidelines for Vblock Operations Task Creating a vnic, on page 64 Creating a vhba, on page 64 Configuration Notes Create a vnic for each fabric interconnect. Follow the instructions in the task and use the following configuration guideline: Note From the Adapter Policy drop-down list, choose VMware. If the PXE server and the Cisco UCS server are in separate VLANs, you must create separate vnic templates for both servers in each fabric interconnect. Create a vhba for each fabric interconnect. Follow the instructions in the task and use the following configuration guideline: From the Adapter Policy drop-down list, choose VMware. Creating a Network Policy, on page 65 Creating a Storage Policy, on page 67 Follow the instructions in the task and use the following configuration guidelines: Note From the LAN Connectivity Type drop-down list, choose Expert. In the Add vnic field, specify the number of vnics (for each fabric interconnect) that you want to add to the network policy. From the Template For vnic1/vnic2/vnic3/vnic4 drop-down list, choose the vnic template that you created. If the PXE server and the Cisco UCS server are in separate VLANs, you must create separate vnic templates for both servers in each fabric interconnect. Follow the instructions in the task and use the following configuration guidelines: From the SAN Connectivity Type drop-down list, choose Expert. From the WWNN Pool drop-down list, choose the WWNN pool that you created previously. In the Add vhba field, specify the number of vhbas (for each fabric interconnect) that you want to add to the storage policy. From the Template For vhba1/vhba2/vhba3/vhba4 drop-down list, choose the vhba template that you created. Note If the PXE server and the Cisco UCS server are in separate VLANs, you must create separate vnic templates for both servers in each fabric interconnect. OL

58 Creating an Organization Vblock Operations Creating an Organization You can create a top-level organization which is the root. The policies and pools created in this root are system-wide and are available to all organizations in the system. Step 4 Step 5 On the menu bar, choose Physical > Compute. In the left pane, expand the pod and then click the Cisco UCS Manager account. In the right pane, click the Organizations tab. Click Add. In the Add Organization dialog box, complete the following fields: a) In the field, enter a name for the organization. b) In the field, enter a description for the organization. c) From the Parent Organization drop-down list, choose the organization under which this organization will reside. Configuring the Chassis/FEX Discovery Policy A chassis policy is configured to specify how the system reacts when a new chassis is added. Step 4 Step 5 Step 6 Step 7 On the menu bar, choose Physical > Compute. In the left pane, expand the pod and then click the Cisco UCS Manager account. In the right pane, click the Equipment Global Policies tab. Check the Chassis/FEX Discovery Policy check box. From the Action drop-down list, choose the minimum threshold for the number of links between the chassis or Fabric Extender (FEX) and the fabric interconnect: 1-link 2-link 4-link 8-link From the Link Grouping Preference drop-down list, choose whether the links from the IOMs or FEXes to the fabric interconnects are grouped in a port channel. Note The link grouping preference takes effect only if both sides of the links between an IOM or FEX and the fabric interconnect support fabric port channels. If one side of the links does not support fabric port channels, this preference is ignored and the links are not grouped in a port channel. Click Save. 48 OL

59 Vblock Operations Creating a UUID Pool Creating a UUID Pool Step 4 Step 5 Step 6 Step 7 On the menu bar, choose Physical > Compute. In the left pane, expand the pod and then click the Cisco UCS Manager account. In the right pane, click the Organizations tab. Click the organization in which you want to create the pool and then click View Details. Click the UUID Pools tab. Click Add. In the Add UUID Pool dialog box, complete the following fields: field field Prefix drop-down list A unique name for the pool. A description for the pool. Choose how the prefix is created. This can be one of the following: Derived The system creates the prefix. Other You specify the desired prefix. If you select this option, a text field displays where you can enter the desired prefix, in the format XXXXXXXX-XXXX-XXXX. From field Size field The first UUID address in the block. The number of UUID addresses in the block. Step 8 Click Submit. OL

60 Creating a MAC Pool Vblock Operations Creating a MAC Pool Step 4 Step 5 Step 6 Step 7 On the menu bar, choose Physical > Compute. In the left pane, expand the pod and then click the Cisco UCS Manager account. In the right pane, click the Organizations tab. Click the organization in which you want to create the pool and then click View Details. Click the MAC Pools tab. Click Add. In the Add MAC Pool dialog box, complete the following fields: field field First MAC Address field Size field A unique name for the pool. A description for the pool. The first MAC address in the block. The number of MAC addresses in the block. Step 8 Click Submit. Creating a WWNN Pool Step 4 Step 5 Step 6 Step 7 On the menu bar, choose Physical > Compute. In the left pane, expand the pod and then click the Cisco UCS Manager account. In the right pane, click the Organizations tab. Click the organization in which you want to create the pool and then click View Details. Click the WWNN Pools tab. Click Add. In the Add WWNN Pool dialog box, complete the following fields: field field From field A unique name for the pool. A description for the pool. The first WWNN address in the block. 50 OL

61 Vblock Operations Creating a WWPN Pool Size field The number of WWNN addresses in the block. Step 8 Click Submit. Creating a WWPN Pool Step 4 Step 5 Step 6 Step 7 On the menu bar, choose Physical > Compute. In the left pane, expand the pod and then click the Cisco UCS Manager account. In the right pane, click the Organizations tab. Click the organization in which you want to create the pool and then click View Details. Click the WWPN Pools tab. Click Add. In the Add WWPN Pool dialog box, complete the following fields: field field From field Size field A unique name for the pool. A description for the pool. The first WWPN address in the block. The number of WWPN addresses in the block. Step 8 Click Submit. Creating a Network Control Policy MAC address-based port security for Emulex Converged Network Adapters (N20-AE0102) is not supported. When MAC address-based port security is enabled, the fabric interconnect restricts traffic to packets that contain the MAC address that it first learns, which is either the source MAC address used in the Fibre Channel OL

62 Creating a Network Control Policy Vblock Operations over Ethernet (FCoE) Initialization Protocol packet or the MAC address in an Ethernet packet, whichever is sent first by the adapter. This configuration can result in either FCoE or Ethernet packets being dropped. Step 4 Step 5 Step 6 Step 7 On the menu bar, choose Physical > Compute. In the left pane, expand the pod and then click the Cisco UCS Manager account. In the right pane, click the Organizations tab. Click the organization in which you want to create the policy and then click View Details. Click the Network Control Policies tab. Click Add. In the Add Network Control Policy dialog box, complete the following fields: field CDP drop-down list A unique name for the policy. Choose whether the Cisco Discovery Protocol (CDP) is enabled on servers associated with a service profile that includes this policy. This can be one of the following: Disabled Enabled Action on Uplink Fail drop-down list Choose how the virtual interface (VIF) behaves if no uplink port is available when the fabric interconnect is in end-host mode. This can be one of the following: Link Down Changes the operational state of a vnic to down when uplink connectivity is lost on the fabric interconnect, and enables a fabric failover for vnics. Warning Maintains server-to-server connectivity even when no uplink port is available, and disables a fabric failover when uplink connectivity is lost on the fabric interconnect. The default is Link Down. Note If your implementation includes those types of non-vm-fex capable converged network adapters and the adapter is expected to handle both Ethernet and FCoE traffic, we recommend that you configure the Action on Uplink Fail property with a value of Warning. Note that this configuration might result in an Ethernet teaming driver not being able to detect a link failure when the border port goes down. 52 OL

63 Vblock Operations Creating a vnic Template Forge drop-down list Choose whether forged MAC addresses are allowed or denied when packets are sent from the server to the fabric interconnect. This can be one of the following: Allow All server packets are accepted by the fabric interconnect, regardless of the MAC address associated with the packets. Deny After the first packet has been sent to the fabric interconnect, all other packets must use the same MAC address or they will be silently rejected by the fabric interconnect. This option enables port security for the associated vnic. If you plan to install VMware ESX on the associated server, you must configure MAC Security to allow for the network control policy applied to the default vnic. If you do not configure MAC Security to Allow, the ESX installation might fail because the MAC Security permits only one MAC address while the installation process requires more than one MAC address. Step 8 Click Submit. Creating a vnic Template Before You Begin One or more of the following resources must already exist: d VLAN MAC pool QoS policy LAN pin group OL

64 Creating a vnic Template Vblock Operations Statistics threshold policy Step 4 Step 5 Step 6 Step 7 On the menu bar, choose Physical > Compute. In the left pane, expand the pod and then click the Cisco UCS Manager account. In the right pane, click the Organizations tab. Click the organization in which you want to create the policy and then click View Details. Click the vnic Templates tab. Click Add. In the Add vnic Template dialog box, complete the following fields: field field Fabric ID drop-down list A unique name for the policy. A description for the policy. Choose the fabric interconnect that vnics created with this template are associated with. If you want vnics created from this template to be able to access the second fabric interconnect if the default one is unavailable, check the Enable Failover check box. Note Do not enable vnic fabric failover under the following circumstances: If the Cisco UCS domain is running in Ethernet Switch Mode. vnic fabric failover is not supported in that mode. If all Ethernet uplinks on one fabric interconnect fail, the vnics do not fail over to the other. If you plan to associate one or more vnics created from this template with a server adapter that does not support a fabric failover, such as the Cisco UCS 82598KR-CI 10-Gigabit Ethernet Adapter. If you do so, Cisco UCS Manager generates a configuration fault when you associate the service profile with the server. 54 OL

65 Vblock Operations Creating a vnic Template Target check boxes If checked, the target that you choose determines whether a VM-FEX port profile is automatically created with the appropriate settings for the vnic template. This can be one of the following: Adapter The vnics apply to all adapters. No VM-FEX port profile is created if you choose this option. VM The vnics apply to all virtual machines. A VM-FEX port profile is created if you choose this option. Template Type drop-down list Choose the type of template. This can be one of the following: Initial Template vnics created from this template are not updated if the template changes. Updating Template vnics created from this template are updated if the template changes. Step 8 In the VLANs area, do the following to select the VLAN to be assigned to vnics created from this template: a) Click Add. b) In the Add Entry to VLANs dialog box, complete the following fields and click Submit: drop-down list Choose the VLAN that you want to associate with the vnic template. Set as Native VLAN check box Check the check box if you want this VLAN to be the native VLAN for the port. Step 9 To associate policies with vnics created from this template, complete the following fields: MTU field MAC Pool drop-down list The maximum transmission unit (MTU), or packet size, that vnics created from this vnic template should use. Enter an integer between 1500 and Note If the vnic template has an associated QoS policy, the MTU specified here must be equal to or less than the MTU specified in the associated QoS system class. If this MTU value exceeds the MTU value in the QoS system class, packets might be dropped during data transmission. Choose the MAC address pool that vnics created from this vnic template should use. OL

66 Creating a vnic Template Vblock Operations QoS Policy drop-down list Network Control Policy drop-down list Pin Group drop-down list Stats Threshold Policy drop-down list VNIC Template Connection Policy drop-down list usnic Template Connection Policy drop-down list VMQ Template Connection Policy drop-down list Choose the quality of service policy that vnics created from this vnic template should use. Choose the network control policy that vnics created from this vnic template should use. Choose the LAN pin group that vnics created from this vnic template should use. Choose the statistics collection policy that vnics created from this vnic template should use. Choose the collection policy that vnics created from this template should use. It can be one of the following: Dynamic Policy usnic Policy VMQ Policy Only usnic and VM connection policies created in Cisco UCS Manager are displayed in this drop-down list. Note This field is available only with Cisco UCS Manager Release 2.2. Choose the usnic collection policy that vnics created from this vnic template should use. This field is visible only if you choose usnic Policy as the VNIC Template connection policy. Choose the VM collection policy that vnics created from this vnic template should use. This field is visible only if you choose VMQ Policy as the VNIC Template connection policy. 0 Click Submit. What to Do Next Include the vnic template in a network policy. 56 OL

67 Vblock Operations Creating a VSAN Creating a VSAN Note Fibre Channel over Ethernet (FCoE) VLANs in the SAN cloud and VLANs in the LAN cloud must have different IDs. Using the same ID for an FCoE VLAN in a VSAN and a VLAN results in a critical fault and traffic disruption for all vnics and uplink ports using that FCoE VLAN. Ethernet traffic is dropped on any VLAN that has an ID that overlaps with an FCoE VLAN ID. Step 4 Step 5 On the menu bar, choose Physical > Compute. In the left pane, expand the pod and then click the Cisco UCS Manager account. In the right pane, click the VSANs tab. Click Add. In the Add VSAN dialog box, complete the following fields: VSAN field VSAN ID field Type drop-down list A unique name for the VSAN. The unique identifier assigned to the network. Choose the type of VSAN. This can be one of the following: SAN Cloud Storage Cloud If you are creating a VSAN for Fibre Channel zoning, we recommend that you choose Storage Cloud. Fabric ID drop-down list Choose how the VSAN should be configured. This can be one of the following: Common/Global The VSAN maps to the same VSAN ID in all available fabrics. Fabric A The VSAN maps to a VSAN ID that exists only in fabric A. Fabric B The VSAN maps to a VSAN ID that exists only in fabric B. OL

68 Creating a vhba Template Vblock Operations FCoE VLAN field The unique identifier assigned to the VLAN used for Fibre Channel connections. For FCoE Initialization Protocol (FIP)-capable, converged network adapters, such as the Cisco UCS CNA M72KR-Q and the Cisco UCS CNA M72KR-E, the named VSAN must be configured with a named VLAN that is not the native VLAN for the FCoE VLAN ID. This configuration ensures that FCoE traffic can pass through these adapters. Step 6 Click Submit. What to Do Next If you plan to use this VSAN for Fibre Channel zoning, see Configuring a VSAN for Fibre Channel Zoning. Creating a vhba Template Before You Begin One or more of the following resources must already exist: VSAN WWPN pool SAN pin group Statistics threshold policy Step 4 Step 5 Step 6 Step 7 On the menu bar, choose Physical > Compute. In the left pane, expand the pod and then click the Cisco UCS Manager account. In the right pane, click the Organizations tab. Click the organization in which you want to create the policy and then click View Details. Click the vhba Templates tab. Click Add. In the Add vhba Template dialog box, complete the following fields: field field A unique name for the policy. A description for the policy. 58 OL

69 Vblock Operations Creating a vhba Template Fabric ID drop-down list VSAN drop-down list Template Type drop-down list Choose the fabric interconnect that vhbas created with this template are associated with. Choose the VSAN that you want to associate with vhbas created from this template. Choose the type of template that you want to use. This can be one of the following: Initial Template vhbas created from this template are not updated if the template changes. Updating Template vhbas created from this template are updated if the template changes. Max Data Field Size field WWPN Pool drop-down list QoS Policy drop-down list Pin Group drop-down list Stats Threshold Policy drop-down list The maximum size of the Fibre Channel frame payload bytes that the vhba supports. Enter an integer between 256 and The default is Choose the WWPN pool that a vhba created from this template uses to derive its WWPN address. Choose the QoS policy that is associated with vhbas created from this template. Choose the SAN pin group that is associated with vhbas created from this template. Choose the statistics threshold policy that is associated with vhbas created from this template. Step 8 Click Submit. What to Do Next Include the vhba template in a storage policy. OL

70 Creating a LAN Boot Policy Vblock Operations Creating a LAN Boot Policy You can add more than one type of boot device to a boot policy. For example, you could add a local disk boot as a secondary boot device. Step 4 Step 5 Step 6 Step 7 On the menu bar, choose Physical > Compute. In the left pane, expand the pod and then click the Cisco UCS Manager account. In the right pane, click the Organizations tab. Click the organization in which you want to create the policy and then click View Details. Click the Boot Policies tab. Click Add. In the Add Boot Policy dialog box, complete the following fields: field field Reboot on Order Change check box Enforce vnic/vhba check box Boot Mode drop-down list A unique name for the policy. A description for the policy. If checked, reboots all servers that use this boot policy after you make changes to the boot order. If this check box is checked and if CD-ROM or Floppy is the last device in the boot order, deleting or adding the device does not directly affect the boot order and the server does not reboot. If checked, a configuration error is displayed if one or more of the vnics, vhbas, or iscsi vnics listed in the Boot Order table matches the server configuration in the service profile. If this check box is not checked, the policy uses the vnics, vhbas, or iscsi vnics (as appropriate for the boot option) from the server configuration in the service profile. It does not report whether the vnics, vhbas, or iscsi vnics specified in the boot policy match the server configuration in the service profile. The boot mode for the servers that use this boot policy. It can be one of the following: Legacy UEFI With this option, you can specify second-level boot devices and you can enable the secure boot option. 60 OL

71 Vblock Operations Creating a SAN Boot Policy Boot Security check box Enables the secure boot option for the servers that use this boot policy. This option is visible only when UEFI is selected as the boot mode. Step 8 Step In the Add Boot Device area, check the Add LAN Boot check box. In the Primary vnic field, enter the name of the vnic that you want to use as the first address defined for the LAN boot location. In the Secondary vnic field, enter the name of the vnic that you want to use as the second address defined for the LAN boot location. In the Add Boot Device area, check the Add iscsi Boot check box. In the Add Primary iscsi Vnic field, enter the name of the iscsi VNIC that you want to use as the first address defined for the LAN boot location. In the Add Secondary iscsi Vnic field, enter the name of the iscsi VNIC that you want to use as the second address defined for the LAN boot location. Click Submit. Creating a SAN Boot Policy Tip We recommend that the boot order in a boot policy include either a local disk or a SAN LUN, but not both, to avoid the possibility of the server booting from the wrong storage type. If you configure a local disk and a SAN LUN for the boot order storage type and the operating system or logical volume manager (LVM) is configured incorrectly, the server might boot from the local disk rather than the SAN LUN. For example, on a server with Red Hat Linux installed, where the LVM is configured with default LV names and the boot order is configured with a SAN LUN and a local disk, Linux reports that there are two LVs with the same name and boots from the LV with the lowest SCSI ID, which could be the local disk. OL

72 Creating a SAN Boot Policy Vblock Operations Before You Begin If you are creating a boot policy that boots the server from a SAN LUN and you require reliable SAN boot operations, we recommend that you first remove all local disks from servers associated with a service profile that includes the boot policy. Step 4 Step 5 Step 6 Step 7 On the menu bar, choose Physical > Compute. In the left pane, expand the pod and then click the Cisco UCS Manager account. In the right pane, click the Organizations tab. Click the organization in which you want to create the policy and then click View Details. Click the Boot Policies tab. Click Add. In the Add Boot Policy dialog box, complete the following fields: field field Reboot on Order Change check box Enforce vnic/vhba check box Boot Mode drop-down list A unique name for the policy. A description for the policy. If checked, reboots all servers that use this boot policy after you make changes to the boot order. If this check box is checked and if CD-ROM or Floppy is the last device in the boot order, deleting or adding the device does not directly affect the boot order and the server does not reboot. If checked, a configuration error is displayed if one or more of the vnics, vhbas, or iscsi vnics listed in the Boot Order table matches the server configuration in the service profile. If this check box is not checked, the policy uses the vnics, vhbas, or iscsi vnics (as appropriate for the boot option) from the server configuration in the service profile. It does not report whether the vnics, vhbas, or iscsi vnics specified in the boot policy match the server configuration in the service profile. The boot mode for the servers that use this boot policy. It can be one of the following: Legacy UEFI With this option, you can specify second-level boot devices and you can enable the secure boot option. 62 OL

73 Vblock Operations Creating a SAN Boot Policy Boot Security check box Enables the secure boot option for the servers that use this boot policy. This option is visible only when UEFI is selected as the boot mode. Step 8 Step In the Add Boot Device area, check the Add SAN Boot check box. In the Primary vhba field, enter the name of the vhba that you want to use as the first address defined for the SAN boot location. In the Secondary vhba field, enter the name of the vhba that you want to use as the second address defined for the SAN boot location. (Optional) If either or both of the primary and secondary vhbas points to a bootable SAN image, check the appropriate Add SAN Boot Target check box or both check boxes and complete the following fields: Primary Boot Target LUN drop-down list Primary Boot Target WWPN field Secondary Boot Target LUN field Secondary Boot Target WWPN field The primary LUN ID number that corresponds to the location of the boot image. The primary WWPN value that corresponds to the location of the boot image. The secondary LUN ID number that corresponds to the location of the boot image. The secondary WWPN value that corresponds to the location of the boot image In the Add Boot Device area, check the Add iscsi Boot check box. In the Add Primary iscsi Vnic field, enter the name of the iscsi VNIC that you want to use as the first address defined for the SAN boot location. In the Add Secondary iscsi Vnic field, enter the name of the iscsi VNIC that you want to use as the second address defined for the SAN boot location. Click Submit. OL

74 Creating a vnic Vblock Operations Creating a vnic Step 4 On the menu bar, choosepolicies > Physical Infrastructure Policies > UCS Manager. Click the vnic tab. Click Add. In the Create vnic dialog box, complete the following fields to specify the Cisco UCS connections for the vnic: vnic field UCS Account drop-down list UCS Organization drop-down list vnic Template drop-down list Adapter Policy drop-down list The unique name for the vnic. Choose the Cisco UCS Manager account to which you want to add this vnic. Choose the Cisco UCS organization to which you want to add this vnic. Choose the vnic template that you want to assign to this vnic. Choose one of the following Ethernet adapter policies: Default Windows VMware Linux Step 5 Click Submit. What to Do Next Include this vnic in a network policy. Creating a vhba Step 4 On the menu bar, choosepolicies > Physical Infrastructure Policies > UCS Manager. Click the vhba tab. Click Add. In the Create vhba dialog box, complete the following fields to specify the Cisco UCS connections for the vhba: 64 OL

75 Vblock Operations Creating a Network Policy vhba field UCS Account drop-down list UCS Organization drop-down list vhba Template drop-down list Adapter Policy drop-down list The unique name for the vhba. Choose the Cisco UCS Manager account to which you want to add this vhba. Choose the Cisco UCS organization to which you want to add this vhba. Choose the vhba template that you want to assign to this vhba. Choose one of the following Ethernet adapter policies: Default Windows VMware Linux Step 5 Click Submit. What to Do Next Include this vhba in a storage policy. Creating a Network Policy Step 4 On the menu bar, choosepolicies > Physical Infrastructure Policies > UCS Manager. Click the Network Policy tab. Click Add. In the Add Network Policy dialog box, complete the following fields: Policy field Policy field UCS Account drop-down list UCS Organization drop-down list The name of the policy. The description of the policy. Choose the Cisco UCS Manager account to which you want to add this policy. Choose the Cisco UCS organization to which you want to add this policy. OL

76 Creating a Network Policy Vblock Operations Dynamic vnic Connection Policy drop-down list LAN Connectivity Type drop-down list Choose a dynamic vnic connection policy if the policy is being assigned to service profiles for servers that support dynamic vnics. Choose one of the following connectivity types: Expert Allows you to create an unlimited number of vnics that the server can use to access the LAN. Simple Allows you to create a maximum of two vnics that the server can use to access the LAN. No vnics Does not allow you to create any vnics. If you choose this option, any server associated with a service profile that includes this policy is not connected to the LAN. Hardware Inherited Uses the vnics assigned to the Ethernet adapter profile associated with the server. Use LAN Connectivity Policy Uses a LAN connectivity policy to determine the LAN connectivity for the server. Step 5 Step 6 If you chose the Expert LAN option, do the following: a) In the Add vnic field, specify the number of vnics that you want to add to the network policy. b) From the Template For vnic1/vnic2/vnic3/vnic4 drop-down list, choose a vnic template. c) Go to Step 8. If you chose the Simple LAN option, do the following: a) In the vnic0 (Fabric A) area, complete the following fields: In the vnic0 field, enter a unique name for the vnic. From the Select VLAN drop-down list, choose the name of the VLAN with which this vnic should be associated. b) In the vnic1 (Fabric B) area, complete the following fields: In the vnic1 field, enter a unique name for the vnic. From the Select VLAN drop-down list, choose the name of the VLAN with which this vnic should be associated. c) Go to Step 8. Step 7 Step 8 If you chose the Use LAN Connectivity Policy option, choose the policy that you want to associate with the server from the LAN Connectivity Policy drop-down list. Click Submit. 66 OL

77 Vblock Operations Creating a Storage Policy What to Do Next Include the network policy in a service profile. Creating a Storage Policy Step 4 Step 5 On the menu bar, choosepolicies > Physical Infrastructure Policies > UCS Manager. Click the Storage Policy tab. Click Add. enter a name and description for the policy. In the Add Storage Policy dialog box, complete the following fields to specify the Cisco UCS connections for the storage policy: Policy field Policy description field UCS Account drop-down list UCS Organization drop-down list Local Disk Configuration Policy drop-down list SAN Connectivity Type drop-down list The unique name for the storage policy. The description for the storage policy. Choose the Cisco UCS Manager account to which you want to add this storage policy. Choose the Cisco UCS organization to which you want to add this storage policy. Choose the local disk configuration policy that you want to include in this storage policy. Choose one of the following connectivity types: Expert Allows you to create an unlimited number of vhbas that the server can use to access SAN storage. Simple Allows you to create a maximum of two vhbas that the server can use to access SAN storage. No vhbas Does not allow you to create any vhbas. If you choose this option, any server associated with a service profile that includes this policy is not connected to SAN. Hardware Inherited Uses the vhbas assigned to the Fibre Channel adapter profile associated with the server. Use SAN Connectivity Policy Uses a SAN connectivity policy to determine the SAN connectivity for the server. Step 6 If you chose the Expert SAN storage option, do the following: OL

78 Creating a Storage Policy Vblock Operations a) From the WWNN Pool drop-down list, choose the WWNN pool that you want to assign to this policy. The WWNN pool must contain a sufficient number of WWNNs to assign a WWNN to each server that is associated with a service profile that uses this storage policy. b) In the Add vhba field, specify the number of vhbas that you want to add to the storage policy. c) From the Template For vhba1/vhba2/vhba3/vhba4 drop-down list, choose a vhba template. d) Go to Step 9. Step 7 If you chose the Simple SAN storage option, do the following: a) From the WWNN Pool drop-down list, choose the WWNN pool that you want to assign to this policy. The WWNN pool must contain a sufficient number of WWNNs to assign a WWNN to each server that is associated with the service profile that uses this storage policy. b) In the vhba0 (Fabric A) area, complete the following fields: In the vhba0 field, enter a unique name for the vhba. From the Select VSAN drop-down list, choose the name of the VSAN with which this vhba should be associated. c) In the vhba1 (Fabric B) area, complete the following fields: In the vhba1 field, enter a unique name for the vhba. From the Select VSAN drop-down list, choose the name of the VSAN with which this vhba should be associated. d) Go to Step 9. Step 8 Step 9 If you chose the Use SAN Connectivity Policy option, choose the policy that you want to associate with the server from the SAN Connectivity Policy drop-down list. Click Submit. What to Do Next Include the storage policy in a service profile. 68 OL

79 CHAPTER 6 Orchestration Workflow Operations This chapter contains the following sections: Cisco UCS Manager Orchestration Tasks, page 69 Navigating to a Predefined Orchestration Workflow, page 70 Provisioning Vblock Orchestration Workflows, page 71 Validating and Executing an Orchestration Workflow, page 98 Cisco UCS Manager Orchestration Tasks Cisco UCS Director includes orchestration features that allow you to automate configuration and management of tasks performed by Cisco UCS Manager in one or more workflows. The same workflow can include Cisco UCS Manager, network, and storage tasks. For an example of a workflow, see Example: Creating an iscsi Boot Workflow. For more information about orchestration in Cisco UCS Director, see the Cisco UCS Director Orchestration Guide. Location of Orchestration Tasks A complete list of the Cisco UCS Manager orchestration tasks is available in the Workflow Designer, in the Task Library and the Cisco UCS Tasks folder. The Task Library includes a description of the orchestration tasks, and can be accessed from the following locations in Cisco UCS Director: Policies > Orchestration > Workflows where IP_address is the IP address of Cisco UCS Director. Types of Orchestration Tasks The Cisco UCS Manager orchestration tasks include tasks to configure and manage the following: Servers Server boot OL

80 Accessing Task Documentation Orchestration Workflow Operations Pools Policies VLANs vnics Service profiles Service profile templates Organizations Accessing Task Documentation Step 4 On the menu bar, choose Policies > Orchestration. Click the Task Library icon. Check the Regenerate document checkbox to view a list of all new tasks and those by open automation. Click Submit. The orchestration task library appears. Click on an entry to reveal more information regarding specific inputs and outputs that are available. Navigating to a Predefined Orchestration Workflow You can navigate to your orchestration workflow in Cisco UCS Director. You can use several common workflows that already exist to execute common administration and provisioning tasks with the fewest mouse clicks. The procedure below describes how to access the Workflow Designer and create workflows from individual tasks. You can also execute a workflow by right-clicking on it and choosing Execute now. Note This task assumes that your orchestration workflow was created for your environment. For more information, see the Configuring Cisco UCS Server Pools and Policies chapter of the Cisco UCS Director Management Guide for Cisco UCS Manager. Step 4 On the menu bar, choose Policies > Orchestration. In the Orchestration pane, click the Workflows tab. On the left pane of the WorkFlows tab, choose the workflow folder and click the arrow next to the folder to show the workflow. Double-click the workflow. Workflow Designer appears. 70 OL

81 Orchestration Workflow Operations Provisioning Vblock Orchestration Workflows Provisioning Vblock Orchestration Workflows The following Vblock orchestration workflow examples are provided to show how a pre-defined orchestration workflow in Cisco UCS Director can be provisioned in your Vblock implementation. It is beyond the scope of this document to discuss all the orchestration workflows that are available for Vblock. Go to the Cisco Developed Integrations page for Vblock workflows, which are added on a regular basis. Provisioning a Stateless Blade Server Orchestration Workflow Overview The following table provides an overview for configuring the stateless blade server orchestration workflow. Use this table as a point of reference to determine the specific task name, task type, and the section to which it is aligned. Each task covered in subsequent sections references the task name and task type in a generic way. Once all the tasks in the workflow are validated and bound to the local environment, you must validate the entire workflow. The following table provides an overview for implementing the stateless blade server orchestration workflow. See Validating and Executing an Orchestration Workflow, on page 98 for more information. Note A blade server can be booted in a stateless environment, which is a storage area network (SAN), in order to fix a blade server failure state. An example of a stateless environment can be the World Wide Web, which does not follow settings or any other data for the next session. Task ModifyWorkflowPriority_89 CreateUCSServiceProfile_160 SelectBlades_91 AssociateUCSServiceProfile_92 UCSBladePowerOFFAction_146 PXEBoot_93 CreateLUN_247 CreateStorageGroup_117 Task Type 95. Modify Workflow Priority 114. Create UCS Service Profile 96. Select UCS Server 97. Associate UCS Service Profile 108. Power Off UCS Server 98. Setup PXE Boot 115. Create VNX LUN 101. Create VNX Storage Group Section Modifying the Workflow Priority, on page 73 Creating the UCS Service Profile Task, on page 74 Choosing the Cisco UCS Server, on page 75 Associating the Cisco UCS Service Profile, on page 76 Powering Off the Cisco UCS Server, on page 77 Setting Up PXE Boot, on page 78 Creating a VNX LUN, on page 80 Creating a VNX Storage Group, on page 81 OL

82 Provisioning a Stateless Blade Server Orchestration Workflow Overview Orchestration Workflow Operations Task AddHostInitiatorEntry_118 AddHostInitiatorEntry_119 GenericConfigureSANZoning_120 AddHoststoStorageGroup_121 AddLUNtoStorageGroup_122 ModifyUCSServiceProfileBootPolicy_250 ModifySANTargetLUNIdofBootPolicy_123 Reset Blade to kick off PXE PXEBootWait_95 ModifyUCSServiceProfileBootPolicy_96 AddVLANtoServiceProfile_303 DisassociateUCSServiceProfile_158 WaitforDuration_159 AssociateUCSServiceProfile_160 Task Type 102. Add VNX Host Initiator Entry 103. Add VNX Host Initiator Entry 104. Generic Configure SAN Zoning 105. Add Hosts to VNX Storage Group 106. Add VNX LUN to Storage Group 116. Modify UCS Service Profile Boot Policy 107. Modify UCS Boot Policy LUN ID 109. Reset UCS Server 99. Monitor PXE Boot 100. Modify UCS Service Profile Boot Policy 117. Add VLAN to Service Profile 110. Disassociate UCS Service Profile 111. Wait for Specified Duration 112. Associate UCS Service Profile Section Adding a VNX Host Initiator Entry, on page 82 Adding a VNX Host Initiator Entry, on page 82 Configuring Generic Storage Area Network Zoning, on page 83 Adding Hosts to a VNX Storage Group, on page 85 Adding a LUN to a VNX Storage Group, on page 86 Modifying the Cisco UCS Service Profile Boot Policy, on page 87 Modifying the Cisco UCS Boot Policy LUN ID, on page 88 Resetting the Cisco Cisco UCS Server Monitoring PXE Boot, on page 90 Modifying the Cisco UCS Service Profile Boot Policy, on page 87 Adding a VLAN to a Service Profile, on page 91 Disassociating the Cisco UCS Service Profile, on page 92 Configuring the Waiting for Specific Duration Task, on page 93 Associating the Cisco UCS Service Profile, on page OL

83 Orchestration Workflow Operations Provisioning a Stateless Blade Server Orchestration Workflow Overview Task WaitforDuration_161 UCSBladeResetAction_317 Task Type 113. Wait for Specified Duration 118. Reset UCS Server Section Configuring the Waiting for Specific Duration Task, on page 93 Resetting the Cisco Cisco UCS Server Modifying the Workflow Priority See the orchestration workflow overview for the specific task name and task type. Under the blue workflow Start icon, find and double-click the Modify Workflow Priority task. The Edit Task dialog box appears with the Task Information pane. The following parameters are preconfigured: Task field Task Category drop-down list Task Type drop-down list Comment field The modify workflow priority task name is entered. The General Tasks option is chosen. The Modify Workflow Priority task type is chosen. Comments that pertain to this task. Click Next to advance to the User Input Mapping pane. Click Next to again to advance to the Task Inputs pane. The following parameters are configurable: Priority drop-down list Revalidate button Submit button Choose High. The priority is saved. Binds all the necessary parameters identified in this task to the environment. Saves the workflow task changes in the database. A confirmation dialog box appears. OL

84 Provisioning a Stateless Blade Server Orchestration Workflow Overview Orchestration Workflow Operations Creating the UCS Service Profile Task See the orchestration workflow overview for the specific task name and task type. Under the blue workflow Start icon, find and double-click the Create UCS Service Profile task. The Edit Task dialog box appears with the Task Information pane. The following parameters are preconfigured: Task The create UCS service profile task name is entered. Task Category drop-down list Task Type drop-down list Comment field Task Details display field The Cisco UCS Tasks category is chosen. The Create UCS Service Profile task type is chosen. Comments that pertain to this task. The output generated by this task. Click Next to advance to the User Input Mapping pane. The following parameter is configurable: Note Check the Map to User Input check box next to the following attribute to map it to the workflow when the workflow executes. Service Profile drop-down list Choose the Service Profile attribute. Click Next to advance to the Task Inputs pane. Note This workflow assumes that the following actions have been accomplished through Cisco UCS Director: All pod required elements are discovered and managed. All required pools and resources for a service profile are created. All required policies are defined and bound to their respective pools and resources. The following parameters are configurable: Note Any parameter that is not included in the following table is either not set or uses the default setting. field Organization button UUID Assignment drop-down list Comments that pertain to this task. The pre-sales option is chosen. Choose pe_uuid_pool. 74 OL

85 Orchestration Workflow Operations Provisioning a Stateless Blade Server Orchestration Workflow Overview Storage Policy drop-down list Network Policy drop-down list PXE Boot Policy drop-down list Server Boot Policy drop-down list Revalidate button Submit button Choose ps-storage-policy. Choose ps-network-policy. Choose ps-lan-boot. Choose ps-san-policy. Binds all the necessary parameters identified in this task to the environment. Saves the workflow task changes in the database. A confirmation dialog box appears. Choosing the Cisco UCS Server See the orchestration workflow overview for the specific task name and task type. Under the blue workflow Start icon, find and double-click the Select UCS Server task. The Edit Task dialog box appears with the Task Information pane. The following parameters are preconfigured: Task Task Category drop-down list Task Type drop-down list Comment field Task Details display field The select blades task name is entered. The UCS Tasks category is chosen. The Select UCS Server task type is chosen. Comments that pertain to this task. The output generated by this task. Click Next to advance to the User Input Mapping pane. No parameters are configured for this pane. Click Next to advance to the Task Inputs pane. The following parameters are configurable: Account drop-down list Choose the account name. For example, vblock-300-ucs. OL

86 Provisioning a Stateless Blade Server Orchestration Workflow Overview Orchestration Workflow Operations Server Selection Scope drop-down list Servers field Select button Use Unassociated Servers Only check box Number of CPUs field Total Memory (GB) field Revalidate button Submit button Choose Include Servers. Click the Select button to select a Cisco UCS server. For example, *sys/chassis-1/blade-3. Note The asterisk (*) at the beginning of the path indicates this server is associated to your environment. Check the check box for your environment's requirements. The number of CPUs in your environment. The total memory in gigabytes (GB). Binds all the necessary parameters identified in this task to the environment. Saves the workflow task changes in the database. A confirmation dialog box appears. Associating the Cisco UCS Service Profile See the orchestration workflow overview for the specific task name and task type. Under the blue workflow Start icon, find and double-click the Associate UCS Service Profile task. The Edit Task dialog box displays with the Task Information pane. The following parameters are preconfigured: Task field The associate UCS service profile task name is entered. Task Category drop-down list Task Type drop-down list Comment field Task Details display field The Cisco UCS Tasks category is chosen. The Associate UCS Service Profile task type is chosen. Comments that pertain to this task. The output generated by this task. 76 OL

87 Orchestration Workflow Operations Provisioning a Stateless Blade Server Orchestration Workflow Overview Click Next to advance to the User Input Mapping pane. The following parameters are configurable: Service Profile drop-down list Choose the create UCS service profile task service profile identity. Server drop-down list Choose the select blades task server identity. Click Next to advance to the Task Input pane. The following parameters are configurable: Server Selection Scope drop-down list Choose the Include Servers option. Revalidate button Submit button Binds all the necessary parameters identified in this task to the environment. Saves the workflow task changes in the database. A confirmation dialog box appears. Powering Off the Cisco UCS Server See the orchestration workflow overview for the specific task name and task type. Under the blue workflow Start icon, find and double-click the Power Off UCS Server task. The Edit Task dialog box appears with the Task Information pane. The following parameters are preconfigured: Task field The Cisco UCS blade power off action task name is entered. Task Category drop-down list Task Type drop-down list Comment field Task Details display field The Cisco UCS Tasks category is chosen. The Power Off UCS Server task type is chosen. Comments that pertain to this task. The output generated by this task. OL

88 Provisioning a Stateless Blade Server Orchestration Workflow Overview Orchestration Workflow Operations Click Next to advance to the User Input Mapping pane. The following parameter is configurable: Note Check the Map to User Input check box next to the following attribute to map it to the workflow when the workflow executes. Server drop-down list Choose the server identity attribute. For example, SelectBlades_91_SERVER_IDENTITY. Click Next to advance to the Task Input pane. The following parameters are configurable: Revalidate button Binds all the necessary parameters identified in this task to the environment. Submit button Saves the workflow task changes in the database. A confirmation dialog box appears. Setting Up PXE Boot See the orchestration workflow overview for the specific task name and task type. Under the blue workflow Start icon, find and double-click the Setup PXE Boot task. The Edit Task dialog box appears with the Task Information pane. The following parameters are preconfigured: Task field The PXE Boot task name is entered. Task Category drop-down list Task Type drop-down list Comment field Task Details display field The Network Services Tasks category is chosen. The Setup PXE Boot task type is chosen. Comments that pertain to this task. The output generated by this task. Click Next to advance to the User Input Mapping pane. The following parameters are configurable: 78 OL

89 Orchestration Workflow Operations Provisioning a Stateless Blade Server Orchestration Workflow Overview Note Check the Map to User Input check box next to each of the following attributes to map them to the workflow when the workflow executes. Server MAC Address drop-down list Choose the UCS service profile name to the output UCS blade MAC address attribute. For example, Associate UCSServiceProfile_92.OUTPUT_UCS_BLADE_MAC_ADDRESS. Server Host drop-down list Choose the hostname (machine name) attribute. For example, Host. Click Next to advance to the Task Input pane. The following parameters are configurable: OS Type drop-down list Choose the network device OS type. For example, ESXi5.0-u1 (with Nexus 1000v VEM). Server IP Address field Server Net Mask field Server Gateway field Server Server field Management VLAN field Root Password field Timezone drop-down list Revalidate button Submit button The server IP address range. The server subnetwork (subnet) mask. The server gateway IP address. The server name server IP address. The management VLAN number. The root password. Choose the time zone for your environment. Binds all the necessary parameters identified in this task to the environment. Saves the workflow task changes in the database. A confirmation dialog box appears. OL

90 Provisioning a Stateless Blade Server Orchestration Workflow Overview Orchestration Workflow Operations Creating a VNX LUN See the orchestration workflow overview for the specific task name and task type. Under the blue workflow Start icon, find and double-click the Create VNX LUN task. The Edit Task dialog box appears with the Task Information pane. The following parameters are preconfigured: Task field Task Category drop-down list Task Type drop-down list Comment field Task Details display field The task name for creating a logical unit number (LUN) is entered. For example, CreateLUN_247. The EMC VNX Tasks category is chosen. The Create VNX LUN task type is chosen. Comments that pertain to this task. The output generated by this task. Click Next to advance to the User Input Mapping pane. No parameters are configured for this pane. Click Next to advance to the Task Inputs pane. The following parameters are configurable: Select EMC Account Select... button LUN field Let System Specify LUN ID checkbox Storage Pool Type drop-down list User Capacity field Capacity Units drop-down list Default Owner drop-down list Initial Tier Placement drop-down list Revalidate button Choose the EMC account name (if required). The name of the LUN. For example, VB_LUN_Boot_ESXi_$(SR_ID). Check the check box to allow the system to specify the LUN ID. Choose Pool for the type of storage pool. The LUN capacity created by user. Choose the size of the LUN that is requested by user. Choose Auto to allow the system to automatically assign the default owner of the LUN. Choose Optimize for Pool Performance. Binds all the necessary parameters identified in this task to the environment. 80 OL

91 Orchestration Workflow Operations Provisioning a Stateless Blade Server Orchestration Workflow Overview Submit button Saves the workflow task changes in the database. A confirmation dialog box appears. Creating a VNX Storage Group See the orchestration workflow overview for the specific task name and task type. Under the blue workflow Start icon, find and double-click the Create VNX Storage Group task. The Edit Task dialog box appears with the Task Information pane. The following parameters are preconfigured: Task Task Category drop-down list Task Type drop-down list Comment field Task Details display field The create storage group task name is entered. The EMC VNX Tasks category is chosen. The Create VNX Storage Group task type is chosen. Comments that pertain to this task. The output generated by this task. Click Next to advance to the User Input Mapping pane. No parameters are configured for this pane. Click Next to advance to the Task Inputs pane. The following parameters are configurable: Select EMC Account Select... button Storage Group field Submit button Choose the EMC account name (if required). The storage group name. For example, VB_SG_ESXi_${SR_ID}. Saves the workflow task changes in the database. A confirmation dialog box appears. OL

92 Provisioning a Stateless Blade Server Orchestration Workflow Overview Orchestration Workflow Operations Adding a VNX Host Initiator Entry See the orchestration workflow overview for the specific task name and task type. Under the blue workflow Start icon, find and double-click the Add VNX Host Initiator Entry task. The Edit Task dialog box appears with the Task Information pane. The following parameters are preconfigured: Task The VNX host initiator task name is entered. Task Category drop-down list Task Type drop-down list Comment field Task Details display field The EMC VNX Tasks category is chosen. The Add VNX Host Initiator Entry task type is chosen. Comments that pertain to this task. The output generated by this task. Click Next to advance to the User Input Mapping pane. The following parameters are configurable: Note Check the Map to User Input check box next to each of the following attributes to map them to the workflow when the workflow executes. Host drop-down list Choose the host name attribute. For example, Host. IP Address drop-down list WWN/IQN drop-down list Choose the IP address attribute. For example, PXEBoot_93.OUTPUT_HOST_IP_ADDRESS. Choose the WWN/IQN attribute. For example, CreateUCSServiceProfile_160.OUTPUT_SP_VHBA1_WWN. Click Next to advance to the Task Inputs pane. The following parameters are configurable: Select EMC Account Select... button Choose the EMC account name (if required). For example, vblock-300. Add Initiator to drop-down list SP Port Select... button Initiator Type drop-down list Choose New Host. Choose the SP Port. For example, A-2, A-0. Choose CLARiiON Open. 82 OL

93 Orchestration Workflow Operations Provisioning a Stateless Blade Server Orchestration Workflow Overview Failover Mode drop-down list Revalidate button Submit button Choose Active-Active mode(alua)-failovermode4. Binds all the necessary parameters identified in this task to the environment. Saves the workflow task changes in the database. A confirmation dialog box appears. Configuring Generic Storage Area Network Zoning See the orchestration workflow overview for the specific task name and task type. Under the blue workflow Start icon, find and double-click the Generic Configure SAN Zoning task. The Edit Task dialog box appears with the Task Information pane. The following parameters are preconfigured: Task The generic configure SAN zoning task name is entered. Task Category drop-down list Task Type drop-down list Comment field Task Details display field The Cisco Network Tasks category is chosen. The Generic Configure SAN Zoning task type is chosen. Comments that pertain to this task. The output generated by this task. Click Next to advance to the User Input Mapping pane. The following parameters are configurable: Note Check the Map to User Input check box next to each of the following attributes to map them to the workflow when the workflow executes. Service Profile drop-down list Choose the service profile attribute. For example, UCSBladePowerOFFAction_146.SERVICE_PROFILE_IDENTITY. Select vhba drop-down list Choose the vhba attribute. For example, CreateUCSServiceProfile_160.SP_VHBA1. OL

94 Provisioning a Stateless Blade Server Orchestration Workflow Overview Orchestration Workflow Operations Select VSAN drop-down list Choose the VSAN attribute. For example, CreateUCSServiceProfile_160.SP_VSAN1. Click Next to advance to the Task Inputs pane. The following parameters are configurable for Fabric A: Configure One to One zones check box Check the check box. Storage Account Type drop-down list Storage Account (Primary) drop-down list Storage FC Adapter (Primary) field Select... button Select Device drop-down list Configure Fabric B check box Choose the storage account type. For example, EMC VNX. Choose the storage account name. For example, vbloc-300. Choose the storage FC adapter(s). For example, A-0(FIBRE_CHANNEL), A-2(FIBRE_CHANNEL). Choose the network device. For example, SJ-02-VBLOCK-300-N5K-A vblock-300. Check the check box to initiate the ability to configure Fabric B. The following parameters are configured for Fabric B: Storage Account Type drop-down list Choose the same storage account type that was chosen for Fabric A. Storage Account (Primary) drop-down list Storage FC Adapter (Primary) field Select... button Choose the same storage account name that was chosen for Fabric A. vbloc-300. Choose the storage FC adapter(s). For example: B-1(FIBRE_CHANNEL), B-3(FIBRE_CHANNEL). Step 4 Configure the remaining parameters in the Task Inputs pane. Revalidate button Binds all the necessary parameters identified in this task to the environment. 84 OL

95 Orchestration Workflow Operations Provisioning a Stateless Blade Server Orchestration Workflow Overview Submit button Saves the workflow task changes in the database. A confirmation dialog box appears. Adding Hosts to a VNX Storage Group See the orchestration workflow overview for the specific task name and task type. Under the blue workflow Start icon, find and double-click the Add Hosts to VNX Storage Group task. The Edit Task dialog box appears with the Task Information pane. The following parameters are preconfigured: Task field Task Category drop-down list Task Type drop-down list Comment field Task Details display field The add host to storage group task name is entered. The EMC VNX Tasks category is chosen. The Add Hosts to VNX Storage Group task type is chosen. Comments that pertain to this task. The output generated by this task. Click Next to advance to the User Input Mapping pane. The following parameters are configurable: Note Check the Map to User Input check box next to the attribute to map it to the workflow when the workflow executes. Hosts drop-down list Choose the name of the host attribute. For example, AddHostInitiatorEntry_118.OUTPUT_HOST_IDENTITY. Storage Group drop-down list Choose the name of the storage group attribute. For example, CreateStorageGroup_117.OUTPUT_STORAGE_GROUP_IDENTITY. Click Next to advance to the Task Inputs pane. The following parameters are configurable: OL

96 Provisioning a Stateless Blade Server Orchestration Workflow Overview Orchestration Workflow Operations Revalidate button Submit button Binds all the necessary parameters identified in this task to the environment. Saves the workflow task changes in the database. A confirmation dialog box appears. Adding a LUN to a VNX Storage Group See the orchestration workflow overview for the specific task name and task type. Under the blue workflow Start icon, find and double-click the Add VNX LUN to Storage Group task. The Edit Task dialog box appears with the Task Information pane. The following parameters are preconfigured: Task field Task Category drop-down list Task Type drop-down list Comment field Task Details display field The add VNX LUN to storage group task name is entered. The EMC VNX Tasks category is chosen. The Add VNX LUN to Storage Group task type is chosen. Comments that pertain to this task. The output generated by this task. Click Next to advance to the User Input Mapping pane. The following parameters are configurable: Note Check the Map to User Input check box next to the attribute to map it to the workflow when the workflow executes. LUNs to Add drop-down list Choose the name of the LUN attribute. For example, CreateLUN_247.OUTPUT_LUN_IDENTITY. Storage Group drop-down list Host LUN ID drop-down list Choose the name of the storage group attribute. For example, AddHoststoStorageGroup_121.OUTPUT_STORAGE_GROUP_IDENTITY. Choose the name of the host LUN ID attribute. For example, Host LUN Id. 86 OL

97 Orchestration Workflow Operations Provisioning a Stateless Blade Server Orchestration Workflow Overview Click Next to advance to the Task Inputs pane. The following parameters are configurable: Revalidate button Submit button Binds all the necessary parameters identified in this task to the environment. Saves the workflow task changes in the database. A confirmation dialog box appears. Modifying the Cisco UCS Service Profile Boot Policy See the orchestration workflow overview for the specific task name and task type. Under the blue workflow Start icon, find and double-click the Modify UCS Service Profile Boot Policy task. The Edit Task dialog box appears with the Task Information pane. The following parameters are preconfigured: Task field The modify UCS service profile boot policy task name is entered. Task Category drop-down list Task Type drop-down list Comment field Task Details display field The Cisco UCS Tasks category is chosen. The Modify UCS Service Profile Boot Policy task type is chosen. Comments that pertain to this task. The output generated by this task. Click Next to advance to the User Input Mapping pane. The following parameters are configurable: Note Check the Map to User Input check box next to each of the following attributes to map them to the workflow when the workflow executes. Service Profile drop-down list Choose the service profile attribute. For example, CreateUCSServiceProfile_2034.SERVICE_PROFILE_IDENTITY. Account drop-down list Choose the storage account name attribute (this drop-down list is available if a storage account name was configured). For example, CreateUCSServiceProfile_2034.ACCOUNT_NAME. OL

98 Provisioning a Stateless Blade Server Orchestration Workflow Overview Orchestration Workflow Operations Boot Policy drop-down list Choose the boot policy attribute for the blade. For example, CreateUCSServiceProfile_2034.BLADE_BOOT_POLICY. Click Next to advance to the Task Inputs pane. The following parameters are configurable: Revalidate button Binds all the necessary parameters identified in this task to the environment. Submit button Saves the workflow task changes in the database. A confirmation dialog box appears. Modifying the Cisco UCS Boot Policy LUN ID See the orchestration workflow overview for the specific task name and task type. Under the blue workflow Start icon, find and double-click the Update Boot Policy with LUN task. The Edit Task dialog box appears with the Task Information pane. The following parameters are preconfigured: Task The update boot policy with LUN task name is entered. Task Category drop-down list Task Type drop-down list The Cisco UCS Tasks category is chosen. The Modify UCS Boot Policy LUN ID task type is chosen. Click Next to advance to the User Input Mapping pane. The following parameters are configurable: Note Check the Map to User Input check box next to each of the following attributes to map them to the workflow when the workflow executes. Service Profile drop-down list Choose the service profile attribute. For example, CreateUCSServiceProfile_2034.SERVICE_PROFILE_IDENTITY. 88 OL

99 Orchestration Workflow Operations Provisioning a Stateless Blade Server Orchestration Workflow Overview PXE Boot Policy drop-down list Server Boot Policy drop-down list Lun ID drop-down list Choose the PXE blade boot policy attribute. For example, CreateUCSServiceProfile_2034.PXE_BOOT_POLICY. Choose the server boot policy attribute. For example, CreateUCSServiceProfile_2034.BLADE_BOOT_POLICY. Choose the LUN ID attribute. For example, ProvisionLUN.LUN_ID. Click Next to advance to the Task Inputs pane. The following parameters are configurable: Revalidate button Binds all the necessary parameters identified in this task to the environment. Submit button Saves the workflow task changes in the database. A confirmation dialog box appears. Resetting the UCS Server Under the blue workflow Start icon, find and double-click the Reset UCS Server task. The Edit Task dialog box appears with the Task Information panel. The following parameters are preconfigured: Task The reset UCS Server task name is entered. Task Category drop-down list Task Type drop-down list Comment field Task Details display field The Cisco UCS Tasks category is chosen. The Reset UCS Server option is chosen. Comments pertaining to this task. The log output for this task. Click Next to advance to the User Input Mapping panel. The following parameters are configured: OL

100 Provisioning a Stateless Blade Server Orchestration Workflow Overview Orchestration Workflow Operations Note Check the Map to User Input check box next to the following attribute to map it to the workflow when the workflow executes. Server drop-down list Choose the server attribute. For example: SelectBlades_91.SERVER_IDENTITY Click Next to advance to the Task Inputs panel. The following parameters are configured: Revalidate button Binds all the necessary parameters identified in this task to the environment. Submit button Saves the workflow task changes in the database. A confirmation dialog box appears. Monitoring PXE Boot See the orchestration workflow overview for the specific task name and task type. Under the blue workflow Start icon, find and double-click the Monitor PXE Boot task. The Edit Task dialog box appears with the Task Information pane. The following parameters are preconfigured: Task field The monitor PXE boot task name is entered. Task Category drop-down list Task Type drop-down list Comment field Task Details display field The Network Services Tasks category is chosen. The Monitor PXE Boot task type is chosen. Comments that pertain to this task. The output generated by this task. Click Next to advance to the User Input Mapping pane. The following parameter is configurable: Note Check the Map to User Input check box next to the following attribute to map it to the workflow when the workflow executes. 90 OL

101 Orchestration Workflow Operations Provisioning a Stateless Blade Server Orchestration Workflow Overview PXE Request ID drop-down list Choose the PXE request ID attribute. For example, PXEBoot_93.OUTPUT_PXE_BOOT_ID. Click Next to advance to the Task Input pane. The following parameters are configurable: Max Wait Time (Hours) field The maximum wait time in hours for the monitor PXE boot task. Revalidate button Submit button Binds all the necessary parameters identified in this task to the environment. Saves the workflow task changes in the database. A confirmation dialog box appears. Adding a VLAN to a Service Profile See the orchestration workflow overview for the specific task name and task type. Under the blue workflow Start icon, find and double-click the Add VLAN to Service Profile task. The Edit Task dialog box appears with the Task Information pane. The following parameters are preconfigured: Task field The add VLAN to service profile task name is entered. Task Category drop-down list Task Type drop-down list Comment field Task Details display field The Cisco UCS Tasks category is chosen. The Add VLAN to Service Profile task type is chosen. Comments that pertain to this task. The output generated by this task. Click Next to advance to the User Input Mapping pane. The following parameters are configurable: Note Check the Map to User Input check box next to each of the following attributes to map them to the workflow when the workflow executes. OL

102 Provisioning a Stateless Blade Server Orchestration Workflow Overview Orchestration Workflow Operations Account drop-down list Service Profile drop-down list Choose an account name attribute (if required). Choose the service profile identity. Click Next to advance to the Task Input pane. The following parameters are configurable: Account drop-down list Choose the UCS Manager account name (if required). VLAN Type drop-down list Common/Global VLANs drop-down list Revalidate button Submit button Choose the Common/Global option. Choose the Native-VLAN option. Binds all the necessary parameters identified in this task to the environment. Saves the workflow task changes in the database. A confirmation dialog box appears. Disassociating the Cisco UCS Service Profile See the orchestration workflow overview for the specific task name and task type. Under the blue workflow Start icon, find and double-click the Disassociate UCS Service Profile task. The Edit Task dialog box displays with the Task Information pane. The following parameters are preconfigured: Task field The disassociate service profile task name is entered. Task Category drop-down list Task Type drop-down list Comment field Task Details display field The Cisco UCS Tasks category is chosen. The Disassociate UCS Service Profile task type is chosen. Comments that pertain to this task. The output generated by this task. 92 OL

103 Orchestration Workflow Operations Provisioning a Stateless Blade Server Orchestration Workflow Overview Click Next to advance to the User Input Mapping pane. The following parameter is configurable: Note Check the Map to User Input check box next to the following attribute to map it to the workflow when the workflow executes. Service Profile drop-down list Choose the create UCS service profile algorithm. Click Next to advance to the Task Input pane. The following parameters are configurable: Revalidate button Binds all the necessary parameters identified in this task to the environment. Submit button Saves the workflow task changes in the database. A confirmation dialog box appears. Configuring the Waiting for Specific Duration Task See the orchestration workflow overview for the specific task name and task type. Under the blue workflow Start icon, find and double-click the Wait for Specific Duration task. The Edit Task dialog box displays with the Task Information pane. The following parameters are preconfigured: Task field The wait for specific duration task name is entered. Task Category drop-down list Task Type drop-down list Comment field Task Details display field The General Tasks category is chosen. The Wait for Specified Duration task type is chosen. Comments that pertain to this task. The output generated by this task. OL

104 Provisioning a File System Mounting Orchestration Workflow Orchestration Workflow Operations Click Next to advance to the User Input Mapping pane. No parameters are configured for this pane. Click Next to advance to the Task Input pane. The following parameters are configurable: Duration drop-down list Revalidate button Submit button The wait time in seconds. Binds all the necessary parameters identified in this task to the environment. Saves the workflow task changes in the database. A confirmation dialog box appears. Provisioning a File System Mounting Orchestration Workflow Cisco UCS Director handles the VSPEX file system mounting orchestration workflow by creating a file system and mounting the file system as a Network File System (NFS) datastore. File System Mounting Orchestration Workflow Overview The following table provides an overview for implementing the file system mounting orchestration workflow. Note Use this table as a point of reference to determine the specific task name, task type, and the section to which it is aligned. Each task covered in subsequent sections references the task name and task type in a generic way. Once all the tasks in the workflow are validated and bound to the local environment, you must validate the entire workflow. See Validating and Executing an Orchestration Workflow, on page 98 for more information. Task CreateEMCVNXFileSystem_247 AddNFSExport_248 SelectBlades_91 Task Type 253. Create VNX File System 254. Add VNX NFS Export 255. Mount NFS Datastore Section Creating a VNX File System, on page 95 Adding a VNX NFS Export Task, on page 96 Mounting the NFS Datastore, on page OL

105 Orchestration Workflow Operations Provisioning a File System Mounting Orchestration Workflow Creating a VNX File System See the orchestration workflow overview for the specific task name and task type. Under the blue workflow Start icon, find and double-click the Create VNX File System task. The Edit Task dialog box appears with the Task Information pane. The following parameters are preconfigured: Task Task Category drop-down list Task Type drop-down list Comment field Task Details display field The create EMC VNX file system task name is entered. The EMC VNX Tasks category is chosen. The Create VNX File System task type is chosen. Comments that pertain to this task. The output generated by this task. Click Next to advance to the User Input Mapping pane. No parameters are required to be configured for this step. Click Next to advance to the Task Inputs pane. The following parameters are configurable: Select EMC Account Select... button field Create from drop-down list Storage Pool drop-down list Storage Capacity field Capacity Units drop-down list Data Mover drop-down list Revalidate button Submit button The EMC account name (if required). The VNX file system name. Choose Storage Pool. Choose a storage pool. For example, Pool 3( GB). The storage capacity of the file system to be created. Choose the capacity unit. For example, GB (gigabytes). Choose the data mover (server) on which to mount the file system. Binds all the necessary parameters identified in this task to the environment. Saves the workflow task changes in the database. A confirmation dialog box appears. OL

106 Provisioning a File System Mounting Orchestration Workflow Orchestration Workflow Operations Adding a VNX NFS Export Task See the orchestration workflow overview for the specific task name and task type. Under the blue workflow Start icon, find and double-click the Add VNX NFS Export task. The Edit Task dialog box appears with the Task Information pane. The following parameters are preconfigured: Task The add NFS export task name is entered. Task Category drop-down list Task Type drop-down list Comment field Task Details display field The EMC VNX Tasks category is chosen. The Add VNX NFS Export task type is chosen. Comments that pertain to this task. The output generated by this task. Click Next to advance to the User Input Mapping pane. The following parameter is configurable: Note Check the Map to User Input check box next to the following attribute to map it to the workflow when the workflow executes. File Systems drop-down list Choose the output file system mount path parameter. For example, CreateEMCVNXFileSystem_247.OUTPUT_FILE_SYSTEM_MOUNT_PATH. Click Next to advance to the Task Inputs pane. The following parameters are configurable: Data Mover Select... button The data mover from which the file system is exported. File Systems drop-down list Read only Hosts field Read/Write Hosts field Root Hosts field Access Hosts field Choose the file system. The hostnames or IP addresses that get read-only access. The hostnames or IP addresses that get read-write access. The hostnames or IP addresses that get root access. The hostnames or IP addresses that get mount access. 96 OL

107 Orchestration Workflow Operations Provisioning a File System Mounting Orchestration Workflow Hosts Access Read-only Export check box Revalidate button Submit button Check the check box to allow read-only access only to hostnames or IP addresses that get mount access. Binds all the necessary parameters identified in this task to the environment. Saves the workflow task changes in the database. A confirmation dialog box appears. Mounting the NFS Datastore See the orchestration workflow overview for the specific task name and task type. Under the blue workflow Start icon, find and double-click the Mount NFS Datastore task. The Edit Task dialog box appears with the Task Information pane. The following parameters are preconfigured: Task The mount NFS Datastore task name is entered. Task Category drop-down list Task Type drop-down list Comment field Task Details display field The VMware Host Tasks category is chosen. The Mount NFS Datastore task type is chosen. Comments that pertain to this task. The output generated by this task. Click Next to advance to the User Input Mapping pane. The following parameter is configurable: Note Check the Map to User Input check box next to the following attribute to map it to the workflow when the workflow executes. File Systems drop-down list Choose the NFS export path parameter. For example, AddNFSExport_248.OUTPUT_NFS_EXPORT_PATH. Click Next to advance to the Task Inputs pane. The following parameters are configurable: OL

108 Validating and Executing an Orchestration Workflow Orchestration Workflow Operations Storage IP Address field Host Select... button Datastore field Access Mode drop-down list Success Criteria drop-down list Revalidate button Submit button The IP address of the interface which was configured for NFS data. The VMWare hostname. The name of the NFS VNX datastore. For example, VNXDataStore. Choose Read/Write. Choose Mount successful at least on one Host. Binds all the necessary parameters identified in this task to the environment. Saves the workflow task changes in the database. A confirmation dialog box appears. Validating and Executing an Orchestration Workflow After you validate all the tasks in a workflow and bind them to the local environment, you must validate the entire workflow. At the top right corner of Workflow Designer, click the Validate button. Workflow Designer confirms if the workflow is valid with a "Completed (Sucess)" message. Click Execute Now to activate the orchestration workflow. 98 OL

109 CHAPTER 7 Troubleshooting This chapter contains the following sections: Troubleshooting Cisco UCS Director Connectivity, page 99 Troubleshooting Cisco UCS Director Baremetal Agent Connectivity, page 100 Troubleshooting Cisco UCS Director Connectivity Ensure Cisco UCS Director services are active. Check Do the following: Cisco UCS Director Virtual Machine Ensure that there is sufficient resource reservation. For more information, see (VM) the System Requirements section. Cisco UCS Director appliance Access the appliance using Secure Shell (SSH) and the shelladmin user. Ensure that all the services are running (including the database). If services are not running, restart the services and wait a few minutes before accessing Cisco UCS Director through the web interface. Ensure that the IP address of Cisco UCS Director can be pinged over the network. Check Do the following: Cisco UCS Director network configuration Log into vcenter and check the network configuration of the Cisco UCS Director virtual appliance and its connectivity. Port group and management network Ping the port group and management network. Cisco UCS Director VM Ensure that the Connect check box is checked in the VM. OL