Cisco UCS Director Vblock Management Guide, Release 5.1
First Published: September 29, 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
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS,
INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH
THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY,
CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB's public domain version
of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS" WITH ALL FAULTS.
CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT
LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS
HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network
topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional
and coincidental.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: http://
www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership
relationship between Cisco and any other company. (1110R)
© 2014
Cisco Systems, Inc. All rights reserved.
CONTENTS
Preface
Preface ix
Audience ix
Conventions ix
Related Documentation xi
Documentation Feedback xi
Obtaining Documentation and Submitting a Service Request xi
CHAPTER 1
New and Changed Information for this Release 1
New and Changed Information for this Release 1
CHAPTER 2
Overview 3
About Vblock 3
Vblock Support 4
System Requirements 5
EMC VNX Block, File, and Unified Storage 6
EMC VMAX Storage 6
Vblock Implementation Overview 7
Accessory Storage Software for Vblock 7
PowerPath Virtual Environment Support 8
Accessory Storage Devices for Vblock 8
About EMC Isilon 8
Cisco UCS Director Support for EMC Isilon 8
About EMC VPLEX 9
Pod Support for EMC VPLEX 9
About EMC RecoverPoint 10
CHAPTER 3
Initial Vblock Configuration 11
Cisco UCS Director Vblock Management Guide, Release 5.1
iii
Contents
Adding a Pod 11
Cisco UCS Manager Accounts 12
Adding a Cisco UCS Manager Account 13
Testing the Connection to a Physical Account 15
Verifying the Discovery of a Cisco UCS Manager Account 15
Viewing the Topology and Connectivity of Devices in a Cisco UCS Domain 16
Exporting the Configuration of a Cisco UCS Manager Account 17
Importing the Configuration of a Cisco UCS Manager Account 17
Adding a Vblock Account 18
Verifying Vblock Account Discovery 19
Configuring VNX 20
Adding a VNX Block Account 21
Adding a VNX File Account 23
Adding a VNX Unified Account 24
Configuring VMAX 27
Installing the EMC Solutions Enabler for VMAX Storage 27
Adding a Solutions Enabler Account 29
Network Configuration 30
Adding a Network Device to a Pod 30
Verifying Network Device Details in a Pod Environment 31
Configuring Accessory Storage Device Accounts for Vblock 32
Initial VPLEX Configuration 32
Creating a VPLEX Account 32
Assigning a Pod to a Cluster 33
Initial EMC Isilon Configuration 34
Creating an EMC Isilon Account 34
Initial EMC RecoverPoint Configuration 35
Creating a RecoverPoint Account 36
CHAPTER 4
Network Configuration for Cisco UCS Director Baremetal Agent 39
About the Network Configuration Options 39
Single Network for Management and PXE 39
Prerequisites and Assumptions for a Single Network Configuration 40
Separate Networks for Management and PXE 40
Prerequisites and Assumptions for a Separate Network Configuration 41
Cisco UCS Director Vblock Management Guide, Release 5.1
iv
Contents
Configuring Cisco UCS Director Baremetal Agent 42
Configuring the DHCP Server for a Baremetal Agent Account 43
Starting and Stopping Baremetal Agent Services 44
Configuring the Interface for the PXE Network 45
Changing the Default Baremetal Agent Account 45
CHAPTER 5
Vblock Operations 47
Configuration Guidelines for Vblock Operations 47
Creating an Organization 50
Configuring the Chassis/FEX Discovery Policy 50
Creating a UUID Pool 51
Creating a MAC Pool 52
Creating a WWNN Pool 52
Creating a WWPN Pool 53
Creating a Network Control Policy 53
Creating a vNIC Template 55
Creating a VSAN 59
Creating a vHBA Template 60
Creating a LAN Boot Policy 62
Creating a SAN Boot Policy 63
Creating a vNIC 66
Creating a vHBA 66
Creating a Network Policy 67
Creating a Storage Policy 69
CHAPTER 6
Vision Intelligent Operations for Vblock 71
About Vision Intelligent Operations 71
Initial VCE Vision Intelligent Operations Configuration 71
Creating a Vision Intelligent Operations Account 72
Vision Intelligent Operations for Vblock 73
Accessing or Modifying a Vision Intelligent Operations Orchestration Workflow Task 73
Verifying Vblock Release Certification Matrix Compliance 74
Viewing Vblock Compute, Network, and Storage Information 74
Assigning a Policy to a Vision Intelligent Operations Task 75
Cisco UCS Director Vblock Management Guide, Release 5.1
v
Contents
CHAPTER 7
Orchestration Workflow Operations 77
Cisco UCS Manager Orchestration Tasks 77
Importing a Workflow 78
Accessing Task Documentation 79
Navigating to a Predefined Orchestration Workflow 79
Provisioning Vblock Orchestration Workflows 79
Provisioning a Stateless Blade Server Orchestration Workflow Overview 80
Modifying the Workflow Priority 82
Creating the Cisco UCS Service Profile Task 83
Choosing the Cisco UCS Server 84
Associating the Cisco UCS Service Profile 85
Powering Off the Cisco UCS Server 86
Setting Up PXE Boot 87
Creating a VNX LUN 89
Creating a VNX Storage Group 90
Adding a VNX Host Initiator Entry 91
Configuring Generic Storage Area Network Zoning 92
Adding Hosts to a VNX Storage Group 94
Adding a LUN to a VNX Storage Group 95
Modifying the Cisco UCS Service Profile Boot Policy 96
Modifying the Cisco UCS Boot Policy LUN ID 97
Resetting the Cisco UCS Server 98
Monitoring PXE Boot 99
Adding a VLAN to a Service Profile 100
Disassociating the Cisco UCS Service Profile 101
Configuring the Waiting for a Specific Duration Task 102
Provisioning a File System Mounting Orchestration Workflow 103
File System Mounting Orchestration Workflow Overview 103
Creating a VNX File System 104
Adding a VNX NFS Export Task 105
Mounting the NFS Datastore 106
Validating and Executing an Orchestration Workflow 107
CHAPTER 8
Troubleshooting 109
Cisco UCS Director Vblock Management Guide, Release 5.1
vi
Contents
Troubleshooting Cisco UCS Director Connectivity 109
Troubleshooting Cisco UCS Director Baremetal Agent Connectivity 110
Cisco UCS Director Vblock Management Guide, Release 5.1
vii
Contents
Cisco UCS Director Vblock Management Guide, Release 5.1
viii
Preface
This preface contains the following sections:
• Audience, page ix
• Conventions, page ix
• Related Documentation, page xi
• Documentation Feedback, page xi
• Obtaining Documentation and Submitting a Service Request, page xi
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 Vblock Management Guide, Release 5.1
ix
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 Vblock Management Guide, Release 5.1
x
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 Vblock Management Guide, Release 5.1
xi
Preface
Obtaining Documentation and Submitting a Service Request
Cisco UCS Director Vblock Management Guide, Release 5.1
xii
CHAPTER
1
New and Changed Information for this Release
This chapter contains the following section:
• New and Changed Information for this Release, page 1
New and Changed Information for this Release
The following table provides an overview of the significant changes to this guide for this current release. The
table does not provide an exhaustive list of all changes made to this guide or of all new features in this release.
Table 1: New Features and Changed Behavior in Vblock, Release 5.1
Feature
Description
Where Documented
VCE Vision Intelligent Operations Automates release certification
See the “About Vision
compliance in the Vblock converged Intelligent Operations” section
infrastructure environment and
in this guide.
validates the health or operating status
of the Vblock pod.
Cisco UCS Director Vblock Management Guide, Release 5.1
1
New and Changed Information for this Release
New and Changed Information for this Release
Cisco UCS Director Vblock Management Guide, Release 5.1
2
CHAPTER
2
Overview
This chapter contains the following sections:
• About Vblock, page 3
• EMC VNX Block, File, and Unified Storage, page 6
• EMC VMAX Storage, page 6
• Vblock Implementation Overview, page 7
• Accessory Storage Software for Vblock, page 7
• Accessory Storage Devices for Vblock, page 8
About Vblock
Vblock is an integrated hardware and software system that you can use for virtualized and nonvirtualized
converged computing, networking, and storage solutions. You can use Vblock for the following:
• Data centers that need high availability and scalable Vblock storage solutions to reduce operating costs
and converge the infrastructure so that it supports hybrid cloud computing.
• Interface to private cloud services that provides computing resources for end users and virtualized
applications.
Note
The hardware deployed for the Vbock system is highly modular and varies depending on the specific
Vblock rack-mount scheme needed for each customer deployment. For more information, see Cisco
Validated Designs on the web.
The Vblock system contains the following hardware and software:
Note
See the Compatibility Matrix for all supported software and hardware versions.
• 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,
Cisco UCS Director Vblock Management Guide, Release 5.1
3
Overview
Vblock Support
storage, and security settings for multiple hosts and to monitor the host compliance. See the Cisco UCS
Director Installation Guide and Cisco UCS Director Baremetal Agent Setup Guide for more information.
• The Vblock virtualization software, computing, and the EMC VNX and EMC Symmetrix VMAX storage
components are located in a single 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
Vblock hardware and software components.
Figure 1: Vblock System Series Hardware and Software Component with EMC VNX Storage
Vblock Support
Cisco UCS Director helps support the unified storage systems in the following ways:
• Auto-discovery
• Monitoring
Cisco UCS Director Vblock Management Guide, Release 5.1
4
Overview
System Requirements
• Visibly manage all the VNX components—RAID groups, storage pools, logical unit numbers (LUNs),
storage groups, initiators, file systems, volumes, Network File System (NFS) and Common Internet File
System (CIFS).
Note
Make sure that you create a pod before you add a Vblock account. For more information, see Adding a
Pod.
System Requirements
Component
Requirement
Vblock Hardware Connectivity
For more information, see the VCE Vblock Series
300 Technical Specifications, and VCE Vblock Series
700 Technical Specifications.
Networking
Two Cisco Nexus 5000/5500 Series switches
Two Cisco UCS 6100 or 6200 Series Fabric
Interconnects
Cisco Nexus 1000V switch
Computing
One or multiple Cisco UCS chassis with modules
that have two Fabric Extenders per chassis
Storage
EMC VNX or VMAX 10K or 20K storage system.
See the Compatibility Matrix for all supported
versions.
Management and Software
Cisco UCS Manager, VCE Vision Intelligent
Operations software (Vblock System 300 and 700).
Cisco UCS Director
See the Compatibility Matrix for all supported
versions.
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/vSphere, or
Microsoft Hyper-V Manager) server
See the Compatibility Matrix for all supported
versions.
Cisco UCS Director Vblock Management Guide, Release 5.1
5
Overview
EMC VNX Block, File, and Unified Storage
EMC VNX Block, File, and Unified Storage
EMC VNX Block, File, and Unified accounts for VNX storage is supported in Cisco UCS Director.
Note
See the Compatibility Matrix for all supported versions.
In Cisco UCS Director, you can add the following VNX storage account types:
• VNX File account—X-Blade enclosure, two to eight blades, configurable failover options, and flexible
I/O connectivity. There is one data mover per license.
• VNX Block account—Storage or data processor enclosure, dual active storage processors, automatic
failover, and flexible I/O connectivity. There are two service providers per license.
• VNX Unified account—Single platform for VNX File and VNX Block. There are two service providers
per license.
Note
This document discusses the configuration of EMC VNX Block, File, and Unified accounts only. See the
Cisco UCS Director EMC VNX Management Guide for more information about these VNX accounts and
how they are managed.
EMC VMAX Storage
An EMC VMAX system is a storage platform that is intended for open systems and mainframe computing.
VMAX systems run in an Enginuity operating environment. The system scales from a single Symmetrix
VMAX Engine system with one storage bay to a large eight-engine system and a maximum of ten storage
bays.
Cisco UCS Director supports EMC Symmetrix VMAX 10K and 20K engine systems. A VMAX license
supports one engine (two directors). Each engine contains two director boards, memory chips, and front and
back end ports for connectivity to hosts and storage bays.
Each director board contains 2 Intel quad core processors for data processing, 16, 32, or 64 GB of physical
memory, one system interface board (SIB) that connects the director to the Matrix Interface Board Enclosure
(MIBE), and front and back end ports.
The VMAX has up to 10 storage bays. Hard drives are installed in the storage bays. Each storage bay contains
16 Disk Array Enclosures (DAEs). Each DAE contains 15 to 25 hard drives. The VMAX supports SATA,
Fiber Channel, SAS, and solid state drives.
Cisco UCS Director connects to EMC VMAX using the EMC Solutions Enabler.
Cisco UCS Director Vblock Management Guide, Release 5.1
6
Overview
Vblock Implementation Overview
Vblock Implementation Overview
You can implement Vblock several ways. This section describes the basic tasks involved in a typical Vblock
implementation.
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Research and plan the configuration design that works best for your Vblock network. For more information on Vblock
solutions, services, and support, see the Cisco Vblock Systems page. See also the VCE Management and Orchestration
Workflow Automation for Vblock Infrastructure Platforms white paper.
Use the VCE Vblock Series 700 Technical Specifications and VCE Vblock Series 300 Technical Specifications to
determine what hardware connectivity requirements that you need for your Vblock design.
Use the EMC VNX Series Technical Specifications or EMC Symmetrix VMAX 10K and 20K specifications to determine
what network connectivity requirements that you need for your Vblock design for VNX or VMAX (whichever one that
you choose).
Obtain licensing information for Vblock or the individual devices or software in your implementation. For more
information, see the Cisco UCS Director Install and Upgrade Guides.
Install Cisco UCS Director and the Cisco UCS Director Baremetal Agent on your VMware (vCenter Server/ESXI/ESXi,
vSphere, or Microsoft Hyper-V Manager) server. See the Cisco UCS Director Install and Upgrade Guides web page for
more information.
Add the Vblock account using the task in the “Initial Vblock Configuration” chapter.
Connect devices to Cisco UCS Director to the network using the following tasks in the Initial Vblock Configuration
chapter:
a) Connect Cisco UCS Manager by adding an account.
b) Connect EMC VNX unified storage system(s) or EMC Symmetrix VMAX 10K and 20K storage system(s).
c) Connect Cisco Nexus series switches.
Note
For more information about configuring UCS Manager, see Cisco UCS Director Management Guide for Cisco
UCS Manager.
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.
Step 10
Use the “Vblock Operations” chapter to create a top-level root organization, policies, pools, vNIC templates and so on.
Step 11
Use the “Vision Intelligent Operations for Vblock” chapter to create a Vision Intelligent Operations account and set
benchmark parameters for Release Compatibility Matrix (RCM) and inventory data.
Step 12
Use the “Orchestration Workflow Operations” chapter to navigate to a predifined orchestration workflow, learn how a
predefined orchestration workflow can be configured, and learn 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.
Accessory Storage Software for Vblock
Cisco UCS Director supports the following accessory storage software for Vblock:
Cisco UCS Director Vblock Management Guide, Release 5.1
7
Overview
PowerPath Virtual Environment Support
• EMC PowerPath Virtual Environment (VE)
PowerPath Virtual Environment Support
PowerPath Virtual Environment (VE) is an EMC feature that is enabled between the EMC storage component
and VMware host. EMC PowerPath VE automates and optimizes data path pools in virtual environments by
automating failover and recovery operations, optimizing load balancing, and standardizing path management.
The PowerPath VE software is installed on the VMware host. Once the PowerPath VE feature is enabled, a
host can discover the EMC storage component. From within Cisco UCS Director, the storage can be discovered
and associated as a datastore.
Note
Configuring PowerPath VE on the VMware host and EMC storage component is outside the scope of this
document.
Accessory Storage Devices for Vblock
Cisco UCS Director supports the following accessory storage devices for Vblock:
• EMC Isilon
• EMC VPLEX
• EMC RecoverPoint
About EMC Isilon
The EMC Isilon storage system consists of three or more nodes that make a cluster. Each node is a
self-contained, rack-mountable device that contains industry standard hardware, such as disk drives, CPU,
memory, and network interfaces. Each EMS Isilon system is integrated with the OneFS operating system
(OS) that is based on FreeBSD.
OneFS unifies a cluster of nodes into a single shared resource. OneFS also has a file-striping functionality
across each node in a cluster, a fully distributed lock manager, caching, fully distributed metadata, and a
remote block manager to maintain global coherency and synchronization across the Isilon cluster.
The Isilon cluster is a single storage pool with a global namespace. This cluster enables you to support multiple
volumes and file systems.
Cisco UCS Director Support for EMC Isilon
Cisco UCS Director manages, monitors, and does reporting for the EMC Isilon system. Data is collected
through the Isilon cluster platform and namespace REST API, which is connected to Cisco UCS Director
through HTTP or HTTPS. This data is parsed and bound to the output as Plain Old Java Objects (POJOs),
and these objects are distributed throughout the pod.
Cisco UCS Director Vblock Management Guide, Release 5.1
8
Overview
About EMC VPLEX
About EMC VPLEX
VPLEX is an EMC technology that provides a virtual storage system and access to data in the private cloud.
A VPLEX can be implemented on Cisco UCS Director through a pod deployment such as Vblock, or as a
standalone device. VPLEX has the following capabilities:
• Uses a single interface for a multi-vendor high-availability storage and compute infrastructure to
dynamically move applications and data across different compute and storage locations in real time,
with no outage required. VPLEX combines scaled clustering with distributed cache coherence intelligence
within the same data center, across a campus, or within a specific geographical region. Cache coherency
manages the cache so that data is not lost, corrupted, or overwritten.
• Dynamically makes data available for organizations. For example, a business can be sustained through
a failure that would have traditionally required outages or manual restore procedures.
• Presents and maintains the same data consistently within and between sites, and enables distributed data
collaboration.
• Establishes itself between ESX hosts that act as servers for virtual machines (VMs) and storage in a
storage area network (SAN) where data can be extended within, between, and across pods.
Pod Support for EMC VPLEX
The VPLEX virtual storage system technology for accessing data in the private cloud is associated with and
supported by this pod. Cisco UCS Director collects data through the VPLEX Element Manager API and
connects to the VPLEX server through HTTPS. Once a VPLEX account is established and a pod is associated
with a VPLEX cluster, VPLEX provides the following management and monitoring capabilities:
• Cluster inventory of ESX hosts and reports for two or more VPLEX directors that form a single
fault-tolerant cluster, deployed as one to four engines.
• VPLEX engine inventory and reports for an engine that contains two directors, management modules,
and redundant power.
• Director inventory and reports for the CPU module(s) that run GeoSynchrony, the core VPLEX software.
Two directors are in each engine. Each has dedicated resources and can function independently.
• Port inventory and reports for Fast Ethernet ports and initiator ports.
• VPLEX (local or global) data cache report for the temporary storage for recent writes and recently
accessed data.
• Storage volume inventory and reports for a logical unit number (LUN) exported from an array.
• Extent management (create, delete, and report) for a slice (range of blocks) of a storage volume.
• Device management (create, delete, attach/detach mirror, and report) for a RAID 1 device whose mirrors
are in geographically separate locations.
• Virtual volume management (create, modify, delete, and report) for a virtual volume that can be distributed
over two or more storage volumes that are presented to ESX hosts.
• Storage views management (create, modify, delete, and report) for a combination of registered initiators
(hosts), front-end ports, and virtual volumes that are used to control host access to storage.
• Recovery point for determining the amount of data that can be lost before a failure event.
Cisco UCS Director Vblock Management Guide, Release 5.1
9
Overview
About EMC RecoverPoint
For more information about VPLEX use cases, see the EMC VPLEX Metro Functional Overview section of
the Cisco Virtualized Workload Mobility Design Considerations chapter. This chapter is in the Data Center
Interconnect Design Guide for Virtualized Workload Mobility with Cisco, EMC, and VMware.
About EMC RecoverPoint
EMC RecoverPoint protects storage array logical unit numbers (LUNs) and provides concurrent local and
remote data replication. RecoverPoint also provides continuous data protection for operational and disaster
recovery by enabling any point-in-time recovery (PITR) for diversified storage environments both within and
across pods.
RecoverPoint secures data by providing synchronous and asynchronous replication across heterogeneous
arrays for block-based storage protocols. Replication improves reliability, fault-tolerance, and accessibility
to data. If data becomes compromised or lost, you can look at data back in time and recover it by extending
the vCenter VMware Site Recovery Manager (SRM) functionality with any PITR capabilities.
RecoveryPoint provides the ability to do the following:
• Enable continuous data protection for any PITR to optimize the recovery point objective (RPO) and
recovery time objective (RTO).
• Ensure recovery consistency for inter-dependent applications.
• Provide synchronous or asynchronous replication policies.
• Reduce WAN bandwidth consumption and utilize available bandwidth optimally.
In Cisco UCS Director, you can access the following EMC RecoverPoint reports for Vblock clusters:
• Consistency groups that ensure that there is application-dependent write consistency of application data
on VPLEX distributed virtual volumes within the VPLEX system in the event of a disaster.
• Consistency group copies of the initial consistency groups.
• Replication sets that consist of a production source volume and its local or local and remote replica
volumes. One or more replication sets makes up a consistency group.
Cisco UCS Director Vblock Management Guide, Release 5.1
10
CHAPTER
3
Initial Vblock Configuration
This chapter contains the following sections:
Note
The procedures in this chapter assume you are logged into Cisco UCS Director.
• Adding a Pod, page 11
• Cisco UCS Manager Accounts, page 12
• Adding a Vblock Account, page 18
• Configuring VNX, page 20
• Configuring VMAX, page 27
• Network Configuration, page 30
• Configuring Accessory Storage Device Accounts for Vblock, page 32
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 Vblock Management Guide, Release 5.1
11
Initial Vblock Configuration
Cisco UCS Manager Accounts
Name
Description
Type drop-down list
Choose the type of pod that you want to add. This can be one of the
following supported types:
• Generic
• VSPEX
• Vblock
If you choose any type of pod except the generic type, you must have a
license for that pod type. In addition, the nongeneric pod types accommodate
only specific physical and virtual components. A generic pod does not
require a specific pod license. You can add any type of physical or virtual
component to a generic pod. For more information about pod licenses, see
Cisco UCS Director Install and Upgrade Guides.
Description field
(Optional) A description of the pod.
Address field
The physical location of the pod. For example, this field could include the
city or other internal identification used for the pod.
Hide Pod check box
Check this check box to hide the pod if you do not want it to show in the
Converged Check View. You can continue to add or delete accounts from
the pod.
For example, you can use this check box to ensure that a pod that does not
have any physical or virtual elements is not displayed in the Converged
View.
Step 5
Click Add.
What to Do Next
Add one or more accounts to the pod.
Cisco UCS Manager Accounts
Each Cisco UCS Manager account represents a single Cisco UCS domain that you want to have managed by
Cisco UCS Director.
For an environment that does not include Cisco UCS Central, you create Cisco UCS Manager accounts in a
pod.
For an environment that includes Cisco UCS Central, you must create a Cisco UCS Central account under
multi-domain managers. All Cisco UCS domains that are registered with that Cisco UCS Central, and their
related Cisco UCS Manager accounts are brought into 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
Cisco UCS Director Vblock Management Guide, Release 5.1
12
Initial Vblock Configuration
Adding a Cisco UCS Manager Account
Central account to a pod if needed. You can also register a Cisco UCS Manager account with a Cisco UCS
Central account.
Adding a Cisco UCS Manager Account
Before You Begin
Add the pod to which this Cisco UCS Manager account belongs.
Step 1
Step 2
Step 3
On the menu bar, choose Administration > Physical Accounts.
Click the Physical Accounts tab.
Click Add.
Step 4
In the Add Account dialog box, complete the following fields:
Name
Description
Pod drop-down list
Choose the pod to which this account belongs.
Category Type drop-down list
Choose the category type. You must choose Computing. This is the type
of infrastructure for the account.
Account Type drop-down list
Choose the account type. You must choose UCSM.
Authentication Type drop-down list
Choose the type of authentication to be used for this account. This can be
one of the following:
• Locally Authenticated—A locally authenticated user account is
authenticated directly through the fabric interconnect and can be
enabled or disabled by anyone with admin or AAA privileges.
• Remotely Authenticated—A remotely authenticated user account is
any user account that is authenticated through LDAP, RADIUS, or
TACACS+.
Server Management drop-down list
Choose how you want to have the servers in this account managed. This
can be one of the following:
• All Servers—All servers are managed. 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.
Server Address field
The IP address of Cisco UCS Manager. For a cluster configuration, this is
the virtual IP address.
Cisco UCS Director Vblock Management Guide, Release 5.1
13
Initial Vblock Configuration
Adding a Cisco UCS Manager Account
Name
Description
User ID field
The username that this account will use to access Cisco UCS Manager. This
username must be a valid account in Cisco UCS Manager.
Password field
The password associated with the username.
UCS Authentication Domain field
The authentication domain for the remotely authenticated account.
This field is not displayed if you are using a locally authenticated account.
Transport Type drop-down list
Choose the transport type that you want to use for this account. This can be
one of the following:
• http
• https
Step 5
Port field
The port used to access Cisco UCS Manager.
Description field
(Optional) A description of this account.
Contact Email field
The email address that you can use to contact the administrator or other
person responsible for this account.
Location field
The location of this account.
Service Provider field
(Optional) The name of the service provider associated with this account,
if any.
Click Add.
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 Vblock Management Guide, Release 5.1
14
Initial Vblock Configuration
Testing the Connection to a Physical Account
Testing the Connection to a Physical Account
You can test the connection at any time after you add an account to a pod.
Step 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 Vblock Management Guide, Release 5.1
15
Initial Vblock 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 Vblock Management Guide, Release 5.1
16
Initial Vblock Configuration
Exporting the Configuration of a Cisco UCS Manager Account
Exporting the Configuration of a Cisco UCS Manager Account
Cisco UCS Director exports a file named Ucs-Timestamp-configuration.zip to the location
configured for downloads in your browser.
Step 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 Vblock Management Guide, Release 5.1
17
Initial Vblock Configuration
Adding a Vblock Account
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.
Adding a Vblock Account
Before You Begin
Make sure that you create a pod before you add a Vblock account.
Step 1
Step 2
On the menu bar, choose Administration > Physical Accounts.
In the Physical Acccounts tab, click Add.
Step 3
In the Add Account dialog box, complete the following fields:
Name
Description
Pod drop-down list
Choose Vblock for this account.
Category drop-down list
Choose Storage.
Account Type drop-down list
The account type EMC VNX is selected for you when Storage is selected as
the category.
Account Sub Type drop-down list
Choose from the following VNX account subtypes:
• VNX File—X-Blade enclosure, two to eight blades, configurable failover
options, and flexible I/O connectivity. There is one data mover per license.
• VNX Block—Storage or data processor enclosure, dual active storage
processors, automatic failover, and flexible I/O connectivity. There are two
service providers per license.
• VNX Unified—Single platform for VNX File and VNX Block. There are
two service providers per license.
Authentication Type drop-down list Choose the Authentication Type for this account.
Account Name field
The account name.
Server Address field
The IP address of the Vblock server.
User ID field
The user ID of the Vblock server.
Cisco UCS Director Vblock Management Guide, Release 5.1
18
Initial Vblock Configuration
Verifying Vblock Account Discovery
Name
Description
Password field
The password for the Vblock server.
Transport Type drop-down list
Choose the protocol transport type that you want to use for the account. This
can be one of the following:
• http (Hypertext Transfer Protocol)
• https (Hypertext Transfer Protocol Secure)
Note
The default transport type protocol for this account is
HTTPS.
Port field
The port (80 is the default).
Description field
The account description.
Contact Email field
The contact's email.
Location field
The site location for this account.
Service Provider field
The service provider name, if any.
Step 4
Click Add.
Cisco UCS Director automatically discovers all storage elements in the Vblock account, including aggregates, disks,
volumes, LUNs, and Qtree.
Step 5
In the Physical Accounts pane, click the account.
Step 6
Click Test Connection.
What to Do Next
Verify that the account has been discovered. The discovery process typically takes a few minutes.
Verifying Vblock Account Discovery
After you add a Cisco UCS Manager to a Cisco UCS Director Vblock environment, all discovered components
of this environment are displayed at the account level.
Step 1
Step 2
On the menu bar, choose Physical > Storage.
In the Storage pane, click the Vblock account.
Step 3
Click the System Summary tab.
The Summary reports for this account appear.
Cisco UCS Director Vblock Management Guide, Release 5.1
19
Initial Vblock Configuration
Configuring VNX
Configuring VNX
Cisco UCS Director supports EMC VNX Block, File, and Unified accounts for VNX.
Note
See the Compatibility Matrix for all supported versions.
For a VNX Block account, you create the following:
• Storage pools
• Storage groups
• RAID groups
• Initiators
• Logical unit numbers (LUNs)
The reports available for VNX Block accounts include details on all of these items, as well as on storage
processors, ports, data movers, and disk devices. You can also view tabular reports for RAID groups or hosts,
and instant reports for file system allocation, the top five storage capacity file systems, the top five file systems
file count, and the top five storage capacity volumes.
For a VNX File account, you create use either Common Internet File Servers (CIFS) or Network File System
(NFS) Export. For CIFS, you create the CIFS servers and shares and the Domain Name System (DNS) domains.
For NFS Export, you create the following:
• Storage pools for files
• File systems
• Interfaces
• Volumes
• Mounts
The reports available for VNX File accounts include details on these items, as well as system overview
summaries.
For a VNX Unified account, which combines VNX Block and VNX File, you perform all the steps needed
for both VNX block and VNX file accounts.
You can view any of the reports available for VNX block or VNX file accounts.
After an account is established, you can configure, manage and monitor EMC VNX features in Cisco UCS
Director. For more information about configuring EMC VNX management and monitoring features for this
pod, see the Cisco UCS Director EMC VNX Management Guide.
Cisco UCS Director Vblock Management Guide, Release 5.1
20
Initial Vblock Configuration
Adding a VNX Block Account
Adding a VNX Block Account
Before You Begin
• Create a pod for either the Generic or vBlock account types.
• Configure a VM.
• Uninstall the legacy CLI "navicli" software (if it is currently installed).
• Install the new secure "NaviSecCli" software so that all Navisphere features are supported (if it is not
currently installed).
• Create a set of user credentials for the NavisecCli package with enough privileges to run NavisecCli
commands to manage and configure VNX storage.
Step 1
Step 2
On the menu bar, choose Administration > Physical Accounts.
In the Physical Accounts pane, click Add.
Step 3
In the Add Account dialog box, complete the following fields:
Step 4
Step 5
Name
Description
Pod drop-down list
Choose the pod for this account.
Category drop-down list
Choose Storage.
Account Type drop-down list
Choose EMC VNX Block.
Another Add Account dialog box appears to collect data.
Click Submit.
In this Add Account dialog box, complete the following fields:
Name
Description
Pod drop-down list
The preselected pod (data center) for this account appears.
Account Type drop-down list
The preselected type for this account appears.
Account Name field
The account name.
Description field
The description of this account.
Storage Processor A IP Address
field
The IP address for Storage Processor A.
Storage Processor B IP Address
field
The IP address for Storage Processor B.
Cisco UCS Director Vblock Management Guide, Release 5.1
21
Initial Vblock Configuration
Adding a VNX Block Account
Name
Description
Use Credential Policy check box
Check this check box to apply a new or existing credential policy to the VNX.
See the description of your options below.
Note
Credential Policy drop-down list
and Add Credential Policy form
icon
If you click this option and apply a policy, the Block Access User Name
and Block Access Password fields described below do not appear in
this form.
You have these two options if you check the Use Credential Policy check box.
• From the credential policy drop-down list, choose a predefined policy for
this type of account and apply that policy data to this account.
• Click the Add Credential Policy form icon, and use it to define a policy
for this type of account. You can use a defined credential policy in future
sessions; it will appear in the drop-down list.
Block Access User Name field
The username for block access.
Note
If you apply a policy, the Block Access User Name and Block Access
Password fields described below do not appear in this form.
Block Access Password field
The password for block access.
Protocol drop-down list
Choose the protocol to be used.
NaviSecCLI Host IP Address field The address for the secure Navisphere CLI host.
Use Credential Policy check box
Check this check box to apply a new or existing credential policy. See the
description of your options above.
Note
If you apply a policy, the NaviSecCLI Host User Name and
NaviSecCLI Host User Password fields described below do not appear
in this form.
NaviSecCLI Host User Name field The username for the specified secure Navisphere CLI host.
NaviSecCLI Host User Password
field
The password for the specified secure Navisphere CLI host.
Block Access Port field
The port to be used.
Scope drop-down list
Choose the scope.
Contact field
The contact email.
Location field
The contact's location (user defined).
Cisco UCS Director Vblock Management Guide, Release 5.1
22
Initial Vblock Configuration
Adding a VNX File Account
Step 6
Step 7
Click Submit.
In the Physical Accounts pane, choose the account.
Step 8
Click Test Connection.
Adding a VNX File Account
Before You Begin
You must create a pod for the account.
Step 1
Step 2
On the menu bar, choose Administration > Physical Accounts.
In the Physical Acccounts pane, click Add.
Step 3
In the Add Account dialog box, complete the following fields:
Step 4
Step 5
Name
Description
Pod drop-down list
Choose the pod for this account.
Category drop-down list
Choose Storage.
Account Type drop-down list
Choose EMC VNX File.
Another Add Account dialog box appears to collect data.
Click Submit.
In the longer Add Account dialog box, complete the following fields:
Name
Description
Pod drop-down list
The preselected pod for this account appears.
Account Type drop-down list
The preselected type for this account appears.
Account Name field
The account name.
Description field
The description of this account.
Control Station IP Address field
The control station IP address of the VNX device.
Use Credential Policy check box
Check this check box to apply a new or existing policy to the VNX. See the
description of your options below.
Note
If you click this option and apply a policy, the Control Station IP
Address field, Password field, Transport type drop-down list and the
Port field described below do not appear in this form. They are
administered by the policy.
Cisco UCS Director Vblock Management Guide, Release 5.1
23
Initial Vblock Configuration
Adding a VNX Unified Account
Name
Description
Credential Policy drop-down list
and Add Credential Policy form
icon
You have these two options if you check the Use Credential Policy check box.
• From the Credential Policy drop-down list, choose a predefined policy
for this type of account and apply that policy data to this account
• Click the Add Credential Policy form icon, and use it to define a policy
for this type of account. You can use a defined credential policy in future
sessions; it will appear in the drop-down list.
Password field
The password associated with the specified Control Station address.
Transport Type drop-down list
Choose the transport type.
Port field
The port.
Contact Email field
The contact's email.
Location field
The contact's location (user defined).
Step 6
Step 7
Click Submit.
In the Physical Accounts pane, choose the account.
Step 8
Click Test Connection.
What to Do Next
To change information in a VNX account, click Edit.
Adding a VNX Unified Account
• Create a pod for either the Generic or vBlock account types.
• Uninstall the legacy CLI "navicli" software (if it is currently installed).
• Install the new secure "NaviSecCli" software so that all Navisphere features are supported (if it is not
currently installed).
• Create a set of user credentials for the NavisecCli package with enough privileges to run NavisecCli
commands to manage and configure VNX storage.
Cisco UCS Director Vblock Management Guide, Release 5.1
24
Initial Vblock Configuration
Adding a VNX Unified Account
Before You Begin
Step 1
Step 2
On the menu bar, choose Administration > Physical Accounts.
In the Physical Accounts pane, click Add.
Step 3
In the Add Account dialog box, complete the following fields:
Step 4
Step 5
Name
Description
Pod drop-down list
Choose the pod (data center) for this account.
Category drop-down list
Choose Storage.
Account Type drop-down list
Choose EMC VNX Unified.
Another Add Account dialog box appears to collect data.
Click Submit.
In the longer Add Account dialog box, complete the following fields:
Name
Description
Pod drop-down list
The preselected pod (data center) for this account appears.
Account Type drop-down list
The preselected type for this account appears.
Account Name field
The account name.
Description field
Describe this account so that others can distinguish it from similar accounts.
The Control Station IP Address
field
The control station IP address of the VNX device.
Use Credential Policy checkbox
Check this check box to apply a new or existing policy to the VNX. See the
description of your options below.
Note
Credential Policy drop-down list
and Add Credential Policy form
icon
If you click this option and apply a policy, the Control Station Name
and Password, and the file Access Protocol and Port fields described
below will not appear in this form. They are administered by the policy.
You have these two options if you check the Use Credential Policy check box.
• From the credential policy drop-down list, choose a predefined policy for
this type of account and apply that policy data to this account.
• Click the Add Credential Policy form icon, and use it to define a policy
for this type of account. You can use a defined credential policy in future
sessions; it will appear in the drop-down list.
Control Station User Name field
The username associated with the specified control station address.
Cisco UCS Director Vblock Management Guide, Release 5.1
25
Initial Vblock Configuration
Adding a VNX Unified Account
Name
Description
Password field
The password associated with the control station IP address and user name.
File Access Protocol drop-down list Choose the protocol to be used.
File Access Port field
Choose the port to be used.
Storage Processor A IP Address
field
The IP address for Storage Processor A.
Storage Processor B IP Address
field
The IP address for Storage Processor B.
Use Credential Policy check box
Check this check box to apply a new or existing credential policy. See the
description of your options above.
Note
If you apply a policy, the NaviSecCLI Host User Name and
NaviSecCLI Host User Password fields described below do not appear
in this form.
Block Access User Name field
The username for block access.
Block Access Password field
The associated password for block access.
NaviSecCLI Host IP Address field The address for the secure Navisphere CLI host.
Use Credential Policy check box
Check this check box to apply a new or existing credential policy. See the
description of your options above.
Note
If you apply a policy, the NaviSecCLI Host User Name and
NaviSecCLI Host User Password fields described below do not appear
in this form.
NaviSecCLI Host User Name field The username for the specified secure Navisphere CLI host.
NaviSecCLI Host User Password
field
The password for the specified secure Navisphere CLI host.
Block Access Port field
The port to be used.
Scope drop-down list
Choose the scope.
Contact field
The contact email.
Location field
The contact's location (user defined).
Cisco UCS Director Vblock Management Guide, Release 5.1
26
Initial Vblock Configuration
Configuring VMAX
Step 6
Step 7
Click Submit.
In the Physical Accounts pane, choose the account.
Step 8
Click Test Connection.
What to Do Next
To change information in a VNX account, click Edit.
Configuring VMAX
To manage VMAX in Cisco UCS Director, you use a Linux-based Symmetrix Performance Analyzer (SPA)
or Symmetrix Management Console (SMC) server. We recommend that you use Linux version 7.5.1+.
After building the Linux image and installing the EMC Solutions Enabler, you create an EMC VMAX Solutions
Enabler account.
Note
This document discusses how to configure the EMC Solutions Enabler and the EMC VMAX Solutions
account only.
After an account is established, you can configure, manage and monitor EMC VMAX features in Cisco UCS
Director. For more information about configuring EMC VMAX management and monitoring features for this
pod, see the Cisco UCS Director EMC Symmetrix VMAX Management Guide.
Installing the EMC Solutions Enabler for VMAX Storage
Before You Begin
To communicate with VMAX, Cisco UCS Director now supports a Windows-based EMC Solutions Enabler
(SE). Before using this SE, you must establish a Secure Shell (SSH).
To set up an SSH, we recommend that you install Cygwin version 1.7.27, and use the SSH daemon on the
host. Cygwin provides a Linux-like environment on Microsoft Windows. See http://www.cygwin.com/ for
the download.
After you install the SSH server on the Windows-based SE, modify the path in the profile to include the
Solutions Enabler bin folder so that whoever uses SSH to get into the Windows SE can immediately run
VMAX commands. You should set up new default paths to enable the user-installed software to override the
system software. The following sample provides an generic example of code used to modify the path:
VMAXHOME="/cygdrive/c/Program Files/EMC/SYMCLI/bin"
PATH="/usr/local/bin:/usr/bin:${VMAXHOME}:${PATH}"
Cisco UCS Director Vblock Management Guide, Release 5.1
27
Initial Vblock Configuration
Installing the EMC Solutions Enabler for VMAX Storage
Note
You can add libraries and legacy libraries, such as glibc, to the VM.
You will need gatekeepers to serve as Raw Device Mappings (RDMs). Allow 6,000 to 8,000 mappings
for each RDM.
Step 1
Create the base Linux image for the VM you will use.
For the base Linux image, you can use an SMC or SPA servers that run CentOS, version 5.7 x86 or x86_64. For an SMC
server, allow 20 GB of space. For an SPA server, allow at least 120 GB.
Step 2
Step 3
Step 4
Assign a few gatekeepers as RDMs.
Reboot the Linux VM.
From the EMC Powerlink site, download the EMC Solutions Enabler package for Linux and the Services Management
Application System (SMAS) package se7310-Linux-i386-ni.tar.gz.
Note
See the Cisco UCS Director Compatibility Matrix to identify which version to download and install.
Use MD5 Checksum 9809ac14ed8bfcc19789d7d5671d6015.
Step 5
Step 6
Using SCP, transfer the tar file to your VM.
At a command prompt, enter the following command to decompress the tar file: [root@smc ~]# tar xzvf
se7310-Linux-i386-ni.tar.gz
Step 7
Install the EMC Solutions Enabler by entering the following command: [root@smc ~]# ./se7310_install.sh
-install]
Step 8
Verify that the emc/symcli bin folder is in the Linux path, with this directory structure: <symcli path>/bin. An
example is: /opt/emc/symcli/bin.
To connect to the VMAX device from Cisco UCS Director, you must update the PATH variable with the SYMCLI
binary dir by updating the .bashrc file for the user that logs in to VMAX.
a) Log in to the Solutions Enabler machine with the credentials that Cisco UCS Director will use.
b) Edit .bashrc using your editor of choice; for example vi .bashrc
c) Add the following line to the .bashrc file:
Step 9
PATH=$PATH:$HOME/bin:<symcli binary path>/bin
d) Save the file and exit.
Cisco UCS Director Vblock Management Guide, Release 5.1
28
Initial Vblock Configuration
Adding a Solutions Enabler Account
Adding a Solutions Enabler Account
Before You Begin
You must install an EMC VMAX Solutions Enabler on a Linux Virtual Machine (VM).
Step 1
Step 2
Step 3
Log into Cisco UCS Director.
Choose Administration > Physical Accounts.
In the Physical Acccounts pane, click Add.
Step 4
In the Add Account dialog box, complete the following fields:
Name
Description
Data Center drop-down list
Choose a data center for this account.
Category drop-down list
Choose Storage.
Account Type drop-down list
Choose EMC VMAX Solutions Enabler.
Authentication Type drop-down list Choose Locally or Remotely.
If you chose to authenticate remotely, continue to Step 5.
Account Name field
The account name.
Server Address field
The control station IP address for the VMAX device.
User ID field
The user ID for this account.
Password field
The password for this account.
Transport Type drop-down list
Choose ssh.
Port field
The port.
Description field
The account description.
Contact Email field
The contact's email.
Location field
The location for this account.
Service Provider field
The service provider for this account.
Cisco UCS Director Vblock Management Guide, Release 5.1
29
Initial Vblock Configuration
Network Configuration
Step 5
Step 6
Step 7
For remote authentication, complete the additional field for UCS Authentication Domain.
Click Add.
In the Physical Acccounts pane, choose the account.
Step 8
Click Test Connection.
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.
• Vendor 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.
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
Cisco UCS Director Vblock Management Guide, Release 5.1
30
Initial Vblock Configuration
Verifying Network Device Details in a Pod Environment
Name
Description
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.
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 Vblock Management Guide, Release 5.1
31
Initial Vblock Configuration
Configuring Accessory Storage Device Accounts for Vblock
Configuring Accessory Storage Device Accounts for Vblock
The following tasks are used to configure optional accessory storage device accounts for Vblock.
Initial VPLEX Configuration
This document discusses how to configure a VPLEX account and assign this pod to a VPLEX cluster
(plex) only.
Note
After a VPLEX account is established and a pod is associated with a VPLEX cluster, you can configure,
manage, and monitor VPLEX features in Cisco UCS Director. For more information about configuring VPLEX
management and monitoring features for this pod, see the Cisco UCS Director EMC VPLEX Management
Guide.
Creating a VPLEX Account
Step 1
Step 2
On the menu bar, choose Administration > Physical Accounts.
Click the Multi-domain Managers tab.
Step 3
Step 4
Click New.
In the Add Account dialog box, choose EMC VPLEX from the Account Type drop-down list.
Step 5
Step 6
Click Submit.
In the Add Account dialog box, complete the following fields:
Name
Description
Account Name field
A unique name that you assign to this account.
Server IP field
The IP address of the VPLEX server.
Use Credential check box
Check the check box if you want to use a policy to give the credentials.
Username field
The username that this account uses to access the VPLEX server. This username
must be a valid account in the VPLEX server.
Password field
The password associated with the username.
Protocol drop-down list
The https parameter is preselected for the transport type protocol.
Note
http is not supported for
VPLEX.
Port field
The port used to access the VPLEX server. Port 443 is the default secure HTTPS
port.
Cisco UCS Director Vblock Management Guide, Release 5.1
32
Initial Vblock Configuration
Initial VPLEX Configuration
Name
Description
Contact field
The email address that you use to contact the administrator or other person
responsible for this account.
Location field
The location of the contact.
Step 7
Step 8
Click Submit.
In the Multi-Domain Managers tab, choose the EMC VSPEX account that you just created.
Step 9
Click Test Connection.
The Test Connectivity dialog box displays and confirms if the connection was successful.
Assigning a Pod to a Cluster
You must also create a pod with each VPLEX cluster (1 and 2).
Step 1
Step 2
On the menu bar, choose Physical > Storage.
On the Storage pane, click the Multi-Domain Managers icon to expand the list of connected multi-domain managers.
Step 3
Step 4
Step 5
Step 6
Choose EMC VPLEX to expand the connected VPLEX device(s) and click the VPLEX device that you want.
Click the Clusters tab and click the cluster that you want to assign to the pod.
Click Assign to Pod.
In the Assign Pod to Cluster dialog box, complete the following field:
Name
Description
Select Pod drop-down list
Choose a pod type. This can be one of the following:
• Default Pod
• VSPEX
• Generic
• Vblock
Step 7
Step 8
Click Submit.
Repeat the previous steps to assign a pod to the other cluster.
Cisco UCS Director Vblock Management Guide, Release 5.1
33
Initial Vblock Configuration
Initial EMC Isilon Configuration
Initial EMC Isilon Configuration
Note
This document discusses how to configure an EMC Isilon account only.
After an account is established, you can configure, manage, and monitor EMC Isilon features in Cisco UCS
Director. For more information about configuring EMC Isilon management and monitoring features for this
pod, see the Cisco UCS Director EMC Isilon Management Guide.
Creating an EMC Isilon Account
Step 1
Step 2
On the menu bar, choose Administration > Physical Accounts.
Click the Physical Accounts tab.
Step 3
Step 4
Click New.
In the Add Account dialog box, complete the following fields:
Name
Description
Pod drop-down list
The pod type. This can be one of the following:
• Default Pod
• Generic
• VSPEX
• Vblock
Step 5
Step 6
Category drop-down list
Choose Storage.
Account Type drop-down list
Choose EMC Isilon Cluster.
Click Submit.
In the next Add Account dialog box, complete the following fields:
Name
Description
Account Name field
The name of this Isilon account. For example, isilon-1.
Server IP field
The IP address of the Isilon storage system.
Description field
The description of the Isilon storage system.
Use Credential check box
Check the check box if you want to use a policy to give the credentials.
Cisco UCS Director Vblock Management Guide, Release 5.1
34
Initial Vblock Configuration
Initial EMC RecoverPoint Configuration
Name
Description
Username field
The username that this account uses to access the Isilon storage system. This
username must be a valid account in the Isilon storage system.
Password field
The password associated with the username.
Protocol drop-down list
Choose the protocol transport type that you want to use for the account. This
can be one of the following:
• http (Hypertext Transfer Protocol)
• https (Hypertext Transfer Protocol Secure)
Note
The default transport type protocol for this account is
HTTPS.
Port field
The port used to access the Isilon storage system. Port 443 is the default secure
HTTPS port.
Note
Port 8080 is used for both HTTP and
HTTPS.
Contact field
The email address that you use to contact the administrator or other person
responsible for this account.
Location field
The location of the contact.
Step 7
In the Physical Accounts tab, choose the EMC Isilon account that you just created.
Step 8
Click Test Connection.
Initial EMC RecoverPoint Configuration
Note
This document discusses how to configure an EMC RecoverPoint account only.
After an account is established, you can configure, manage, and monitor EMC RecoverPoint features in Cisco
UCS Director. For more information about configuring EMC RecoverPoint management and monitoring
features for this pod, see the Cisco UCS Director EMC RecoverPoint Management Guide.
Cisco UCS Director Vblock Management Guide, Release 5.1
35
Initial Vblock Configuration
Initial EMC RecoverPoint Configuration
Creating a RecoverPoint Account
Step 1
Step 2
On the menu bar, choose Administration > Physical Accounts.
Click the Multi-Domain Managers tab.
Step 3
Step 4
Click Add.
In the Add Account dialog box, complete the following field:
Step 5
Step 6
Name
Description
Account Type drop-down list
Choose EMC RecoverPoint.
Click Submit.
In the next Add Account dialog box, complete the following fields:
Name
Description
Account Name field
The name of this RecoverPoint account. For example, RP-1.
Server IP field
The IP address of the RecoverPoint system.
Description field
The description of the RecoverPoint system.
Use Credential check box
Check the check box if you want to use a policy to give the credentials.
Username field
The username that this account uses to access the RecoveryPoint system. This
username must be a valid account in the RecoverPoint system.
Password field
The password associated with the username.
Protocol drop-down list
Choose the protocol transport type that you want to use for the account. This
can be one of the following:
• http (Hypertext Transfer Protocol)
• https (Hypertext Transfer Protocol Secure)
Note
The default transport type protocol for this account is
HTTPS.
Port field
The port used to access the RecoverPoint system. Port 7225 is the default secure
HTTPS port through which Cisco UCS Director connects to the RecoverPoint
system to obtain data.
Contact field
The email address that you use to contact the administrator or other person
responsible for this account.
Location field
The location of the contact.
Cisco UCS Director Vblock Management Guide, Release 5.1
36
Initial Vblock Configuration
Initial EMC RecoverPoint Configuration
Step 7
In the Multi-Domain Managers tab, choose the EMC RecoverPoint account that you just created.
Step 8
Click Test Connection.
What to Do Next
Verify that the account has been discovered. The discovery process typically takes a few minutes.
Cisco UCS Director Vblock Management Guide, Release 5.1
37
Initial Vblock Configuration
Initial EMC RecoverPoint Configuration
Cisco UCS Director Vblock Management Guide, Release 5.1
38
CHAPTER
4
Network Configuration for Cisco UCS Director
Baremetal Agent
This chapter contains the following sections:
• About the Network Configuration Options, page 39
• Single Network for Management and PXE, page 39
• Separate Networks for Management and PXE, page 40
• Configuring Cisco UCS Director Baremetal Agent , page 42
• Configuring the DHCP Server for a Baremetal Agent Account, page 43
• Starting and Stopping Baremetal Agent Services, page 44
• Configuring the Interface for the PXE Network, page 45
• Changing the Default Baremetal Agent Account, page 45
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 Preboot Execution Environment (PXE)
• Separate networks for management and PXE
Choose the network configuration option that best meets the requirements of your environment.
Single Network for Management and PXE
We recommend that you choose this network configuration option if your environment permits the following
to be hosted on the same network interface and Layer 2 network (see the following figure):
• Services provided by Baremetal Agent, such as DHCP, TFTP, and HTTP
Cisco UCS Director Vblock Management Guide, Release 5.1
39
Network Configuration for Cisco UCS Director Baremetal Agent
Prerequisites and Assumptions for a Single Network Configuration
• Management traffic between 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 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.
• 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 (see the following figure):
• On the PXE network, services provided by Baremetal Agent, such as DHCP, TFTP, and HTTP
Cisco UCS Director Vblock Management Guide, Release 5.1
40
Network Configuration for Cisco UCS Director Baremetal Agent
Prerequisites and Assumptions for a Separate Network Configuration
• On the Management network, traffic between 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 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 Baremetal Agent is reachable through a web browser and you can log in.
• 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 Baremetal Agent and Cisco UCS
Director Baremetal Agent
◦PXE network—Used for PXE services traffic, such as DHCP, HTTP, and TFTP
Cisco UCS Director Vblock Management Guide, Release 5.1
41
Network Configuration for Cisco UCS Director Baremetal Agent
Configuring Cisco UCS Director Baremetal Agent
Note
The PXE network VLAN must be configured as the native, or default, VLAN on the server. For example,
for a Cisco UCS server, edit the vNIC template associated with the server and choose the PXE network
VLAN as the native VLAN. You can perform this configuration in Cisco UCS Manager or Cisco UCS
Director.
Configuring Cisco UCS Director Baremetal Agent
Before you can use Baremetal Agent to PXE boot an operating system, you must first provision that operating
system image.
Before You Begin
Before you configure Cisco UCS Director Baremetal Agent (Baremetal Agent), you must do the following:
• Install Baremetal Agent, as described in Installation of Cisco UCS Director Baremetal Agent.
• Ensure that the Baremetal Agent VM is completely booted up, and that any VM Console is closed. You
must have the IP address of the Baremetal Agent VM.
• Set up the environment required to support a single or separate PXE and Management network
configuration, with the appropriate VLANs.
• To provide required DHCP services, ensure that at least one DHCP server is located in the same PXE
VLAN as Baremetal Agent and configure that DHCP server with an appropriate IP address range.
Step 1
Step 2
Step 3
Step 4
On the menu bar, choose Administration > Physical Accounts.
Click the Bare Metal Agents tab.
Click Add.
In the Add Baremetal Agent Appliance dialog box, complete the following fields:
Name
Description
BMA Name field
The name you assign to this Baremetal Agent account. We
recommend that you use a naming convention that includes
the names of the managed system components.
BMA Management/PXE Address field
The IP address assigned to the Management network for
Baremetal Agent. If your configuration uses a single
network for the Management and PXE networks, this IP
address is automatically assigned as the PXE address.
Note
Login ID field
An account with administrative privileges that you can use
to log in to Baremetal Agent.
Password field
The password for the account.
Cisco UCS Director Vblock Management Guide, Release 5.1
42
This address must be reachable from Cisco UCS
Director.
Network Configuration for Cisco UCS Director Baremetal Agent
Configuring the DHCP Server for a Baremetal Agent Account
Name
Description
BMA uses Different Interfaces for Management and
PXE Traffic check box
Check this check box if your configuration uses separate
networks for the PXE server and the Management network
that hosts the traffic manager.
BMA PXE Interface Address field
The IP address for the Baremetal Agent PXE network, if
your configuration uses separate networks.
Note
Description field
(Optional) A description of this Baremetal Agent.
Location field
(Optional) The location of this Baremetal Agent, such as
a physical location.
UCSD Database Address drop-down list
Choose the IP address that is associated with the Cisco
UCS Director database that this Baremetal Agent is going
to use.
Note
Step 5
This field appears only if the BMA uses Different
Interfaces... check box has been checked.
If you are configuring Baremetal Agent for
multi-node capabilities, choose the IP address of
the Inventory Database node.
Click Submit.
What to Do Next
Configure the DHCP Server for Cisco UCS Director Baremetal Agent
Configuring the DHCP Server for a Baremetal Agent Account
Note
For a multi-home DHCP configuration, use this procedure to configure the first subnet for the DHCP
server. For the remaining subnets, you must manually edit the DHCP configuration file
(/etc/dhcpd.conf).
Cisco UCS Director Vblock Management Guide, Release 5.1
43
Network Configuration for Cisco UCS Director Baremetal Agent
Starting and Stopping Baremetal Agent Services
Before You Begin
To provide required DHCP services, ensure that at least one DHCP server is located in the same PXE VLAN
as Baremetal Agent and configure that DHCP server with an appropriate IP address range. The DHCP server,
together with the TFTP server, are used to communicate with a PXE server.
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
On the menu bar, choose Administration > Physical Accounts.
Click the Bare Metal Agents tab.
Click the row for the Baremetal Agent account for which you want to configure the DHCP server.
Verify that services for the Baremetal Agent account are stopped.
Click Configure DHCP.
In the Configure DHCP dialog box, complete the following fields and click Submit.
• DHCP Subnet
• DHCP Netmask
• BOOTP Start IP
• BOOTP End IP
• Router IP Address
• PXE Server IP—This IP address must be the same IP address that you specified for the PXE network when you
added the Baremetal Agent account.
The DHCP IP address assignments are updated, and the DHCP service is restarted.
Step 7
Step 8
Click the row for the Baremetal Agent account and click Start Services.
After the services have started, verify that the status of the account is set to Active, and check that the Enabled Services
column indicates that all expected services are running.
What to Do Next
Set up PXE boot requests.
Starting and Stopping Baremetal Agent Services
Step 1
Step 2
Step 3
Step 4
On the menu bar, choose Administration > Physical Accounts.
Click the Bare Metal Agents tab.
Click the row for the Baremetal Agent account whose services you want to start or stop.
Click one of the following:
• Start Services
• Stop Services
Cisco UCS Director Vblock Management Guide, Release 5.1
44
Network Configuration for Cisco UCS Director Baremetal Agent
Configuring the Interface for the PXE Network
If services do not start, check the status displayed in the Enabled Services column. If this status indicates that services
are not enabled, verify the configuration of your DHCP server and try again.
Configuring the Interface for the PXE Network
You can use this to change or add an IP address for the PXE network used by Baremetal Agent.
Step 1
Step 2
Step 3
Step 4
On the menu bar, chooseAdministration > Physical Accounts
Click the Bare Metal Agents tab.
Click the row for the Baremetal Agent account for which you want to configure the interface for the PXE network.
In the Configure PXE Interface dialog box, complete the following fields:
a) From the Interface Name drop-down list, choose the interface you want to use for the PXE network.
b) Enter the IP address and subnet mask for the PXE network.
c) Click Submit.
Changing the Default Baremetal Agent Account
The first Baremetal Agent account that you create is designated as the default account and is used by default
in legacy workflows. To use a different account in the legacy workflows, you must designate that Baremetal
Agent account as the default.
Step 1
Step 2
Step 3
Step 4
On the menu bar, choose Administration > Physical Accounts.
Click the Bare Metal Agents tab.
Click the row for the Baremetal Agent account that you want designate as the default.
Click Set Default BMA.
Cisco UCS Director Vblock Management Guide, Release 5.1
45
Network Configuration for Cisco UCS Director Baremetal Agent
Changing the Default Baremetal Agent Account
Cisco UCS Director Vblock Management Guide, Release 5.1
46
CHAPTER
5
Vblock Operations
This chapter contains the following sections:
Tip
For more information about the Vblock operations described in this chapter, see the Cisco UCS Director
Management Guide for Cisco UCS Manager.
• Configuration Guidelines for Vblock Operations, page 47
Configuration Guidelines for Vblock Operations
The following table provides Cisco UCS Director guidelines for implementing Vblock operations. The
configuration notes explain important configuration details related to each task in this chapter.
Tip
For more information related to the tasks in this chapter, see the Cisco UCS Director Management Guide
for Cisco UCS Manager.
Task
Configuration Notes
Creating an Organization, on page 50 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 50
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 51
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.
Cisco UCS Director Vblock Management Guide, Release 5.1
47
Vblock Operations
Configuration Guidelines for Vblock Operations
Task
Configuration Notes
Creating a MAC Pool, on page 52
Create two MAC pools for each fabric interconnect. For example,
fabric interconnect A and B. Specify 2 in the Size field
(recommended).
Creating a WWNN Pool, on page 52 Create two worldwide node name (WWNN) pools for each fabric
interconnect. Specify 2 in the Size field (recommended).
Creating a WWPN Pool, on page 53 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 53
Create the network control policy with the Cisco Discovery Protocol
(CDP) enabled.
Creating a vNIC Template, on page
55
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 59
If the PXE server and the Cisco UCS server are in separate
VLANs, you must create separate vNIC templates for both
servers in each fabric interconnect.
Create a virtual storage area network (VSAN) for each fabric
interconnect. For example, fabric interconnect A and B.
Associating the VSANs to the Fabric Associate each VSAN with each fabric interconnect.
Interconnects
Creating a vHBA Template, on page Create a vHBA template for each fabric interconnect. Follow the
60
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.
62
Creating a SAN Boot Policy, on page Create a SAN boot policy for each fabric interconnect.
63
Cisco UCS Director Vblock Management Guide, Release 5.1
48
Vblock Operations
Configuration Guidelines for Vblock Operations
Task
Configuration Notes
Creating a vNIC, on page 66
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 66
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
67
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
69
If the PXE server and the Cisco UCS server are in separate
VLANs, you must create separate vNIC templates for both
servers in each fabric interconnect.
Follow the instructions in the task and use the following configuration
guidelines:
• From the SAN Connectivity Type drop-down list, choose
Expert.
• From the WWNN Pool drop-down list, choose the WWNN
pool that you created previously.
• In the Add vHBA field, specify the number of vHBAs (for
each fabric interconnect) that you want to add to the storage
policy.
• From the Template For vHBA1/vHBA2/vHBA3/vHBA4
drop-down list, choose the vHBA template that you created.
Note
If the PXE server and the Cisco UCS server are in separate
VLANs, you must create separate vNIC templates for both
servers in each fabric interconnect.
Cisco UCS Director Vblock Management Guide, Release 5.1
49
Vblock 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
You can configure a chassis policy 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 Vblock Management Guide, Release 5.1
50
Vblock 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 Vblock Management Guide, Release 5.1
51
Vblock 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 Vblock Management Guide, Release 5.1
52
Vblock 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 Vblock Management Guide, Release 5.1
53
Vblock 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
Cisco UCS Director Vblock Management Guide, Release 5.1
54
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.
Vblock 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 Vblock Management Guide, Release 5.1
55
Vblock 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 Vblock Management Guide, Release 5.1
56
Vblock 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 Vblock Management Guide, Release 5.1
57
Vblock 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
Step 10
usNIC Template Connection Policy drop-down list
(Displays only if you choose usNIC Policy as the VNIC
Template connection policy.) Choose the usNIC collection
policy that vNICs created from this vNIC template should
use.
VMQ Template Connection Policy drop-down list
(Displays only if you choose VMQ Policy as the VNIC
Template connection policy.) Choose the VM collection
policy that vNICs created from this vNIC template should
use.
Click Submit.
What to Do Next
Include the vNIC template in a network policy.
Cisco UCS Director Vblock Management Guide, Release 5.1
58
This field is available only with Cisco UCS
Manager Release 2.2.
Vblock Operations
Creating a VSAN
Creating a VSAN
Note
Fibre Channel over Ethernet (FCoE) VLANs in the SAN cloud and VLANs in the LAN cloud must have
different IDs. Using the same ID for an FCoE VLAN in a VSAN and a VLAN results in a critical fault
and traffic disruption for all vNICs and uplink ports using that FCoE VLAN. Ethernet traffic is dropped
on any VLAN that has an ID that overlaps with an FCoE VLAN ID.
Step 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 Vblock Management Guide, Release 5.1
59
Vblock 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 Vblock Management Guide, Release 5.1
60
Vblock 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 Vblock Management Guide, Release 5.1
61
Vblock 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 Vblock Management Guide, Release 5.1
62
Vblock Operations
Creating a SAN Boot Policy
Step 8
Step 9
Step 10
Step 11
Step 12
Step 13
Step 14
Name
Description
Boot Security check box
(Displays only when UEFI is selected as the boot mode.)
Enables the secure boot option for the servers that use this
boot policy.
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 Vblock Management Guide, Release 5.1
63
Vblock 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 Vblock Management Guide, Release 5.1
64
Vblock Operations
Creating a SAN Boot Policy
Step 8
Step 9
Step 10
Step 11
Step 12
Step 13
Step 14
Step 15
Name
Description
Boot Security check box
(Displays only when UEFI is selected as the boot mode.)
Enables the secure boot option for the servers that use this
boot policy.
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 field
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 Vblock Management Guide, Release 5.1
65
Vblock 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
A 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, choose Policies > 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 Vblock Management Guide, Release 5.1
66
Vblock Operations
Creating a Network Policy
Name
Description
vHBA Name field
A 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 Vblock Management Guide, Release 5.1
67
Vblock 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.
What to Do Next
Include the network policy in a service profile.
Cisco UCS Director Vblock Management Guide, Release 5.1
68
Vblock Operations
Creating a Storage Policy
Creating a Storage Policy
Step 1
Step 2
Step 3
Step 4
Step 5
On the menu bar, choose Policies > 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
A 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 the 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:
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.
Cisco UCS Director Vblock Management Guide, Release 5.1
69
Vblock Operations
Creating a 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 Vblock Management Guide, Release 5.1
70
CHAPTER
6
Vision Intelligent Operations for Vblock
This chapter contains the following sections:
• About Vision Intelligent Operations, page 71
• Initial VCE Vision Intelligent Operations Configuration, page 71
• Vision Intelligent Operations for Vblock, page 73
About Vision Intelligent Operations
The VCE Vision Intelligent Operations (IO) software suite is used for managing a Vblock pod in a converged
infrastructure environment to enable and simplify Vblock operations in the following ways:
• Identifies Vblock pod locations and their components.
• Reports on the health or operating status of the Vblock pod.
• Verifies if the Vblock pod is compliant with the VCE release certification matrix. For more information,
see the VCE Support web page.
• Acts as a mediation layer between your pod and its existing management tools by dynamically infusing
intelligence into the existing Vblock management system.
• Provides a continuous, real-time perspective of your compute, network, storage, and virtualization
resources as a single object to ensure that your management tools reflect the most current state of your
Vblock pod.
• Gives the Vblock system information natively through VMware vCenter and vCenter Operations Manager.
Initial VCE Vision Intelligent Operations Configuration
A VCE Vision Intelligent Operations account is created on a Vblock pod. After you create this account, the
Vblock pod discovers the VMware vCenter and vCenter Operations Manager on which the Vision Intelligent
Operations software is installed.
Cisco UCS Director Vblock Management Guide, Release 5.1
71
Vision Intelligent Operations for Vblock
Creating a Vision Intelligent Operations Account
Creating a Vision Intelligent Operations Account
Step 1
Step 2
On the menu bar, choose Administration > Physical Accounts.
Click the Physical Accounts tab.
Step 3
Step 4
Click Add.
In the first Add Account dialog box, complete the following fields:
Step 5
Step 6
Name
Description
Pod drop-down list
Choose the Vblock pod name.
Category drop-down list
Choose Pod Management.
Account Type drop-down list
Choose VCE Vision Intelligent Operations.
Click Submit.
In the next Add Account dialog box, complete the following fields:
Name
Description
Account Name field
A unique name that you assign to this account.
Server Domain Name field
The fully qualified domain name (FQDN) of the Vision Intelligent Operations
server.
Note
The Vision Intelligent Operation server FQDN must be resolvable in
DNS or listed in the local host file on the server where the Cisco UCS
Director software is installed. To edit the hosts file, log into the Cisco
UCS Director server root directory and open the hosts file. The following
example is for the Linux platform:
vi etc/hosts
UCS-server-IP-address vision521.cisco.com
Use Credential Policy check box
Check the check box if you want to use a policy to give the credentials.
Credential Policy drop-down list
(Displays if the Use Credential Policy check box is selected) Choose a
pre-defined credential policy. If there is no credential policy, click the plus (+)
icon to add a credential policy. In the Add Credential Policy dialog box, define
the credential parameters for this policy and click Submit.
Username field
The username that this account uses to access the Vision Intelligent Operations
server. This username must be the Vision Intelligent Operations Application
Programable Interface (API) username.
Note
Do not use the Vision Intelligent Operations virtual machine (VM)
username to connect to the Vision Intelligent Operations server through
Cisco UCS Director.
Cisco UCS Director Vblock Management Guide, Release 5.1
72
Vision Intelligent Operations for Vblock
Vision Intelligent Operations for Vblock
Name
Description
Password field
The password associated with the username, which is the Vision Intelligent
Operations API password.
Note
Do not use the Vision Intelligent Operations VM password to connect
to the Vision Intelligent Operations server through Cisco UCS Director.
Protocol drop-down list
The https parameter is preselected for the transport type protocol.
Note
http is not supported for Vision Intelligent
Operations.
Port field
The port used to access the Vision Intelligent Operations server. Port 8443 is
the default secure HTTPS port.
Contact field
The email address that you use to contact the administrator or other person
responsible for this account.
Location field
The location of the contact.
Step 7
In the Physical Accounts tab, click the Vision Intelligent Operations account that you just created.
Step 8
Click Test Connection.
The Test Connectivity dialog box displays and confirms if the connection was successful.
Vision Intelligent Operations for Vblock
Cisco UCS Director uses Vision Intelligent Operations, which functions as a virtual machine (VM), to
auto-discover Release Compatibility Matrix (RCM) and inventory data.
Accessing or Modifying a Vision Intelligent Operations Orchestration Workflow
Task
Step 1
Step 2
On the menu bar, choose Policies > Orchestration.
In the Orchestration pane, click the Workflows tab.
Step 3
Step 4
On the Workflows tab, click to expand the VCE folder and double-click the VCE task.
In the Available Tasks panel of the Workflow Designer dialog box, click Pod Management Tasks > VCE Vision
Intelligent Operations Tasks, and double-click the orchestration workflow task that you want.
Step 5
If you want to edit this orchestration workflow task, click on the orchestration workflow task and click Edit Workflow
Properties in the Workflow Designer tab, or click Edit Workflow in the Workflows tab on the Orchestration pane.
Cisco UCS Director Vblock Management Guide, Release 5.1
73
Vision Intelligent Operations for Vblock
Verifying Vblock Release Certification Matrix Compliance
In the Edit Workflow dialog box, workflow details, user inputs and outputs can be viewed, configured, or modified.
What to Do Next
Validate and execute the Vision Intelligent Operations orchestration workflow task that you modified.
Verifying Vblock Release Certification Matrix Compliance
The Release Certification Matrix (RCM) provides a set of criteria that compares the actual settings found on
your Vblock pod to the default or configured values for the Vision Intelligent Operations Get Compliance
Score for Profile orchestration workflow task. The report provides an RCM score that shows how closely
your Vblock pod complies to the RCM depending on the minimum score specified in the workflow. The score
can tell you whether your Vblock pod passes or fails the RCM compliance check and provides a time stamp
for when you got this score
Step 1
Step 2
Step 3
On the menu bar, click Converged.
Click the Vblock pod.
In the Pod Mgmt row, double-click the VBLOCK icon.
Step 4
In the Release Certification Matrix tab, click the Vblock RCM profile name that you want, and click Get Score.
Step 5
In theGet Score for Profile dialog box, click Submit.
Step 6
In the Submit Result dialog box, when the score appears, click OK.
Step 7
Double-click the Vblock RCM profile name.
The Compliance Rule Summary tab displays the compliance profile group titles (CPG Title), compliance profile rules
(CPR column), managed component title (for software and devices), and expected version information for the component.
Note
The Result column displays either pass or fail for an RCM profile designated as default only. Cisco UCS
Director supports two default profiles at a time only. One default RCM profile is designated for a Vblock
component and the other default RCM profile is designated for the security component.
Viewing Vblock Compute, Network, and Storage Information
This task is used to show the following inventory data collected by the Vision Intelligent Operations software
for your Vblock pod.
The Calculated Status displayed in the Vblock System and Vblock System Compute tabs is determined by
a hierarchical model of the Vblock System inventory. The system library applies the VCE-derived algorithm
to a component, assigns a health status to the component, and then moves up the inventory tree. The health
status of each component is based on the status of the lower level component. When all the components in a
family have been calculated, the family is assigned a status. The statuses of the families are then used to
calculate the health of the Vblock system.
The following Calculated Status conditions can appear. These conditions are determined by the System Library:
• Inoperable—All subcomponents are not operable.
Cisco UCS Director Vblock Management Guide, Release 5.1
74
Vision Intelligent Operations for Vblock
Assigning a Policy to a Vision Intelligent Operations Task
• Operable—All subcomponents are operable.
• Minor—A sub-component is inoperable, but no subcomponents are in a critical, major, or degraded
state.
• Degraded—One-fourth of the subcomponents are not operating properly.
• Major—One-third of the subcomponents are not operating properly.
• Critical—More than half of the subcomponents are not operating properly.
Step 1
Step 2
Step 3
On the menu bar, click Converged.
Click the Vblock pod.
In the Pod Mgmt row, double-click the VBLOCK icon.
Step 4
In the Vision Intelligent Operations panel, click the Vblock System tab to view the Vision Intelligent Operations
software version, overall system health, description, prior state, serial number, operational status and location information
for your Vblock pod.
Click the Vblock System Compute tab to view the Cisco UCS server model, Cisco UCS Manager IP address, Cisco
UCS server version, RCM score, and so on.
Click the Vblock System Network tab to view the Cisco Nexus Series device and switch fabric software revision
numbers, IP addresses, models, and so on.
Click the Vblock System Storage tab to view VNX or VMAX storage system information, such as the storage arrays,
their subcomponents, software versions, and so on.
Step 5
Step 6
Step 7
Assigning a Policy to a Vision Intelligent Operations Task
Step 1
Step 2
Step 3
On the menu bar, click Converged.
Click the Vblock pod.
In the Pod Mgmt row, double-click the VBLOCK icon.
Step 4
In the Vision IO panel, click the System Tasks tab.
Step 5
In the System Tasks panel, click the VCE Vision Intelligent Operations Tasks folder icon to expand the folder.
Step 6
Step 7
Step 8
Click the VCEVisionIntelligentOperationsInventoryCollector task icon.
Click Manage Task.
In the Manage Task dialog box, complete the following fields:
Name
Description
Task Execution drop-down list
Choose Enable or Disable to enable or disable this inventory collector task.
Cisco UCS Director Vblock Management Guide, Release 5.1
75
Vision Intelligent Operations for Vblock
Assigning a Policy to a Vision Intelligent Operations Task
Name
Description
System Task Policy drop-down list Choose from the following options to specify which system task policy is used
for inventory collection:
• Choose default-system-task-policy defined for the entire system.
• Choose local-run-policy for this pod.
Minutes drop-down list
Step 9
Step 10
Step 11
Choose the frequency in minutes for how often the inventory collector task is
executed.
Click Submit.
If you want to run this inventory collector task, click Run Now.
If you want to view this inventory collector task history and reporting information, click View Details.
Cisco UCS Director Vblock Management Guide, Release 5.1
76
CHAPTER
7
Orchestration Workflow Operations
This chapter contains the following sections:
• Cisco UCS Manager Orchestration Tasks, page 77
• Navigating to a Predefined Orchestration Workflow, page 79
• Provisioning Vblock Orchestration Workflows, page 79
• Validating and Executing an Orchestration Workflow, page 107
Cisco UCS Manager Orchestration Tasks
Cisco UCS Director includes orchestration features that allow you to automate the 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 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 Workflow Designer, in the Task
Library and the Cisco UCS Tasks folder. The Task Library, which includes a description of the orchestration
tasks, 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
• Pools
Cisco UCS Director Vblock Management Guide, Release 5.1
77
Orchestration Workflow Operations
Importing a Workflow
• Policies
• VLANs
• vNICs
• Service profiles
• Service profile templates
• Organizations
Importing a Workflow
This task is used to import a workflow that you previously downloaded.
Step 1
Step 2
On the menu bar, choose Policies > Orchestration.
In the Orchestration pane, click the Workflows tab.
Step 3
Step 4
On the Workflows tab, click the workflow folder that you want to import the workflow into and click Import.
In the Import dialog box, click Browse to go to the directory on which the workflow was downloaded.
Step 5
Step 6
Step 7
Step 8
Click on the workflow and click Open.
Click Upload.
Once the zipped file has uploaded successfully, click Import.
(Optional) In the Import dialog box, complete the following fields to specify how assets of the zipped file are handled
if these assets already exist in the workflow folder:
Name
Description
Workflows drop-down list
Choose from the following options to specify how this asset is handled:
• Replace
• Keep Both
• Skip
Custom Tasks drop-down list
Choose from the following options to specify how this asset is handled:
• Replace
• Keep Both
• Skip
Script Modules drop-down list
Choose from the following options to specify how this asset is handled:
• Replace
• Keep Both
• Skip
Cisco UCS Director Vblock Management Guide, Release 5.1
78
Orchestration Workflow Operations
Accessing Task Documentation
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 check box 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 see more information about 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 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
Provisioning Vblock Orchestration Workflows
The following Vblock orchestration workflow examples are provided to show how a predefined orchestration
workflow in Cisco UCS Director can be provisioned in your Vblock implementation. It is beyond the scope
Cisco UCS Director Vblock Management Guide, Release 5.1
79
Orchestration Workflow Operations
Provisioning a Stateless Blade Server Orchestration Workflow Overview
of this document to discuss all the orchestration workflows that are available for Vblock. Go to the Cisco
Developed Integrations page for Vblock workflows, which are added on a regular basis.
Provisioning a Stateless Blade Server Orchestration Workflow Overview
The following table provides an overview for configuring the stateless blade server orchestration workflow.
Use this table as a point of reference to determine the specific task name, task type, and the section to which
it is aligned. Each task covered in subsequent sections references the task name and task type in a generic
way. Once all the tasks in the workflow are validated and bound to the local environment, you must validate
the entire workflow. The following table provides an overview for implementing the stateless blade server
orchestration workflow. See Validating and Executing an Orchestration Workflow, on page 107 for more
information.
Note
A blade server can be booted in a stateless environment, which is a storage area network (SAN), in order
to fix a blade server failure state. An example of a stateless environment can be the World Wide Web,
which does not follow settings or any other data for the next session.
Task Name
Task Type
Section
ModifyWorkflowPriority_89
95. Modify Workflow Priority
Modifying the Workflow
Priority, on page 82
CreateUCSServiceProfile_160
114. Create UCS Service Profile
Creating the Cisco UCS
Service Profile Task, on page
83
SelectBlades_91
96. Select UCS Server
Choosing the Cisco UCS
Server, on page 84
AssociateUCSServiceProfile_92
97. Associate UCS Service Profile
Associating the Cisco UCS
Service Profile, on page 85
UCSBladePowerOFFAction_146
108. Power Off UCS Server
Powering Off the Cisco UCS
Server, on page 86
PXEBoot_93
98. Setup PXE Boot
Setting Up PXE Boot, on page
87
CreateLUN_247
115. Create VNX LUN
Creating a VNX LUN, on
page 89
CreateStorageGroup_117
101. Create VNX Storage Group
Creating a VNX Storage
Group, on page 90
AddHostInitiatorEntry_118
102. Add VNX Host Initiator Entry
Adding a VNX Host Initiator
Entry, on page 91
Cisco UCS Director Vblock Management Guide, Release 5.1
80
Orchestration Workflow Operations
Provisioning a Stateless Blade Server Orchestration Workflow Overview
Task Name
Task Type
Section
AddHostInitiatorEntry_119
103. Add VNX Host Initiator Entry
Adding a VNX Host Initiator
Entry, on page 91
GenericConfigureSANZoning_120 104. Generic Configure SAN Zoning
Configuring Generic Storage
Area Network Zoning, on
page 92
AddHoststoStorageGroup_121
105. Add Hosts to VNX Storage Group Adding Hosts to a VNX
Storage Group, on page 94
AddLUNtoStorageGroup_122
106. Add VNX LUN to Storage Group Adding a LUN to a VNX
Storage Group, on page 95
ModifyUCSServiceProfileBootPolicy_250 116. Modify UCS Service Profile Boot Modifying the Cisco UCS
Policy
Service Profile Boot Policy,
on page 96
ModifySANTargetLUNIdofBootPolicy_123 107. Modify UCS Boot Policy LUN ID Modifying the Cisco UCS
Boot Policy LUN ID, on page
97
Reset Blade to kick off PXE
109. Reset UCS Server
Resetting the Cisco UCS
Server, on page 98
PXEBootWait_95
99. Monitor PXE Boot
Monitoring PXE Boot, on
page 99
ModifyUCSServiceProfileBootPolicy_96 100. Modify UCS Service Profile Boot Modifying the Cisco UCS
Policy
Service Profile Boot Policy,
on page 96
AddVLANtoServiceProfile_303
117. Add VLAN to Service Profile
Adding a VLAN to a Service
Profile, on page 100
DisassociateUCSServiceProfile_158 110. Disassociate UCS Service Profile Disassociating the Cisco UCS
Service Profile, on page 101
WaitforDuration_159
111. Wait for Specified Duration
Configuring the Waiting for a
Specific Duration Task, on
page 102
AssociateUCSServiceProfile_160 112. Associate UCS Service Profile
Associating the Cisco UCS
Service Profile, on page 85
WaitforDuration_161
Configuring the Waiting for a
Specific Duration Task, on
page 102
113. Wait for Specified Duration
Cisco UCS Director Vblock Management Guide, Release 5.1
81
Orchestration Workflow Operations
Provisioning a Stateless Blade Server Orchestration Workflow Overview
Task Name
Task Type
Section
UCSBladeResetAction_317
118. Reset UCS Server
Resetting the Cisco UCS
Server, on page 98
Modifying the Workflow Priority
See the orchestration workflow overview for the specific task name and task type.
Step 1
Under the blue workflow Start icon, find and double-click the Modify Workflow Priority task. The Edit Task dialog
box appears with the Task Information pane.
The following parameters are preconfigured:
Name
Description
Task Name field
The modify workflow priority task name is entered.
Task Category drop-down list
The General Tasks option is chosen.
Task Type drop-down list
The Modify Workflow Priority task type is chosen.
Comment field
Comments that pertain to this task.
Step 2
Click Next to advance to the User Input Mapping pane.
Step 3
Click Next to again to advance to the Task Inputs pane.
The following parameters are configurable:
Name
Description
Priority drop-down list
Choose High. The priority is saved.
Revalidate button
Binds all the necessary parameters identified in this task to the environment.
Submit button
Saves the workflow task changes in the database. A confirmation dialog box
appears.
Cisco UCS Director Vblock Management Guide, Release 5.1
82
Orchestration Workflow Operations
Provisioning a Stateless Blade Server Orchestration Workflow Overview
Creating the Cisco UCS Service Profile Task
See the orchestration workflow overview for the specific task name and task type.
Step 1
Step 2
Under the blue workflow Start icon, find and double-click the Create UCS Service Profile task. The Edit Task dialog
box appears with the Task Information pane.
The following parameters are preconfigured:
Name
Description
Task Name
The create UCS service profile task name is entered.
Task Category drop-down list
The Cisco UCS Tasks category is chosen.
Task Type drop-down list
The Create UCS Service Profile task type is chosen.
Comment field
Comments that pertain to this task.
Task Details display field
The output generated by this task.
Click Next to advance to the User Input Mapping pane.
The following parameter is configurable:
Note
Check the Map to User Input check box next to the following attribute to map it to the workflow when the
workflow executes.
Name
Description
Service Profile Name drop-down list Choose the Service Profile Name attribute.
Step 3
Click Next to advance to the Task Inputs pane.
Note
This workflow assumes that the following actions have been accomplished through Cisco UCS Director:
• All pod required elements are discovered and managed.
• All required pools and resources for a service profile are created.
• All required policies are defined and bound to their respective pools and resources.
The following parameters are configurable:
Note
Any parameter that is not included in the following table is either not set or uses the default setting.
Name
Description
Description field
Comments that pertain to this task.
Organization button
The pre-sales option is chosen.
UUID Assignment drop-down list
Choose pe_uuid_pool.
Cisco UCS Director Vblock Management Guide, Release 5.1
83
Orchestration Workflow Operations
Provisioning a Stateless Blade Server Orchestration Workflow Overview
Name
Description
Storage Policy drop-down list
Choose ps-storage-policy.
Network Policy drop-down list
Choose ps-network-policy.
PXE Boot Policy drop-down list
Choose ps-lan-boot.
Server Boot Policy drop-down list
Choose ps-san-policy.
Revalidate button
Binds all the necessary parameters identified in this task to the environment.
Submit button
Saves the workflow task changes in the database. A confirmation dialog box
appears.
Choosing the Cisco UCS Server
See the orchestration workflow overview for the specific task name and task type.
Step 1
Under the blue workflow Start icon, find and double-click the Select UCS Server task. The Edit Task dialog box
appears with the Task Information pane.
The following parameters are preconfigured:
Name
Description
Task Name
The select blades task name is entered.
Task Category drop-down list
The UCS Tasks category is chosen.
Task Type drop-down list
The Select UCS Server task type is chosen.
Comment field
Comments that pertain to this task.
Task Details display field
The output generated by this task.
Step 2
Click Next to advance to the User Input Mapping pane. No parameters are configured for this pane.
Step 3
Click Next to advance to the Task Inputs pane.
The following parameters are configurable:
Name
Description
Account Name drop-down list
Choose the account name. For example, vBLOCK-300-UCS.
Cisco UCS Director Vblock Management Guide, Release 5.1
84
Orchestration Workflow Operations
Provisioning a Stateless Blade Server Orchestration Workflow Overview
Name
Description
Server Selection Scope drop-down Choose Include Servers.
list
Servers field Select button
Click the Select button to select a Cisco UCS server. For example,
*sys/chassis-1/blade-3.
Note
The asterisk (*) at the beginning of the path indicates this server is
associated to your environment.
Use Unassociated Servers Only
check box
Check the check box for your environment's requirements.
Number of CPUs field
The number of CPUs in your environment.
Total Memory (GB) field
The total memory in gigabytes (GB).
Revalidate button
Binds all the necessary parameters identified in this task to the environment.
Submit button
Saves the workflow task changes in the database. A confirmation dialog box
appears.
Associating the Cisco UCS Service Profile
See the orchestration workflow overview for the specific task name and task type.
Step 1
Under the blue workflow Start icon, find and double-click the Associate UCS Service Profile task. The Edit Task
dialog box displays with the Task Information pane.
The following parameters are preconfigured:
Name
Description
Task Name field
The associate UCS service profile task name is entered.
Task Category drop-down list
The Cisco UCS Tasks category is chosen.
Task Type drop-down list
The Associate UCS Service Profile task type is chosen.
Comment field
Comments that pertain to this task.
Task Details display field
The output generated by this task.
Cisco UCS Director Vblock Management Guide, Release 5.1
85
Orchestration Workflow Operations
Provisioning a Stateless Blade Server Orchestration Workflow Overview
Step 2
Step 3
Click Next to advance to the User Input Mapping pane.
The following parameters are configurable:
Name
Description
Service Profile drop-down list
Choose the create UCS service profile task service profile identity.
Server drop-down list
Choose the select blades task server identity.
Click Next to advance to the Task Input pane.
The following parameters are configurable:
Name
Description
Server Selection Scope drop-down Choose the Include Servers option.
list
Revalidate button
Binds all the necessary parameters identified in this task to the environment.
Submit button
Saves the workflow task changes in the database. A confirmation dialog box
appears.
Powering Off the Cisco UCS Server
See the orchestration workflow overview for the specific task name and task type.
Step 1
Under the blue workflow Start icon, find and double-click the Power Off UCS Server task. The Edit Task dialog box
appears with the Task Information pane.
The following parameters are preconfigured:
Name
Description
Task Name field
The Cisco UCS blade power off action task name is entered.
Task Category drop-down list
The Cisco UCS Tasks category is chosen.
Task Type drop-down list
The Power Off UCS Server task type is chosen.
Comment field
Comments that pertain to this task.
Task Details display field
The output generated by this task.
Cisco UCS Director Vblock Management Guide, Release 5.1
86
Orchestration Workflow Operations
Provisioning a Stateless Blade Server Orchestration Workflow Overview
Step 2
Step 3
Click Next to advance to the User Input Mapping pane.
The following parameter is configurable:
Note
Check the Map to User Input check box next to the following attribute to map it to the workflow when the
workflow executes.
Name
Description
Server drop-down list
Choose the server identity attribute. For example,
SelectBlades_91_SERVER_IDENTITY.
Click Next to advance to the Task Input pane.
The following parameters are configurable:
Name
Description
Revalidate button
Binds all the necessary parameters identified in this task to the environment.
Submit button
Saves the workflow task changes in the database. A confirmation dialog box
appears.
Setting Up PXE Boot
See the orchestration workflow overview for the specific task name and task type.
Step 1
Step 2
Under the blue workflow Start icon, find and double-click the Setup PXE Boot task. The Edit Task dialog box appears
with the Task Information pane.
The following parameters are preconfigured:
Name
Description
Task Name field
The PXE Boot task name is entered.
Task Category drop-down list
The Network Services Tasks category is chosen.
Task Type drop-down list
The Setup PXE Boot task type is chosen.
Comment field
Comments that pertain to this task.
Task Details display field
The output generated by this task.
Click Next to advance to the User Input Mapping pane.
The following parameters are configurable:
Cisco UCS Director Vblock Management Guide, Release 5.1
87
Orchestration Workflow Operations
Provisioning a Stateless Blade Server Orchestration Workflow Overview
Note
Step 3
Check the Map to User Input check box next to each of the following attributes to map them to the workflow
when the workflow executes.
Name
Description
Server MAC Address drop-down
list
Choose the UCS service profile name to the output UCS blade MAC address
attribute. For example, Associate
UCSServiceProfile_92.OUTPUT_UCS_BLADE_MAC_ADDRESS.
Server Host Name drop-down list
Choose the hostname (machine name) attribute. For example, Host Name.
Click Next to advance to the Task Input pane.
The following parameters are configurable:
Name
Description
OS Type drop-down list
Choose the network device OS type. For example, ESXi5.0-u1 (with Nexus
1000v VEM).
Server IP Address field
The server IP address range.
Server Net Mask field
The server subnetwork (subnet) mask.
Server Gateway field
The server gateway IP address.
Server Name Server field
The server name server IP address.
Management VLAN field
The management VLAN number.
Root Password field
The root password.
Timezone drop-down list
Choose the time zone for your environment.
Revalidate button
Binds all the necessary parameters identified in this task to the environment.
Submit button
Saves the workflow task changes in the database. A confirmation dialog box
appears.
Cisco UCS Director Vblock Management Guide, Release 5.1
88
Orchestration Workflow Operations
Provisioning a Stateless Blade Server Orchestration Workflow Overview
Creating a VNX LUN
See the orchestration workflow overview for the specific task name and task type.
Step 1
Under the blue workflow Start icon, find and double-click the Create VNX LUN task. The Edit Task dialog box appears
with the Task Information pane.
The following parameters are preconfigured:
Name
Description
Task Name field
The task name for creating a logical unit number (LUN) is entered. For example,
CreateLUN_247.
Task Category drop-down list
The EMC VNX Tasks category is chosen.
Task Type drop-down list
The Create VNX LUN task type is chosen.
Comment field
Comments that pertain to this task.
Task Details display field
The output generated by this task.
Step 2
Click Next to advance to the User Input Mapping pane. No parameters are configured for this pane.
Step 3
Click Next to advance to the Task Inputs pane.
The following parameters are configurable:
Name
Description
Select EMC Account Select... button Chooses the EMC account name (if required).
LUN Name field
The name of the LUN. For example, VB_LUN_Boot_ESXi_$(SR_ID).
Let System Specify LUN ID check Check the check box to allow the system to specify the LUN ID.
box
Storage Pool Type drop-down list
Choose Pool for the type of storage pool.
User Capacity field
The LUN capacity created by user.
Capacity Units drop-down list
Choose the size of the LUN that is requested by user.
Default Owner drop-down list
Choose Auto to allow the system to automatically assign the default owner of
the LUN.
Initial Tier Placement drop-down
list
Choose Optimize for Pool Performance.
Revalidate button
Binds all the necessary parameters identified in this task to the environment.
Cisco UCS Director Vblock Management Guide, Release 5.1
89
Orchestration Workflow Operations
Provisioning a Stateless Blade Server Orchestration Workflow Overview
Name
Description
Submit button
Saves the workflow task changes in the database. A confirmation dialog box
appears.
Creating a VNX Storage Group
See the orchestration workflow overview for the specific task name and task type.
Step 1
Under the blue workflow Start icon, find and double-click the Create VNX Storage Group task. The Edit Task dialog
box appears with the Task Information pane.
The following parameters are preconfigured:
Name
Description
Task Name
The create storage group task name is entered.
Task Category drop-down list
The EMC VNX Tasks category is chosen.
Task Type drop-down list
The Create VNX Storage Group task type is chosen.
Comment field
Comments that pertain to this task.
Task Details field
The output generated by this task.
Step 2
Click Next to advance to the User Input Mapping pane. No parameters are configured for this pane.
Step 3
Click Next to advance to the Task Inputs pane.
The following parameters are configurable:
Name
Description
Select EMC Account Select... button Chooses the EMC account name (if required).
Storage Group Name field
The storage group name. For example, VB_SG_ESXi_${SR_ID}.
Submit button
Saves the workflow task changes in the database. A confirmation dialog box
appears.
Cisco UCS Director Vblock Management Guide, Release 5.1
90
Orchestration Workflow Operations
Provisioning a Stateless Blade Server Orchestration Workflow Overview
Adding a VNX Host Initiator Entry
See the orchestration workflow overview for the specific task name and task type.
Step 1
Step 2
Step 3
Under the blue workflow Start icon, find and double-click the Add VNX Host Initiator Entry task. The Edit Task
dialog box appears with the Task Information pane.
The following parameters are preconfigured:
Name
Description
Task Name
The VNX host initiator task name is entered.
Task Category drop-down list
The EMC VNX Tasks category is chosen.
Task Type drop-down list
The Add VNX Host Initiator Entry task type is chosen.
Comment field
Comments that pertain to this task.
Task Details display field
The output generated by this task.
Click Next to advance to the User Input Mapping pane.
The following parameters are configurable:
Note
Check the Map to User Input check box next to each of the following attributes to map them to the workflow
when the workflow executes.
Name
Description
Host Name drop-down list
Choose the hostname attribute. For example, Host Name.
IP Address drop-down list
Choose the IP address attribute. For example,
PXEBoot_93.OUTPUT_HOST_IP_ADDRESS.
WWN/IQN drop-down list
Choose the WWN/IQN attribute. For example,
CreateUCSServiceProfile_160.OUTPUT_SP_VHBA1_WWN.
Click Next to advance to the Task Inputs pane.
The following parameters are configurable:
Name
Description
Select EMC Account Select... button Choose the EMC account name (if required). For example, vBLOCK-300.
Add Initiator to drop-down list
Choose New Host.
SP Port Select... button
Choose the SP Port. For example, A-2, A-0.
Initiator Type drop-down list
Choose CLARiiON Open.
Cisco UCS Director Vblock Management Guide, Release 5.1
91
Orchestration Workflow Operations
Provisioning a Stateless Blade Server Orchestration Workflow Overview
Name
Description
Failover Mode drop-down list
Choose Active-Active mode(ALUA)-failovermode4.
Revalidate button
Binds all the necessary parameters identified in this task to the environment.
Submit button
Saves the workflow task changes in the database. A confirmation dialog box
appears.
Configuring Generic Storage Area Network Zoning
See the orchestration workflow overview for the specific task name and task type.
Step 1
Step 2
Under the blue workflow Start icon, find and double-click the Generic Configure SAN Zoning task. The Edit Task
dialog box appears with the Task Information pane.
The following parameters are preconfigured:
Name
Description
Task Name
The generic configure SAN zoning task name is entered.
Task Category drop-down list
The Cisco Network Tasks category is chosen.
Task Type drop-down list
The Generic Configure SAN Zoning task type is chosen.
Comment field
Comments that pertain to this task.
Task Details display field
The output generated by this task.
Click Next to advance to the User Input Mapping pane.
The following parameters are configurable:
Note
Check the Map to User Input check box next to each of the following attributes to map them to the workflow
when the workflow executes.
Name
Description
Service Profile drop-down list
Choose the service profile attribute. For example,
UCSBladePowerOFFAction_146.SERVICE_PROFILE_IDENTITY.
Select vHBA drop-down list
Choose the vHBA attribute. For example,
CreateUCSServiceProfile_160.SP_VHBA1.
Cisco UCS Director Vblock Management Guide, Release 5.1
92
Orchestration Workflow Operations
Provisioning a Stateless Blade Server Orchestration Workflow Overview
Step 3
Name
Description
Select VSAN drop-down list
Choose the VSAN attribute. For example,
CreateUCSServiceProfile_160.SP_VSAN1.
Click Next to advance to the Task Inputs pane.
The following parameters are configurable for Fabric A:
Name
Description
Configure One to One zones check Check the check box.
box
Storage Account Type drop-down
list
Choose the storage account type. For example, EMC VNX.
Storage Account Name (Primary) Choose the storage account name. For example, vBLOC-300.
drop-down list
Storage FC Adapter (Primary)
field Select... button
Choose the storage FC adapter(s). For example, A-0(FIBRE_CHANNEL),
A-2(FIBRE_CHANNEL).
Select Device drop-down list
Choose the network device. For example, SJ-02-VBLOCK-300-N5K-A |
172.29.108.37 | vBLOCK-300.
Configure Fabric B check box
Check the check box to initiate the ability to configure Fabric B.
The following parameters are configured for Fabric B:
Name
Description
Storage Account Type drop-down
list
Choose the same storage account type that was chosen for Fabric A.
Storage Account Name (Primary) Choose the same storage account name that was chosen for Fabric A.
drop-down list
vBLOC-300.
Storage FC Adapter (Primary)
field Select... button
Step 4
Choose the storage FC adapter(s). For example: B-1(FIBRE_CHANNEL),
B-3(FIBRE_CHANNEL).
Configure the remaining parameters in the Task Inputs pane.
Name
Description
Revalidate button
Binds all the necessary parameters identified in this task to the environment.
Cisco UCS Director Vblock Management Guide, Release 5.1
93
Orchestration Workflow Operations
Provisioning a Stateless Blade Server Orchestration Workflow Overview
Name
Description
Submit button
Saves the workflow task changes in the database. A confirmation dialog box
appears.
Adding Hosts to a VNX Storage Group
See the orchestration workflow overview for the specific task name and task type.
Step 1
Step 2
Under the blue workflow Start icon, find and double-click the Add Hosts to VNX Storage Group task. The Edit Task
dialog box appears with the Task Information pane.
The following parameters are preconfigured:
Name
Description
Task Name field
The add host to storage group task name is entered.
Task Category drop-down list
The EMC VNX Tasks category is chosen.
Task Type drop-down list
The Add Hosts to VNX Storage Group task type is chosen.
Comment field
Comments that pertain to this task.
Task Details display field
The output generated by this task.
Click Next to advance to the User Input Mapping pane.
The following parameters are configurable:
Note
Step 3
Check the Map to User Input check box next to the attribute to map it to the workflow when the workflow
executes.
Name
Description
Hosts drop-down list
Choose the name of the host attribute. For example,
AddHostInitiatorEntry_118.OUTPUT_HOST_IDENTITY.
Storage Group drop-down list
Choose the name of the storage group attribute. For example,
CreateStorageGroup_117.OUTPUT_STORAGE_GROUP_IDENTITY.
Click Next to advance to the Task Inputs pane.
The following parameters are configurable:
Cisco UCS Director Vblock Management Guide, Release 5.1
94
Orchestration Workflow Operations
Provisioning a Stateless Blade Server Orchestration Workflow Overview
Name
Description
Revalidate button
Binds all the necessary parameters identified in this task to the environment.
Submit button
Saves the workflow task changes in the database. A confirmation dialog box
appears.
Adding a LUN to a VNX Storage Group
See the orchestration workflow overview for the specific task name and task type.
Step 1
Step 2
Under the blue workflow Start icon, find and double-click the Add VNX LUN to Storage Group task. The Edit Task
dialog box appears with the Task Information pane.
The following parameters are preconfigured:
Name
Description
Task Name field
The add VNX LUN to storage group task name is entered.
Task Category drop-down list
The EMC VNX Tasks category is chosen.
Task Type drop-down list
The Add VNX LUN to Storage Group task type is chosen.
Comment field
Comments that pertain to this task.
Task Details display field
The output generated by this task.
Click Next to advance to the User Input Mapping pane.
The following parameters are configurable:
Note
Check the Map to User Input check box next to the attribute to map it to the workflow when the workflow
executes.
Name
Description
LUNs to Add drop-down list
Choose the name of the LUN attribute. For example,
CreateLUN_247.OUTPUT_LUN_IDENTITY.
Storage Group drop-down list
Choose the name of the storage group attribute. For example,
AddHoststoStorageGroup_121.OUTPUT_STORAGE_GROUP_IDENTITY.
Host LUN ID drop-down list
Choose the name of the host LUN ID attribute. For example, Host LUN Id.
Cisco UCS Director Vblock Management Guide, Release 5.1
95
Orchestration Workflow Operations
Provisioning a Stateless Blade Server Orchestration Workflow Overview
Step 3
Click Next to advance to the Task Inputs pane.
The following parameters are configurable:
Name
Description
Revalidate button
Binds all the necessary parameters identified in this task to the environment.
Submit button
Saves the workflow task changes in the database. A confirmation dialog box
appears.
Modifying the Cisco UCS Service Profile Boot Policy
See the orchestration workflow overview for the specific task name and task type.
Step 1
Step 2
Under the blue workflow Start icon, find and double-click the Modify UCS Service Profile Boot Policy task. The Edit
Task dialog box appears with the Task Information pane.
The following parameters are preconfigured:
Name
Description
Task Name field
The modify UCS service profile boot policy task name is entered.
Task Category drop-down list
The Cisco UCS Tasks category is chosen.
Task Type drop-down list
The Modify UCS Service Profile Boot Policy task type is chosen.
Comment field
Comments that pertain to this task.
Task Details display field
The output generated by this task.
Click Next to advance to the User Input Mapping pane.
The following parameters are configurable:
Note
Check the Map to User Input check box next to each of the following attributes to map them to the workflow
when the workflow executes.
Name
Description
Service Profile drop-down list
Choose the service profile attribute. For example,
CreateUCSServiceProfile_2034.SERVICE_PROFILE_IDENTITY.
Account Name drop-down list
Choose the storage account name attribute (this drop-down list is available if a
storage account name was configured). For example,
CreateUCSServiceProfile_2034.ACCOUNT_NAME.
Cisco UCS Director Vblock Management Guide, Release 5.1
96
Orchestration Workflow Operations
Provisioning a Stateless Blade Server Orchestration Workflow Overview
Step 3
Name
Description
Boot Policy drop-down list
Choose the boot policy attribute for the blade. For example,
CreateUCSServiceProfile_2034.BLADE_BOOT_POLICY.
Click Next to advance to the Task Inputs pane.
The following parameters are configurable:
Name
Description
Revalidate button
Binds all the necessary parameters identified in this task to the environment.
Submit button
Saves the workflow task changes in the database. A confirmation dialog box
appears.
Modifying the Cisco UCS Boot Policy LUN ID
See the orchestration workflow overview for the specific task name and task type.
Step 1
Step 2
Under the blue workflow Start icon, find and double-click the Update Boot Policy with LUN task. The Edit Task
dialog box appears with the Task Information pane.
The following parameters are preconfigured:
Name
Description
Task Name
The update boot policy with LUN task name is entered.
Task Category drop-down list
The Cisco UCS Tasks category is chosen.
Task Type drop-down list
The Modify UCS Boot Policy LUN ID task type is chosen.
Click Next to advance to the User Input Mapping pane.
The following parameters are configurable:
Note
Check the Map to User Input check box next to each of the following attributes to map them to the workflow
when the workflow executes.
Name
Description
Service Profile drop-down list
Choose the service profile attribute. For example,
CreateUCSServiceProfile_2034.SERVICE_PROFILE_IDENTITY.
Cisco UCS Director Vblock Management Guide, Release 5.1
97
Orchestration Workflow Operations
Provisioning a Stateless Blade Server Orchestration Workflow Overview
Step 3
Name
Description
PXE Boot Policy drop-down list
Choose the PXE blade boot policy attribute. For example,
CreateUCSServiceProfile_2034.PXE_BOOT_POLICY.
Server Boot Policy drop-down list
Choose the server boot policy attribute. For example,
CreateUCSServiceProfile_2034.BLADE_BOOT_POLICY.
Lun ID drop-down list
Choose the LUN ID attribute. For example, ProvisionLUN.LUN_ID.
Click Next to advance to the Task Inputs pane.
The following parameters are configurable:
Name
Description
Revalidate button
Binds all the necessary parameters identified in this task to the environment.
Submit button
Saves the workflow task changes in the database. A confirmation dialog box
appears.
Resetting the 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 Reset UCS Server task. The Edit Task dialog box appears
with the Task Information pane.
The following parameters are preconfigured:
Name
Description
Task Name
The reset blade to kick off PXE task name is entered.
Task Category drop-down list
The Cisco UCS Tasks category is chosen.
Task Type drop-down list
The Reset UCS Server 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.
Cisco UCS Director Vblock Management Guide, Release 5.1
98
Orchestration Workflow Operations
Provisioning a Stateless Blade Server Orchestration Workflow Overview
The following parameter is configurable:
Note
Check the Map to User Input check box next to the following attribute to map it to the workflow when the
workflow executes.
Step 3
Name
Description
Server drop-down list
Choose the reset blade to kick off PXE task server identity.
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.
Monitoring PXE Boot
See the orchestration workflow overview for the specific task name and task type.
Step 1
Step 2
Under the blue workflow Start icon, find and double-click the Monitor PXE Boot task. The Edit Task dialog box
appears with the Task Information pane.
The following parameters are preconfigured:
Name
Description
Task Name field
The monitor PXE boot task name is entered.
Task Category drop-down list
The Network Services Tasks category is chosen.
Task Type drop-down list
The Monitor PXE Boot task type is chosen.
Comment field
Comments that pertain to this task.
Task Details display field
The output generated by this task.
Click Next to advance to the User Input Mapping pane.
The following parameter is configurable:
Note
Check the Map to User Input check box next to the following attribute to map it to the workflow when the
workflow executes.
Cisco UCS Director Vblock Management Guide, Release 5.1
99
Orchestration Workflow Operations
Provisioning a Stateless Blade Server Orchestration Workflow Overview
Step 3
Name
Description
PXE Request ID drop-down list
Choose the PXE request ID attribute. For example,
PXEBoot_93.OUTPUT_PXE_BOOT_ID.
Click Next to advance to the Task Input pane.
The following parameters are configurable:
Name
Description
Max Wait Time (Hours) field
The maximum wait time in hours for the monitor PXE boot task.
Revalidate button
Binds all the necessary parameters identified in this task to the environment.
Submit button
Saves the workflow task changes in the database. A confirmation dialog box
appears.
Adding a VLAN to a Service Profile
See the orchestration workflow overview for the specific task name and task type.
Step 1
Step 2
Under the blue workflow Start icon, find and double-click the Add VLAN to Service Profile task. The Edit Task
dialog box appears with the Task Information pane.
The following parameters are preconfigured:
Name
Description
Task Name field
The add VLAN to service profile task name is entered.
Task Category drop-down list
The Cisco UCS Tasks category is chosen.
Task Type drop-down list
The Add VLAN to Service Profile task type is chosen.
Comment field
Comments that pertain to this task.
Task Details display field
The output generated by this task.
Click Next to advance to the User Input Mapping pane.
The following parameters are configurable:
Note
Check the Map to User Input check box next to each of the following attributes to map them to the workflow
when the workflow executes.
Cisco UCS Director Vblock Management Guide, Release 5.1
100
Orchestration Workflow Operations
Provisioning a Stateless Blade Server Orchestration Workflow Overview
Step 3
Name
Description
Account Name drop-down list
Choose an account name attribute (if required).
Service Profile drop-down list
Choose the service profile identity.
Click Next to advance to the Task Input pane.
The following parameters are configurable:
Name
Description
Account Name drop-down list
Choose the UCS Manager account name (if required).
VLAN Type drop-down list
Choose the Common/Global option.
Common/Global VLANs drop-down Choose the Native-VLAN option.
list
Revalidate button
Binds all the necessary parameters identified in this task to the environment.
Submit button
Saves the workflow task changes in the database. A confirmation dialog box
appears.
Disassociating the Cisco UCS Service Profile
See the orchestration workflow overview for the specific task name and task type.
Step 1
Under the blue workflow Start icon, find and double-click the Disassociate UCS Service Profile task. The Edit Task
dialog box displays with the Task Information pane.
The following parameters are preconfigured:
Name
Description
Task Name field
The disassociate service profile task name is entered.
Task Category drop-down list
The Cisco UCS Tasks category is chosen.
Task Type drop-down list
The Disassociate UCS Service Profile task type is chosen.
Comment field
Comments that pertain to this task.
Task Details display field
The output generated by this task.
Cisco UCS Director Vblock Management Guide, Release 5.1
101
Orchestration Workflow Operations
Provisioning a Stateless Blade Server Orchestration Workflow Overview
Step 2
Step 3
Click Next to advance to the User Input Mapping pane.
The following parameter is configurable:
Note
Check the Map to User Input check box next to the following attribute to map it to the workflow when the
workflow executes.
Name
Description
Service Profile drop-down list
Choose the create UCS service profile algorithm.
Click Next to advance to the Task Input pane.
The following parameters are configurable:
Name
Description
Revalidate button
Binds all the necessary parameters identified in this task to the environment.
Submit button
Saves the workflow task changes in the database. A confirmation dialog box
appears.
Configuring the Waiting for a Specific Duration Task
See the orchestration workflow overview for the specific task name and task type.
Step 1
Under the blue workflow Start icon, find and double-click the Wait for Specific Duration task. The Edit Task dialog
box displays with the Task Information pane.
The following parameters are preconfigured:
Name
Description
Task Name field
The wait for specific duration task name is entered.
Task Category drop-down list
The General Tasks category is chosen.
Task Type drop-down list
The Wait for Specified Duration task type is chosen.
Comment field
Comments that pertain to this task.
Task Details display field
The output generated by this task.
Cisco UCS Director Vblock Management Guide, Release 5.1
102
Orchestration Workflow Operations
Provisioning a File System Mounting Orchestration Workflow
Step 2
Click Next to advance to the User Input Mapping pane. No parameters are configured for this pane.
Step 3
Click Next to advance to the Task Input pane.
The following parameters are configurable:
Name
Description
Duration drop-down list
The wait time in seconds.
Revalidate button
Binds all the necessary parameters identified in this task to the environment.
Submit button
Saves the workflow task changes in the database. A confirmation dialog box
appears.
Provisioning a File System Mounting Orchestration Workflow
Cisco UCS Director handles the VSPEX file system mounting orchestration workflow by creating a file system
and mounting the file system as a Network File System (NFS) datastore.
File System Mounting Orchestration Workflow Overview
The following table provides an overview for implementing the file system mounting orchestration workflow.
Note
Use this table as a point of reference to determine the specific task name, task type, and the section to
which it is aligned. Each task covered in subsequent sections references the task name and task type in a
generic way. Once all the tasks in the workflow are validated and bound to the local environment, you
must validate the entire workflow. See Validating and Executing an Orchestration Workflow, on page
107 for more information.
Task Name
Task Type
Section
CreateEMCVNXFileSystem_247 253. Create VNX File System
Creating a VNX File System,
on page 104
AddNFSExport_248
254. Add VNX NFS Export
Adding a VNX NFS Export
Task, on page 105
SelectBlades_91
255. Mount NFS Datastore
Mounting the NFS Datastore,
on page 106
Cisco UCS Director Vblock Management Guide, Release 5.1
103
Orchestration Workflow Operations
Provisioning a File System Mounting Orchestration Workflow
Creating a VNX File System
See the orchestration workflow overview for the specific task name and task type.
Step 1
Under the blue workflow Start icon, find and double-click the Create VNX File System task. The Edit Task dialog
box appears with the Task Information pane.
The following parameters are preconfigured:
Name
Description
Task Name
The create EMC VNX file system task name is entered.
Task Category drop-down list
The EMC VNX Tasks category is chosen.
Task Type drop-down list
The Create VNX File System task type is chosen.
Comment field
Comments that pertain to this task.
Task Details display field
The output generated by this task.
Step 2
Click Next to advance to the User Input Mapping pane. No parameters are required to be configured for this step.
Step 3
Click Next to advance to the Task Inputs pane.
The following parameters are configurable:
Name
Description
Select EMC Account Select... button The EMC account name (if required).
Name field
The VNX file system name.
Create from drop-down list
Choose Storage Pool.
Storage Pool drop-down list
Choose a storage pool. For example, Pool 3(170.999 GB).
Storage Capacity field
The storage capacity of the file system to be created.
Capacity Units drop-down list
Choose the capacity unit. For example, GB (gigabytes).
Data Mover drop-down list
Choose the data mover (server) on which to mount the file system.
Revalidate button
Binds all the necessary parameters identified in this task to the environment.
Submit button
Saves the workflow task changes in the database. A confirmation dialog box
appears.
Cisco UCS Director Vblock Management Guide, Release 5.1
104
Orchestration Workflow Operations
Provisioning a File System Mounting Orchestration Workflow
Adding a VNX NFS Export Task
See the orchestration workflow overview for the specific task name and task type.
Step 1
Step 2
Step 3
Under the blue workflow Start icon, find and double-click the Add VNX NFS Export task. The Edit Task dialog box
appears with the Task Information pane.
The following parameters are preconfigured:
Name
Description
Task Name
The add NFS export task name is entered.
Task Category drop-down list
The EMC VNX Tasks category is chosen.
Task Type drop-down list
The Add VNX NFS Export task type is chosen.
Comment field
Comments that pertain to this task.
Task Details display field
The output generated by this task.
Click Next to advance to the User Input Mapping pane.
The following parameter is configurable:
Note
Check the Map to User Input check box next to the following attribute to map it to the workflow when the
workflow executes.
Name
Description
File Systems drop-down list
Choose the output file system mount path parameter. For example,
CreateEMCVNXFileSystem_247.OUTPUT_FILE_SYSTEM_MOUNT_PATH.
Click Next to advance to the Task Inputs pane.
The following parameters are configurable:
Name
Description
Data Mover Select... button
The data mover from which the file system is exported.
File Systems drop-down list
Choose the file system.
Read only Hosts field
The hostnames or IP addresses that get read-only access.
Read/Write Hosts field
The hostnames or IP addresses that get read-write access.
Root Hosts field
The hostnames or IP addresses that get root access.
Access Hosts field
The hostnames or IP addresses that get mount access.
Cisco UCS Director Vblock Management Guide, Release 5.1
105
Orchestration Workflow Operations
Provisioning a File System Mounting Orchestration Workflow
Name
Description
Hosts Access Read-only Export
check box
Check the check box to allow read-only access only to hostnames or IP addresses
that get mount access.
Revalidate button
Binds all the necessary parameters identified in this task to the environment.
Submit button
Saves the workflow task changes in the database. A confirmation dialog box
appears.
Mounting the NFS Datastore
See the orchestration workflow overview for the specific task name and task type.
Step 1
Step 2
Step 3
Under the blue workflow Start icon, find and double-click the Mount NFS Datastore task. The Edit Task dialog box
appears with the Task Information pane.
The following parameters are preconfigured:
Name
Description
Task Name
The mount NFS Datastore task name is entered.
Task Category drop-down list
The VMware Host Tasks category is chosen.
Task Type drop-down list
The Mount NFS Datastore task type is chosen.
Comment field
Comments that pertain to this task.
Task Details display field
The output generated by this task.
Click Next to advance to the User Input Mapping pane.
The following parameter is configurable:
Note
Check the Map to User Input check box next to the following attribute to map it to the workflow when the
workflow executes.
Name
Description
File Systems drop-down list
Choose the NFS export path parameter. For example,
AddNFSExport_248.OUTPUT_NFS_EXPORT_PATH.
Click Next to advance to the Task Inputs pane.
The following parameters are configurable:
Cisco UCS Director Vblock Management Guide, Release 5.1
106
Orchestration Workflow Operations
Validating and Executing an Orchestration Workflow
Name
Description
Storage IP Address field
The IP address of the interface which was configured for NFS data.
Host Name Select... button
Specifies the VMware hostname.
Datastore Name field
The name of the NFS VNX datastore. For example, VNXDataStore.
Access Mode drop-down list
Choose Read/Write.
Success Criteria drop-down list
Choose Mount successful at least on one Host.
Revalidate button
Binds all the necessary parameters identified in this task to the environment.
Submit button
Saves the workflow task changes in the database. A confirmation dialog box
appears.
Validating and Executing an Orchestration Workflow
After you validate all the tasks in a workflow and bind them to the local environment, you must validate the
entire workflow.
Step 1
Step 2
At the top right corner of Workflow Designer, click the Validate button. Workflow Designer confirms if the workflow
is valid with a "Completed (Sucess)" message.
Click Execute Now to activate the orchestration workflow.
Cisco UCS Director Vblock Management Guide, Release 5.1
107
Orchestration Workflow Operations
Validating and Executing an Orchestration Workflow
Cisco UCS Director Vblock Management Guide, Release 5.1
108
CHAPTER
8
Troubleshooting
This chapter contains the following sections:
• Troubleshooting Cisco UCS Director Connectivity, page 109
• Troubleshooting Cisco UCS Director Baremetal Agent Connectivity, page 110
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 Vblock Management Guide, Release 5.1
109
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 Vblock Management Guide, Release 5.1
110
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 management 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
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 Vblock Management Guide, Release 5.1
111
Troubleshooting
Troubleshooting Cisco UCS Director Baremetal Agent Connectivity
Cisco UCS Director Vblock Management Guide, Release 5.1
112