Cisco UCS Director FlexPod Management Guide, Release 4.1

Transcription

1 First Published: Last Modified: 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 Preface Preface vii Audience vii Conventions vii Related Documentation ix Documentation Feedback ix Obtaining Documentation and Submitting a Service Request ix CHAPTER 1 Overview 1 About FlexPod 1 About NetApp C-Mode 2 CHAPTER 2 Configuration 5 Prerequisites 5 System Requirements 7 Adding a Pod 7 Cisco UCS Manager Accounts 8 Adding a Cisco UCS Manager Account 9 Testing the Connection to a Physical Account 11 Verifying the Discovery of a Cisco UCS Manager Account 11 Viewing the Topology and Connectivity of Devices in a Cisco UCS Domain 12 Exporting the Configuration of a Cisco UCS Manager Account 13 Importing the Configuration of a Cisco UCS Manager Account 13 NetApp Support 14 Adding a NetApp Account 14 Network Configuration 16 Adding a Network Device to a Pod 16 Verifying Network Device Details in a Pod Environment 17 OL iii

4 Contents CHAPTER 3 Network Configuration for Cisco UCS Director Baremetal Agent 19 About the Network Configuration Options 19 Single Network for Management and PXE 19 Prerequisites and Assumptions for a Single Network Configuration 20 Configuring Cisco UCS Director Baremetal Agent for a Single Network 20 Separate Networks for Management and PXE 23 Prerequisites and Assumptions for a Separate Network Configuration 23 Configuring Cisco UCS Director Baremetal Agent for Separate Networks 24 Configuring Cisco UCS Director Baremetal Agent as a DHCP Server 28 Configuring Cisco UCS Director Baremetal Agent to Use a Static IP Address 29 CHAPTER 4 Operations and Management 31 FlexPod Operations Task Overview 31 Creating an Organization 34 Configuring the Chassis/FEX Discovery Policy 35 Creating a UUID Pool 35 Creating a MAC Pool 36 Creating a WWNN Pool 37 Creating a WWPN Pool 37 Creating a Network Control Policy 38 Creating a vnic Template 40 Creating a VSAN 43 Creating a vhba Template 44 Creating a LAN Boot Policy 46 Creating a SAN Boot Policy 47 Creating a vnic 49 Creating a vhba 50 Creating a Network Policy 51 Creating a Storage Policy 52 CHAPTER 5 Sample Orchestration Workflows 55 Navigating to a Predefined Orchestration Workflow 55 Provisioning a Stateless Blade Server Orchestration Workflow 56 Stateless Blade Server Orchestration Workflow Overview 56 iv OL

5 Contents Modifying the Workflow Priority 57 Creating the UCS Service Profile Task 58 Configuring Storage Area Network Zoning 59 Adding a LUN Dataset Using OnCommand 61 Modifying the Cisco UCS Boot Policy LUN ID 62 Choosing the Cisco UCS Server 63 Associating the Cisco UCS Service Profile 64 Setting Up PXE Boot 66 Monitoring PXE Boot 67 Adding a VLAN to a Service Profile 68 Modifying the Cisco UCS Service Profile Boot Policy 69 Powering Off the Cisco UCS Server 70 Powering On the Cisco UCS Server 71 Registering the Host with vcenter 72 Adding Hosts to a Distributed Virtual Switch 74 Migrating a Default Virtual Switch to a Distributed Virtual Switch 75 Validating and Executing an Orchestration Workflow 76 CHAPTER 6 Troubleshooting 77 Troubleshooting Cisco UCS Director Connectivity 77 Troubleshooting Cisco UCS Director Baremetal Agent Connectivity 78 OL v

6 Contents 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/or Cisco UCS Director Express 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 Overview This chapter contains the following sections: About FlexPod, page 1 About NetApp C-Mode, page 2 About FlexPod FlexPod is an integrated hardware and software environment that you can use for virtualized and nonvirtualized converged computing, networking, and storage solutions. You can use FlexPod for the following: Data centers that need high availability and scalable storage to reduce operating costs and to converge the infrastructure so that it supports hybrid cloud computing. Interface to public cloud services. Purpose-built, high capacity platforms for specialized workloads where large-scale, real-time data analytics place unique demands on compute stacks. You can also use FlexPod for video surveillance, in-memory databases, and public cloud infrastructures. Note The hardware deployed for the FlexPod environment is highly modular and varies depending on the specific FlexPod rack-mount scheme needed for each customer deployment. For more information, see Cisco Validated Designs on the web. The FlexPod 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, 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 FlexPod virtualization software, computing, and NetApp FAS storage components that are located in one rack to provide scalable storage. Cisco Nexus components that provide routing and switching functionality. OL

12 About NetApp C-Mode Overview 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 FlexPod hardware and software components. Figure 1: FlexPod Hardware and Software Components About NetApp C-Mode FlexPod incorperates NetApp cluster-mode (C-mode) software functionality. C-mode defines an architecture that is made of a group of connected NetApp storage controllers (nodes) that share a global namespace (GNS). The physical NetApp storage controllers can have attached disk shelves, network interface cards (NICs), and flash cards. Together, these components create a physical resource pool that is virtualized as a logical cluster to provide data access. Cisco UCS Director is used to abstract and virtualize the physical equipment into logical resources, which allow data operations to be moved in a nondisruptive way when needed. NetApp C-mode has the following benefits: Scalability C-Mode scales because it allows storage controllers to be added as the storage environment grows without disruption to the resource pool that resides on a shared storage infrastructure. Host and client connections and datastores can move anywhere in the resource pool, and existing workloads can be balanced over the available resources. New workloads can also be deployed. Technology refreshes, 2 OL

13 Overview About NetApp C-Mode such as replacing disk shelves and adding or completely replacing storage controllers, can be accomplished while the environment remains online and serving data. High availability (HA) The HA node pair is redundantly configured to serve data in case one of the nodes fails. Operations such as volume movement, node failover, and switch failure can be performed without any disruption to the storage or applications. Storage failover protection is a core attribute of C-Mode. HA pairs of controllers are the building blocks that form the storage cluster. This architecture enables transparent controller clustering and failover capability in which a failed storage controller causes its partner node to take over its disk arrays, volumes, and running services to provide continuous operation. C-Mode can scale up linearly as the number of nodes increases. To attain high availability, the layers in the setup also have the following redundant features: Linear throughput scaling to multi-gigabytes per second. Linear scale performance for a single volume with striping. A striped volume uses the free space on more than one physical hard disk to create a bigger volume. Linear scale read performance with load-sharing mirrors and collective read/write performance in a single namespace. Flexibility Storage operations increase flexibility as follows: Accommodating any mix of Fibre Channel (FC) and serial advanced technology attachment (SATA) drives. Allowing nondisruptive data movement between tiers. Transparently accessing volumes on any node from any node. Connecting many volumes into a single namespace. Moving volumes between nodes transparently. Moving existing mailboxes to a different storage tier. OL

