Cisco UCS Director FlexPod Management Guide, Release 5.0
First Published: July 31, 2014
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-32118-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
CHAPTER 1
New and Changed Information for this Release 1
New and Changed Information for this Release 1
CHAPTER 2
Overview 3
About FlexPod 3
About NetApp C-Mode 4
About the Cisco Secure Enclaves Architecture 5
Managing Adaptive Security Appliances 6
SEA Deployment 6
System Requirements 6
FlexPod Implementation Overview 7
CHAPTER 3
Initial Cisco UCS Director FlexPod Configuration 9
Adding a Pod 9
Cisco UCS Manager Accounts 10
Adding a Cisco UCS Manager Account 11
Testing the Connection to a Physical Account 13
Verifying the Discovery of a Cisco UCS Manager Account 13
Viewing the Topology and Connectivity of Devices in a Cisco UCS Domain 14
Exporting the Configuration of a Cisco UCS Manager Account 15
Importing the Configuration of a Cisco UCS Manager Account 15
About Managing the NetApp Storage System 16
Adding a NetApp Account 16
Network Configuration 18
Adding a Network Device to a Pod 18
Verifying Network Device Details in a Pod Environment 20
CHAPTER 4
Network Configuration for Cisco UCS Director Baremetal Agent 21
Cisco UCS Director FlexPod Management Guide, Release 5.0
OL-32118-01
iii
Contents
About the Network Configuration Options 21
Single Network for Management and PXE 21
Prerequisites and Assumptions for a Single Network Configuration 22
Separate Networks for Management and PXE 22
Prerequisites and Assumptions for a Separate Network Configuration 23
Configuring the Baremetal Agent Appliance through the Cisco UCS Director GUI 24
Configuring the DHCP Server for a Baremetal Agent Appliance in Cisco UCS Director
GUI 26
CHAPTER 5
FlexPod Operations 29
Configuration Guidelines for FlexPod Operations 29
Creating an Organization 32
Configuring the Chassis/FEX Discovery Policy 32
Creating a UUID Pool 33
Creating a MAC Pool 34
Creating a WWNN Pool 34
Creating a WWPN Pool 35
Creating a Network Control Policy 35
Creating a vNIC Template 37
Creating a VSAN 41
Creating a vHBA Template 42
Creating a LAN Boot Policy 44
Creating a SAN Boot Policy 45
Creating a vNIC 48
Creating a vHBA 48
Creating a Network Policy 49
Creating a Storage Policy 51
CHAPTER 6
Orchestration Workflow Operations 53
Cisco UCS Manager Orchestration Tasks 53
Accessing Task Documentation 54
Navigating to a Predefined Orchestration Workflow 54
Provisioning a FlexPod Orchestration Workflow 55
Provisioning a Stateless Blade Server Orchestration Workflow for FlexPod 55
Modifying the Workflow Priority 56
Cisco UCS Director FlexPod Management Guide, Release 5.0
iv
OL-32118-01
Contents
Creating the Cisco UCS Service Profile Task 57
Configuring Storage Area Network Zoning 58
Adding a LUN Dataset Using OnCommand 60
Modifying the Cisco UCS Boot Policy LUN ID 61
Choosing the Cisco UCS Server 62
Associating the Cisco UCS Service Profile 63
Setting Up PXE Boot 64
Monitoring PXE Boot 66
Adding a VLAN to a Service Profile 67
Modifying the Cisco UCS Service Profile Boot Policy 68
Powering Off the Cisco UCS Server 69
Powering On the Cisco UCS Server 70
Registering the Host with vCenter 71
Adding Hosts to a Distributed Virtual Switch 72
Migrating a Default Virtual Switch to a Distributed Virtual Switch 73
Validating and Executing an Orchestration Workflow 75
CHAPTER 7
Troubleshooting 77
Troubleshooting Cisco UCS Director Connectivity 77
Troubleshooting Cisco UCS Director Baremetal Agent Connectivity 78
Cisco UCS Director FlexPod Management Guide, Release 5.0
OL-32118-01
v
Contents
Cisco UCS Director FlexPod Management Guide, Release 5.0
vi
OL-32118-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 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 FlexPod Management Guide, Release 5.0
OL-32118-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 FlexPod Management Guide, Release 5.0
viii
OL-32118-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 FlexPod Management Guide, Release 5.0
OL-32118-01
ix
Preface
Obtaining Documentation and Submitting a Service Request
Cisco UCS Director FlexPod Management Guide, Release 5.0
x
OL-32118-01
CHAPTER
1
New and Changed Information for this Release
This chapter contains the following section:
• New and Changed Information for this Release, page 1
New and Changed Information for this Release
The following table provides an overview of the significant changes to this guide for this current release. The
table does not provide an exhaustive list of all changes made to this guide or of all new features in this release.
Table 1: New Features and Changed Behavior in FlexPod, Release 5.0
Feature
Description
Where Documented
Secure Enclaves Architecture
Provides a standard approach for
About the Cisco Secure
application security and extends the
Enclaves Architecture, on
FlexPod infrastructure by integrating page 5
and enabling security technologies
uniformly, allowing application specific
policies to be consistently enforced.
Cisco Nexus 7000 Series switch
support.
Adds support for the Cisco Nexus 7000 System Requirements, on page
Series switches used in the SEA
6
implementation.
Cisco UCS Director FlexPod Management Guide, Release 5.0
OL-32118-01
1
New and Changed Information for this Release
New and Changed Information for this Release
Cisco UCS Director FlexPod Management Guide, Release 5.0
2
OL-32118-01
CHAPTER
2
Overview
This chapter contains the following sections:
• About FlexPod, page 3
• About NetApp C-Mode, page 4
• About the Cisco Secure Enclaves Architecture, page 5
• System Requirements, page 6
• FlexPod Implementation Overview, page 7
About FlexPod
FlexPod is an integrated hardware and software environment that you can use for virtualized and nonvirtualized
converged computing, networking, and storage solutions. You can use FlexPod for the following:
• Data centers that need high availability and scalable storage to reduce operating costs and to converge
the infrastructure so that it supports hybrid cloud computing.
• Interface to public cloud services.
• Purpose-built, high capacity platforms for specialized workloads where large-scale, real-time data
analytics place unique demands on compute stacks. You can also use FlexPod for video surveillance,
in-memory databases, and public cloud infrastructures.
Note
The hardware deployed for the FlexPod environment is highly modular and varies depending on the
specific FlexPod rack-mount scheme needed for each customer deployment. For more information, see
Cisco Validated Designs on the web.
The FlexPod environment has the following components:
• Cisco UCS Director and Cisco UCS Director Baremetal Agent that are installed and configured on either
a VMware vCenter host or Hyper-V host to standardize and simplify the configuration of networking,
storage, and security settings for multiple hosts and to monitor the host compliance. See the Cisco UCS
Director Installation Guide and Cisco UCS Director Baremetal Agent Setup Guide for more information.
Cisco UCS Director FlexPod Management Guide, Release 5.0
OL-32118-01
3
Overview
About NetApp C-Mode
• The FlexPod virtualization software, computing, and NetApp FAS storage components that are located
in one rack to provide scalable storage.
• Cisco Nexus components that provide routing and switching functionality.
• Cisco UCS Manager that provides unified, embedded management of all software and hardware
components in Cisco UCS Director including virtual machines (VMs). The following figure shows the
FlexPod hardware and software components.
Figure 1: FlexPod Hardware and Software Components
About NetApp C-Mode
FlexPod incorporates NetApp cluster-mode (C-mode) software functionality. C-mode defines an architecture
that is made of a group of connected NetApp storage controllers (nodes) that share a global namespace (GNS).
The physical NetApp storage controllers can have attached disk shelves, network interface cards (NICs), and
flash cards. Together, these components create a physical resource pool that is virtualized as a logical cluster
to provide data access. Cisco UCS Director is used to abstract and virtualize the physical equipment into
logical resources, which allow data operations to be moved in a nondisruptive way when needed.
NetApp C-mode has the following benefits:
Cisco UCS Director FlexPod Management Guide, Release 5.0
4
OL-32118-01
Overview
About the Cisco Secure Enclaves Architecture
• Scalability—C-Mode scales because it allows storage controllers to be added as the storage environment
grows without disruption to the resource pool that resides on a shared storage infrastructure. Host and
client connections and datastores can move anywhere in the resource pool, and existing workloads can
be balanced over the available resources. New workloads can also be deployed. Technology refreshes,
such as replacing disk shelves and adding or completely replacing storage controllers, can be accomplished
while the environment remains online and serving data.
• High availability (HA)—The HA node pair is redundantly configured to serve data in case one of the
nodes fails. Operations such as volume movement, node failover, and switch failure can be performed
without any disruption to the storage or applications. Storage failover protection is a core attribute of
C-Mode. HA pairs of controllers are the building blocks that form the storage cluster. This architecture
enables transparent controller clustering and failover capability in which a failed storage controller
causes its partner node to take over its disk arrays, volumes, and running services to provide continuous
operation. C-Mode can scale up linearly as the number of nodes increases. To attain high availability,
the layers in the setup also have the following redundant features:
◦Linear throughput scaling to multi-gigabytes per second.
◦Linear scale performance for a single volume with striping. A striped volume uses the free space
on more than one physical hard disk to create a bigger volume.
◦Linear scale read performance with load-sharing mirrors and collective read/write performance in
a single namespace.
• Flexibility—Storage operations increase flexibility as follows:
◦Accommodating any mix of Fibre Channel (FC) and serial advanced technology attachment (SATA)
drives.
◦Allowing nondisruptive data movement between tiers.
◦Transparently accessing volumes on any node from any node.
◦Connecting many volumes into a single namespace.
◦Moving volumes between nodes transparently.
◦Moving existing mailboxes to a different storage tier.
About the Cisco Secure Enclaves Architecture
The Secure Enclaves Architecture (SEA) is built using the Cisco Nexus switching platforms already included
in FlexPod, Cisco TrustSec, and the Cisco Adaptive Security Appliance (ASA) firewall software. SEA provides
a standard approach for application security and extends the FlexPod infrastructure by integrating and enabling
security technologies uniformly, allowing application specific policies to be consistently enforced. Through
the FlexPod infrastructure, SEA standardization to helps automate operations over the enterprise network
securely from users to applications they use.
SEA simplifies and standardizes the delivery of Cisco applications and security services in an architecturally
consistent pod environment. This pod environment helps many enterprises and IT service providers develop
cloud service offerings for public and private consumption in each of the following ways:
• Improves service quality through virtualization features.
• Helps customers to meet their application and business requirements.
Cisco UCS Director FlexPod Management Guide, Release 5.0
OL-32118-01
5
Overview
Managing Adaptive Security Appliances
• Automates well-known and well-understood resource pools of networking, computing, and storage
resources to provide operational efficiency and agility.
• Onboards services and applications to the cloud (pod).
• Hardens platforms and automates configuration, auditing, patching, and response security operations.
• Operates with regulatory compliance measures and certifications.
• Implements Cisco Adaptive Security Appliance (ASA) transparent mode through the configuration of
a transparent VLAN with Virtual Extensible LAN (VXLAN).
Managing Adaptive Security Appliances
Cisco UCS Director manages physical or virtual Adaptive Security Appliance (ASA or ASAv) contexts in
the Cisco Secure Enclaves Architecture (SEA). Each physical or virtual ASA has its own management IP
address for communication with the Cisco Identity Services Engine (ISE) policy manager. Cisco UCS Director
learns Cisco security group tags (SGTs) from the ISE policy manager, which authenticates and authorizes the
ASA. As a Cisco UCS Director administrator, you can choose an SGT label to classify a source within the
TrustSec domain switch interface (Cisco Nexus 1000V virtual port profile or Cisco Nexus 7000 series port).
SEA Deployment
See the Cisco-validated design document FlexPod Datacenter with Cisco Secure Enclaves for more information
about how SEA can be deployed in your FlexPod environment.
Note
SEA is not configured through Cisco UCS Director.
System Requirements
Component
Requirement
Networking
Two Cisco Nexus 5000/5500 Series or Cisco Nexus
7000 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
NetApp storage system. See the Compatibility Matrix
for all supported versions.
Cisco UCS Director
See the Compatibility Matrix for all supported
versions.
Cisco UCS Director FlexPod Management Guide, Release 5.0
6
OL-32118-01
Overview
FlexPod Implementation Overview
Component
Requirement
Cisco UCS Director Baremetal Agent
See the Compatibility Matrix for all supported
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) host or
Hyper-Vhost
See the Compatibility Matrix for all supported
versions.
FlexPod Implementation Overview
There are a variety of ways in which FlexPod can be implemented. This section describes the basic tasks
involved in a typical FlexPod implementation.
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Research and plan the configuration design that works best for your FlexPod Network. For more information on the
specific FlexPod designs created and validated by Cisco, called Cisco Validated Designs (CVDs), see the DesignZone
for FlexPod on the web.
Use the NetApp FlexPod Technical Specifications document to determine what hardware and network connectivity
requirements that you need for your FlexPod design.
Obtain licensing information for FlexPod or the individual devices or software in your implementation. For more
information, see the Cisco UCS Director Install and Upgrade Guides.
Install Cisco UCS Director and the Baremetal Agent on your VMware (vCenter Server/ESXI/ESXi, vSphere, or Microsoft
Hyper-V Manager) server. See the Cisco UCS Director Install and Upgrade Guides web page, for more information.
Add the FlexPod account using the task in the Initial Cisco UCS Director FlexPod Configuration chapter.
Connect devices to Cisco UCS Director to the network using the following tasks in the Initial Cisco UCS Director
FlexPod Configuration chapter:
a) Connect UCS Manager by adding an account.
b) Connect NetApp storage system(s).
c) Connect Cisco Nexus series switches.
Note
For more information on configuring UCS Manager, see Cisco UCS Director Management Guide for Cisco
UCS Manager on the web.
Cisco UCS Director FlexPod Management Guide, Release 5.0
OL-32118-01
7
Overview
FlexPod Implementation Overview
Step 7
Step 8
Step 9
Step 10
Use the Network Configuration for Cisco UCS Director Baremetal Agent chapter to connect Cisco UCS Director
BareMetal Agent to Cisco UCS Director, and configure the DHCP server parameters for single or separate networks for
management and the Preboot eXecution Environment (PXE).
Verify that Cisco UCS Director Baremetal Agent connects to Cisco UCS Director and that baremetal provisioning is on
the same network as Cisco UCS Director Baremetal Agent.
Use the FlexPod Operations chapter to create a top-level root organization, policies, pools, vNIC templates and so on.
Use the Orchestration Workflow Operations chapter to navigate to a predifined orchestration workflow, learn how a
predefined orchestration workflow can be configured, and how to validate a workflow once it has been configured. Go
to the Cisco Developed Integrations page for Cisco UCS Director workflows, which are added on a regular basis.
Cisco UCS Director FlexPod Management Guide, Release 5.0
8
OL-32118-01
CHAPTER
3
Initial Cisco UCS Director FlexPod Configuration
This chapter contains the following sections:
Note
The procedures in this chapter assume you are logged into Cisco UCS Director.
• Adding a Pod, page 9
• Cisco UCS Manager Accounts, page 10
• About Managing the NetApp Storage System, page 16
• Network Configuration, page 18
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 FlexPod Management Guide, Release 5.0
OL-32118-01
9
Initial Cisco UCS Director FlexPod 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:
• Flexpod
• Generic
• ExpressPod Medium
• VSPEX
• ExpressPod Small
• Vblock
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 bundled pod licenses (FlexPod, Vblock, and
VSPEX), which include the necessary individual device licenses to run a
pod, see the Cisco UCS Director Installation 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
Cisco UCS Director.
For an environment that does not include Cisco UCS Central, you create Cisco UCS Manager accounts in a
pod.
Cisco UCS Director FlexPod Management Guide, Release 5.0
10
OL-32118-01
Initial Cisco UCS Director FlexPod Configuration
Adding a Cisco UCS Manager Account
For an environment that includes Cisco UCS Central, you must create a Cisco UCS Central account under
multi-domain managers. All Cisco UCS domains that are registered with that Cisco UCS Central, and their
related Cisco UCS Manager accounts are brought into Cisco UCS Director when the Cisco UCS Central
account is created. You can assign one or more of those Cisco UCS Manager accounts from the Cisco UCS
Central account to a pod if needed. You can also register a Cisco UCS Manager account with a Cisco UCS
Central account.
Adding a Cisco UCS Manager Account
Before You Begin
Add the pod to which this Cisco UCS Manager account belongs.
Step 1
Step 2
Step 3
Step 4
On the menu bar, choose Administration > Physical Accounts.
Click the Physical Accounts tab.
Click Add.
In the Add Account dialog box, complete the following fields:
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 . This option is the default. If
you choose this option, all servers are added in the Managed state.
• Selected Servers—Only selected servers are managed. You can add
and remove servers from the managed server list as needed. If you
choose this option, all servers are added in the Unmanaged state.
Account Name field
A unique name that you assign to this account.
Cisco UCS Director FlexPod Management Guide, Release 5.0
OL-32118-01
11
Initial Cisco UCS Director FlexPod Configuration
Adding a Cisco UCS Manager Account
Name
Description
Server Address field
The IP address of Cisco UCS Manager. For a cluster configuration, this is
the virtual IP address.
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.
Cisco UCS Director tests the connection to Cisco UCS Manager. If that test is successful, it adds the Cisco
UCS Manager account and discovers all infrastructure elements in Cisco UCS Manager that are associated
with that account, including chassis, servers, fabric interconnects, service profiles, and pools. This discovery
process and inventory collection cycle takes approximately five minutes to complete.
The polling interval configured on the Administration > System > System Tasks tab specifies the frequency
of inventory collection.
Cisco UCS Director FlexPod Management Guide, Release 5.0
12
OL-32118-01
Initial Cisco UCS Director FlexPod Configuration
Testing the Connection to a Physical Account
Testing the Connection to a Physical Account
You can test the connection at any time after you add an account to a pod.
Step 1
Step 2
On the menu bar, choose Administration > Physical Accounts.
Click the tab for the type of account that you want to test.
For example, click the Physical Accounts tab or the Multi-Domain Managers tab.
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 the
username and password 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.
Cisco UCS Director FlexPod Management Guide, Release 5.0
OL-32118-01
13
Initial Cisco UCS Director FlexPod Configuration
Viewing the Topology and Connectivity of Devices in a Cisco UCS Domain
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:
• 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.
Cisco UCS Director FlexPod Management Guide, Release 5.0
14
OL-32118-01
Initial Cisco UCS Director FlexPod Configuration
Exporting the Configuration of a Cisco UCS Manager Account
Exporting the Configuration of a Cisco UCS Manager Account
Cisco UCS Director exports a file named Ucs-Timestamp-configuration.zip to the location
configured for downloads in your browser.
Step 1
Step 2
Step 3
Step 4
Step 5
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.
Step 6
In the Export UCS Configuration dialog box, click Submit.
Step 7
When the configuration export is complete, click Close.
Importing the Configuration of a Cisco UCS Manager Account
You can import a configuration that has been exported from a Cisco UCS Manager account in Cisco UCS
Director or from Cisco UCS Manager.
Note
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 for which you want to import the
configuration.
Click the Compute Accounts tab.
In the table, click the row of the account for which you want to import the configuration.
Click Import Configuration.
On the Upload Configuration screen of the Import UCS Configuration wizard, do the following:
a)
b)
c)
d)
Step 7
When you import a configuration into a Cisco UCS Manager account, you overwrite any existing
configuration in that account.
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.
Cisco UCS Director FlexPod Management Guide, Release 5.0
OL-32118-01
15
Initial Cisco UCS Director FlexPod Configuration
About Managing the NetApp Storage System
Step 8
Step 9
Option
Description
Customize Import
Imports only the configuration settings that you choose.
Click Submit.
When the configuration import is complete, click Close.
About Managing the NetApp Storage System
Cisco UCS Director supports the NetApp storage infrastructure. Cisco UCS Director provides auto-discovery,
monitoring, and complete visibility that enables you to manage all NetApp filer components. The NetApp
filer, also known as NetApp Fabric Attached Storage (FAS), is a type of disk storage device.
Cisco UCS Director enables you to monitor and manage various components of the NetApp storage system.
To manage the NetApp storage system, you need to add a pod and create a NetApp account.
NetApp has two types of accounts:
• OnCommand—Manages and monitors all NetApp appliances (filers and NetCache appliances) within
a network, by accessing global and detailed status reports of current and past activities. Cisco UCS
Director discovers all storage elements in the NetApp account, such as, aggregates, raid groups, disks,
volumes, LUNs, Qtrees, and so on. Typically, the discovery process takes about 5 minutes or within a
time interval that you configured in theSystem Tasks tab. To access the System Tasks tab, choose
Administration > System.
• Data ONTAP—Is an operating system used by the NetApp filer. NetApp provides two versions of Data
ONTAP: Data ONTAP 7G and Data ONTAP GX which is based upon grid technology.
◦Cluster mode—Defines an architecture that is made of a group of connected NetApp storage
controllers (nodes) that share a global namespace (GNS). The physical NetApp storage controllers
can have attached disk shelves, network interface cards (NICs), and flash cards. These components
create a physical resource pool that is virtualized as a logical cluster to provide data access. Cisco
UCS Director abstracts and virtualizes the physical equipment into logical resources, which allow
data operations to be moved in a nondisruptive way.
Adding a NetApp Account
NetApp has two types of accounts: NetApp ONTAP and NetApp OnCommand. While you are adding a
NetApp account, choose the required account type.
Note
You must manually configure an aggregate on the ONTAP filer before you can use the filer management
of Cisco UCS Director.
Cisco UCS Director FlexPod Management Guide, Release 5.0
16
OL-32118-01
Initial Cisco UCS Director FlexPod Configuration
Adding a NetApp Account
Before You Begin
Add the pod to which this NetApp account belongs.
Step 1
Step 2
Step 3
Step 4
On the menu bar, choose Administration > Physical Accounts.
Click the Physical Accounts tab.
Click Add.
In the Add Account dialog box, complete the following fields:
Name
Description
Pod drop-down list
Choose the pod to which this account belongs. Allowed pod types are
Default, Generic, and Flexpod.
Category Type drop-down list
Choose the category type. You must choose Storage. This is the type of
infrastructure for the account.
Account Type drop-down list
Choose one of the following account types that you want to use for this
account:
• NetApp ONTAP
• NetApp OnCommand
Account Name field
A unique name that you assign to this account.
Server Address field
The IP address of the NetApp server. For a cluster configuration, this is the
virtual IP address.
User ID field
The username that this account will use to access the NetApp server. This
username must be a valid account in the NetApp server.
Password field
The password associated with the username.
Transport Type drop-down list
Choose one of the following transport types that you want to use for this
account:
• http
• https
Port field
The port used to access the NetApp account.
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.
Cisco UCS Director FlexPod Management Guide, Release 5.0
OL-32118-01
17
Initial Cisco UCS Director FlexPod Configuration
Network Configuration
Step 5
Name
Description
Service Provider field
(Optional) The name of the service provider associated with this account,
if any.
Click Add.
Cisco UCS Director tests the connection to the NetApp server. If that test is successful, it adds the NetApp
account and discovers all infrastructure elements in the server that are associated with that account, including
the server's information, slots, processors, memory, and NICs. This discovery process and inventory collection
cycle takes few minutes to complete.
The polling interval configured on the System Tasks tab on the Administration > System window specifies
the frequency of inventory collection. For more information about configuring the polling interval, see the
Cisco UCS Director Network Devices Management Guide.
Network Configuration
Cisco UCS Director enables you to manage, orchestrate, and monitor multiple network devices and fabric
platforms from Cisco and select vendors:
• Cisco network and fabric support for Cisco Nexus switches.
• Brocade network and fabric support.
• Cisco UCS fabric interconnects that operate in the N-Port Virtualization (NPV) mode in which the server
Fibre Channel traffic is either manually or automatically pinned to a specific Fibre Channel over Ethernet
(FCoE) uplink.
Note
See Compatibility Matrix for Cisco UCS Director for more specific network support information.
Adding a Network Device to a Pod
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.
Cisco UCS Director FlexPod Management Guide, Release 5.0
18
OL-32118-01
Initial Cisco UCS Director FlexPod Configuration
Adding a Network Device to a Pod
Name
Description
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. This can be one of
the following:
• telnet
• ssh
Step 4
Step 5
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.
What to Do Next
Verify that the managed network devices are configured properly.
Cisco UCS Director FlexPod Management Guide, Release 5.0
OL-32118-01
19
Initial Cisco UCS Director FlexPod Configuration
Verifying Network Device Details in a Pod Environment
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 FlexPod Management Guide, Release 5.0
20
OL-32118-01
CHAPTER
4
Network Configuration for Cisco UCS Director
Baremetal Agent
This chapter contains the following sections:
• About the Network Configuration Options, page 21
• Single Network for Management and PXE, page 21
• Separate Networks for Management and PXE, page 22
• Configuring the Baremetal Agent Appliance through the Cisco UCS Director GUI, page 24
• Configuring the DHCP Server for a Baremetal Agent Appliance in Cisco UCS Director GUI, page 26
About the Network Configuration Options
You can choose between the following network configuration options for Cisco UCS Director Baremetal
Agent:
• Single network for management and PXE (Preboot Execution Environment)
• Separate networks for management and PXE
Choose the network configuration option that best meets the requirements of your environment. For advice
on this decision, refer to the high-level discussions in this chapter.
Single Network for Management and PXE
We recommend that you choose this network configuration option if your environment permits the following
to be hosted on the same network interface and Layer 2 network (see the following figure):
• Services provided by Cisco UCS Director Baremetal Agent, such as DHCP, TFTP, and HTTP
Cisco UCS Director FlexPod Management Guide, Release 5.0
OL-32118-01
21
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 virtual machines (VMs) can be attached to or leverage.
Separate Networks for Management and PXE
We recommend that you choose this network configuration option if your environment does not permit the
following to be hosted on the same network interface and layer 2 network:
• On the PXE network, services provided by Cisco UCS Director Baremetal Agent, such as DHCP, TFTP,
and HTTP
Cisco UCS Director FlexPod Management Guide, Release 5.0
22
OL-32118-01
Network Configuration for Cisco UCS Director Baremetal Agent
Prerequisites and Assumptions for a Separate Network Configuration
• On the Management network, traffic between Cisco UCS Director Baremetal Agent and Cisco UCS
Director or other devices and appliances
Figure 3: Sample Topology for Separate PXE and Management Networks
Prerequisites and Assumptions for a Separate Network Configuration
If you plan to configure Cisco UCS Director Baremetal Agent with a separate network configuration, ensure
that your environment meets the following prerequisites and assumptions:
• Cisco UCS Director has been installed and the network interface configured, as described in the
appropriate Cisco UCS Director installation guide.
• Cisco UCS Director is reachable through a web browser and you can log in.
• Cisco UCS Director Baremetal Agent has been installed, as described in the Cisco UCS Director Baremetal
Agent Installation and Configuration Guide and no additional configuration has been performed.
• The following networks are provisioned and available as a virtual port group or port profile that VMs
can be attached to or leverage:
◦Management (MGMT) network—Used for traffic between Cisco UCS Director Baremetal Agent
and Cisco UCS Director
◦PXE network—Used for PXE services traffic, such as DHCP, HTTP, and TFTP
Cisco UCS Director FlexPod Management Guide, Release 5.0
OL-32118-01
23
Network Configuration for Cisco UCS Director Baremetal Agent
Configuring the Baremetal Agent Appliance through the Cisco UCS Director GUI
Note
The PXE network/VLAN must be configured as the native, or default, VLAN on the server. For example,
for a Cisco UCS Director server, edit the vNIC template associated with the server and choose the PXE
network/VLAN as the native VLAN. You can perform this configuration in Cisco UCS Manager or Cisco
UCS Director.
Configuring the Baremetal Agent Appliance through the Cisco
UCS Director GUI
At this point, you have two options when you create a new Baremetal Agent:
• Use a single network for both management and PXE traffic.
• Use separate networks: one for management and another for PXE traffic.
Before You Begin
The BMA 5.0 ovf must be deployed and its network must be configured.
Cisco UCS Director 5.0 Multi-Node configuration must be completed.
You must have created VMs in the VMware vSphere hypervisor. The network must be configured, the
Baremetal Agent VM must be completely booted up, and the VMware vSphere VM Console must be closed.
You have the IP address of the Baremetal Agent VM.
You must have an environment that supports the network configuration you intend to use: either the single
network or the separate network configuration. Refer as necessary to the topics in this documentation set that
explain these different configurations.
To provide required DHCP services, locate one DHCP server in the same PXE VLAN as Cisco UCS Director
Baremetal Agent and configure that DHCP server with an appropriate IP address range.
To use Cisco UCS Director Baremetal Agent to PXE boot a given operating system, you must first provision
that operating system image.
Step 1
Step 2
Step 3
Step 4
On the Menu bar, chooseAdministration > Physical Accounts
Click the Baremetal Agents tab.
Click Add.
In the Add Baremetal Agent Appliance dialog box, complete the appropriate fields as described in the following table:
To configure Cisco UCS Director Baremetal Agent for multi-node capabilities, set the UCSD Database Address to use
the InventoryNode IP address. See the entry in the table below.
Cisco UCS Director FlexPod Management Guide, Release 5.0
24
OL-32118-01
Network Configuration for Cisco UCS Director Baremetal Agent
Configuring the Baremetal Agent Appliance through the Cisco UCS Director GUI
Name
Description
BMA Name field
The name you assign to the Bare Metal Agent for a given
purpose. As a best practice, apply a naming convention
that includes the names of the managed system components.
This will enable you to recognize the constraints and
capabilities of the agent.
BMA Management /PXE Address field
The IP address of the BMA manager. If you are using a
single network for both BMA manager and the PXE, then
this same address will automatically be assigned as the
PXE address.
Important
This address must be reachable from the
UCSD appliance.
Login ID field
The Login ID for the Baremetal Agent administrator.
Password field
The Password for the same Baremetal Agent administrator.
BMA uses Different Interfaces for Management and
PXE Traffic checkbox
Check this box if you want the network hosting the PXE
server to be separate from the network hosting the traffic
manager.
Note
If you check this box, a different set of fields will
appear in this form below the checkbox.
BMA PXE Interface Address field
The IP address for the BMA PXE server, if different from
the address of the BMA manager.
Note
This field appears only if the BMA uses Different
Interfaces... checkbox above has been selected.
Description field
Additional useful information about this Baremetal agent.
Optional.
Location field
Location of this Baremetal agent. A physical location name,
for example. Optional.
UCSD Database Address drop-down list
Choose the IP address associated with the UCSD database
that this BMA is going to use.
Attention
Step 5
If you are configuring BMA for multi-node
capabilities, select the InventoryNode IP
address.
Click Submit.
Troubleshooting Tips
Be aware that the first BMA defined in Cisco UCS Director Baremetal Agent is automatically labeled as the Default
BMA.
Cisco UCS Director FlexPod Management Guide, Release 5.0
OL-32118-01
25
Network Configuration for Cisco UCS Director Baremetal Agent
Configuring the DHCP Server for a Baremetal Agent Appliance in Cisco UCS Director GUI
Step 6
A new row appears in the Baremetal Agents tab, showing current information for this agent.
Initiate BMA services by clicking Start Services.
If the DHCP sever is not correctly configured, the status displayed in the Enabled Services column will indicate that
services are not enabled.
BMA status will become "active" once the network services are started correctly.
The first BMA created with Release 5.0 or later will be designated as the "Default" BMA. By default, the
Default BMA will be used as the target BMA for the Setup PXE Boot task, if you use this task in a Workflow.
To designate a different BMA as the Default, select it in the Baremetal Agents tab and click Set Default
BMA.
What to Do Next
Check the service status by clicking Service Status.
To see the SSH-based test connection status with the BMA, check the Baremetal Agents table column labeled
Reachable. By default, a test Connection request is triggered every 15 minutes. This frequency can be adjusted
by using the "BMA Heartbeat Task".
To check the BMA log, click View BMA logs.
To check for Cisco UCS Director Baremetal Agent database updates by BMA, check the Baremetal Agents
table column labeled Status. If there is no update in the database then the status will be "Inactive"
To configure a PXE interface IP address, click Configure Interface.
Optional: Test by using the agent to perform a PXE boot in a controlled test environment. For details about
setting up the PXE Boot request, see the documentation about "Adding and Configuring PXE Boot Requests".
Configuring the DHCP Server for a Baremetal Agent Appliance
in Cisco UCS Director GUI
The DHCP server and the TFTP server are the crucial components of a PXE server. This configuration feature
reads the DHCP configuration from the BMA appliance and enables you to edit the configuration. You use
the BMA option titled Configure DHCP to edit configuration data that applies to the DHCP subnet, netmask,
bootp, router, and PXE server.
Note
If you are configuring the DHCP service for the first time, or you have made a change in the DHCP
configuration, be aware you must click Start Services to start or re-start the DHCP. The current status of
the services appears in the Enabled Services column in Baremetal Agents tab.
Restriction
For a multi-home DHCP configuration, you can use the Configure DHCP option to edit only the first
subnet information. For the remaining subnets, you must manually edit the DHCP configuration file
(/etc/dhcpd.conf).
Cisco UCS Director FlexPod Management Guide, Release 5.0
26
OL-32118-01
Network Configuration for Cisco UCS Director Baremetal Agent
Configuring the DHCP Server for a Baremetal Agent Appliance in Cisco UCS Director GUI
Before You Begin
• The BMA 5.0 ovf must be deployed and its network must be configured.
• Cisco UCS Director 5.0 Multi-Node configuration must be completed.
• You must have one DHCP server in the same PXE VLAN as theCisco UCS Director Baremetal Agent,
and this DHCP server must be configured with an appropriate IP address range.
Step 1
Step 2
On the Menu bar, choose Administration > Physical Accounts > Baremetal Agents
Select a Baremetal Agent and click Configure DHCP.
The Configure DHCP dialog box appears. This form contains the default DHCP configuration available in the BMA.
Tip
The PXE Server IP address should be the same PXE interface address that you specify when adding the BMA
account.
Step 3
Update or otherwise modify the DHCP configuration data, as appropriate, and click Submit.
All the DHCP IP address assignments shown in the dialog box will be updated in the BMA DHCP configuration and
the DHCP service will be restarted.
Step 4
Step 5
Select the BMA account just added and click Start Services.
After the services have started, verify that the status of the account is set to Active, and that the Enable Services column
indicates that all expected services are running.
What to Do Next
At this point, if you have a Baremetal agent defined to use the PXE server that you have just configured, click
Start Services to start the services that comprise your PXE server. This results in a change in the protocol
status. Details are displayed in the Enabled Services column. To edit or delete configuration data, click Stop
Services first.
Cisco UCS Director FlexPod Management Guide, Release 5.0
OL-32118-01
27
Network Configuration for Cisco UCS Director Baremetal Agent
Configuring the DHCP Server for a Baremetal Agent Appliance in Cisco UCS Director GUI
Cisco UCS Director FlexPod Management Guide, Release 5.0
28
OL-32118-01
CHAPTER
5
FlexPod Operations
This chapter contains the following sections:
• Configuration Guidelines for FlexPod Operations, page 29
Configuration Guidelines for FlexPod Operations
The following table provides Cisco UCS Director guidelines for implementing FlexPod operations. The
configuration notes explain important configuration details related to each task in this chapter.
Tip
For more information related to the following tasks, 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 32
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).
Cisco UCS Director FlexPod Management Guide, Release 5.0
OL-32118-01
29
FlexPod Operations
Configuration Guidelines for FlexPod Operations
Task
Configuration Notes
Creating a WWNN Pool, on page 34 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 35
Create the network control policy with the Cisco Discovery Protocol
(CDP) enabled.
Creating a vNIC Template, on page
37
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 Preboot Execution Environment (PXE) server and
the Cisco UCS server are in separate VLANs, you must
create separate vNIC templates for both servers in each
fabric interconnect.
Create a virtual storage area network (VSAN) for each fabric
interconnect. For example, fabric interconnect A and B.
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
Cisco UCS Director FlexPod Management Guide, Release 5.0
30
OL-32118-01
FlexPod Operations
Configuration Guidelines for FlexPod Operations
Task
Configuration Notes
Creating a vNIC, on page 48
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 48
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
49
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
Creating a Storage Policy, on page
51
If the PXE server and the Cisco UCS server are in separate
VLANs, you must create separate vNIC templates for both
servers in each fabric interconnect.
Follow the instructions in the task and use the following configuration
guidelines:
• From the SAN Connectivity Type drop-down list, choose
Expert.
• From the WWNN Pool drop-down list, choose the WWNN
pool that you created previously.
• In the Add vHBA field, specify the number of vHBAs (for
each fabric interconnect) that you want to add to the storage
policy.
• From the Template For vHBA1/vHBA2/vHBA3/vHBA4
drop-down list, choose the vHBA template that you created.
Note
Deploying the Secure Enclave
Architecture for FlexPod
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.
Use this information to optionally deploy Secure Enclosures
Architecture (SEA) in your FlexPod environment.
Cisco UCS Director FlexPod Management Guide, Release 5.0
OL-32118-01
31
FlexPod Operations
Creating an Organization
Creating an Organization
You can create a top-level organization which is the root. The policies and pools created in this root are
system-wide and are available to all organizations in the system.
Step 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.
Configuring the Chassis/FEX Discovery Policy
A chassis policy is configured to specify how the system reacts when a new chassis is added.
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-down list, choose the minimum threshold for the number of links between the chassis or Fabric
Extender (FEX) and the fabric interconnect:
• 1-link
• 2-link
• 4-link
• 8-link
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.
Cisco UCS Director FlexPod Management Guide, Release 5.0
32
OL-32118-01
FlexPod Operations
Creating a UUID Pool
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.
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.
Cisco UCS Director FlexPod Management Guide, Release 5.0
OL-32118-01
33
FlexPod Operations
Creating a MAC Pool
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.
Creating a WWNN 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 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.
Cisco UCS Director FlexPod Management Guide, Release 5.0
34
OL-32118-01
FlexPod Operations
Creating a WWPN Pool
Step 8
Name
Description
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
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 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.
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
Cisco UCS Director FlexPod Management Guide, Release 5.0
OL-32118-01
35
FlexPod Operations
Creating a Network Control Policy
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
Action on Uplink Fail drop-down list
Choose how the virtual interface (VIF) behaves if no uplink
port is available when the fabric interconnect is in end-host
mode. This can be one of the following:
• Link Down—Changes the operational state of a vNIC
to down when uplink connectivity is lost on the fabric
interconnect, and enables a fabric failover for vNICs.
• Warning—Maintains server-to-server connectivity
even when no uplink port is available, and disables
a fabric failover when uplink connectivity is lost on
the fabric interconnect.
The default is Link Down.
Note
If your implementation includes those types of
non-VM-FEX capable converged network adapters
and the adapter is expected to handle both Ethernet
and FCoE traffic, we recommend that you
configure the Action on Uplink Fail property with
a value of Warning. Note that this configuration
might result in an Ethernet teaming driver not
being able to detect a link failure when the border
port goes down.
Cisco UCS Director FlexPod Management Guide, Release 5.0
36
OL-32118-01
FlexPod Operations
Creating a vNIC Template
Name
Description
Forge drop-down list
Choose whether forged MAC addresses are allowed or
denied when packets are sent from the server to the fabric
interconnect. This can be one of the following:
• Allow—All server packets are accepted by the fabric
interconnect, regardless of the MAC address
associated with the packets.
• Deny—After the first packet has been sent to the
fabric interconnect, all other packets must use the
same MAC address or they will be silently rejected
by the fabric interconnect. This option enables port
security for the associated vNIC.
If you plan to install VMware ESX on the associated server,
you must configure MAC Security to allow for the network
control policy applied to the default vNIC. If you do not
configure MAC Security to Allow, the ESX installation
might fail because the MAC Security permits only one
MAC address while the installation process requires more
than one MAC address.
Step 8
Click Submit.
Creating a vNIC Template
Before You Begin
One or more of the following resources must already exist:
• Named VLAN
• MAC pool
• QoS policy
• LAN pin group
Cisco UCS Director FlexPod Management Guide, Release 5.0
OL-32118-01
37
FlexPod Operations
Creating a vNIC Template
• 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.
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.
Cisco UCS Director FlexPod Management Guide, Release 5.0
38
OL-32118-01
FlexPod Operations
Creating a vNIC Template
Name
Description
Target check boxes
If checked, the target that you choose determines whether
a VM-FEX port profile is automatically created with the
appropriate settings for the vNIC template. This can be one
of the following:
• Adapter—The vNICs apply to all adapters. No
VM-FEX port profile is created if you choose this
option.
• VM—The vNICs apply to all virtual machines. A
VM-FEX port profile is created if you choose this
option.
Template Type drop-down list
Choose the type of template. This can be one of the
following:
• Initial Template—vNICs created from this template
are not updated if the template changes.
• Updating Template—vNICs created from this
template are updated if the template changes.
Step 8
In the VLANs area, do the following to select the VLAN to be assigned to vNICs created from this template:
a) Click Add.
b) In the Add Entry to VLANs dialog box, complete the following fields and click Submit:
• 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
MAC Pool drop-down list
If the vNIC template has an associated QoS policy,
the MTU specified here must be equal to or less
than the MTU specified in the associated QoS
system class. If this MTU value exceeds the MTU
value in the QoS system class, packets might be
dropped during data transmission.
Choose the MAC address pool that vNICs created from
this vNIC template should use.
Cisco UCS Director FlexPod Management Guide, Release 5.0
OL-32118-01
39
FlexPod Operations
Creating a vNIC Template
Name
Description
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.
VNIC Template Connection Policy drop-down list
Choose the collection policy that vNICs created from this
template should use. It can be one of the following:
• Dynamic Policy
• usNIC Policy
• VMQ Policy
Only usNIC and VM connection policies created in Cisco
UCS Manager are displayed in this drop-down list.
Note
usNIC Template Connection Policy drop-down list
This field is available only with Cisco UCS
Manager Release 2.2.
Choose the usNIC collection policy that vNICs created
from this vNIC template should use.
This field is visible only if you choose usNIC Policy as
the VNIC Template connection policy.
VMQ Template Connection Policy drop-down list
Choose the VM collection policy that vNICs created from
this vNIC template should use.
This field is visible only if you choose VMQ Policy as the
VNIC Template connection policy.
Step 10
Click Submit.
What to Do Next
Include the vNIC template in a network policy.
Cisco UCS Director FlexPod Management Guide, Release 5.0
40
OL-32118-01
FlexPod Operations
Creating a VSAN
Creating a VSAN
Note
Fibre Channel over Ethernet (FCoE) VLANs in the SAN cloud and VLANs in the LAN cloud must have
different IDs. Using the same ID for an FCoE VLAN in a VSAN and a VLAN results in a critical fault
and traffic disruption for all vNICs and uplink ports using that FCoE VLAN. Ethernet traffic is dropped
on any VLAN that has an ID that overlaps with an FCoE VLAN ID.
Step 1
Step 2
Step 3
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.
Step 4
Step 5
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 the VSAN should be configured. This can be
one of the following:
• Common/Global—The VSAN maps to the same
VSAN ID in all available fabrics.
• Fabric A—The VSAN maps to a VSAN ID that
exists only in fabric A.
• Fabric B—The VSAN maps to a VSAN ID that
exists only in fabric B.
Cisco UCS Director FlexPod Management Guide, Release 5.0
OL-32118-01
41
FlexPod Operations
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 Configuring a VSAN for Fibre Channel Zoning.
Creating a vHBA Template
Before You Begin
One or more of the following resources must already exist:
• VSAN
• WWPN pool
• SAN pin group
• Statistics threshold policy
Step 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.
Description field
A description for the policy.
Cisco UCS Director FlexPod Management Guide, Release 5.0
42
OL-32118-01
FlexPod Operations
Creating a vHBA Template
Name
Description
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 FlexPod Management Guide, Release 5.0
OL-32118-01
43
FlexPod Operations
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.
Boot Mode drop-down list
The boot mode for the servers that use this boot policy. It
can be one of the following:
• Legacy
• UEFI
With this option, you can specify second-level boot
devices and you can enable the secure boot option.
Cisco UCS Director FlexPod Management Guide, Release 5.0
44
OL-32118-01
FlexPod Operations
Creating a SAN Boot Policy
Name
Description
Boot Security check box
Enables the secure boot option for the servers that use this
boot policy.
This option is visible only when UEFI is selected as the
boot mode.
Step 8
Step 9
Step 10
Step 11
Step 12
Step 13
Step 14
In the Add Boot Device area, check the Add LAN Boot check box.
In the Primary vNIC field, enter the name of the vNIC that you want to use as the first address defined for the LAN
boot location.
In the Secondary vNIC field, enter the name of the vNIC that you want to use as the second address defined for the
LAN boot location.
In the Add Boot Device area, check the Add iSCSI Boot check box.
In the Add Primary iSCSI Vnic field, enter the name of the iSCSI VNIC that you want to use as the first address defined
for the LAN boot location.
In the Add Secondary iSCSI Vnic field, enter the name of the iSCSI VNIC that you want to use as the second address
defined for the LAN boot location.
Click Submit.
Creating a SAN Boot Policy
Tip
We recommend that the boot order in a boot policy include either a local disk or a SAN LUN, but not
both, to avoid the possibility of the server booting from the wrong storage type. If you configure a local
disk and a SAN LUN for the boot order storage type and the operating system or logical volume manager
(LVM) is configured incorrectly, the server might boot from the local disk rather than the SAN LUN.
For example, on a server with Red Hat Linux installed, where the LVM is configured with default LV
names and the boot order is configured with a SAN LUN and a local disk, Linux reports that there are
two LVs with the same name and boots from the LV with the lowest SCSI ID, which could be the local
disk.
Cisco UCS Director FlexPod Management Guide, Release 5.0
OL-32118-01
45
FlexPod Operations
Creating a SAN Boot Policy
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.
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.
Boot Mode drop-down list
The boot mode for the servers that use this boot policy. It
can be one of the following:
• Legacy
• UEFI
With this option, you can specify second-level boot
devices and you can enable the secure boot option.
Cisco UCS Director FlexPod Management Guide, Release 5.0
46
OL-32118-01
FlexPod Operations
Creating a SAN Boot Policy
Name
Description
Boot Security check box
Enables the secure boot option for the servers that use this
boot policy.
This option is visible only when UEFI is selected as the
boot mode.
Step 8
Step 9
Step 10
Step 11
Step 12
Step 13
Step 14
Step 15
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.
In the Add Boot Device area, check the Add iSCSI Boot check box.
In the Add Primary iSCSI Vnic field, enter the name of the iSCSI VNIC that you want to use as the first address defined
for the SAN boot location.
In the Add Secondary iSCSI Vnic field, enter the name of the iSCSI VNIC that you want to use as the second address
defined for the SAN boot location.
Click Submit.
Cisco UCS Director FlexPod Management Guide, Release 5.0
OL-32118-01
47
FlexPod Operations
Creating a vNIC
Creating a vNIC
Step 1
Step 2
Step 3
Step 4
On the menu bar, choosePolicies > Physical Infrastructure Policies > UCS Manager.
Click the vNIC tab.
Click Add.
In the Create vNIC dialog box, complete the following fields to specify the Cisco UCS connections for the vNIC:
Name
Description
vNIC Name field
The unique name 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.
vNIC Template drop-down list
Choose the vNIC template that you want to assign to this vNIC.
Adapter Policy drop-down list
Choose one of the following Ethernet adapter policies:
• Default
• Windows
• VMware
• Linux
Step 5
Click Submit.
What to Do Next
Include this vNIC in a network policy.
Creating a vHBA
Step 1
Step 2
Step 3
Step 4
On the menu bar, choosePolicies > Physical Infrastructure Policies > UCS Manager.
Click the vHBA tab.
Click Add.
In the Create vHBA dialog box, complete the following fields to specify the Cisco UCS connections for the vHBA:
Cisco UCS Director FlexPod Management Guide, Release 5.0
48
OL-32118-01
FlexPod Operations
Creating a Network Policy
Name
Description
vHBA Name field
The unique name for the vHBA.
UCS Account Name drop-down list Choose the Cisco UCS Manager account to which you want to add this vHBA.
UCS Organization Name
drop-down list
Choose the Cisco UCS organization to which you want to add this vHBA.
vHBA Template drop-down list
Choose the vHBA template that you want to assign to this vHBA.
Adapter Policy drop-down list
Choose one of the following Ethernet adapter policies:
• Default
• Windows
• VMware
• Linux
Step 5
Click Submit.
What to Do Next
Include this vHBA in a storage policy.
Creating a Network Policy
Step 1
Step 2
Step 3
Step 4
On the menu bar, choosePolicies > Physical Infrastructure Policies > UCS Manager.
Click the Network Policy tab.
Click Add.
In the Add Network Policy dialog box, complete the following fields:
Name
Description
Policy Name field
The name of the policy.
Policy Description field
The description of 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.
Cisco UCS Director FlexPod Management Guide, Release 5.0
OL-32118-01
49
FlexPod Operations
Creating a Network Policy
Name
Description
Dynamic vNIC Connection Policy Choose a dynamic vNIC connection policy if the policy is being assigned to
drop-down list
service profiles for servers that support dynamic vNICs.
LAN Connectivity Type drop-down Choose one of the following connectivity types:
list
• Expert—
Allows you to create an unlimited number of vNICs that the server can use
to access the LAN.
• Simple—Allows you to create a maximum of two vNICs that the server
can use to access the LAN.
• No vNICs—Does not allow you to create any vNICs. If you choose this
option, any server associated with a service profile that includes this policy
is not connected to the LAN.
• Hardware Inherited—Uses the vNICs assigned to the Ethernet adapter
profile associated with the server.
• Use LAN Connectivity Policy—Uses a LAN connectivity policy to
determine the LAN connectivity for the server.
Step 5
If you chose the Expert LAN option, do the following:
a) In the Add vNIC field, specify the number of vNICs that you want to add to the network policy.
b) From the Template For vNIC1/vNIC2/vNIC3/vNIC4 drop-down list, choose a vNIC template.
c) Go to Step 8.
Step 6
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) Go to Step 8.
Step 7
Step 8
If you chose the Use LAN Connectivity Policy option, choose the policy that you want to associate with the server from
the LAN Connectivity Policy drop-down list.
Click Submit.
Cisco UCS Director FlexPod Management Guide, Release 5.0
50
OL-32118-01
FlexPod Operations
Creating a Storage Policy
What to Do Next
Include the network policy in a service profile.
Creating a Storage Policy
Step 1
Step 2
Step 3
Step 4
Step 5
On the menu bar, choosePolicies > Physical Infrastructure Policies > UCS Manager.
Click the Storage Policy tab.
Click Add.
enter a name and description for the policy.
In the Add Storage Policy dialog box, complete the following fields to specify the Cisco UCS connections for the storage
policy:
Name
Description
Policy Name field
The unique name for the storage policy.
Policy description field
The description for the storage policy.
UCS Account Name drop-down list Choose the Cisco UCS Manager account to which you want to add this storage
policy.
UCS Organization Name
drop-down list
Choose the Cisco UCS organization to which you want to add this storage policy.
Local Disk Configuration Policy
drop-down list
Choose the local disk configuration policy that you want to include in this storage
policy.
SAN Connectivity Type drop-down Choose one of the following connectivity types:
list
• Expert—Allows you to create an unlimited number of vHBAs that the
server can use to access SAN storage.
• Simple—Allows you to create a maximum of two vHBAs that the server
can use to access SAN storage.
• No vHBAs—Does not allow you to create any vHBAs. If you choose this
option, any server associated with a service profile that includes this policy
is not connected to SAN.
• Hardware Inherited—Uses the vHBAs assigned to the Fibre Channel
adapter profile associated with the server.
• Use SAN Connectivity Policy—Uses a SAN connectivity policy to
determine the SAN connectivity for the server.
Step 6
If you chose the Expert SAN storage option, do the following:
Cisco UCS Director FlexPod Management Guide, Release 5.0
OL-32118-01
51
FlexPod Operations
Creating a Storage Policy
a) From the WWNN Pool drop-down list, choose the WWNN pool that you want to assign to this policy.
The WWNN pool must contain a sufficient number of WWNNs to assign a WWNN to each server that is associated
with a service profile that uses this storage policy.
b) In the Add vHBA field, specify the number of vHBAs that you want to add to the storage policy.
c) From the Template For vHBA1/vHBA2/vHBA3/vHBA4 drop-down list, choose a vHBA template.
d) Go to Step 9.
Step 7
If you chose the Simple SAN storage option, do the following:
a) From the WWNN Pool drop-down list, choose the WWNN pool that you want to assign to this policy.
The WWNN pool must contain a sufficient number of WWNNs to assign a WWNN to each server that is associated
with the service profile that uses this storage policy.
b) In the vHBA0 (Fabric A) area, complete the following fields:
• In the vHBA0 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) Go to Step 9.
Step 8
Step 9
If you chose the Use SAN Connectivity Policy option, choose the policy that you want to associate with the server from
the SAN Connectivity Policy drop-down list.
Click Submit.
What to Do Next
Include the storage policy in a service profile.
Cisco UCS Director FlexPod Management Guide, Release 5.0
52
OL-32118-01
CHAPTER
6
Orchestration Workflow Operations
This chapter contains the following sections:
• Cisco UCS Manager Orchestration Tasks, page 53
• Navigating to a Predefined Orchestration Workflow, page 54
• Provisioning a FlexPod Orchestration Workflow, page 55
• Validating and Executing an Orchestration Workflow, page 75
Cisco UCS Manager Orchestration Tasks
Cisco UCS Director includes orchestration features that allow you to automate configuration and management
of tasks performed by Cisco UCS Manager in one or more workflows. The same workflow can include Cisco
UCS Manager, network, and storage tasks. For an example of a workflow, see the example presented in this
chapter.
For more information about orchestration in Cisco UCS Director, see the Cisco UCS Director Orchestration
Guide.
Location of Orchestration Tasks
A complete list of the Cisco UCS Manager orchestration tasks is available in the Workflow Designer, in the
Task Library and the Cisco UCS Tasks folder. The Task Library includes a description of the orchestration
tasks, and can be accessed from the following locations in Cisco UCS Director:
• Policies > Orchestration > Workflows
• http://IP_address/app/cloudmgr/onlinedocs/cloupiaTaskLib.html where
IP_address is the IP address of Cisco UCS Director.
Types of Orchestration Tasks
The Cisco UCS Manager orchestration tasks include tasks to configure and manage the following:
• Servers
• Server boot
Cisco UCS Director FlexPod Management Guide, Release 5.0
OL-32118-01
53
Orchestration Workflow Operations
Accessing Task Documentation
• Pools
• Policies
• VLANs
• vNICs
• Service profiles
• Service profile templates
• Organizations
Accessing Task Documentation
Step 1
Step 2
Step 3
Step 4
On the menu bar, choose Policies > Orchestration.
Click the Task Library icon.
Check the Regenerate document checkbox to view a list of all new tasks and those by open automation.
Click Submit.
The orchestration task library appears. Click on an entry to reveal more information regarding specific inputs and outputs
that are available.
Navigating to a Predefined Orchestration Workflow
You can navigate to your orchestration workflow in Cisco UCS Director. You can use several common
workflows that already exist to execute common administration and provisioning tasks with the fewest mouse
clicks. The procedure below describes how to access the Workflow Designer and create workflows from
individual tasks. You can also execute a workflow by right-clicking on it and choosing Execute now.
Note
This task assumes that your orchestration workflow was created for your environment. For more
information, see the Configuring Cisco UCS Server Pools and Policies chapter of the Cisco UCS Director
Management Guide for Cisco UCS Manager.
Step 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 FlexPod Management Guide, Release 5.0
54
OL-32118-01
Orchestration Workflow Operations
Provisioning a FlexPod Orchestration Workflow
Provisioning a FlexPod Orchestration Workflow
The following stateless blade server orchestration workflow example is provided to show how a pre-defined
orchestration workflow in Cisco UCS Director can be provisioned in your FlexPod implementation. It is
beyond the scope of this document to discuss all the orchestration workflows that are available for FlexPod.
Go to the Cisco Developed Integrations page for FlexPod workflows, which are added on a regular basis.
Provisioning a Stateless Blade Server Orchestration Workflow for FlexPod
The following table provides an overview for configuring the FlexPod 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. See Validating and Executing an Orchestration Workflow, on page 75 for more
information.
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.
Task Name
Task Type
Section
WF Priority
2352. Modify Workflow Priority
Modifying the Workflow
Priority, on page 56
CreateUCSServiceProfile_2034
2359. Create UCS Service Profile
Creating the Cisco UCS
Service Profile Task, on page
57
Task25
2349. Configure SAN Zoning
Configuring Storage Area
Network Zoning, on page 58
ProvisionLUN
2357. Add LUN to Dataset using
OnCom...
Adding a LUN Dataset Using
OnCommand, on page 60
Update Boot Policy with LUN
2354. Modify UCS Boot Policy LUN
ID
Modifying the Cisco UCS
Boot Policy LUN ID, on page
61
Task536
2353. Select UCS Server
Choosing the Cisco UCS
Server, on page 62
Cisco UCS Director FlexPod Management Guide, Release 5.0
OL-32118-01
55
Orchestration Workflow Operations
Provisioning a Stateless Blade Server Orchestration Workflow for FlexPod
Task Name
Task Type
Section
Associate SP
2344. Associate UCS Service Profile
Associating the Cisco UCS
Service Profile, on page 63
PXE Boot Setup
2351. Set up PXE Boot
Setting Up PXE Boot, on page
64
Power ON Blade
2345. Power On UCS Server
Powering On the Cisco UCS
Server, on page 70
Wait for PXE Boot
2348. Monitor PXE boot
Monitoring PXE Boot, on
page 66
AddVLANtoServiceProfile_2036 2361. Add VLAN to Service Profile
Adding a VLAN to a Service
Profile, on page 67
Modify UCS Service Profile
BootPolicy
2463. Modify UCS Service Profile Boot Modifying the Cisco UCS
Policy
Service Profile Boot Policy,
on page 68
Task29
2350. Power Off UCS Server
Powering Off the Cisco UCS
Server, on page 69
Power ON
2347. Power On UCS Server
Powering On the Cisco UCS
Server, on page 70
RegisterHostwithvCenter_954
2355. Register Host with vCenter
Registering the Host with
vCenter, on page 71
AddHoststodvSwitch_955
2356. Add Hosts to dvSwitch
Adding Hosts to a Distributed
Virtual Switch, on page 72
MigrateDefaultvSwitchtoDVSwitch_198X 2358. Migrate Default vSwitch to
dvSwitch
Migrating a Default Virtual
Switch to a Distributed Virtual
Switch, on page 73
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.
Cisco UCS Director FlexPod Management Guide, Release 5.0
56
OL-32118-01
Orchestration Workflow Operations
Provisioning a Stateless Blade Server Orchestration Workflow for FlexPod
Name
Description
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.
Creating the Cisco UCS Service Profile 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 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.
Cisco UCS Director FlexPod Management Guide, Release 5.0
OL-32118-01
57
Orchestration Workflow Operations
Provisioning a Stateless Blade Server Orchestration Workflow for FlexPod
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.
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.
The following parameters are configurable:
Name
Description
Organization button
The management organization name. For example, FlexPod-Mgmt.
UUID Assignment drop-down list
Choose the UUID assignment pool. For example, CL_UUID_Pool.
Storage Policy drop-down list
Choose the storage policy name. For example, FlexPod_SP.
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 Storage Area Network Zoning
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 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 SAN zoning task name is entered. For example, Task25.
Task Category drop-down list
The Network Tasks category is chosen.
Task Type drop-down list
The 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.
Cisco UCS Director FlexPod Management Guide, Release 5.0
58
OL-32118-01
Orchestration Workflow Operations
Provisioning a Stateless Blade Server Orchestration Workflow for FlexPod
Step 2
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 identity. For example,
CreateUCSServiceProfile_2034.SERVICE_PROFILE_IDENTITY.
UCS Account Name drop-down list Choose the UCS account name. For example,
CreateUCSServiceProfile_2034.ACCOUNT_NAME.
Select Service Profile drop-down list Choose the UCS service profile name. For example,
CreateUCSServiceProfile_2034.SERVICEPROFILE_NAME.
Step 3
Select vHBA drop-down list
Choose the vHBA. For example, CreateUCSServiceProfile_2034.SP_VHBA1.
Select VSAN drop-down list
Choose the VSAN. For example, CreateUCSServiceProfile_2034.SP_VSAN1.
Click Next to advance to the Task Inputs pane.
The following parameters are configurable:
Name
Description
NetApp Account Name (Primary) Choose the NetApp storage account name. For example, ice3270-1a (FlexPOD).
drop-down list
NetApp FC Adapter (Primary)
drop-down list
Choose the primary NetApp FC Adapter. For example,Ob
[50:0a:09:84:89:bb:3f:22].
Note
The Configure Secondary Head check box is
checked.
Storage Policy drop-down list
Choose the storage policy name. For example, FlexPod_SP.
PXE Boot Policy drop-down list
Choose the PXE boot policy name. For example, LANSANPolicy.
Server Boot Policy drop-down list
Choose the server boot policy name. For example, SANBootPolicy.
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 FlexPod Management Guide, Release 5.0
OL-32118-01
59
Orchestration Workflow Operations
Provisioning a Stateless Blade Server Orchestration Workflow for FlexPod
Adding a LUN Dataset Using OnCommand
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 LUN to Dataset using OnCom... task. The Edit
Task dialog box appears with the Task Information pane.
The following parameters are preconfigured:
Name
Description
Task Name field
The ProvisionLUN task name is entered.
Task Category drop-down list
The Storage Tasks category is chosen.
Task Type drop-down list
The Add LUN to Dataset using OnCommand 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
Initiator Name
Choose the UCS service profile initiator attribute name. For example,
CreateUCSServiceProfile_2034.OP_CSV_SP_VHBAs.
Click Next to advance to the Task Inputs pane.
The following parameters are configurable:
Name
Description
Dataset Name Select... button
The dataset name.
Storage Size (GB) field
The storage size in gigabytes. For example, 20.
Snapshow Reserve (%) field
The percentage of storage space set aside to accommodate for snapshots of a
volume. Cisco recommends 4 percent.
LUN Export Settings checkbox
The check box is checked.
Export Protocol Type drop-down
list
Choose FCP for the Fibre Channel Protocol.
Cisco UCS Director FlexPod Management Guide, Release 5.0
60
OL-32118-01
Orchestration Workflow Operations
Provisioning a Stateless Blade Server Orchestration Workflow for FlexPod
Name
Description
OS Type drop-down list
Choose VMware for the operating system type.
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.
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.
Cisco UCS Director FlexPod Management Guide, Release 5.0
OL-32118-01
61
Orchestration Workflow Operations
Provisioning a Stateless Blade Server Orchestration Workflow for FlexPod
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.
Choosing the Cisco UCS Server
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 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 UCS server task name is entered. For example, Task536.
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.
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
Account Name drop-down list
Choose the UCS service profile account name attribute. For example,
CreateUCSServiceProfile_2034.ACCOUNT_NAME.
Cisco UCS Director FlexPod Management Guide, Release 5.0
62
OL-32118-01
Orchestration Workflow Operations
Provisioning a Stateless Blade Server Orchestration Workflow for FlexPod
Step 3
Click Next to advance to the Task Inputs pane.
The following parameters are configurable:
Name
Description
Server Selection Scope drop-down Choose Include Servers.
list
Click the Select button to select a Cisco UCS server. For example,
*sys/chassis-1/blade-4 [Service Profile :
org-root/org-FlexPod-Mgmt/Is-demtomark],...
Servers
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 to use unassociated servers only.
Number of CPUs field
The number of CPUs.
Total Memory (GB) field
The amount of memory in gigabytes.
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.
Cisco UCS Director FlexPod Management Guide, Release 5.0
OL-32118-01
63
Orchestration Workflow Operations
Provisioning a Stateless Blade Server Orchestration Workflow for FlexPod
Step 2
Name
Description
Task Details display field
The output generated by this task.
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.
Setting Up PXE Boot
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 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.
Cisco UCS Director FlexPod Management Guide, Release 5.0
64
OL-32118-01
Orchestration Workflow Operations
Provisioning a Stateless Blade Server Orchestration Workflow for FlexPod
Step 2
Step 3
Name
Description
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
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 FlexPod Management Guide, Release 5.0
OL-32118-01
65
Orchestration Workflow Operations
Provisioning a Stateless Blade Server Orchestration Workflow for FlexPod
Monitoring PXE Boot
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 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.
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.
Cisco UCS Director FlexPod Management Guide, Release 5.0
66
OL-32118-01
Orchestration Workflow Operations
Provisioning a Stateless Blade Server Orchestration Workflow for FlexPod
Adding a VLAN to a Service Profile
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 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.
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.
Cisco UCS Director FlexPod Management Guide, Release 5.0
OL-32118-01
67
Orchestration Workflow Operations
Provisioning a Stateless Blade Server Orchestration Workflow for FlexPod
Name
Description
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 list is available if a
storage account name was configured). For example,
CreateUCSServiceProfile_2034.ACCOUNT_NAME.
Boot Policy drop-down list
Choose the boot policy attribute for the blade. For example,
CreateUCSServiceProfile_2034.BLADE_BOOT_POLICY.
Cisco UCS Director FlexPod Management Guide, Release 5.0
68
OL-32118-01
Orchestration Workflow Operations
Provisioning a Stateless Blade Server Orchestration Workflow for FlexPod
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.
Powering Off the Cisco UCS Server
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 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.
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
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:
Cisco UCS Director FlexPod Management Guide, Release 5.0
OL-32118-01
69
Orchestration Workflow Operations
Provisioning a Stateless Blade Server Orchestration Workflow for FlexPod
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.
Powering On the Cisco UCS Server
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 Power On 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 Power On task name is entered.
Task Category drop-down list
The Cisco UCS Tasks category option is chosen.
Task Type drop-down list
The Power On UCS Server task type is chosen.
Comment field
Comments that pertain to this task.
Retry Count drop-down list
The number of retries is entered. The Retry Execution box next to this field is
checked.
Retry Frequency field
The number of seconds before the next retry is entered. Subsequent retry entries
can be entered with a semicolon and the number.
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
Server drop-down list
Choose the server identity attribute. For example, Associate
SP.SERVER_IDENTITY.
Cisco UCS Director FlexPod Management Guide, Release 5.0
70
OL-32118-01
Orchestration Workflow Operations
Provisioning a Stateless Blade Server Orchestration Workflow for FlexPod
Step 3
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.
Registering the Host with vCenter
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 Register Host with vCenter task. The Edit Task dialog
box appears with the Task Information pane.
The following parameters are preconfigured:
Name
Description
Task Name field
The register host with vCenter task name is entered.
Task Category drop-down list
The VMware Host Tasks category is chosen.
Task Type drop-down list
The Register Host with vCenter task type is chosen.
Comment field
Comments that pertain to this task.
Retry Count drop-down list
The number of retries is chosen. The Retry Execution check box next to this
field is checked.
Retry Frequency field
The frequency of retries in seconds.
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 FlexPod Management Guide, Release 5.0
OL-32118-01
71
Orchestration Workflow Operations
Provisioning a Stateless Blade Server Orchestration Workflow for FlexPod
Step 3
Name
Description
PXE Boot Request ID drop-down
list
Choose the PXE boot request ID attribute. For example, PXE Boot
Setup.OUTPUT_PXE_BOOT_ID.
Click Next to advance to the Task Input pane.
The following parameters are configurable:
Name
Description
Account Name drop-down list
Choose the name of the account. For example, icefxp-vc-1. Check the Register
PXE Host check box next to this field.
Host License field
The license of the host. For example, P10C4-QLHD5-K8C31-099K4-CRYQH.
Associate With drop-down list
Choose the Data Center option.
Cluster/Data Center drop-down list Choose the cluster or data center. For example, FlexPod_DC_1.
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 Hosts to a Distributed Virtual Switch
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 Add Hosts to dvSwitch task. The Edit Task dialog box
appears with the Task Information pane.
The following parameters are preconfigured:
Name
Description
Task Name field
The Power On task name is entered.
Task Category drop-down list
The VMware Host Tasks option is chosen.
Task Type drop-down list
The Add Hosts to dvSwitch task type is chosen.
Comment field
Comments that pertain to this task.
Cisco UCS Director FlexPod Management Guide, Release 5.0
72
OL-32118-01
Orchestration Workflow Operations
Provisioning a Stateless Blade Server Orchestration Workflow for FlexPod
Step 2
Name
Description
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
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
Select Hosts drop-down list
Choose the host attribute. For example,
RegisterHostwithvCenter_954.OUTPUT_HOST_IP.
Click Next to advance to the Task Inputs pane.
The following parameters are configurable:
Name
Description
Account Name drop-down list
Choose the account name. For example, icafxp-vc-1.
Datacenter Name drop-down list
Choose the pod name. For example, FlexPod_DC_1.
dvSwitch Name drop-down list
Choose the network switch name. For example, n1000v.
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.
Migrating a Default Virtual Switch to a Distributed Virtual Switch
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 Migrate Default vSwitch to DVSwitch task. The Edit
Task dialog box appears with the Task Information pane.
The following parameters are preconfigured:
Name
Description
Task Name field
The migrate default vSwitch to DV switch task name is entered.
Cisco UCS Director FlexPod Management Guide, Release 5.0
OL-32118-01
73
Orchestration Workflow Operations
Provisioning a Stateless Blade Server Orchestration Workflow for FlexPod
Step 2
Step 3
Name
Description
Task Category drop-down list
The VMware VM Tasks category is chosen.
Task Type drop-down list
The Migrate Default vSwitch to DVSwitch task type is chosen.
Comment field
Comments that pertain to this task.
Task Details display field
No output is generated by this task.
Click Next to advance to the User Input Mapping pane.
The following parameter is configurable:
Note
Check the Map to User Input check box next to the following attribute to map it to the workflow when the
workflow executes.
Name
Description
Host Node drop-down list
Choose the host node attribute. For example,
RegisterHostwithvCenter_954.OUTPUT_HOST_IP.
Click Next to advance to the Task Input pane.
The following parameters are configurable:
Name
Description
Account Name drop-down list
Choose the account name. For example, icefxp-vc-1.
dvSwitch Name drop-down list
Choose the DV switch name. For example, FlexPod_DC_1 @ n1000v.
uplinkPortGroup Name drop-down Choose the port group uplink name. For example, system-uplink.
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.
Cisco UCS Director FlexPod Management Guide, Release 5.0
74
OL-32118-01
Orchestration Workflow Operations
Validating and Executing an Orchestration Workflow
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 FlexPod Management Guide, Release 5.0
OL-32118-01
75
Orchestration Workflow Operations
Validating and Executing an Orchestration Workflow
Cisco UCS Director FlexPod Management Guide, Release 5.0
76
OL-32118-01
CHAPTER
7
Troubleshooting
This chapter contains the following sections:
• Troubleshooting Cisco UCS Director Connectivity, page 77
• Troubleshooting Cisco UCS Director Baremetal Agent Connectivity, page 78
Troubleshooting Cisco UCS Director Connectivity
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 FlexPod Management Guide, Release 5.0
OL-32118-01
77
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 FlexPod Management Guide, Release 5.0
78
OL-32118-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 FlexPod Management Guide, Release 5.0
OL-32118-01
79
Troubleshooting
Troubleshooting Cisco UCS Director Baremetal Agent Connectivity
Cisco UCS Director FlexPod Management Guide, Release 5.0
80
OL-32118-01