Cisco UCS Director VSPEX Management Guide, Release 4.1
First Published: 2014-03-26
Americas Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 527-0883
Text Part Number: OL-31268-01
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: http://
www.cisco.com/go/trademarks. 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.
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 VSPEX 1
VSPEX Power-Path Enabled Host Encryption 2
CHAPTER 2
Configuration 3
Prerequisites 3
System Requirements 5
Adding a Pod 5
Cisco UCS Manager Accounts 6
Adding a Cisco UCS Manager Account 7
Testing the Connection to an Account 8
Verifying the Discovery of a Cisco UCS Manager Account 9
Viewing the Topology and Connectivity of Devices in a Cisco UCS Domain 9
Exporting the Configuration of a Cisco UCS Manager Account 10
Importing the Configuration of a Cisco UCS Manager Account 11
VSPEX Support 11
Adding a VSPEX Account 12
Verifying VSPEX Account Discovery 13
Network Configuration 14
Adding a Network Device to a Pod 14
Cisco UCS Director VSPEX Management Guide, Release 4.1
OL-31268-01
iii
Contents
Verifying Network Device Details in a Pod Environment 15
CHAPTER 3
Network Configuration for Cisco UCS Director Baremetal Agent 17
About the Network Configuration Options 17
Single Network for Management and PXE 17
Prerequisites and Assumptions for a Single Network Configuration 18
Configuring Cisco UCS Director Baremetal Agent for a Single Network 19
Separate Networks for Management and PXE 21
Prerequisites and Assumptions for a Separate Network Configuration 22
Configuring Cisco UCS Director Baremetal Agent for Separate Networks 23
Configuring Cisco UCS Director Baremetal Agent as a DHCP Server 27
Configuring Cisco UCS Director Baremetal Agent to Use a Static IP Address 27
CHAPTER 4
Operations and Management 29
Configuration Guidelines for VSPEX Operations 29
Creating an Organization 32
Configuring the Chassis/FEX Discovery Policy 33
Creating a UUID Pool 33
Creating a MAC Pool 34
Creating a WWNN Pool 35
Creating a WWPN Pool 35
Creating a Network Control Policy 36
Creating a vNIC Template 38
Creating a VSAN 41
Creating a vHBA Template 42
Creating a LAN Boot Policy 44
Creating a SAN Boot Policy 45
Creating a vNIC 47
Creating a vHBA 47
Creating a Network Policy 48
Creating a Storage Policy 50
CHAPTER 5
Sample Orchestration Workflows 53
Navigating to a Predefined Orchestration Workflow 53
Provisioning a Stateless Blade Server Orchestration Workflow 54
Cisco UCS Director VSPEX Management Guide, Release 4.1
iv
OL-31268-01
Contents
Provisioning a Stateless Blade Server Orchestration Workflow Overview 54
Modifying the Workflow Priority 56
Creating the UCS Service Profile Task 57
Choosing the Cisco UCS Server 58
Associating the Cisco UCS Service Profile 59
Powering Off the Cisco UCS Server 60
Setting Up PXE Boot 61
Creating a VNX LUN 63
Creating a VNX Storage Group 64
Adding a VNX Host Initiator Entry 65
Configuring Generic Storage Area Network Zoning 66
Adding Hosts to a VNX Storage Group 68
Adding a LUN to a VNX Storage Group 69
Modifying the Cisco UCS Service Profile Boot Policy 70
Modifying the Cisco UCS Boot Policy LUN ID 71
Resetting the UCS Server 72
Monitoring PXE Boot 73
Adding a VLAN to a Service Profile 74
Disassociating the Cisco UCS Service Profile 75
Configuring the Waiting for Specific Duration Task 76
Provisioning a File System Mounting Orchestration Workflow 77
File System Mounting Orchestration Workflow Overview 77
Creating a VNX File System 78
Adding a VNX NFS Export Task 79
Mounting the NFS Datastore 80
Validating and Executing an Orchestration Workflow 81
CHAPTER 6
Troubleshooting 83
Troubleshooting Cisco UCS Director Connectivity 83
Troubleshooting Cisco UCS Director Baremetal Agent Connectivity 84
Cisco UCS Director VSPEX Management Guide, Release 4.1
OL-31268-01
v
Contents
Cisco UCS Director VSPEX Management Guide, Release 4.1
vi
OL-31268-01
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.
Cisco UCS Director VSPEX Management Guide, Release 4.1
OL-31268-01
vii
Preface
Conventions
Text Type
Indication
System output
Terminal sessions and information that the system displays appear in this
font.
CLI commands
CLI command keywords appear in this font.
Variables in a CLI command appear in this font.
Note
Tip
[]
Elements in square brackets are optional.
{x | y | z}
Required alternative keywords are grouped in braces and separated by vertical
bars.
[x | y | z]
Optional alternative keywords are grouped in brackets and separated by vertical
bars.
string
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.
Means reader take note. Notes contain helpful suggestions or references to material not covered in the
document.
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.
Cisco UCS Director VSPEX Management Guide, Release 4.1
viii
OL-31268-01
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: http://www.cisco.com/en/US/docs/unified_computing/ucs/
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: http://www.cisco.com/go/unifiedcomputing/b-series-doc.
For a complete list of all C-Series documentation, see the Cisco UCS C-Series Servers Documentation Roadmap
available at the following URL: http://www.cisco.com/go/unifiedcomputing/c-series-doc.
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 [email protected]. 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.
Cisco UCS Director VSPEX Management Guide, Release 4.1
OL-31268-01
ix
Preface
Obtaining Documentation and Submitting a Service Request
Cisco UCS Director VSPEX Management Guide, Release 4.1
x
OL-31268-01
CHAPTER
1
Overview
This chapter contains the following sections:
• About VSPEX, page 1
• VSPEX Power-Path Enabled Host Encryption, page 2
About VSPEX
VSPEX is an integrated hardware and software environment that you can use for virtualized and nonvirtualized
converged computing, networking, and storage solutions. You can use VSPEX for the following:
• Data centers that need high availability and scalable EMC VSPEX VNX storage to reduce operating
costs and converge the infrastructure so that it supports hybrid cloud computing.
• Interface to private cloud services that provides computing resources for end users and virtualized
applications.
Note
The hardware deployed for the VSPEX environment is highly modular and varies depending on the specific
VSPEX rack-mount scheme needed for each customer deployment. For more information, see Cisco
Validated Designs on the web.
The VSPEX 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 VSPEX virtualization software, computing, and EMC VSPEX VNX storage components that are
located in one rack to provide scalable storage.
• Cisco Nexus components that provide routing and switching functionality.
Cisco UCS Director VSPEX Management Guide, Release 4.1
OL-31268-01
1
Overview
VSPEX Power-Path Enabled Host Encryption
• 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
VSPEX hardware and software components.
Figure 1: VSPEX Hardware and Software Components
VSPEX Power-Path Enabled Host Encryption
The VSPEX power-path enabled host encryption feature uses software agents on host servers and centralized
RSA Data Protection Manager appliances for key management that encrypts data at the host servers and as a
result, protects this data anywhere it goes outside the host server. You can use power-path enabled host
encryption to do the following:
• Protect storage environment data from being compromised through unauthorized access or disk removal.
• Comply with internal, private, and government standards-including the widely used Payment Card
Industry Data Security Standard (PCI DSS).
• Choose specific LUNs or volumes that contain sensitive data that need to be encrypted without having
to encrypt the entire SAN or array.
Cisco UCS Director VSPEX Management Guide, Release 4.1
2
OL-31268-01
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 3
• System Requirements, page 5
• Adding a Pod, page 5
• Cisco UCS Manager Accounts, page 6
• VSPEX Support, page 11
• Network Configuration, page 14
Prerequisites
Prerequisite
Description
Hardware Connectivity
For more information, see the EMC VSPEX VNX
Series Technical Specifications.
VSPEX License
For more information about pod licenses, see Cisco
UCS Director Install and Upgrade Guides.
Network Connectivity
Verify that network connectivity conforms to the
EMC VSPEX VNX Series Technical Specifications.
One DHCP server is permitted in the VLAN where
Cisco UCS Director Baremetal Agent is installed.
Cisco UCS Director VSPEX Management Guide, Release 4.1
OL-31268-01
3
Configuration
Prerequisites
Prerequisite
Description
Servers must be reachable from Cisco UCS Director. Verify Cisco UCS Director connects to the following:
See the Cisco UCS Director Baremetal Agent
• Cisco UCS Manager
Installation Guide for more information about
establishing this connectivity.
• EMC VSPEX VNX unified storage system
• 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 Verify Cisco UCS Director Baremetal Agent connects
to Cisco UCS Director.
Baremetal Agent. See the Cisco UCS Director
Baremetal Agent Installation Guide for more
information about establishing this connectivity.
Baremetal provisioning reachability.
Verify baremetal provisioning is on the same network
as Cisco UCS Director Baremetal Agent.
DHCP setup
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.
Cisco UCS Director database setup
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.
Cisco UCS Director /etc/hosts file
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.
Cisco UCS Director Baremetal Agent /etc/hosts file
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.
VMware (vCenter Server/ESXI/ESXi)
All versions are supported from ESXI 4.0 to ESXi
5.5.
Cisco UCS Director VSPEX Management Guide, Release 4.1
4
OL-31268-01
Configuration
System Requirements
System Requirements
Component
Requirement
Networking
Two Cisco Nexus 5000/5500 Series switches
Two Cisco UCS 6100 or 6200 Series Fabric
Interconnects
Cisco Nexus 1000V switch
Computing
One or multiple Cisco UCS chassis with modules
that have two Fabric Extenders per chassis
Storage
EMC VNX unified storage system
Cisco UCS Director
Version 2.5.0.2 and later versions
Cisco UCS Director Baremetal Agent
Version 2.5.0.2 and later versions
Cisco UCS Director—resource reservation
2 GB memory and minimum 3000-GHz CPU
Cisco UCS Director Baremetal Agent—resource
reservation
2 GB memory and minimum 2000-GHz CPU
VMware (vCenter Server/ESXI/ESXi)
All versions are supported from ESXI 4.0 to ESXi
5.5.
Adding a Pod
Step 1
Step 2
Step 3
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:
Name
Description
Name field
A descriptive name for the pod.
Site drop-down list
Choose the site where you want to add the pod. If your environment does
not include sites, you can omit this step.
Cisco UCS Director VSPEX Management Guide, Release 4.1
OL-31268-01
5
Configuration
Cisco UCS Manager Accounts
Name
Description
Type drop-down list
Choose the type of pod that you want to add. This can be one of the
following supported types:
• Generic
• VSPEX
• Vblock
If you choose any type of pod except the generic type, you must have a
license for that pod type. In addition, the nongeneric pod types accommodate
only specific physical and virtual components. A generic pod does not
require a specific pod license. You can add any type of physical or virtual
component to a generic pod. For more information about pod licenses, see
Cisco UCS Director Install and Upgrade Guides.
Description field
(Optional) A description of the pod.
Address field
The physical location of the pod. For example, this field could include the
city or other internal identification used for the pod.
Hide Pod check box
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.
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
Cisco UCS Director VSPEX Management Guide, Release 4.1
6
OL-31268-01
Configuration
Adding a Cisco UCS Manager Account
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 1
Step 2
Step 3
On the menu bar, choose Administration > Physical Accounts.
Click the Physical Accounts tab.
Click Add.
Step 4
In the Add Account dialog box, complete the following fields:
Name
Description
Pod drop-down list
Choose the pod to which this account belongs.
Category Type drop-down list
Choose the category type. You must choose Computing. This is the type
of infrastructure for the account.
Account Type drop-down list
Choose the account type. You must choose UCSM.
Authentication Type drop-down list
Choose the type of authentication to be used for this account. This can be
one of the following:
• Locally Authenticated—A locally authenticated user account is
authenticated directly through the fabric interconnect and can be
enabled or disabled by anyone with admin or AAA privileges.
Remotely Authenticated—A remotely authenticated user account is
any user account that is authenticated through LDAP, RADIUS, or
TACACS+.
Server Management drop-down list
Choose how you want to have the servers in this account managed. This
can be one of the following:
• All Servers—All servers are managed 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 Name field
A unique name that you assign to this account.
Server Address field
The IP address of Cisco UCS Manager. For a cluster configuration, this is
the virtual IP address.
Cisco UCS Director VSPEX Management Guide, Release 4.1
OL-31268-01
7
Configuration
Testing the Connection to an Account
Name
Description
User ID field
The username that this account will use to access Cisco UCS Manager. This
username must be a valid account in Cisco UCS Manager.
Password field
The password associated with the username.
UCS Authentication Domain field
The authentication domain for the remotely authenticated account.
This field is not displayed if you are using a locally authenticated account.
Transport Type drop-down list
Choose the transport type that you want to use for this account. This can be
one of the following:
• http
• https
Step 5
Port field
The port used to access Cisco UCS Manager.
Description field
(Optional) A description of this account.
Contact Email field
The email address that you can use to contact the administrator or other
person responsible for this account.
Location field
The location of this account.
Service Provider field
(Optional) The name of the service provider associated with this account,
if any.
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 an Account
You can test the connection at any time after you add an account to a pod.
Step 1
Step 2
On the menu bar, choose Administration > Physical Accounts.
Click the tab for the type of account you want to test.
Cisco UCS Director VSPEX Management Guide, Release 4.1
8
OL-31268-01
Configuration
Verifying the Discovery of a Cisco UCS Manager Account
For example, click the Physical Accounts tab or the Multi-Domain Managers tab.
Step 3
Step 4
Step 5
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 1
Step 2
Step 3
Step 4
Step 5
Step 6
On the menu bar, choose Physical > Compute.
In the left column, choose the pod that includes the Cisco UCS Manager account that you want to verify.
Note
The left column tree structure lists nodes for Sites, Unassigned Pods, and Multi-Domain Managers. When a
Sites node is expanded, all the pods for that site node are displayed. When you expand an Unassigned Pods
node, all the pods that are not assigned to any site are displayed. When you expand the Multi-Domain Managers
list, all multi-domain manager account types that you added to Cisco UCS Director are displayed.
Click the Compute Accounts tab.
In the table, click the row of the account that you want to verify.
Click View Details.
Cisco UCS Director displays a set of tabs that contain information about the components of that account that it has
discovered.
Click Back to return to the Compute Accounts tab.
Viewing the Topology and Connectivity of Devices in a Cisco UCS Domain
Step 1
Step 2
Step 3
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 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.
Step 6
If desired, you can modify the following view options:
Cisco UCS Director VSPEX Management Guide, Release 4.1
OL-31268-01
9
Configuration
Exporting the Configuration of a Cisco UCS Manager Account
• 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.
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 1
Step 2
Step 3
Step 4
Step 5
Step 6
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.
Step 7
When the configuration export is complete, click Close.
Cisco UCS Director VSPEX Management Guide, Release 4.1
10
OL-31268-01
Configuration
Importing the Configuration of a Cisco UCS Manager Account
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 1
Step 2
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.
Step 3
Step 4
Step 5
Step 6
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)
b)
c)
d)
Step 7
Step 8
Step 9
Click Browse and navigate to the configuration file that you want to import.
Click Upload.
When the file upload is complete, click OK.
Click Next.
On the Select Configuration screen of the Import UCS Configuration wizard, check one of the following check boxes:
Option
Description
Import All Configuration
Imports all configuration settings in the file.
Customize Import
Imports only the configuration settings that you choose.
Click Submit.
When the configuration import is complete, click Close.
VSPEX Support
Cisco UCS Director helps support the unified storage systems in the following ways:
• Auto-discovery
• Monitoring
• Visibly manage all the VNX components—RAID groups, storage pools, logical unit numbers (LUNs),
storage groups, initiators, file systems, volumes, Network File System (NFS) and Common Internet File
System (CIFS).
Cisco UCS Director VSPEX Management Guide, Release 4.1
OL-31268-01
11
Configuration
Adding a VSPEX Account
Note
Make sure that you create a pod before you add a VSPEX account.
Adding a VSPEX Account
Before You Begin
Make sure that you create a pod before you add a VSPEX account.
Step 1
Step 2
On the menu bar, choose Administration > Physical Accounts.
In the Physical Acccounts tab, click Add.
Step 3
In the Add Account dialog box, complete the following fields:
Name
Description
Pod drop-down list
Choose VSPEX for this account.
Category drop-down list
Choose Storage.
Account Type drop-down list
The account type EMC VNX is selected for you when Storage is selected as
the category.
Account Sub Type drop-down list
Choose from the following VNX account subtypes:
• VNX File—X-Blade enclosured, 2 to 8 blades, configurable failover
options, and flexible I/O connectivity. There is one datamover per license.
• VNX Block—Storage or data processor enclosure, dual active storage
processors, automatic failover, and flexible I/O connectivity. There are two
service providers per license.
• VNX Unified—Single platform for VNX File and VNX Block. There are
two service providers per license.
Authentication Type drop-down list Choose the Authentication Type for this account.
Account Name field
The account name.
Server Address field
The IP address of the VSPEX server.
User ID field
The user ID of the VSPEX server.
Password field
The password for the VSPEX server.
Cisco UCS Director VSPEX Management Guide, Release 4.1
12
OL-31268-01
Configuration
Verifying VSPEX Account Discovery
Name
Description
Transport Type drop-down list
Choose the transport type that you want to use for the account. This can be one
of the following:
• http
• https
Port field
The port (80 is the default).
Description field
The account description.
Contact Email field
The contact's email.
Location field
The site location for this account.
Service Provider field
The service provider name, if any.
Step 4
Click Add.
Cisco UCS Director automatically discovers all storage elements in the VSPEX account, including aggregates, disks,
volumes, LUNs, and Qtree.
Step 5
In the Physical Acccounts pane, click the account.
Step 6
Click Test Connection.
What to Do Next
Verify that the account has been discovered. The discovery process typically takes a few minutes.
Verifying VSPEX Account Discovery
After you add a Cisco UCS Manager to a Cisco UCS Director VSPEX environment, all discovered components
of this environment are displayed at the account level.
Step 1
Step 2
On the menu bar, choose Physical > Storage.
In the Storage pane, click the VSPEX account.
Step 3
Click the System Summary tab.
The Summary reports for this account appear.
Cisco UCS Director VSPEX Management Guide, Release 4.1
OL-31268-01
13
Configuration
Network Configuration
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
Step 1
Step 2
On the menu bar, choose Administration > Physical Accounts.
In the Managed Network Elements tab, click the Add Network Element icon.
Step 3
In the Add Network Element dialog box, complete the following fields:
Name
Description
Pod drop-down list
Choose a pod.
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
The IP address of the device.
Protocol drop-down list
Choose the protocol to use to communicate with the device (telnet or ssh).
Cisco UCS Director VSPEX Management Guide, Release 4.1
14
OL-31268-01
Configuration
Verifying Network Device Details in a Pod Environment
Step 4
Step 5
Name
Description
Port field
The port number for the device. The default is port 23.
Login field
The login username.
Password field
The login password for the device.
Enable Password field
The enable password for the device.
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.
Step 1
Step 2
On the menu bar, choose Physical > Network.
In the Network pane, click the pod.
Step 3
Click the Managed Network Elements tab.
Step 4
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.
Cisco UCS Director VSPEX Management Guide, Release 4.1
OL-31268-01
15
Configuration
Verifying Network Device Details in a Pod Environment
Cisco UCS Director VSPEX Management Guide, Release 4.1
16
OL-31268-01
CHAPTER
3
Network Configuration for Cisco UCS Director
Baremetal Agent
This chapter contains the following sections:
• About the Network Configuration Options, page 17
• Single Network for Management and PXE, page 17
• Separate Networks for Management and PXE, page 21
• Configuring Cisco UCS Director Baremetal Agent as a DHCP Server, page 27
• Configuring Cisco UCS Director Baremetal Agent to Use a Static IP Address, page 27
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
Cisco UCS Director VSPEX Management Guide, Release 4.1
OL-31268-01
17
Network Configuration for Cisco UCS Director Baremetal Agent
Prerequisites and Assumptions for a Single Network Configuration
• 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.
Cisco UCS Director VSPEX Management Guide, Release 4.1
18
OL-31268-01
Network Configuration for Cisco UCS Director Baremetal Agent
Configuring Cisco UCS Director Baremetal Agent for a Single Network
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.
Step 1
Step 2
Step 3
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 27. 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 27
Step 4
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 https://IP_address:443/, where IP_address represents the IP address of the Cisco UCS Director
Baremetal Agent VM.
Step 5
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
Use ifconfig to verify that the network interface “eth0” is configured properly and make a note of the IP address.
Step 7
Navigate to the /opt/infra/networkServices/ directory.
Step 8
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=
Step 9
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
Step 10
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.
Cisco UCS Director VSPEX Management Guide, Release 4.1
OL-31268-01
19
Network Configuration for Cisco UCS Director Baremetal Agent
Configuring Cisco UCS Director Baremetal Agent for a Single Network
b) When prompted, enter the IP Address and Hostname of the Cisco UCS Director Baremetal Agent VM.
Step 11
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.
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.
Step 12
Step 13
Step 14
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.
Step 15
Copy the dhcpd.conf.sample file, as follows: cp ./dhcpd.conf.sample ./dhcpd.conf
Step 16
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 209.165.202.158 netmask 255.255.255.224 {
option routers 209.165.200.254;
option subnet-mask 255.255.255.224;
option nis-domain "domain.org";
option domain-name "domain.org";
option domain-name-servers 209.165.201.1;
option time-offset -18000; # Eastern Standard Time
range dynamic-bootp 209.165.200.225 209.165.200.254;
default-lease-time 21600;
max-lease-time 43200;
allow booting;
allow bootp;
next-server 209.165.201.30; # IP of my PXE server
filename "/pxelinux.0";
}
Cisco UCS Director VSPEX Management Guide, Release 4.1
20
OL-31268-01
Network Configuration for Cisco UCS Director Baremetal Agent
Separate Networks for Management and PXE
Step 17
At the prompt, enter service dhcpd restart to restart the DHCP services.
Step 18
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.
Step 19
Navigate to the /opt/infra/ directory.
Step 20
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.
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.
Step 21
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
Cisco UCS Director VSPEX Management Guide, Release 4.1
OL-31268-01
21
Network Configuration for Cisco UCS Director Baremetal Agent
Prerequisites and Assumptions for a Separate Network Configuration
• On the Management network, traffic between Cisco UCS Director Baremetal Agent and Cisco UCS
Director or other devices and appliances
Figure 3: Sample Topology for Separate PXE and Management Networks
Prerequisites and Assumptions for a Separate Network Configuration
If you plan to configure Cisco UCS Director Baremetal Agent with a separate network configuration, ensure
that your environment meets the following prerequisites and assumptions:
• Cisco UCS Director has been installed and the network interface configured, as described in the
appropriate Cisco UCS Director installation guide.
• Cisco UCS Director is reachable through a web browser and you can log in.
• Cisco UCS Director Baremetal Agent has been installed, as described in the Cisco UCS Director Baremetal
Agent Installation and Configuration Guide, 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
Cisco UCS Director VSPEX Management Guide, Release 4.1
22
OL-31268-01
Network Configuration for Cisco UCS Director Baremetal Agent
Configuring Cisco UCS Director Baremetal Agent for Separate Networks
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
Step 1
Step 2
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.
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.
Step 3
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.
Step 4
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.
c) Click Next.
Step 5
Step 6
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.
Step 7
Step 8
Step 9
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 27. 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 27
Step 10
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 https://IP_address:443/, where IP_address represents the IP address of the Cisco UCS Director
Baremetal Agent VM.
Step 11
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:
Cisco UCS Director VSPEX Management Guide, Release 4.1
OL-31268-01
23
Network Configuration for Cisco UCS Director Baremetal Agent
Configuring Cisco UCS Director Baremetal Agent for Separate Networks
• User name—root
• Password—pxeboot
Step 12
Use ifconfig to verify that the network interface “eth0” is configured properly and make a note of the IP address.
Step 13
Navigate to the etc/sysconfig/nework-scripts/ directory.
Step 14
Copy the ifcfg-eth0 file to ifcfg-eth1, as follows: cp ./ifcfg-eth0 ./ifcfg-eth1
Step 15
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
Step 16
At the prompt, enter ifup eth1 to bring the eth1 interface online.
Step 17
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
inet addr:209.165.202.158 Bcast:209.165.202.159 Mask:255.255.255.224
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:1088996 (1.7 KiB) TX bytes:554021 (541.0 KiB)
Interrupt: 59 Base address:0x2024
eth1 Link encap:Ethernet HWaddr 00:50:56:AB:61:1D
inet addr:209.165.202.156 Bcast:209.165.202.159 Mask:255.255.255.224
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:172.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128
Scope:Host
Cisco UCS Director VSPEX Management Guide, Release 4.1
24
OL-31268-01
Network Configuration for Cisco UCS Director Baremetal Agent
Configuring Cisco UCS Director Baremetal Agent for Separate Networks
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)
Step 18
Navigate to the /opt/infra/networkServices/ directory.
Step 19
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=
Step 20
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
Step 21
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.
Step 22
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.
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.
Step 23
Step 24
Step 25
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.
Step 26
Copy the dhcpd.conf.sample file, as follows: cp ./dhcpd.conf.sample ./dhcpd.conf
Step 27
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
#
Cisco UCS Director VSPEX Management Guide, Release 4.1
OL-31268-01
25
Network Configuration for Cisco UCS Director Baremetal Agent
Configuring Cisco UCS Director Baremetal Agent for Separate Networks
ddns-update-style interim;
ignore client-updates;
subnet 209.165.202.158 netmask 255.255.255.224 {
option routers 209.165.200.254;
option subnet-mask 255.255.255.224;
option nis-domain "domain.org";
option domain-name "domain.org";
option domain-name-servers 209.165.201.1;
option time-offset -18000; # Eastern Standard Time
range dynamic-bootp 209.165.200.225 209.165.200.254;
default-lease-time 21600;
max-lease-time 43200;
allow booting;
allow bootp;
next-server 209.165.201.30; # IP of my PXE server
filename "/pxelinux.0";
}
Step 28
Navigate to the /etc/sysconfig/ directory.
Step 29
Edit the dhcpd file to add eth1 to the DHCPDARGS= parameter.
Step 30
At the prompt, enter service dhcpd restart to restart the DHCP services.
Step 31
Navigate to the /opt/infra/ directory.
Step 32
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.
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.
Step 33
Cisco UCS Director VSPEX Management Guide, Release 4.1
26
OL-31268-01
Network Configuration for Cisco UCS Director Baremetal Agent
Configuring Cisco UCS Director Baremetal Agent as a DHCP Server
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 1
Step 2
Log in to Cisco UCS Director Baremetal Agent.
In the shelladmin, navigate to the /etc directory.
cd /etc
Step 3
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
Step 4
When you are prompted to overwrite dhcpd.conf, enter yes.
Step 5
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
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.
Step 1
Step 2
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.
Step 3
Edit the ifcfg-interface_number file with the static IP address you want to assign.
Cisco UCS Director VSPEX Management Guide, Release 4.1
OL-31268-01
27
Network Configuration for Cisco UCS Director Baremetal Agent
Configuring Cisco UCS Director Baremetal Agent to Use a Static IP Address
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=209.165.202.139
NETMASK=255.255.255.224
GATEWAY=209.165.202.245
BROADCAST=209.165.202.159
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
Cisco UCS Director VSPEX Management Guide, Release 4.1
28
OL-31268-01
CHAPTER
4
Operations and Management
This chapter contains the following sections:
• Configuration Guidelines for VSPEX Operations, page 29
• Creating an Organization, page 32
• Configuring the Chassis/FEX Discovery Policy, page 33
• Creating a UUID Pool, page 33
• Creating a MAC Pool, page 34
• Creating a WWNN Pool, page 35
• Creating a WWPN Pool, page 35
• Creating a Network Control Policy, page 36
• Creating a vNIC Template, page 38
• Creating a VSAN, page 41
• Creating a vHBA Template, page 42
• Creating a LAN Boot Policy, page 44
• Creating a SAN Boot Policy, page 45
• Creating a vNIC, page 47
• Creating a vHBA, page 47
• Creating a Network Policy, page 48
• Creating a Storage Policy, page 50
Configuration Guidelines for VSPEX Operations
The following table provides Cisco UCS Director guidelines for implementing VSPEX operations. The
configuration notes explain important configuration details related to each task in this chapter.
Cisco UCS Director VSPEX Management Guide, Release 4.1
OL-31268-01
29
Operations and Management
Configuration Guidelines for VSPEX Operations
Tip
For more information related to the tasks in this chapter, see the Cisco UCS Director Management Guide
for Cisco UCS Manager.
Task
Configuration Notes
Creating an Organization, on page 32 Create a top-level organization which is the root. The policies and
pools created in this root are system-wide and are available to all
organizations in the system.
Configuring the Chassis/FEX
Discovery Policy, on page 33
A chassis policy is configured to specify how the system reacts when
a new chassis is added. Ensure that the 2-link option is selected from
the Action drop-down list.
Creating a UUID Pool, on page 33
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.
Creating a MAC Pool, on page 34
Create two MAC pools for each fabric interconnect. For example,
fabric interconnect A and B. Specify 2 in the Size field
(recommended).
Creating a WWNN Pool, on page 35 Create two worldwide node name (WWNN) pools for each fabric
interconnect. Specify 2 in the Size field (recommended).
Creating a WWPN Pool, on page 35 Create two worldwide port name (WWPN) pools for each fabric
interconnect. Specify 2 in the Size field (recommended).
Creating a Network Control Policy,
on page 36
Create the network control policy with the Cisco Discovery Protocol
(CDP) enabled.
Creating a vNIC Template, on page
38
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 9000.
Note
Creating a VSAN, on page 41
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 virtual storage area network (VSAN) for each fabric
interconnect. For example, fabric interconnect A and B.
Cisco UCS Director VSPEX Management Guide, Release 4.1
30
OL-31268-01
Operations and Management
Configuration Guidelines for VSPEX Operations
Task
Configuration Notes
Associating the VSANs to the Fabric Associate each VSAN with each fabric interconnect.
Interconnects
See the Cisco UCS Director Management Guide for Cisco UCS
Manager.
Creating a vHBA Template, on page Create a vHBA template for each fabric interconnect. Follow the
42
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 2048.
Creating a LAN Boot Policy, on page Create a LAN boot policy for each fabric interconnect.
44
Creating a SAN Boot Policy, on page Create a SAN boot policy for each fabric interconnect.
45
Creating a vNIC, on page 47
Create a vNIC 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.
Note
Creating a vHBA, on page 47
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
48
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.
Cisco UCS Director VSPEX Management Guide, Release 4.1
OL-31268-01
31
Operations and Management
Creating an Organization
Task
Configuration Notes
Creating a Storage Policy, on page
50
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 1
Step 2
Step 3
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 Name field, enter a name for the organization.
b) In the Description field, enter a description for the organization.
c) From the Parent Organization drop-down list, choose the organization under which this organization will reside.
Cisco UCS Director VSPEX Management Guide, Release 4.1
32
OL-31268-01
Operations and Management
Configuring the Chassis/FEX Discovery Policy
Configuring the Chassis/FEX Discovery Policy
Step 1
Step 2
Step 3
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 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
Step 6
Step 7
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 1
Step 2
Step 3
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:
Name
Description
Name field
A unique name for the pool.
Description field
A description for the pool.
Cisco UCS Director VSPEX Management Guide, Release 4.1
OL-31268-01
33
Operations and Management
Creating a MAC Pool
Name
Description
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.
Step 8
From field
The first UUID address in the block.
Size field
The number of UUID addresses in the block.
Click Submit.
Creating a MAC Pool
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
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:
Name
Description
Name field
A unique name for the pool.
Description field
A description for the pool.
First MAC Address field
The first MAC address in the block.
Size field
The number of MAC addresses in the block.
Click Submit.
Cisco UCS Director VSPEX Management Guide, Release 4.1
34
OL-31268-01
Operations and Management
Creating a WWNN Pool
Creating a WWNN Pool
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
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:
Name
Description
Name field
A unique name for the pool.
Description field
A description for the pool.
From field
The first WWNN address in the block.
Size field
The number of WWNN addresses in the block.
Click Submit.
Creating a WWPN Pool
Step 1
Step 2
Step 3
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:
Name
Description
Name field
A unique name for the pool.
Cisco UCS Director VSPEX Management Guide, Release 4.1
OL-31268-01
35
Operations and Management
Creating a Network Control Policy
Step 8
Name
Description
Description field
A description for the pool.
From field
The first WWPN address in the block.
Size field
The number of WWPN addresses in the block.
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 1
Step 2
Step 3
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:
Name
Description
Name field
A unique name for the policy.
CDP drop-down list
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
Cisco UCS Director VSPEX Management Guide, Release 4.1
36
OL-31268-01
Operations and Management
Creating a Network Control Policy
Name
Description
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
Forge drop-down list
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.
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.
Cisco UCS Director VSPEX Management Guide, Release 4.1
OL-31268-01
37
Operations and Management
Creating a vNIC Template
Creating a vNIC Template
Before You Begin
One or more of the following resources must already exist:
• Named VLAN
• MAC pool
• QoS policy
• LAN pin group
• Statistics threshold policy
Step 1
Step 2
Step 3
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:
Name
Description
Name field
A unique name for the policy.
Description field
A description for the policy.
Cisco UCS Director VSPEX Management Guide, Release 4.1
38
OL-31268-01
Operations and Management
Creating a vNIC Template
Name
Description
Fabric ID drop-down list
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.
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:
Cisco UCS Director VSPEX Management Guide, Release 4.1
OL-31268-01
39
Operations and Management
Creating a vNIC Template
a) Click Add.
b) In the Add Entry to VLANs dialog box, complete the following fields and click Submit:
• Name 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:
Name
Description
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 9216.
Note
Step 10
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.
MAC Pool drop-down list
Choose the MAC address pool that vNICs created from
this vNIC template should use.
QoS Policy drop-down list
Choose the quality of service policy that vNICs created
from this vNIC template should use.
Network Control Policy drop-down list
Choose the network control policy that vNICs created from
this vNIC template should use.
Pin Group drop-down list
Choose the LAN pin group that vNICs created from this
vNIC template should use.
Stats Threshold Policy drop-down list
Choose the statistics collection policy that vNICs created
from this vNIC template should use.
Click Submit.
What to Do Next
Include the vNIC template in a network policy.
Cisco UCS Director VSPEX Management Guide, Release 4.1
40
OL-31268-01
Operations and Management
Creating a VSAN
Creating a VSAN
Note
Step 1
Step 2
Step 3
Step 4
Step 5
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.
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:
Name
Description
VSAN Name field
A unique name for the VSAN.
VSAN ID field
The unique identifier assigned to the network.
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.
Cisco UCS Director VSPEX Management Guide, Release 4.1
OL-31268-01
41
Operations and Management
Creating a vHBA Template
Name
Description
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
• WWPN pool
• SAN pin group
• Statistics threshold policy
Step 1
Step 2
Step 3
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:
Name
Description
Name field
A unique name for the policy.
Cisco UCS Director VSPEX Management Guide, Release 4.1
42
OL-31268-01
Operations and Management
Creating a vHBA Template
Name
Description
Description field
A description for the policy.
Fabric ID drop-down list
Choose the fabric interconnect that vHBAs created with
this template are associated with.
VSAN drop-down list
Choose the VSAN that you want to associate with vHBAs
created from this template.
Template Type drop-down list
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
The maximum size of the Fibre Channel frame payload
bytes that the vHBA supports.
Enter an integer between 256 and 2112. The default is 2048.
Step 8
WWPN Pool drop-down list
Choose the WWPN pool that a vHBA created from this
template uses to derive its WWPN address.
QoS Policy drop-down list
Choose the QoS policy that is associated with vHBAs
created from this template.
Pin Group drop-down list
Choose the SAN pin group that is associated with vHBAs
created from this template.
Stats Threshold Policy drop-down list
Choose the statistics threshold policy that is associated with
vHBAs created from this template.
Click Submit.
What to Do Next
Include the vHBA template in a storage policy.
Cisco UCS Director VSPEX Management Guide, Release 4.1
OL-31268-01
43
Operations and Management
Creating a LAN Boot 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 1
Step 2
Step 3
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:
Name
Description
Name field
A unique name for the policy.
Description field
A description for the policy.
Reboot on Order Change check box
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.
Enforce vNIC/vHBA Name 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 9
Step 10
Step 11
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.
Cisco UCS Director VSPEX Management Guide, Release 4.1
44
OL-31268-01
Operations and Management
Creating a SAN Boot Policy
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.
Step 1
Step 2
Step 3
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:
Name
Description
Name field
A unique name for the policy.
Description field
A description for the policy.
Reboot on Order Change check box
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.
Cisco UCS Director VSPEX Management Guide, Release 4.1
OL-31268-01
45
Operations and Management
Creating a SAN Boot Policy
Name
Description
Enforce vNIC/vHBA Name 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 9
Step 10
Step 11
Step 12
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:
Name
Description
Primary Boot Target LUN drop-down list
The primary LUN ID number that corresponds to the
location of the boot image.
Primary Boot Target WWPN field
The primary WWPN value that corresponds to the location
of the boot image.
Secondary Boot Target LUN field
The secondary LUN ID number that corresponds to the
location of the boot image.
Secondary Boot Target WWPN field
The secondary WWPN value that corresponds to the
location of the boot image.
Click Submit.
Cisco UCS Director VSPEX Management Guide, Release 4.1
46
OL-31268-01
Operations and Management
Creating a vNIC
Creating a vNIC
Step 1
Step 2
Step 3
Step 4
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.
Step 5
Complete the following fields to specify the Cisco UCS connections for the vNIC:
• UCS Account Name drop-down list—Choose the Cisco UCS Manager account to which you want to add this
vNIC.
• UCS Organization Name 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.
What to Do Next
Include this vNIC in a network policy.
Creating a vHBA
Step 1
Step 2
Step 3
Step 4
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.
Step 5
Complete the following fields to specify the Cisco UCS connections for the vHBA:
• UCS Account Name drop-down list—Choose the Cisco UCS Manager account to which you want to add this
vHBA.
Cisco UCS Director VSPEX Management Guide, Release 4.1
OL-31268-01
47
Operations and Management
Creating a Network Policy
• UCS Organization Name 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.
Creating a Network Policy
Step 1
Step 2
Step 3
Step 4
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.
Step 5
Complete the following fields to specify the Cisco UCS connections for the policy:
• UCS Account Name drop-down list—Choose the Cisco UCS Manager account to which you want to add this
policy.
• UCS Organization Name 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
Description
Expert
Allows you to create an unlimited number of vNICs that the server can use to access
the LAN.
Continue with Step 8.
Cisco UCS Director VSPEX Management Guide, Release 4.1
48
OL-31268-01
Operations and Management
Creating a Network Policy
Option
Description
Simple
Allows you to create a maximum of two vNICs that the server can use to access the
LAN.
Continue with Step 9.
No vNICs
Does not allow you to create any vNICs. If you choose this option, any server associated
with a service profile that includes this policy is not connected to the LAN.
Continue with Step 11.
Hardware Inherited
Uses the vNICs assigned to the Ethernet adapter profile associated with the server.
Continue with Step 11.
Use LAN Connectivity Policy Uses a LAN connectivity policy to determine the LAN connectivity for the server.
Continue with Step 10.
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.
b) From the Template For vNIC1/vNIC2/vNIC3/vNIC4 drop-down list, choose a vNIC template.
c) Continue with Step 11.
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 Name 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 Name 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 Step 11.
Step 10
Step 11
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.
Cisco UCS Director VSPEX Management Guide, Release 4.1
OL-31268-01
49
Operations and Management
Creating a Storage Policy
Creating a Storage Policy
Step 1
Step 2
Step 3
Step 4
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.
Step 5
Complete the following fields to specify the Cisco UCS connections for the policy:
• UCS Account Name drop-down list—Choose the Cisco UCS Manager account to which you want to add this
policy.
• UCS Organization Name 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:
Option
Description
Expert
Allows you to create an unlimited number of vHBAs that the server can use to access
SAN storage.
Continue with Step 8.
Simple
Allows you to create a maximum of two vHBAs that the server can use to access SAN
storage.
Continue with Step 9.
No vHBAs
Does not allow you to create any vHBAs. If you choose this option, any server associated
with a service profile that includes this policy is not connected to SAN.
Continue with Step 11.
Hardware Inherited
Uses the vHBAs assigned to the Fibre Channel adapter profile associated with the
server.
Continue with Step 11.
Use SAN Connectivity Policy Uses a SAN connectivity policy to determine the SAN connectivity for the server.
Continue with Step 10.
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.
Cisco UCS Director VSPEX Management Guide, Release 4.1
50
OL-31268-01
Operations and Management
Creating a Storage Policy
c) From the Template For vHBA1/vHBA2/vHBA3/vHBA4 drop-down list, choose a vHBA template.
d) Continue with Step 11.
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 Name 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 Name field, enter a unique name for the vHBA.
• From the Select VSAN drop-down list, choose the name of the VSAN with which this vHBA should be
associated.
d) Continue with Step 11.
Step 10
Step 11
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.
Cisco UCS Director VSPEX Management Guide, Release 4.1
OL-31268-01
51
Operations and Management
Creating a Storage Policy
Cisco UCS Director VSPEX Management Guide, Release 4.1
52
OL-31268-01
CHAPTER
5
Sample Orchestration Workflows
This chapter contains the following sections:
• Navigating to a Predefined Orchestration Workflow, page 53
• Provisioning a Stateless Blade Server Orchestration Workflow, page 54
• Provisioning a File System Mounting Orchestration Workflow, page 77
• Validating and Executing an Orchestration Workflow, page 81
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.
Step 1
Step 2
On the menu bar, choose Policies > Orchestration.
In the Orchestration pane, click the Workflows tab.
Step 3
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
Cisco UCS Director VSPEX Management Guide, Release 4.1
OL-31268-01
53
Sample Orchestration Workflows
Provisioning a Stateless Blade Server Orchestration Workflow
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.
Provisioning a Stateless Blade Server Orchestration Workflow Overview
The following table provides an overview for configuring the stateless blade server orchestration workflow.
Use this table as a point of reference to determine the specific task name, task type, and the section to which
it is aligned. Each task covered in subsequent sections references the task name and task type in a generic
way. Once all the tasks in the workflow are validated and bound to the local environment, you must validate
the entire workflow. The following table provides an overview for implementing the stateless blade server
orchestration workflow. See Validating and Executing an Orchestration Workflow, on page 81 for more
information.
Note
A blade server can be booted in a stateless environment, which is a storage area network (SAN), in order
to fix a blade server failure state. An example of a stateless environment can be the World Wide Web,
which does not follow settings or any other data for the next session.
Task Name
Task Type
Section
ModifyWorkflowPriority_89
95. Modify Workflow Priority
Modifying the Workflow
Priority, on page 56
CreateUCSServiceProfile_160
114. Create UCS Service Profile
Creating the UCS Service
Profile Task, on page 57
SelectBlades_91
96. Select UCS Server
Choosing the Cisco UCS
Server, on page 58
AssociateUCSServiceProfile_92
97. Associate UCS Service Profile
Associating the Cisco UCS
Service Profile, on page 59
UCSBladePowerOFFAction_146
108. Power Off UCS Server
Powering Off the Cisco UCS
Server, on page 60
PXEBoot_93
98. Setup PXE Boot
Setting Up PXE Boot, on page
61
Cisco UCS Director VSPEX Management Guide, Release 4.1
54
OL-31268-01
Sample Orchestration Workflows
Provisioning a Stateless Blade Server Orchestration Workflow Overview
Task Name
Task Type
Section
CreateLUN_247
115. Create VNX LUN
Creating a VNX LUN, on
page 63
CreateStorageGroup_117
101. Create VNX Storage Group
Creating a VNX Storage
Group, on page 64
AddHostInitiatorEntry_118
102. Add VNX Host Initiator Entry
Adding a VNX Host Initiator
Entry, on page 65
AddHostInitiatorEntry_119
103. Add VNX Host Initiator Entry
Adding a VNX Host Initiator
Entry, on page 65
GenericConfigureSANZoning_120 104. Generic Configure SAN Zoning
Configuring Generic Storage
Area Network Zoning, on
page 66
AddHoststoStorageGroup_121
105. Add Hosts to VNX Storage Group Adding Hosts to a VNX
Storage Group, on page 68
AddLUNtoStorageGroup_122
106. Add VNX LUN to Storage Group Adding a LUN to a VNX
Storage Group, on page 69
ModifyUCSServiceProfileBootPolicy_250 116. Modify UCS Service Profile Boot Modifying the Cisco UCS
Policy
Service Profile Boot Policy,
on page 70
ModifySANTargetLUNIdofBootPolicy_123 107. Modify UCS Boot Policy LUN ID Modifying the Cisco UCS
Boot Policy LUN ID, on page
71
Reset Blade to kick off PXE
109. Reset UCS Server
Resetting the Cisco UCS
Server
PXEBootWait_95
99. Monitor PXE Boot
Monitoring PXE Boot, on
page 73
ModifyUCSServiceProfileBootPolicy_96 100. Modify UCS Service Profile Boot Modifying the Cisco UCS
Policy
Service Profile Boot Policy,
on page 70
AddVLANtoServiceProfile_303
117. Add VLAN to Service Profile
Adding a VLAN to a Service
Profile, on page 74
DisassociateUCSServiceProfile_158 110. Disassociate UCS Service Profile Disassociating the Cisco UCS
Service Profile, on page 75
WaitforDuration_159
111. Wait for Specified Duration
Configuring the Waiting for
Specific Duration Task, on
page 76
Cisco UCS Director VSPEX Management Guide, Release 4.1
OL-31268-01
55
Sample Orchestration Workflows
Provisioning a Stateless Blade Server Orchestration Workflow Overview
Task Name
Task Type
Section
AssociateUCSServiceProfile_160 112. Associate UCS Service Profile
Associating the Cisco UCS
Service Profile, on page 59
WaitforDuration_161
113. Wait for Specified Duration
Configuring the Waiting for
Specific Duration Task, on
page 76
UCSBladeResetAction_317
118. Reset UCS Server
Resetting the Cisco UCS
Server
Modifying the Workflow Priority
See the orchestration workflow overview for the specific task name and task type.
Step 1
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:
Name
Description
Task Name field
The modify workflow priority task name is entered.
Task Category drop-down list
The General Tasks option is chosen.
Task Type drop-down list
The Modify Workflow Priority task type is chosen.
Comment field
Comments that pertain to this task.
Step 2
Click Next to advance to the User Input Mapping pane.
Step 3
Click Next to again to advance to the Task Inputs pane.
The following parameters are configurable:
Name
Description
Priority drop-down list
Choose High. The priority is saved.
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.
Cisco UCS Director VSPEX Management Guide, Release 4.1
56
OL-31268-01
Sample Orchestration Workflows
Provisioning a Stateless Blade Server Orchestration Workflow Overview
Creating the UCS Service Profile Task
See the orchestration workflow overview for the specific task name and task type.
Step 1
Step 2
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:
Name
Description
Task Name
The create UCS service profile task name is entered.
Task Category drop-down list
The Cisco UCS Tasks category is chosen.
Task Type drop-down list
The Create UCS Service Profile task type is chosen.
Comment field
Comments that pertain to this task.
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.
Name
Description
Service Profile Name drop-down list Choose the Service Profile Name attribute.
Step 3
Click Next to advance to the Task Inputs pane.
Note
This workflow assumes that the following actions have been accomplished through Cisco UCS Director:
• All pod required elements are discovered and managed.
• All required pools and resources for a service profile are created.
• All required policies are defined and bound to their respective pools and resources.
The following parameters are configurable:
Note
Any parameter that is not included in the following table is either not set or uses the default setting.
Name
Description
Description field
Comments that pertain to this task.
Organization button
The pre-sales option is chosen.
UUID Assignment drop-down list
Choose pe_uuid_pool.
Cisco UCS Director VSPEX Management Guide, Release 4.1
OL-31268-01
57
Sample Orchestration Workflows
Provisioning a Stateless Blade Server Orchestration Workflow Overview
Name
Description
Storage Policy drop-down list
Choose ps-storage-policy.
Network Policy drop-down list
Choose ps-network-policy.
PXE Boot Policy drop-down list
Choose ps-lan-boot.
Server Boot Policy drop-down list
Choose ps-san-policy.
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.
Step 1
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:
Name
Description
Task Name
The select blades task name is entered.
Task Category drop-down list
The UCS Tasks category is chosen.
Task Type drop-down list
The Select UCS Server task type is chosen.
Comment field
Comments that pertain to this task.
Task Details display field
The output generated by this task.
Step 2
Click Next to advance to the User Input Mapping pane. No parameters are configured for this pane.
Step 3
Click Next to advance to the Task Inputs pane.
The following parameters are configurable:
Name
Description
Account Name drop-down list
Choose the account name. For example, vBLOCK-300-UCS.
Cisco UCS Director VSPEX Management Guide, Release 4.1
58
OL-31268-01
Sample Orchestration Workflows
Provisioning a Stateless Blade Server Orchestration Workflow Overview
Name
Description
Server Selection Scope drop-down Choose Include Servers.
list
Servers field Select button
Click the Select button to select a Cisco UCS server. For example,
*sys/chassis-1/blade-3.
Note
The asterisk (*) at the beginning of the path indicates this server is
associated to your environment.
Use Unassociated Servers Only
check box
Check the check box for your environment's requirements.
Number of CPUs field
The number of CPUs in your environment.
Total Memory (GB) field
The total memory in gigabytes (GB).
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.
Associating the Cisco UCS Service Profile
See the orchestration workflow overview for the specific task name and task type.
Step 1
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:
Name
Description
Task Name field
The associate UCS service profile task name is entered.
Task Category drop-down list
The Cisco UCS Tasks category is chosen.
Task Type drop-down list
The Associate UCS Service Profile task type is chosen.
Comment field
Comments that pertain to this task.
Task Details display field
The output generated by this task.
Cisco UCS Director VSPEX Management Guide, Release 4.1
OL-31268-01
59
Sample Orchestration Workflows
Provisioning a Stateless Blade Server Orchestration Workflow Overview
Step 2
Step 3
Click Next to advance to the User Input Mapping pane.
The following parameters are configurable:
Name
Description
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:
Name
Description
Server Selection Scope drop-down Choose the Include Servers option.
list
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.
Step 1
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:
Name
Description
Task Name field
The Cisco UCS blade power off action task name is entered.
Task Category drop-down list
The Cisco UCS Tasks category is chosen.
Task Type drop-down list
The Power Off UCS Server task type is chosen.
Comment field
Comments that pertain to this task.
Task Details display field
The output generated by this task.
Cisco UCS Director VSPEX Management Guide, Release 4.1
60
OL-31268-01
Sample Orchestration Workflows
Provisioning a Stateless Blade Server Orchestration Workflow Overview
Step 2
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.
Step 3
Name
Description
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:
Name
Description
Revalidate button
Binds all the necessary parameters identified in this task to the environment.
Submit button
Saves the workflow task changes in the database. A confirmation dialog box
appears.
Setting Up PXE Boot
See the orchestration workflow overview for the specific task name and task type.
Step 1
Step 2
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:
Name
Description
Task Name field
The PXE Boot task name is entered.
Task Category drop-down list
The Network Services Tasks category is chosen.
Task Type drop-down list
The Setup PXE Boot task type is chosen.
Comment field
Comments that pertain to this task.
Task Details display field
The output generated by this task.
Click Next to advance to the User Input Mapping pane.
The following parameters are configurable:
Cisco UCS Director VSPEX Management Guide, Release 4.1
OL-31268-01
61
Sample Orchestration Workflows
Provisioning a Stateless Blade Server Orchestration Workflow Overview
Note
Step 3
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.
Name
Description
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 Name drop-down list
Choose the hostname (machine name) attribute. For example, Host Name.
Click Next to advance to the Task Input pane.
The following parameters are configurable:
Name
Description
OS Type drop-down list
Choose the network device OS type. For example, ESXi5.0-u1 (with Nexus
1000v VEM).
Server IP Address field
The server IP address range.
Server Net Mask field
The server subnetwork (subnet) mask.
Server Gateway field
The server gateway IP address.
Server Name Server field
The server name server IP address.
Management VLAN field
The management VLAN number.
Root Password field
The root password.
Timezone drop-down list
Choose the time zone for your environment.
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.
Cisco UCS Director VSPEX Management Guide, Release 4.1
62
OL-31268-01
Sample Orchestration Workflows
Provisioning a Stateless Blade Server Orchestration Workflow Overview
Creating a VNX LUN
See the orchestration workflow overview for the specific task name and task type.
Step 1
Under the blue workflow Start icon, find and double-click the Create VNX LUN task. The Edit Task dialog box appears
with the Task Information pane.
The following parameters are preconfigured:
Name
Description
Task Name field
The task name for creating a logical unit number (LUN) is entered. For example:
CreateLUN_247.
Task Category drop-down list
The EMC VNX Tasks category is chosen.
Task Type drop-down list
The Create VNX LUN task type is chosen.
Comment field
Comments that pertain to this task.
Task Details display field
The output generated by this task.
Step 2
Click Next to advance to the User Input Mapping pane. No parameters are configured for this pane.
Step 3
Click Next to advance to the Task Inputs pane.
The following parameters are configurable:
Name
Description
Select EMC Account Select... button Choose the EMC account name (if required).
LUN Name field
The name of the LUN. For example, VB_LUN_Boot_ESXi_$(SR_ID).
Let System Specify LUN ID
checkbox
Check the check box to allow the system to specify the LUN ID.
Storage Pool Type drop-down list
Choose Pool for the type of storage pool.
User Capacity field
The LUN capacity created by user.
Capacity Units drop-down list
Choose the size of the LUN that is requested by user.
Default Owner drop-down list
Choose Auto to let the system automatically assign the default owner of the
LUN.
Initial Tier Placement drop-down
list
Choose Optimize for Pool Performance.
Revalidate button
Binds all the necessary parameters identified in this task to the environment.
Cisco UCS Director VSPEX Management Guide, Release 4.1
OL-31268-01
63
Sample Orchestration Workflows
Provisioning a Stateless Blade Server Orchestration Workflow Overview
Name
Description
Submit button
Saves the workflow task changes in the database. A confirmation dialog box
appears.
Creating a VNX Storage Group
See the orchestration workflow overview for the specific task name and task type.
Step 1
Under the blue workflow Start icon, find and double-click the Create VNX Storage Group task. The Edit Task dialog
box appears with the Task Information pane.
The following parameters are preconfigured:
Name
Description
Task Name
The create storage group task name is entered.
Task Category drop-down list
The EMC VNX Tasks category is chosen.
Task Type drop-down list
The Create VNX Storage Group task type is chosen.
Comment field
Comments that pertain to this task.
Task Details display field
The output generated by this task.
Step 2
Click Next to advance to the User Input Mapping pane. No parameters are configured for this pane.
Step 3
Click Next to advance to the Task Inputs pane.
The following parameters are configurable:
Name
Description
Select EMC Account Select... button Choose the EMC account name (if required).
Storage Group Name field
The storage group name. For example, VB_SG_ESXi_${SR_ID}.
Submit button
Saves the workflow task changes in the database. A confirmation dialog box
appears.
Cisco UCS Director VSPEX Management Guide, Release 4.1
64
OL-31268-01
Sample Orchestration Workflows
Provisioning a Stateless Blade Server Orchestration Workflow Overview
Adding a VNX Host Initiator Entry
See the orchestration workflow overview for the specific task name and task type.
Step 1
Step 2
Step 3
Under the blue workflow Start icon, find and double-click the Add VNX Host Initiator Entry task. The Edit Task
dialog box appears with the Task Information pane.
The following parameters are preconfigured:
Name
Description
Task Name
The VNX host initiator task name is entered.
Task Category drop-down list
The EMC VNX Tasks category is chosen.
Task Type drop-down list
The Add VNX Host Initiator Entry task type is chosen.
Comment field
Comments that pertain to this task.
Task Details display field
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.
Name
Description
Host Name drop-down list
Choose the host name attribute. For example, Host Name.
IP Address drop-down list
Choose the IP address attribute. For example,
PXEBoot_93.OUTPUT_HOST_IP_ADDRESS.
WWN/IQN drop-down list
Choose the WWN/IQN attribute. For example,
CreateUCSServiceProfile_160.OUTPUT_SP_VHBA1_WWN.
Click Next to advance to the Task Inputs pane.
The following parameters are configurable:
Name
Description
Select EMC Account Select... button Choose the EMC account name (if required). For example, vBLOCK-300.
Add Initiator to drop-down list
Choose New Host.
SP Port Select... button
Choose the SP Port. For example, A-2, A-0.
Initiator Type drop-down list
Choose CLARiiON Open.
Cisco UCS Director VSPEX Management Guide, Release 4.1
OL-31268-01
65
Sample Orchestration Workflows
Provisioning a Stateless Blade Server Orchestration Workflow Overview
Name
Description
Failover Mode drop-down list
Choose Active-Active mode(ALUA)-failovermode4.
Revalidate button
Binds all the necessary parameters identified in this task to the environment.
Submit button
Saves the workflow task changes in the database. A confirmation dialog box
appears.
Configuring Generic Storage Area Network Zoning
See the orchestration workflow overview for the specific task name and task type.
Step 1
Step 2
Under the blue workflow Start icon, find and double-click the Generic Configure SAN Zoning task. The Edit Task
dialog box appears with the Task Information pane.
The following parameters are preconfigured:
Name
Description
Task Name
The generic configure SAN zoning task name is entered.
Task Category drop-down list
The Cisco Network Tasks category is chosen.
Task Type drop-down list
The Generic Configure SAN Zoning task type is chosen.
Comment field
Comments that pertain to this task.
Task Details display field
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.
Name
Description
Service Profile drop-down list
Choose the service profile attribute. For example,
UCSBladePowerOFFAction_146.SERVICE_PROFILE_IDENTITY.
Select vHBA drop-down list
Choose the vHBA attribute. For example,
CreateUCSServiceProfile_160.SP_VHBA1.
Cisco UCS Director VSPEX Management Guide, Release 4.1
66
OL-31268-01
Sample Orchestration Workflows
Provisioning a Stateless Blade Server Orchestration Workflow Overview
Step 3
Name
Description
Select VSAN drop-down list
Choose the VSAN attribute. For example,
CreateUCSServiceProfile_160.SP_VSAN1.
Click Next to advance to the Task Inputs pane.
The following parameters are configurable for Fabric A:
Name
Description
Configure One to One zones check Check the check box.
box
Storage Account Type drop-down
list
Choose the storage account type. For example, EMC VNX.
Storage Account Name (Primary) Choose the storage account name. For example, vBLOC-300.
drop-down list
Storage FC Adapter (Primary)
field Select... button
Choose the storage FC adapter(s). For example, A-0(FIBRE_CHANNEL),
A-2(FIBRE_CHANNEL).
Select Device drop-down list
Choose the network device. For example, SJ-02-VBLOCK-300-N5K-A |
172.29.108.37 | vBLOCK-300.
Configure Fabric B check box
Check the check box to initiate the ability to configure Fabric B.
The following parameters are configured for Fabric B:
Name
Description
Storage Account Type drop-down
list
Choose the same storage account type that was chosen for Fabric A.
Storage Account Name (Primary) Choose the same storage account name that was chosen for Fabric A.
drop-down list
vBLOC-300.
Storage FC Adapter (Primary)
field Select... button
Step 4
Choose the storage FC adapter(s). For example: B-1(FIBRE_CHANNEL),
B-3(FIBRE_CHANNEL).
Configure the remaining parameters in the Task Inputs pane.
Name
Description
Revalidate button
Binds all the necessary parameters identified in this task to the environment.
Cisco UCS Director VSPEX Management Guide, Release 4.1
OL-31268-01
67
Sample Orchestration Workflows
Provisioning a Stateless Blade Server Orchestration Workflow Overview
Name
Description
Submit button
Saves the workflow task changes in the database. A confirmation dialog box
appears.
Adding Hosts to a VNX Storage Group
See the orchestration workflow overview for the specific task name and task type.
Step 1
Step 2
Under the blue workflow Start icon, find and double-click the Add Hosts to VNX Storage Group task. The Edit Task
dialog box appears with the Task Information pane.
The following parameters are preconfigured:
Name
Description
Task Name field
The add host to storage group task name is entered.
Task Category drop-down list
The EMC VNX Tasks category is chosen.
Task Type drop-down list
The Add Hosts to VNX Storage Group task type is chosen.
Comment field
Comments that pertain to this task.
Task Details display field
The output generated by this task.
Click Next to advance to the User Input Mapping pane.
The following parameters are configurable:
Note
Step 3
Check the Map to User Input check box next to the attribute to map it to the workflow when the workflow
executes.
Name
Description
Hosts drop-down list
Choose the name of the host attribute. For example,
AddHostInitiatorEntry_118.OUTPUT_HOST_IDENTITY.
Storage Group drop-down list
Choose the name of the storage group attribute. For example,
CreateStorageGroup_117.OUTPUT_STORAGE_GROUP_IDENTITY.
Click Next to advance to the Task Inputs pane.
The following parameters are configurable:
Cisco UCS Director VSPEX Management Guide, Release 4.1
68
OL-31268-01
Sample Orchestration Workflows
Provisioning a Stateless Blade Server Orchestration Workflow Overview
Name
Description
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.
Adding a LUN to a VNX Storage Group
See the orchestration workflow overview for the specific task name and task type.
Step 1
Step 2
Under the blue workflow Start icon, find and double-click the Add VNX LUN to Storage Group task. The Edit Task
dialog box appears with the Task Information pane.
The following parameters are preconfigured:
Name
Description
Task Name field
The add VNX LUN to storage group task name is entered.
Task Category drop-down list
The EMC VNX Tasks category is chosen.
Task Type drop-down list
The Add VNX LUN to Storage Group task type is chosen.
Comment field
Comments that pertain to this task.
Task Details display field
The output generated by this task.
Click Next to advance to the User Input Mapping pane.
The following parameters are configurable:
Note
Check the Map to User Input check box next to the attribute to map it to the workflow when the workflow
executes.
Name
Description
LUNs to Add drop-down list
Choose the name of the LUN attribute. For example,
CreateLUN_247.OUTPUT_LUN_IDENTITY.
Storage Group drop-down list
Choose the name of the storage group attribute. For example,
AddHoststoStorageGroup_121.OUTPUT_STORAGE_GROUP_IDENTITY.
Host LUN ID drop-down list
Choose the name of the host LUN ID attribute. For example, Host LUN Id.
Cisco UCS Director VSPEX Management Guide, Release 4.1
OL-31268-01
69
Sample Orchestration Workflows
Provisioning a Stateless Blade Server Orchestration Workflow Overview
Step 3
Click Next to advance to the Task Inputs pane.
The following parameters are configurable:
Name
Description
Revalidate button
Binds all the necessary parameters identified in this task to the environment.
Submit button
Saves the workflow task changes in the database. A confirmation dialog box
appears.
Modifying the Cisco UCS Service Profile Boot Policy
See the orchestration workflow overview for the specific task name and task type.
Step 1
Step 2
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:
Name
Description
Task Name field
The modify UCS service profile boot policy task name is entered.
Task Category drop-down list
The Cisco UCS Tasks category is chosen.
Task Type drop-down list
The Modify UCS Service Profile Boot Policy task type is chosen.
Comment field
Comments that pertain to this task.
Task Details display field
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.
Name
Description
Service Profile drop-down list
Choose the service profile attribute. For example,
CreateUCSServiceProfile_2034.SERVICE_PROFILE_IDENTITY.
Account Name 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.
Cisco UCS Director VSPEX Management Guide, Release 4.1
70
OL-31268-01
Sample Orchestration Workflows
Provisioning a Stateless Blade Server Orchestration Workflow Overview
Step 3
Name
Description
Boot Policy drop-down list
Choose the boot policy attribute for the blade. For example,
CreateUCSServiceProfile_2034.BLADE_BOOT_POLICY.
Click Next to advance to the Task Inputs pane.
The following parameters are configurable:
Name
Description
Revalidate button
Binds all the necessary parameters identified in this task to the environment.
Submit button
Saves the workflow task changes in the database. A confirmation dialog box
appears.
Modifying the Cisco UCS Boot Policy LUN ID
See the orchestration workflow overview for the specific task name and task type.
Step 1
Step 2
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:
Name
Description
Task Name
The update boot policy with LUN task name is entered.
Task Category drop-down list
The Cisco UCS Tasks category is chosen.
Task Type drop-down list
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.
Name
Description
Service Profile drop-down list
Choose the service profile attribute. For example,
CreateUCSServiceProfile_2034.SERVICE_PROFILE_IDENTITY.
Cisco UCS Director VSPEX Management Guide, Release 4.1
OL-31268-01
71
Sample Orchestration Workflows
Provisioning a Stateless Blade Server Orchestration Workflow Overview
Step 3
Name
Description
PXE Boot Policy drop-down list
Choose the PXE blade boot policy attribute. For example,
CreateUCSServiceProfile_2034.PXE_BOOT_POLICY.
Server Boot Policy drop-down list
Choose the server boot policy attribute. For example,
CreateUCSServiceProfile_2034.BLADE_BOOT_POLICY.
Lun ID drop-down list
Choose the LUN ID attribute. For example, ProvisionLUN.LUN_ID.
Click Next to advance to the Task Inputs pane.
The following parameters are configurable:
Name
Description
Revalidate button
Binds all the necessary parameters identified in this task to the environment.
Submit button
Saves the workflow task changes in the database. A confirmation dialog box
appears.
Resetting the UCS Server
Step 1
Step 2
Under the blue workflow Start icon, find and double-click the Reset UCS Server task. The Edit Task dialog box appears
with the Task Information panel.
The following parameters are preconfigured:
Name
Description
Task Name
The reset UCS Server task name is entered.
Task Category drop-down list
The Cisco UCS Tasks category is chosen.
Task Type drop-down list
The Reset UCS Server option is chosen.
Comment field
Comments pertaining to this task.
Task Details display field
The log output for this task.
Click Next to advance to the User Input Mapping panel.
The following parameters are configured:
Cisco UCS Director VSPEX Management Guide, Release 4.1
72
OL-31268-01
Sample Orchestration Workflows
Provisioning a Stateless Blade Server Orchestration Workflow Overview
Check the Map to User Input check box next to the following attribute to map it to the workflow when the
workflow executes.
Name
Description
Note
Server drop-down list
Step 3
Choose the server attribute. For example:
SelectBlades_91.SERVER_IDENTITY
Click Next to advance to the Task Inputs panel.
The following parameters are configured:
Name
Description
Revalidate button
Binds all the necessary parameters identified in this task to the environment.
Submit button
Saves the workflow task changes in the database. A confirmation dialog box
appears.
Monitoring PXE Boot
See the orchestration workflow overview for the specific task name and task type.
Step 1
Step 2
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:
Name
Description
Task Name field
The monitor PXE boot task name is entered.
Task Category drop-down list
The Network Services Tasks category is chosen.
Task Type drop-down list
The Monitor PXE Boot task type is chosen.
Comment field
Comments that pertain to this task.
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.
Cisco UCS Director VSPEX Management Guide, Release 4.1
OL-31268-01
73
Sample Orchestration Workflows
Provisioning a Stateless Blade Server Orchestration Workflow Overview
Step 3
Name
Description
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:
Name
Description
Max Wait Time (Hours) field
The maximum wait time in hours for the monitor PXE boot task.
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.
Adding a VLAN to a Service Profile
See the orchestration workflow overview for the specific task name and task type.
Step 1
Step 2
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:
Name
Description
Task Name field
The add VLAN to service profile task name is entered.
Task Category drop-down list
The Cisco UCS Tasks category is chosen.
Task Type drop-down list
The Add VLAN to Service Profile task type is chosen.
Comment field
Comments that pertain to this task.
Task Details display field
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.
Cisco UCS Director VSPEX Management Guide, Release 4.1
74
OL-31268-01
Sample Orchestration Workflows
Provisioning a Stateless Blade Server Orchestration Workflow Overview
Step 3
Name
Description
Account Name 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.
Name
Description
Account Name drop-down list
Choose the UCS Manager account name (if required).
VLAN Type drop-down list
Choose the Common/Global option.
Common/Global VLANs drop-down Choose the Native-VLAN option.
list
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.
Disassociating the Cisco UCS Service Profile
See the orchestration workflow overview for the specific task name and task type.
Step 1
Under the blue workflow Start icon, find and double-click the Disassociate UCS Service Profile task. The Edit Task
dialog box displays with the Task Information pane.
The following parameters are preconfigured:
Name
Description
Task Name field
The disassociate service profile task name is entered.
Task Category drop-down list
The Cisco UCS Tasks category is chosen.
Task Type drop-down list
The Disassociate UCS Service Profile task type is chosen.
Comment field
Comments that pertain to this task.
Task Details display field
The output generated by this task.
Cisco UCS Director VSPEX Management Guide, Release 4.1
OL-31268-01
75
Sample Orchestration Workflows
Provisioning a Stateless Blade Server Orchestration Workflow Overview
Step 2
Step 3
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.
Name
Description
Service Profile drop-down list
Choose the create UCS service profile algorithm.
Click Next to advance to the Task Input pane.
The following parameters are configurable:
Name
Description
Revalidate button
Binds all the necessary parameters identified in this task to the environment.
Submit button
Saves the workflow task changes in the database. A confirmation dialog box
appears.
Configuring the Waiting for Specific Duration Task
See the orchestration workflow overview for the specific task name and task type.
Step 1
Under the blue workflow Start icon, find and double-click the Wait for Specific Duration task. The Edit Task dialog
box displays with the Task Information pane.
The following parameters are preconfigured:
Name
Description
Task Name field
The wait for specific duration task name is entered.
Task Category drop-down list
The General Tasks category is chosen.
Task Type drop-down list
The Wait for Specified Duration task type is chosen.
Comment field
Comments that pertain to this task.
Task Details display field
The output generated by this task.
Cisco UCS Director VSPEX Management Guide, Release 4.1
76
OL-31268-01
Sample Orchestration Workflows
Provisioning a File System Mounting Orchestration Workflow
Step 2
Click Next to advance to the User Input Mapping pane. No parameters are configured for this pane.
Step 3
Click Next to advance to the Task Input pane.
The following parameters are configurable:
Name
Description
Duration drop-down list
The wait time in seconds.
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.
Provisioning a File System Mounting Orchestration Workflow
Cisco UCS Director handles the VSPEX file system mounting orchestration workflow by creating a file system
and mounting the file system as a Network File System (NFS) datastore.
File System Mounting Orchestration Workflow Overview
The following table provides an overview for implementing the file system mounting orchestration workflow.
Note
Use this table as a point of reference to determine the specific task name, task type, and the section to
which it is aligned. Each task covered in subsequent sections references the task name and task type in a
generic way. Once all the tasks in the workflow are validated and bound to the local environment, you
must validate the entire workflow. See Validating and Executing an Orchestration Workflow, on page
81 for more information.
Task Name
Task Type
Section
CreateEMCVNXFileSystem_247 253. Create VNX File System
Creating a VNX File System,
on page 78
AddNFSExport_248
254. Add VNX NFS Export
Adding a VNX NFS Export
Task, on page 79
SelectBlades_91
255. Mount NFS Datastore
Mounting the NFS Datastore,
on page 80
Cisco UCS Director VSPEX Management Guide, Release 4.1
OL-31268-01
77
Sample Orchestration Workflows
File System Mounting Orchestration Workflow Overview
Creating a VNX File System
See the orchestration workflow overview for the specific task name and task type.
Step 1
Under the blue workflow Start icon, find and double-click the Create VNX File System task. The Edit Task dialog
box appears with the Task Information pane.
The following parameters are preconfigured:
Name
Description
Task Name
The create EMC VNX file system task name is entered.
Task Category drop-down list
The EMC VNX Tasks category is chosen.
Task Type drop-down list
The Create VNX File System task type is chosen.
Comment field
Comments that pertain to this task.
Task Details display field
The output generated by this task.
Step 2
Click Next to advance to the User Input Mapping pane. No parameters are required to be configured for this step.
Step 3
Click Next to advance to the Task Inputs pane.
The following parameters are configurable:
Name
Description
Select EMC Account Select... button The EMC account name (if required).
Name field
The VNX file system name.
Create from drop-down list
Choose Storage Pool.
Storage Pool drop-down list
Choose a storage pool. For example, Pool 3(170.999 GB).
Storage Capacity field
The storage capacity of the file system to be created.
Capacity Units drop-down list
Choose the capacity unit. For example, GB (gigabytes).
Data Mover drop-down list
Choose the data mover (server) on which to mount the file system.
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.
Cisco UCS Director VSPEX Management Guide, Release 4.1
78
OL-31268-01
Sample Orchestration Workflows
File System Mounting Orchestration Workflow Overview
Adding a VNX NFS Export Task
See the orchestration workflow overview for the specific task name and task type.
Step 1
Step 2
Step 3
Under the blue workflow Start icon, find and double-click the Add VNX NFS Export task. The Edit Task dialog box
appears with the Task Information pane.
The following parameters are preconfigured:
Name
Description
Task Name
The add NFS export task name is entered.
Task Category drop-down list
The EMC VNX Tasks category is chosen.
Task Type drop-down list
The Add VNX NFS Export task type is chosen.
Comment field
Comments that pertain to this task.
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.
Name
Description
File Systems drop-down list
Choose the output file system mount path parameter. For example,
CreateEMCVNXFileSystem_247.OUTPUT_FILE_SYSTEM_MOUNT_PATH.
Click Next to advance to the Task Inputs pane.
The following parameters are configurable:
Name
Description
Data Mover Select... button
The data mover from which the file system is exported.
File Systems drop-down list
Choose the file system.
Read only Hosts field
The host names or IP addresses that get read-only access.
Read/Write Hosts field
The host names or IP addresses that get read-write access.
Root Hosts field
The host names or IP addresses that get root access.
Access Hosts field
The host names or IP addresses that get mount access.
Cisco UCS Director VSPEX Management Guide, Release 4.1
OL-31268-01
79
Sample Orchestration Workflows
File System Mounting Orchestration Workflow Overview
Name
Description
Hosts Access Read-only Export
check box
Check the check box to allow read-only access only to host names or IP addresses
that get mount access.
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.
Mounting the NFS Datastore
See the orchestration workflow overview for the specific task name and task type.
Step 1
Step 2
Step 3
Under the blue workflow Start icon, find and double-click the Mount NFS Datastore task. The Edit Task dialog box
appears with the Task Information pane.
The following parameters are preconfigured:
Name
Description
Task Name
The mount NFS Datastore task name is entered.
Task Category drop-down list
The VMware Host Tasks category is chosen.
Task Type drop-down list
The Mount NFS Datastore task type is chosen.
Comment field
Comments that pertain to this task.
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.
Name
Description
File Systems drop-down list
Choose the NFS export path parameter. For example,
AddNFSExport_248.OUTPUT_NFS_EXPORT_PATH.
Click Next to advance to the Task Inputs pane.
Cisco UCS Director VSPEX Management Guide, Release 4.1
80
OL-31268-01
Sample Orchestration Workflows
Validating and Executing an Orchestration Workflow
The following parameters are configurable:
Name
Description
Storage IP Address field
The IP address of the interface which was configured for NFS data.
Host Name Select... button
The VMWare hostname.
Datastore Name field
The name of the NFS VNX datastore. For example, VNXDataStore.
Access Mode drop-down list
Choose Read/Write.
Success Criteria drop-down list
Choose Mount successful at least on one Host.
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.
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.
Step 1
Step 2
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.
Cisco UCS Director VSPEX Management Guide, Release 4.1
OL-31268-01
81
Sample Orchestration Workflows
Validating and Executing an Orchestration Workflow
Cisco UCS Director VSPEX Management Guide, Release 4.1
82
OL-31268-01
CHAPTER
6
Troubleshooting
This chapter contains the following sections:
• Troubleshooting Cisco UCS Director Connectivity, page 83
• Troubleshooting Cisco UCS Director Baremetal Agent Connectivity, page 84
Troubleshooting Cisco UCS Director Connectivity
Step 1
Ensure Cisco UCS Director services are active.
Check
Do the following:
Cisco UCS Director Virtual Machine Ensure that there is sufficient resource reservation. For more information, see
(VM)
the System Requirements section.
Cisco UCS Director appliance
Step 2
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.
Cisco UCS Director VSPEX Management Guide, Release 4.1
OL-31268-01
83
Troubleshooting
Troubleshooting Cisco UCS Director Baremetal Agent Connectivity
Step 3
Step 4
Step 5
Ensure that Cisco UCS Director can be accessed through a web browser. If you cannot access Cisco UCS Director, do
the following:
Note
Wait for the Cisco UCS Director appliance and services to become available before connecting to Cisco UCS
Director. This may take a few minutes.
Check
Do the following:
Web browser cache
Clear the web browser cache before accessing Cisco UCS Director through the
web.
Web browser version
Use the recommended browser version and flash version.
Ensure that Cisco UCS Director is able to reach all of the hardware and software.
Ensure that Cisco UCS Director is on the same interface as Cisco UCS Director Baremetal Agent.
Troubleshooting Cisco UCS Director Baremetal Agent
Connectivity
Step 1
Ensure that the DHCP service (daemon) is active.
Check
Do the following:
DHCP server
Use the following command:
/etc/init.d/dhcp status
Note
Step 2
If the status is down, restart the DHCP
server.
Ensure that the status of Cisco UCS Director Baremetal Agent network services is active.
Check
Do the following:
Cisco UCS Director Baremetal Agent Use the following command:
ps -ef | grep java
Note
Entering the above command should have three Java processes display.
If not, restart the services and recheck to make sure all of them are
active.
/opt/infra/stopInfraAll.sh
/opt/infra/startInfraAll.sh
Cisco UCS Director VSPEX Management Guide, Release 4.1
84
OL-31268-01
Troubleshooting
Troubleshooting Cisco UCS Director Baremetal Agent Connectivity
Step 3
Step 4
Ensure Cisco UCS Director Baremetal Agent can ping the Cisco UCS Director Baremetal Agent IP address. If not, check
the connectivity through the network configuration of the Cisco UCS Director Baremetal Agent appliance using vCenter.
Ensure that Cisco UCS Director Baremetal Agent can ping the Cisco UCS Manager and blade server network.
Check
Do the following:
DHCP server
Ensure that the DHCP server that is running on the Cisco UCS Director Baremetal
Agent provides DHCP functionality for baremetal provisioning. The Cisco UCS
Director Baremetal Agent should be on the same network or interface as the
Cisco UCS Manager so that it can provide Preboot Execution Environment (PXE)
functionality without problems.
Ensure there are no DHCP servers available in the same network as the Cisco
UCS Director Baremetal Agent.
Cisco UCS Director VSPEX Management Guide, Release 4.1
OL-31268-01
85
Troubleshooting
Troubleshooting Cisco UCS Director Baremetal Agent Connectivity
Cisco UCS Director VSPEX Management Guide, Release 4.1
86
OL-31268-01