14 About NetApp C-Mode Overview 4 OL

15 CHAPTER 2 Configuration This chapter contains the following sections: Note The procedures in this chapter assume you are logged into Cisco UCS Director. Prerequisites, page 5 System Requirements, page 7 Adding a Pod, page 7 Cisco UCS Manager Accounts, page 8 NetApp Support, page 14 Network Configuration, page 16 Prerequisites Prerequisite FlexPod configuration design. For more information on FlexPod configurations, see the DesignZone for Flexpod. Hardware Connectivity Follow the NetApp FlexPod Technical Specifications. FlexPod License For more information about pod licenses, see Cisco UCS Director Install and Upgrade Guides. Network Connectivity Verify that network connectivity conforms to the NetApp FlexPod Technical Specifications. One DHCP server is permitted in the VLAN where Cisco UCS Director Baremetal Agent is installed. OL

16 Prerequisites Configuration Prerequisite Servers must be reachable from Cisco UCS Director. See the Cisco UCS Director Baremetal Agent Installation Guide for more information about establishing this connectivity. Verify Cisco UCS Director connects to the following: Cisco UCS Manager NetApp storage system(s) Cisco UCS Director Baremetal Agent Cisco Nexus 5000 and 5500 Series switches and Cisco Nexus 1000V switch Servers must be reachable from Cisco UCS Director Baremetal Agent. See the Cisco UCS Director Baremetal Agent Installation Guide for more information about establishing this connectivity. Baremetal provisioning reachability. DHCP setup Cisco UCS Director database setup Cisco UCS Director /etc/hosts file Cisco UCS Director Baremetal Agent /etc/hosts file VMware (vcenter Server/ESXI/ESXi) Verify Cisco UCS Director Baremetal Agent connects to Cisco UCS Director. Verify baremetal provisioning is on the same network as Cisco UCS Director Baremetal Agent. Configure the DHCP server with the appropriate IP address range on Cisco UCS Director Baremetal Agent. The DHCP server can also be configured to use Cisco UCS Director Baremetal Agent as the next server. For more information, see the Network Configuration for Cisco UCS Director Baremetal Agent chapter for more information. Enable remote database access on Cisco UCS Director Baremetal Agent. For more information, see the Network Configuration for Cisco UCS Director Baremetal Agent chapter for more information. Add an entry for Cisco UCS Director Baremetal Agent (reachable IP address on the same VLAN). For more information, see the Network Configuration for Cisco UCS Director Baremetal Agent chapter for more information. Add an entry for Cisco UCS Director (reachable IP address on the same VLAN). See the Network Configuration for Cisco UCS Director Baremetal Agent chapter for more information. All versions are supported from ESXI 4.0 to ESXi OL

17 Configuration System Requirements System Requirements Component Networking Computing Storage 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) Requirement 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 NetApp storage system Version and later versions Version and later versions 2 GB memory and minimum 3000-GHz CPU 2 GB memory and minimum 2000-GHz CPU All versions are supported from ESXI 4.0 to ESXi 5.5. 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 Site drop-down list A descriptive name for the pod. Choose the site where you want to add the pod. If your environment does not include sites, you can omit this step. OL

18 Cisco UCS Manager Accounts Configuration Type drop-down list Choose the type of pod that you want to add. This can be one of the following supported types: Flexpod Generic ExpressPod Medium VSPEX ExpressPod Small 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. For an environment that does not include Cisco UCS Central, you create Cisco UCS Manager accounts in a pod. 8 OL

19 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 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+. OL

20 Adding a Cisco UCS Manager Account Configuration 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 by. 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 by. 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 Server Address field User ID field Password field UCS Authentication Domain field Transport Type drop-down list A unique name that you assign to this account. 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. 10 OL

21 Configuration Testing the Connection to a Physical Account Step 5 Click Add. 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 System Tasks tab specifies the frequency of inventory collection. 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 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 those are correct, determine whether there is a network connectivity problem. Verifying the Discovery of a Cisco UCS Manager Account Step 4 Step 5 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. OL

22 Viewing the Topology and Connectivity of Devices in a Cisco UCS Domain Configuration Step 6 Click Back to return to the Compute Accounts tab. 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. 12 OL

23 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: OL

24 NetApp Support Configuration Option Import All Configuration Customize Import Imports all configuration settings in the file. Imports only the configuration settings that you choose. Step 8 Step 9 Click Submit. When the configuration import is complete, click Close. NetApp Support Cisco UCS Director helps support the unified storage systems in the following ways: Auto-discovery Monitoring Visibly Manage NetApp storage system components aggregates, volumes, LUNs, Qtrees (special subdirectories in a volume acting as a virtual subvolume with special attributes, primarily quotas and permissions), and so on. Note Make sure that a POD is created before a NetApp account is added. For more information, see Adding a Pod, on page 7. Adding a NetApp Account NetApp has two types of accounts: NetApp ONTAP and NetApp OnCommand. While you are adding a NetApp account, choose the required account type. Note You must manually configure an aggregate on the ONTAP filer before you can use the filer management of Cisco UCS Director. Before You Begin Add the pod to which this NetApp account belongs. 14 OL

25 Configuration Adding a NetApp Account 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 Choose the pod to which this account belongs. Allowed pod types are Default, Generic, and Flexpod. Choose the category type. You must choose Storage. This is the type of infrastructure for the account. Choose one of the following account types that you want to use for this account: NetApp ONTAP NetApp OnCommand Account field Server Address field User ID field Password field Transport Type drop-down list A unique name that you assign to this account. The IP address of the NetApp server. For a cluster configuration, this is the virtual IP address. The username that this account will use to access the NetApp server. This username must be a valid account in the NetApp server. The password associated with the username. Choose one of the following transport types that you want to use for this account: http https Port field field Contact field Location field Service Provider field The port used to access the NetApp account. (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. OL

26 Network Configuration Configuration Step 5 Click Add. Cisco UCS Director tests the connection to the NetApp server. If that test is successful, it adds the NetApp account and discovers all infrastructure elements in the server that are associated with that account, including the server's information, slots, processors, memory, and NICs. This discovery process and inventory collection cycle takes approximately five minutes to complete. Use the polling interval that you configured on the Infrastructure System Parameters tab on the Administration > System window, to specify the frequency of inventory collection. Network Configuration Cisco UCS Director enables the management, orchestration, and monitoring of 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. The network installation includes the following tasks: Adding a Cisco Nexus device to Cisco UCS Director Verifying managed network device details 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 Choose a pod. 16 OL

27 Configuration Verifying Network Device Details in a Pod Environment Device Category drop-down list 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 Port field Login field Password field Enable Password field The IP address of the device. Choose the protocol to use to communicate with the device (telnet or ssh). 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. The pod infrastructure details appear. 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. OL

28 Verifying Network Device Details in a Pod Environment Configuration 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. 18 OL

29 CHAPTER 3 Network Configuration for Cisco UCS Director Baremetal Agent This chapter contains the following sections: About the Network Configuration Options, page 19 Single Network for Management and PXE, page 19 Separate Networks for Management and PXE, page 23 Configuring Cisco UCS Director Baremetal Agent as a DHCP Server, page 28 Configuring Cisco UCS Director Baremetal Agent to Use a Static IP Address, page 29 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 Separate networks for management and PXE You should choose the network configuration option that best meets the requirements of your environment. 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: Services provided by Cisco UCS Director Baremetal Agent, such as DHCP, TFTP, and HTTP OL

30 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 VMs can be attached to or leverage. Configuring Cisco UCS Director Baremetal Agent for a Single Network Note This procedure assumes that the VMs have been created in the VMware vsphere 5.1 hypervisor. Although configurations on other releases of VMware vsphere or on other hypervisors may vary slightly, the required steps are applicable to all supported hypervisors and supported releases. 20 OL

31 Network Configuration for Cisco UCS Director Baremetal Agent Configuring Cisco UCS Director Baremetal Agent for a Single Network Step 4 Step 5 If necessary, power on the Cisco UCS Director Baremetal Agent VM. Open the VMware vsphere VM Console for the Cisco UCS Director Baremetal Agent VM. When prompted, configure the network interface as necessary. By default, this interface is set to use DHCP as described in Configuring Cisco UCS Director Baremetal Agent as a DHCP Server, on page 28. However, you can configure a static IP address, if required, as described in Configuring Cisco UCS Director Baremetal Agent to Use a Static IP Address, on page 29 After the network is configured and the Cisco UCS Director Baremetal Agent VM has completely booted up, close the VMware vsphere VM Console. The VM is fully booted up when you see a screen that prompts with the following text: To manage this VM browse to where IP_address represents the IP address of the Cisco UCS Director Baremetal Agent VM. Open an SSH session to the IP Address for the Cisco UCS Director Baremetal Agent VM, and use the following default credentials if you have not already changed them: User name root Password pxeboot Step 6 Step 7 Step 8 Step 9 Use ifconfig to verify that the network interface eth0 is configured properly and make a note of the IP address. Navigate to the /opt/infra/networkservices/ directory. In the run.sh file, enter the IP address of the Cisco UCS Director Baremetal Agent eth0 interface for the following parameters: -DpxeServer.ip= -DpxeServer.mgmt_vlan_ip= Open a new SSH session to the IP address for the Cisco UCS Director VM. Note In a multi-node setup, you need to open the SSH session to the VM for the Inventory database node. The following default credentials for this VM might have been changed during the configuration of Cisco UCS Director: User name shelladmin Password changeme 0 1 In the shelladmin, do the following to add the Cisco UCS Director Baremetal Agent hostname and IP address: a) From the menu, choose the option for Add Cisco UCS Director Baremetal Agent Hostname/IP and press Enter. b) When prompted, enter the IP Address and Hostname of the Cisco UCS Director Baremetal Agent VM. In the shelladmin, do the following to enable the database for Cisco UCS Director Baremetal Agent: Note In a multi-node setup, you need to perform this step on the Inventory database node. OL

32 Configuring Cisco UCS Director Baremetal Agent for a Single Network Network Configuration for Cisco UCS Director Baremetal Agent a) From the menu, choose the option for Enable Database for Cisco UCS Director Baremetal Agent and press Enter. b) Enter y for yes. c) When prompted, enter the IP Address or Hostname of the Cisco UCS Director Baremetal Agent VM. From the shelladmin menu, choose the option for Quit and exit the console. Return to the SSH console for the Cisco UCS Director Baremetal Agent VM. Navigate to the /etc/ directory. Copy the dhcpd.conf.sample file, as follows: cp./dhcpd.conf.sample./dhcpd.conf Edit the dhcpd.conf file to set up the DHCP services that are required for PXE booting. The following sample dhcpd.conf file includes the DHCP services. Note The next-server line is required and must include the IP address of the Cisco UCS Director Baremetal Agent VM. # # DHCP Server Configuration file. # see /usr/share/doc/dhcp*/dhcpd.conf.sample # ddns-update-style interim; ignore client-updates; subnet netmask { option routers ; option subnet-mask ; option nis-domain "domain.org"; option domain-name "domain.org"; option domain-name-servers ; option time-offset ; # Eastern Standard Time range dynamic-bootp ; default-lease-time 21600; max-lease-time 43200; allow booting; allow bootp; next-server ; # IP of my PXE server filename "/pxelinux.0"; } At the prompt, enter service dhcpd restart to restart the DHCP services. If DNS is not configured on Cisco UCS Director Baremetal Agent, add the hostname and IP address of Cisco UCS Director to the /etc/hosts file to ensure DNS hostname to IP address resolution. Navigate to the /opt/infra/ directory. Run the configure.sh script and, when prompted, provide the IP address of Cisco UCS Director as a parameter. Note In a multi-node setup, you need to perform this step on the Inventory database node. 22 OL

33 Network Configuration for Cisco UCS Director Baremetal Agent Separate Networks for Management and PXE 1 In a web browser, navigate to the IP address for Cisco UCS Director and verify that Cisco UCS Director Baremetal Agent is available and active, as follows: a) Login as a user with admin privileges. b) From the menu bar, choose Administration > Physical Accounts. c) Click the Network Services Agent tab. d) Verify that the list includes Cisco UCS Director Baremetal Agent and that the status is Active. e) If you do not see Cisco UCS Director Baremetal Agent in the list, click Refresh to add it to the list of available network services agents. 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 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: OL

34 Configuring Cisco UCS Director Baremetal Agent for Separate Networks Network Configuration for Cisco UCS Director Baremetal Agent 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, no additional configuration has been performed and the VM is powered off. 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 Note The PXE network/vlan must be configured as the native, or default, VLAN on the server. For example, for a Cisco UCS 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 Cisco UCS Director Baremetal Agent for Separate Networks Note This procedure assumes that the VMs have been created in the VMware vsphere 5.1 hypervisor. Although configurations on other releases of VMware vsphere or on other hypervisors may vary slightly, the required steps are applicable to all supported hypervisors and supported releases. Step 4 In the VMware vsphere Client interface, right-click the Cisco UCS Director Baremetal Agent VM and choose Edit Settings. On the Hardware tab of the Virtual Machine Properties dialog box, click Add. On the Device Type page of the Add Hardware dialog box, choose Network Adapter and click Next. The network adapter option might read Ethernet Adapter. On the Network Type page of the Add Hardware dialog box, do the following: a) From the Type drop-down list, choose an adapter type. You can accept the default value of Flexible. b) From the Network Label drop-down list, choose the network/vlan associated with PXE traffic to which you want to connect this network interface. 24 OL

35 Network Configuration for Cisco UCS Director Baremetal Agent Configuring Cisco UCS Director Baremetal Agent for Separate Networks c) Click Next. Step 5 Step 6 Step 7 Step 8 Step Review the summary and click Finish to add the network adapter to the VM. Click OK to close the Virtual Machine Properties dialog box for the VM. Power on the Cisco UCS Director Baremetal Agent VM. Open the VMware vsphere VM Console for the Cisco UCS Director Baremetal Agent VM. When prompted, configure the network interface as necessary. By default, this interface is set to use DHCP as described in Configuring Cisco UCS Director Baremetal Agent as a DHCP Server, on page 28. However, you can configure a static IP address, if required, as described in Configuring Cisco UCS Director Baremetal Agent to Use a Static IP Address, on page 29 After the network is configured and the Cisco UCS Director Baremetal Agent VM has completely booted up, close the VMware vsphere VM Console. The VM is fully booted up when you see a screen that prompts with the following text: To manage this VM browse to where IP_address represents the IP address of the Cisco UCS Director Baremetal Agent VM. Open an SSH session to the IP Address for the Cisco UCS Director Baremetal Agent VM, and use the following default credentials if you have not already changed them: User name root Password pxeboot Use ifconfig to verify that the network interface eth0 is configured properly and make a note of the IP address. Navigate to the etc/sysconfig/nework-scripts/ directory. Copy the ifcfg-eth0 file to ifcfg-eth1, as follows: cp./ifcfg-eth0./ifcfg-eth1 Edit the ifcfg-eth1 file to set up the PXE traffic interface. The following sample ifcfg-eth1 file shows the values that you need to update in the file. Note If you defined the GATEWAY variable for the eth0 interface, do not define that variable for the eth1 interface. DEVICE=eth [number] BOOTPROTO=[static or DHCP] ONBOOT=yes IPADDR=[if static] GATEWAY=[if static] NETMASK=[if static] TYPE=Ethernet PEERDNS=yes USERCTL=no IPV6INIT=no 6 7 At the prompt, enter ifup eth1 to bring the eth1 interface online. Use ifconfig to verify that the network interfaces are configured properly. The following example shows correctly configured network interfaces: eth0 Link encap:ethernet HWaddr F0:50:56:AB:26:45 OL

36 Configuring Cisco UCS Director Baremetal Agent for Separate Networks Network Configuration for Cisco UCS Director Baremetal Agent inet addr: Bcast: Mask: inet6 addr: fb80::250:56ff:faeb:2654/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:20264 errors:0 dropped:0 overruns:0 frame:0 TX packets:2318 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes: (1.7 KiB) TX bytes: (541.0 KiB) Interrupt: 59 Base address:0x2024 eth1 Link encap:ethernet HWaddr 00:50:56:AB:61:1D inet addr: Bcast: Mask: inet6 addr: fb80::250:56ff:faeb:611d/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:8 errors:0 dropped:0 overruns:0 frame:0 TX packets:109 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1296 (1.2 KiB) TX bytes:22248 (21.7 KiB) Interrupt: 67 Base address:0x20c4 lo Link encap:local loopback inet addr: Mask: inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:1636 Metric:1 RX packets:75 errors:0 dropped:0 overruns:0 frame:0 TX packets:75 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:25479 (24.8 KiB) TX bytes:25479 (24.8 KiB) Navigate to the /opt/infra/networkservices/ directory. In the run.sh file, enter the IP address of the Cisco UCS Director Baremetal Agent eth0 interface for the following parameters: -DpxeServer.ip= -DpxeServer.mgmt_vlan_ip= Open a new SSH session to the IP address for the Cisco UCS Director VM. Note In a multi-node setup, you need to open the SSH session to the VM for the Inventory database node. The following default credentials for this VM might have been changed during the configuration of Cisco UCS Director: User name shelladmin Password changeme 1 2 In the shelladmin, do the following to add the Cisco UCS Director Baremetal Agent hostname and IP address: a) From the menu, choose the option for Add Cisco UCS Director Baremetal Agent Hostname/IP and press Enter. b) When prompted, enter the IP Address and Hostname of the Cisco UCS Director Baremetal Agent VM. In the shelladmin, do the following to enable the database for Cisco UCS Director Baremetal Agent: 26 OL

37 Network Configuration for Cisco UCS Director Baremetal Agent Configuring Cisco UCS Director Baremetal Agent for Separate Networks Note In a multi-node setup, you need to perform this step on the Inventory database node. a) From the menu, choose the option for Enable Database for Cisco UCS Director Baremetal Agent and press Enter. b) Enter y for yes. c) When prompted, enter the IP Address or Hostname of the Cisco UCS Director Baremetal Agent VM From the shelladmin menu, choose the option for Quit and exit the console. Return to the SSH console for the Cisco UCS Director Baremetal Agent VM. Navigate to the /etc/ directory. Copy the dhcpd.conf.sample file, as follows: cp./dhcpd.conf.sample./dhcpd.conf Edit the dhcpd.conf file to set up the DHCP services that are required for PXE booting. The following sample dhcpd.conf file includes the DHCP services. Note The next-server line is required and must include the IP address of eth1, the PXE interface, for the Cisco UCS Director Baremetal Agent VM. # # DHCP Server Configuration file. # see /usr/share/doc/dhcp*/dhcpd.conf.sample # ddns-update-style interim; ignore client-updates; subnet netmask { option routers ; option subnet-mask ; option nis-domain "domain.org"; option domain-name "domain.org"; option domain-name-servers ; option time-offset ; # Eastern Standard Time range dynamic-bootp ; default-lease-time 21600; max-lease-time 43200; allow booting; allow bootp; next-server ; # IP of my PXE server filename "/pxelinux.0"; } Navigate to the /etc/sysconfig/ directory. Edit the dhcpd file to add eth1 to the DHCPDARGS= parameter. At the prompt, enter service dhcpd restart to restart the DHCP services. Navigate to the /opt/infra/ directory. Run the configure.sh script and, when prompted, provide the IP address of Cisco UCS Director as a parameter. OL

38 Configuring Cisco UCS Director Baremetal Agent as a DHCP Server Network Configuration for Cisco UCS Director Baremetal Agent 3 Note In a multi-node setup, you need to perform this step on the Inventory database node. In a web browser, navigate to the IP address for Cisco UCS Director and verify that Cisco UCS Director Baremetal Agent is available and active, as follows: a) Login as a user with admin privileges. b) From the menu bar, choose Administration > Physical Accounts. c) Click the Network Services Agent tab. d) Verify that the list includes Cisco UCS Director Baremetal Agent and that the status is Active. e) If you do not see Cisco UCS Director Baremetal Agent in the list, click Refresh to add it to the list of available network services agents. Configuring Cisco UCS Director Baremetal Agent as a DHCP Server Perform this task if you want to use Cisco UCS Director Baremetal Agent as a DHCP server and did not configure it during installation. Step 4 Step 5 Log in to Cisco UCS Director Baremetal Agent. In the shelladmin, navigate to the /etc directory. cd /etc Copy the dhcpd.conf.sample file to dhcpd.conf so that the existing file can be overwritten. cp /etc/dhcpd.conf.sample /etc/dhcpd.conf When you are prompted to overwrite dhcpd.conf, enter yes. Edit the dhcpd.conf file, using vi or another editor. Example: vi dhcpd.conf Step 6 Edit the following parameters to match your network: Option router Subnet mask Domain name server Dynamic-bootp range Step 7 Start the DHCP server. /etc/init.d/dhcpd start 28 OL

39 Network Configuration for Cisco UCS Director Baremetal Agent Configuring Cisco UCS Director Baremetal Agent to Use a Static IP Address Configuring Cisco UCS Director Baremetal Agent to Use a Static IP Address Perform this task if you want to use a static IP address and did not configure it when you installed Cisco UCS Director Baremetal Agent. In VMware vcenter, right-click on the Cisco UCS Director Baremetal Agent VM and choose Open Console. Navigate to the etc/sysconfig/nework-scripts/ directory. Edit the ifcfg-interface_number file with the static IP address you want to assign. The following sample ifcfg-eth1 file shows the configuration for a static IP address. DEVICE=eth1 BOOTPROTO=none ONBOOT=yes TYPE=Ethernet PEERDNS=yes USERCTL=no IPV6INIT=yes IPV6ADDR=2001:0db8:2f6a:4c03::4/63 #IPV6_AUTOCONF=no IPADDR= NETMASK= GATEWAY= BROADCAST= Step 4 When you are prompted about whether to configure a static IP address, enter yes and then enter the following information: IP address Gateway Netmask OL

40 Configuring Cisco UCS Director Baremetal Agent to Use a Static IP Address Network Configuration for Cisco UCS Director Baremetal Agent 30 OL

41 CHAPTER 4 Operations and Management This chapter contains the following sections: FlexPod Operations Task Overview, page 31 Creating an Organization, page 34 Configuring the Chassis/FEX Discovery Policy, page 35 Creating a UUID Pool, page 35 Creating a MAC Pool, page 36 Creating a WWNN Pool, page 37 Creating a WWPN Pool, page 37 Creating a Network Control Policy, page 38 Creating a vnic Template, page 40 Creating a VSAN, page 43 Creating a vhba Template, page 44 Creating a LAN Boot Policy, page 46 Creating a SAN Boot Policy, page 47 Creating a vnic, page 49 Creating a vhba, page 50 Creating a Network Policy, page 51 Creating a Storage Policy, page 52 FlexPod Operations Task Overview The following table provides a Cisco UCS Director configuration task overview for implementing FlexPod operations. The configuration notes explain important configuration details related to each task. OL

42 FlexPod Operations Task Overview Operations and Management Tip For more information related to the following tasks, see the Cisco UCS Director Management Guide for Cisco UCS Manager. Task Creating an Organization, on page 34 Configuring the Chassis/FEX Discovery Policy, on page 35 Creating a UUID Pool, on page 35 Creating a MAC Pool, on page 36 Creating a WWNN Pool, on page 37 Creating a WWPN Pool, on page 37 Creating a Network Control Policy, on page 38 Creating a vnic Template, on page 40 Configuration Notes 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. 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. 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. 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 Preboot Execution Environment (PXE) server and the Cisco UCS server are in separate VLANs, you must create separate vnic templates for both servers in each fabric interconnect. 32 OL

43 Operations and Management FlexPod Operations Task Overview Task Creating a VSAN, on page 43 Creating a vhba Template, on page 44 Configuration Notes Create a virtual storage area network (VSAN) for each fabric interconnect. For example, fabric interconnect A and B. 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 46 Creating a SAN Boot Policy, on page 47 Creating a vnic, on page 49 Creating a vhba, on page 50 Create a LAN boot policy for each fabric interconnect. Create a SAN boot policy for each fabric interconnect. 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 51 Follow the instructions in the task and use the following configuration guidelines: 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. 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

44 Creating an Organization Operations and Management Task Creating a Storage Policy, on page 52 Configuration Notes 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. Creating an Organization 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. 34 OL

45 Operations and Management Configuring the Chassis/FEX Discovery Policy Configuring the Chassis/FEX Discovery 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 Equipment Global Policies tab. Check the Chassis/FEX Discovery Policy check box. From the Action drop-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. 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 A unique name for the pool. field A description for the pool. OL

46 Creating a MAC Pool Operations and Management Prefix drop-down list 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. 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. 36 OL

47 Operations and Management Creating a WWNN Pool 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 Size field A unique name for the pool. A description for the pool. The first WWNN address in the block. 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: OL

48 Creating a Network Control Policy Operations and Management 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 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 38 OL

49 Operations and Management Creating a Network Control Policy 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. OL

50 Creating a vnic Template Operations and Management 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 Statistics threshold policy 40 OL

51 Operations and Management Creating a vnic Template 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. OL

52 Creating a vnic Template Operations and Management 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 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. 42 OL

53 Operations and Management Creating a VSAN MAC Pool drop-down list QoS Policy drop-down list Network Control Policy drop-down list Pin Group drop-down list Stats Threshold Policy drop-down list Choose the MAC address pool that vnics created from this vnic template should use. 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. 0 Click Submit. What to Do Next Include the vnic template in a network policy. 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 A unique name for the VSAN. The unique identifier assigned to the network. OL

54 Creating a vhba Template Operations and Management Type drop-down list 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 to configure the VSAN. 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. 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 the Cisco UCS Director Management Guide for Cisco UCS Manager. Creating a vhba Template Before You Begin One or more of the following resources must already exist: VSAN 44 OL

55 Operations and Management Creating a vhba Template 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 Fabric ID drop-down list VSAN drop-down list Template Type drop-down list A unique name for the policy. A description for the policy. 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 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. OL

56 Creating a LAN Boot Policy Operations and Management Pin Group drop-down list Stats Threshold Policy drop-down list 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. 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 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. 46 OL

57 Operations and Management Creating a SAN Boot Policy Enforce vnic/vhba check box 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. 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. 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. 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. OL

58 Creating a SAN Boot Policy Operations and Management 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 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. 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 The primary LUN ID number that corresponds to the location of the boot image. 48 OL

59 Operations and Management Creating a vnic Primary Boot Target WWPN field Secondary Boot Target LUN field Secondary Boot Target WWPN field 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. 2 Click Submit. Creating a vnic Step 4 Step 5 On the menu bar, choose Policies > UCS Manager. Click the vnic tab. Click Add. In the Create vnic dialog box, enter a unique name for the vnic. Complete the following fields to specify the Cisco UCS connections for the vnic: UCS Account drop-down list Choose the Cisco UCS Manager account to which you want to add this vnic. UCS Organization drop-down list Choose the Cisco UCS organization to which you want to add this vnic. Step 6 Step 7 From the vnic Template drop-down list, choose the vnic template that you want to assign to this vnic. From the Adapter Policy drop-down list, choose one of the following Ethernet adapter policies: Default Windows VMware Linux Step 8 Click Submit. OL

60 Creating a vhba Operations and Management What to Do Next Include this vnic in a network policy. Creating a vhba Step 4 Step 5 On the menu bar, choose Policies > UCS Manager. Click the vhba tab. Click Add. In the Create vhba dialog box, enter a unique name for the vhba. Complete the following fields to specify the Cisco UCS connections for the vhba: UCS Account drop-down list Choose the Cisco UCS Manager account to which you want to add this vhba. UCS Organization drop-down list Choose the Cisco UCS organization to which you want to add this vhba. Step 6 Step 7 From the vhba Template drop-down list, choose the vhba template that you want to assign to this vhba. From the Adapter Policy drop-down list, choose one of the following Ethernet adapter policies: Default Windows VMware Linux Step 8 Click Submit. What to Do Next Include this vhba in a storage policy. 50 OL

61 Operations and Management Creating a Network Policy Creating a Network Policy Step 4 Step 5 On the menu bar, choose Policies > UCS Manager. Click the Network Policy tab. Click Add. In the Add Network Policy dialog box, enter a name and description for the policy. Complete the following fields to specify the Cisco UCS connections for the policy: UCS Account drop-down list Choose the Cisco UCS Manager account to which you want to add this policy. UCS Organization drop-down list Choose the Cisco UCS organization to which you want to add this policy. Step 6 Step 7 If this policy is to be assigned to service profiles for servers that support dynamic vnics, choose a dynamic vnic connection policy from the Dynamic vnic Connection Policy drop-down list. From the LAN Connectivity Type drop-down list, choose one of the following connectivity types: Option Expert Simple No vnics Hardware Inherited Use LAN Connectivity Policy Allows you to create an unlimited number of vnics that the server can use to access the LAN. Continue with Step 8. Allows you to create a maximum of two vnics that the server can use to access the LAN. Continue with Step 9. 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. Continue with 1. Uses the vnics assigned to the Ethernet adapter profile associated with the server. Continue with 1. Uses a LAN connectivity policy to determine the LAN connectivity for the server. Continue with 0. Step 8 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. OL

62 Creating a Storage Policy Operations and Management b) From the Template For vnic1/vnic2/vnic3/vnic4 drop-down list, choose a vnic template. c) Continue with 1. Step 9 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) Continue with If you chose the 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. What to Do Next Include the network policy in a service profile. Creating a Storage Policy Step 4 Step 5 On the menu bar, choose Policies > UCS Manager. Click the Storage Policy tab. Click Add. In the Add Storage Policy dialog box, enter a name and description for the policy. Complete the following fields to specify the Cisco UCS connections for the policy: UCS Account drop-down list Choose the Cisco UCS Manager account to which you want to add this policy. UCS Organization drop-down list Choose the Cisco UCS organization to which you want to add this policy. Step 6 Step 7 From the Local Disk Configuration Policy drop-down list, choose the local disk configuration policy that you want to include in this storage policy. From the SAN Connectivity Type drop-down list, choose one of the following connectivity types: 52 OL

63 Operations and Management Creating a Storage Policy Option Expert Simple No vhbas Hardware Inherited Use SAN Connectivity Policy Allows you to create an unlimited number of vhbas that the server can use to access SAN storage. Continue with Step 8. Allows you to create a maximum of two vhbas that the server can use to access SAN storage. Continue with Step 9. 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. Continue with 1. Uses the vhbas assigned to the Fibre Channel adapter profile associated with the server. Continue with 1. Uses a SAN connectivity policy to determine the SAN connectivity for the server. Continue with 0. Step 8 If you chose the expert 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 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) Continue with 1. Step 9 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 a 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. OL

64 Creating a Storage Policy Operations and Management d) Continue with If you chose the 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. 54 OL

65 CHAPTER 5 Sample Orchestration Workflows This chapter contains the following sections: Navigating to a Predefined Orchestration Workflow, page 55 Provisioning a Stateless Blade Server Orchestration Workflow, page 56 Validating and Executing an Orchestration Workflow, page 76 Navigating to a Predefined Orchestration Workflow You can navigate to your orchestration workflow in Cisco UCS Director. Several common workflows exist which can be used to execute efficiently (fewest mouse clicks) common administration and provisioning tasks. 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. 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. Step 4 OL

66 Provisioning a Stateless Blade Server Orchestration Workflow Sample Orchestration Workflows Provisioning a Stateless Blade Server Orchestration Workflow Cisco UCS Director handles the stateless blade server orchestration workflow that initiates when a blade server fails and physically transitions to the alternate blade server. Since a service profile is tagged to the slot(s), the alternate blade server obtains its configuration from the blade that failed. 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. Stateless Blade Server Orchestration Workflow Overview The following table provides an overview for implementing the stateless blade server 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 76 for more information. Task WF Priority CreateUCSServiceProfile_2034 Task25 ProvisionLUN Update Boot Policy with LUN Task536 Associate SP Task Type Modify Workflow Priority Create UCS Service Profile Configure SAN Zoning Add LUN to Dataset using OnCom Modify UCS Boot Policy LUN ID Select UCS Server Associate UCS Service Profile Section Modifying the Workflow Priority, on page 57 Creating the UCS Service Profile Task, on page 58 Configuring Storage Area Network Zoning, on page 59 Adding a LUN Dataset Using OnCommand, on page 61 Modifying the Cisco UCS Boot Policy LUN ID, on page 62 Choosing the Cisco UCS Server, on page 63 Associating the Cisco UCS Service Profile, on page OL

67 Sample Orchestration Workflows Modifying the Workflow Priority Task PXE Boot Setup Power ON Blade Wait for PXE Boot AddVLANtoServiceProfile_2036 Task Type Set up PXE Boot Power On UCS Server Monitor PXE boot Add VLAN to Service Profile Section Setting Up PXE Boot, on page 66 Powering On the Cisco UCS Server, on page 71 Monitoring PXE Boot, on page 67 Adding a VLAN to a Service Profile, on page 68 Modify UCS Service Profile BootPolicy Task29 Power ON RegisterHostwithvCenter_954 AddHoststodvSwitch_955 MigrateDefaultvSwitchtoDVSwitch_198X Modify UCS Service Profile Boot Policy Power Off UCS Server Power On UCS Server Register Host with vcenter Add Hosts to dvswitch Migrate Default vswitch to dvswitch Modifying the Cisco UCS Service Profile Boot Policy, on page 69 Powering Off the Cisco UCS Server, on page 70 Powering On the Cisco UCS Server, on page 71 Registering the Host with vcenter, on page 72 Adding Hosts to a Distributed Virtual Switch, on page 74 Migrating a Default Virtual Switch to a Distributed Virtual Switch, on page 75 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 The modify workflow priority task name is entered. OL

68 Creating the UCS Service Profile Task Sample Orchestration Workflows Task Category drop-down list Task Type drop-down list Comment field 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. 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 Task Category drop-down list Task Type drop-down list Comment field Task Details display field The create UCS service profile task name is entered. 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. 58 OL

69 Sample Orchestration Workflows Configuring Storage Area Network Zoning 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. The following parameters are configurable: Organization button The management organization name. For example, FlexPod-Mgmt. UUID Assignment drop-down list Storage Policy drop-down list Revalidate button Submit button Choose the UUID assignment pool. For example, CL_UUID_Pool. Choose the storage policy name. For example, FlexPod_SP. 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 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 Configure SAN Zoning task. The Edit Task dialog box appears with the Task Information pane. The following parameters are preconfigured: Task The SAN zoning task name is entered. For example, Task25. Task Category drop-down list The Network Tasks category is chosen. OL

70 Configuring Storage Area Network Zoning Sample Orchestration Workflows Task Type drop-down list Comment field Task Details display field The 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 identity. For example, CreateUCSServiceProfile_2034.SERVICE_PROFILE_IDENTITY. UCS Account drop-down list Select Service Profile drop-down list Select vhba drop-down list Select VSAN drop-down list Choose the UCS account name. For example, CreateUCSServiceProfile_2034.ACCOUNT_NAME. Choose the UCS service profile name. For example, CreateUCSServiceProfile_2034.SERVICEPROFILE_NAME. Choose the vhba. For example, CreateUCSServiceProfile_2034.SP_VHBA1. Choose the VSAN. For example, CreateUCSServiceProfile_2034.SP_VSAN1. Click Next to advance to the Task Inputs pane. The following parameters are configurable: NetApp Account (Primary) drop-down list Choose the NetApp storage account name. For example, ice3270-1a (FlexPOD). NetApp FC Adapter (Primary) drop-down list Storage Policy drop-down list PXE Boot Policy drop-down list Server Boot Policy drop-down list Choose the primary NetApp FC Adapter. For example,ob [50:0a:09:84:89:bb:3f:22]. Note The Configure Secondary Head check box is checked. Choose the storage policy name. For example, FlexPod_SP. Choose the PXE boot policy name. For example, LANSANPolicy. Choose the server boot policy name. For example, SANBootPolicy. 60 OL

71 Sample Orchestration Workflows Adding a LUN Dataset Using OnCommand 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 Dataset Using OnCommand 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 LUN to Dataset using OnCom... task. The Edit Task dialog box appears with the Task Information pane. The following parameters are preconfigured: Task field The ProvisionLUN task name is entered. Task Category drop-down list Task Type drop-down list Comment field Task Details display field The Storage Tasks category is chosen. The Add LUN to Dataset using OnCommand 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. Initiator Choose the UCS service profile initiator attribute name. For example, CreateUCSServiceProfile_2034.OP_CSV_SP_VHBAs. Click Next to advance to the Task Inputs pane. The following parameters are configurable: OL

72 Modifying the Cisco UCS Boot Policy LUN ID Sample Orchestration Workflows Dataset Select... button Storage Size (GB) field Snapshow Reserve (%) field LUN Export Settings checkbox Export Protocol Type drop-down list OS Type drop-down list Revalidate button Submit button The dataset name. The storage size in gigabytes. For example, 20. The percentage of storage space set aside to accommodate for snapshots of a volume. Cisco recommends 4 percent. The check box is checked. Choose FCP for the Fibre Channel Protocol. Choose VMware for the operating system type. 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 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. 62 OL

73 Sample Orchestration Workflows Choosing the Cisco UCS Server Service Profile drop-down list PXE Boot Policy drop-down list Server Boot Policy drop-down list Lun ID drop-down list Choose the service profile attribute. For example, CreateUCSServiceProfile_2034.SERVICE_PROFILE_IDENTITY. 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. 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 The select UCS server task name is entered. For example, Task536. Task Category drop-down list Task Type drop-down list Comment field The UCS Tasks category is chosen. The Select UCS Server task type is chosen. Comments that pertain to this task. OL

74 Associating the Cisco UCS Service Profile Sample Orchestration Workflows Task Details display field 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. Account drop-down list Choose the UCS service profile account name attribute. For example, CreateUCSServiceProfile_2034.ACCOUNT_NAME. Click Next to advance to the Task Inputs pane. The following parameters are configurable: Server Selection Scope drop-down list Choose Include Servers. Servers Use Unassociated Servers Only check box Number of CPUs field Total Memory (GB) field Revalidate button Submit button Click the Select button to select a Cisco UCS server. For example, *sys/chassis-1/blade-4 [Service Profile : org-root/org-flexpod-mgmt/is-demtomark],... Note The asterisk (*) at the beginning of the path indicates this server is associated to your environment. Check the check box to use unassociated servers only. The number of CPUs. The amount of memory in gigabytes. 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. 64 OL

75 Sample Orchestration Workflows Associating the Cisco UCS Service Profile 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. 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. OL

76 Setting Up PXE Boot Sample Orchestration Workflows 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: 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 The server IP address range. The server subnetwork (subnet) mask. 66 OL

77 Sample Orchestration Workflows Monitoring PXE Boot Server Gateway field Server Server field Management VLAN field Root Password field Timezone drop-down list Revalidate button Submit button 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. 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. OL

78 Adding a VLAN to a Service Profile Sample Orchestration Workflows 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: 68 OL

79 Sample Orchestration Workflows Modifying the Cisco UCS Service Profile Boot Policy 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. Account drop-down list Choose an account name attribute (if required). Service Profile drop-down list 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. 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 The Cisco UCS Tasks category is chosen. The Modify UCS Service Profile Boot Policy task type is chosen. OL

80 Powering Off the Cisco UCS Server Sample Orchestration Workflows Comment field Task Details display field 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 Boot Policy drop-down list Choose the storage account name attribute (this drop-down menu is available if a storage account name was configured). For example, CreateUCSServiceProfile_2034.ACCOUNT_NAME. 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. 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: 70 OL

81 Sample Orchestration Workflows Powering On the Cisco UCS Server Task field Task Category drop-down list Task Type drop-down list Comment field Task Details display field The Cisco UCS blade power off action task name is entered. 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. 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. Powering On 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 On UCS Server task. The Edit Task dialog box appears with the Task Information pane. The following parameters are preconfigured: OL

82 Registering the Host with vcenter Sample Orchestration Workflows Task field Task Category drop-down list Task Type drop-down list Comment field Retry Count drop-down list Retry Frequency field Task Details display field The Power On task name is entered. The Cisco UCS Tasks category option is chosen. The Power On UCS Server task type is chosen Comments that pertain to this task. The number of retries is entered. The Retry Execution box next to this field is checked. The number of seconds before the next retry is entered. Subsequent retry entries can be entered with a semicolon and the number. 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. Server drop-down list Choose the server identity attribute. For example, Associate SP.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. Registering the Host with vcenter See the orchestration workflow overview for the specific task name and task type. 72 OL

83 Sample Orchestration Workflows Registering the Host with vcenter Under the blue workflow Start icon, find and double-click the Register Host with vcenter task. The Edit Task dialog box appears with the Task Information pane. The following parameters are preconfigured: Task field The register host with vcenter task name is entered. Task Category drop-down list Task Type drop-down list Comment field Retry Count drop-down list Retry Frequency field Task Details display field The VMware Host Tasks category is chosen. The Register Host with vcenter task type is chosen. Comments that pertain to this task. The number of retries is chosen. The Retry Execution check box next to this field is checked. The frequency of retries in seconds. 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. PXE Boot Request ID drop-down list Choose the PXE boot request ID attribute. For example, PXE Boot Setup.OUTPUT_PXE_BOOT_ID. Click Next to advance to the Task Input pane. The following parameters are configurable: Account drop-down list Choose the name of the account. For example, icefxp-vc-1. Check the Register PXE Host check box next to this field. Host License field Associate With drop-down list Cluster/Data Center drop-down list The license of the host. For example, P10C4-QLHD5-K8C31-099K4-CRYQH. Choose the Data Center option. Choose the cluster or data center. For example, FlexPod_DC_1. OL

84 Adding Hosts to a Distributed Virtual Switch Sample Orchestration Workflows 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 Hosts to a Distributed Virtual Switch 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 dvswitch 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 Power On task name is entered. The VMware Host Tasks option is chosen. The Add Hosts to dvswitch 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 attribute to map it to the workflow when the workflow executes. Select Hosts drop-down list Choose the host attribute. For example, RegisterHostwithvCenter_954.OUTPUT_HOST_IP. Click Next to advance to the Task Inputs pane. The following parameters are configurable: 74 OL

85 Sample Orchestration Workflows Migrating a Default Virtual Switch to a Distributed Virtual Switch Account drop-down list Datacenter drop-down list dvswitch drop-down list Revalidate button Submit button Choose the account name. For example, icafxp-vc-1. Choose the pod name. For example, FlexPod_DC_1. Choose the network switch name. For example, n1000v. 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. Migrating a Default Virtual Switch to a Distributed Virtual Switch See the orchestration workflow overview for the specific task name and task type. Under the blue workflow Start icon, find and double-click the Migrate Default vswitch to DVSwitch task. The Edit Task dialog box appears with the Task Information pane. The following parameters are preconfigured: Task field The migrate default vswitch to DV switch task name is entered. Task Category drop-down list Task Type drop-down list Comment field Task Details display field The VMware VM Tasks category is chosen. The Migrate Default vswitch to DVSwitch task type is chosen. Comments that pertain to this task. No output is 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. OL

86 Validating and Executing an Orchestration Workflow Sample Orchestration Workflows Host Node drop-down list Choose the host node attribute. For example, RegisterHostwithvCenter_954.OUTPUT_HOST_IP. Click Next to advance to the Task Input pane. The following parameters are configurable: Account drop-down list dvswitch drop-down list uplinkportgroup drop-down list Revalidate button Submit button Choose the account name. For example, icefxp-vc-1. Choose the DV switch name. For example, n1000v. Choose the port group uplink name. For example, system-uplink. 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. 76 OL

87 CHAPTER 6 Troubleshooting This chapter contains the following sections: Troubleshooting Cisco UCS Director Connectivity, page 77 Troubleshooting Cisco UCS Director Baremetal Agent Connectivity, page 78 Troubleshooting Cisco UCS Director Connectivity Ensure Cisco UCS Director services are active. Check Do the following: Cisco UCS Director Virtual Machine (VM) Ensure that there is sufficient resource reservation. For more information, see 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