FlexPod Datacenter with VMware vSphere, Cisco tion Centric Infrastructure (ACI)

advertisement
FlexPod Datacenter with VMware vSphere, Cisco
UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
Deployment Guide for FlexPod with VMware vSphere 5.5 Update
1, Cisco UCS Director and Cisco Nexus 9000 Cisco Application
Centric Infrastructure (ACI)
Last Updated: March 25, 2015
2
Cisco Validated Design
About the Author
About the Author
Michael Zimmerman, Technical Marketing Engineer, UCS Director, Cisco Systems, Inc.
Michael Zimmerman is a TME currently focused on the advancement of data center management and
automation through Cisco UCS Director. Michael has worked in the IT industry for more than 10 years
and prior to his current role was a TME for NetApp, responsible for collaborating with Cisco in
developing, validating and evangelizing FlexPod data center solutions.
Acknowledgments
For their support and contribution to the design, validation, and creation of this Cisco Validated Design,
the author would like to acknowledge the significant contribution and expertise that resulted in
developing this document:
•
Chris O'Brien, Cisco Systems, Inc.
•
Haseeb Niazi, Cisco Systems, Inc.
•
Shankar Varanasy, Cisco Systems, Inc.
•
Tamil Sankaralingam, Cisco Systems, Inc.
•
Henry Vail, NetApp
•
Ganesh Kamath, NetApp
3
About the Author
About Cisco Validated Design (CVD) Program
The CVD program consists of systems and solutions designed, tested, and documented to facilitate
faster, more reliable, and more predictable customer deployments. For more information visit
http://www.cisco.com/go/designzone.
ALL DESIGNS, SPECIFICATIONS, STATEMENTS, INFORMATION, AND RECOMMENDATIONS (COLLECTIVELY, DESIGNS) IN THIS MANUAL ARE PRESENTED AS IS, WITH ALL FAULTS. CISCO AND ITS SUPPLIERS DISCLAIM ALL WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE WARRANTY 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 THE DESIGNS, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED
OF THE POSSIBILITY OF SUCH DAMAGES.
THE DESIGNS ARE SUBJECT TO CHANGE WITHOUT NOTICE. USERS ARE SOLELY RESPONSIBLE FOR
THEIR APPLICATION OF THE DESIGNS. THE DESIGNS DO NOT CONSTITUTE THE TECHNICAL OR
OTHER PROFESSIONAL ADVICE OF CISCO, ITS SUPPLIERS OR PARTNERS. USERS SHOULD CONSULT
THEIR OWN TECHNICAL ADVISORS BEFORE IMPLEMENTING THE DESIGNS. RESULTS MAY VARY
DEPENDING ON FACTORS NOT TESTED BY CISCO.
CCDE, CCENT, Cisco Eos, Cisco Lumin, Cisco Nexus, Cisco StadiumVision, Cisco TelePresence, Cisco
WebEx, the Cisco logo, DCE, and Welcome to the Human Network are trademarks; Changing the Way We
Work, Live, Play, and Learn and Cisco Store are service marks; and Access Registrar, Aironet, AsyncOS,
Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the
Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital,
the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone,
iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace
Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels,
ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to
Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of
Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website 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. (0809R)
© 2015 Cisco Systems, Inc. All rights reserved
About Cisco Validated Design (CVD) Program
4
FlexPod Datacenter with VMware vSphere,
Cisco UCS Director, Cisco Nexus 9000, Cisco
Application Centric Infrastructure (ACI)
Overview
Why Cisco UCS Director and the Cisco Application Policy Infrastructure
Controller?
There is a lot of excitement around the launch and availability of Cisco's Application Centric
Infrastructure (ACI) powered by the Application Policy Infrastructure Controller (APIC). The features
and capabilities ACI enables in regards to policy-driven fabric and services automation from an
application-centric perspective are paramount. Automating the configuration of resources with a
detailed focus on the requirements of the application greatly changes the overall paradigm of
infrastructure provisioning.
With such policy-driven automation at the fingertips of IT, one may question the need for other
automation and orchestration tools such as Cisco UCS Director. While ACI does provide superior fabric
and services automation through policy as aforementioned, there are other aspects of infrastructure that
are required for applications to properly exist and perform, which are outside the scope of ACI and
APIC. Resources such as storage, virtual machines, physical servers and other endpoints are still very
important to applications, however are not automated and configured through ACI or APIC policy. It is
the automation of these other infrastructure resources or endpoints, as well as the aspect of tying all
automation together into a single automation process, where Cisco UCS Director provides incredible
value to IT. Cisco UCS Director is the only automation and orchestration platform with a broad scope
of support including both Cisco and non-Cisco infrastructure components across ACI/APIC, storage,
virtual machines, physical servers and more, creating a complete and comprehensive end-to-end
application infrastructure automation solution.
Audience
Audience
The intended audience includes, but is not limited to, sales engineers, field consultants, professional
services, IT managers and administrators, partners and customers evaluating and deploying Cisco UCS
Director on FlexPod with Cisco Application Centric Infrastructure.
Purpose of This Document
This document provides useful information regarding the value Cisco UCS Director provides above and
beyond the benefits of FlexPod Datacenter with VMware vSphere and Cisco Application Centric
Infrastructure, as well as how to deploy and configure Cisco UCS Director to support specific real-world
use-cases. The real world example use-cases in this document represent a small subset of the use-cases
that can actually be supported by Cisco UCS Director. These use-cases are meant to provide the reader
with the tools and knowledge to deploy and configure Cisco UCS Director to accomplish a wide array
of use-cases specific to the readers' environment and requirements.
The Cisco UCS Director workflows highlighted in this document will be published on the Cisco
Communities as specifically described and detailed in this document. These workflows may be used
exactly as is, or may be reconfigured or edited to fit the needs of the target environment, requirements
and desired provisioning process.
FlexPod Datacenter with VMware vSphere and Cisco
Application Centric Infrastructure
End-to-End Architecture Highlights
FlexPod is a defined set of hardware and software that serves as an integrated foundation for both
virtualized and non-virtualized solutions. VMware® vSphere® built on FlexPod includes NetApp®
storage, NetApp Data ONTAP®, Cisco Nexus® networking, the Cisco Unified Computing System™
(Cisco UCS®), and VMware vSphere software in a single package. The design is flexible enough that
networking, computing, and storage can fit in one datacenter rack or alternatively can be deployed
according to a customer's data center design. Port density enables networking components to
accommodate multiple configurations of this kind.
With FlexPod architecture, you can customize or flex the environment to suit your specific requirements,
and a FlexPod system can be scaled easily as requirements and demand change. A unit can be scaled
both up (adding resources to a FlexPod unit) and out (adding more FlexPod units).
Figure 1 illustrates the components for VMware vSphere built on FlexPod and the network connections
for an IP-based storage configuration. This design uses the Cisco Nexus 9000, the Cisco Nexus 2232PP
FEX, Cisco UCS C-Series and B-Series servers, and the NetApp FAS family of storage controllers
connected in a modular, highly available design. This infrastructure is deployed to provide iSCSI-booted
hosts with file-level and block-level access to shared storage. The reference architecture reinforces the
wire-once strategy, because, as additional storage is added to the architecture, no recabling is required
between the hosts and the Cisco UCS fabric interconnect.
The ACI switching architecture is laid out in a leaf-and-spine topology where every leaf connects to
every spine using 40Gb Ethernet interface(s). The APIC software controller is delivered as an appliance,
and three or more of these appliances form a cluster for high availability and enhanced performance.
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
6
FlexPod Datacenter with VMware vSphere and Cisco Application Centric Infrastructure
Figure 1
Infrastructure Overview
The reference hardware configuration includes:
•
Two Cisco Nexus 9396 switches
•
Two Cisco Nexus 2232 fabric extenders
•
Two Cisco UCS 6248UP fabric interconnects
•
One NetApp FAS8040 (HA pair) running clustered Data ONTAP with disk shelves
While not included in the FlexPod Bill of Materials Cisco ACI spines and APIC controllers are an
integral part of the Cisco ACI design. The following components were used for validation:
•
Three APIC controllers
•
Two Cisco Nexus 9508-based spines
For server virtualization, this deployment includes VMware vSphere. Although this is a base design,
each of the components can be readily scaled to support specific business requirements. For example,
more (or different) servers or blade chassis can be deployed to increase compute capacity, additional disk
shelves can be deployed to improve I/O capability and throughput, and special hardware or software
features can be added to introduce new features.
For Detailed Information
FlexPod on Cisco Design Zone:
http://www.cisco.com/c/en/us/solutions/enterprise/data-center-designs-cloud-computing/fpplatforms.ht
ml
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
7
Cisco UCS Director Overview
FlexPod Datacenter with VMware vSphere 5.5 Update 2 and Cisco Nexus 9000 Application Centric
Infrastructure (ACI) Design Guide:
http://www.cisco.com/c/dam/en/us/td/docs/unified_computing/ucs/UCS_CVDs/flexpod_esxi55u2_n9k
_aci_design.pdf
FlexPod Datacenter with VMware vSphere 5.5 Update 2 and Cisco Nexus 9000 Application Centric
Infrastructure (ACI) Deployment Guide:
http://www.cisco.com/c/dam/en/us/td/docs/unified_computing/ucs/UCS_CVDs/flexpod_esxi55u2_n9k
_aci.pdf
Cisco UCS Director Overview
IT organizations are constantly looking for new, cost effective ways to provide services to their
customers. This is especially true as more and more IT organizations find themselves supporting an
increase in services with little to no increase in operational budgets. Most have evaluated some form of
cloud as a potential solution, and many have gone a step further and are even deploying these
architectures. This change in architecture may solve some problems, however the fact remains that IT
datacenters and their underlying components and processes, cloud or not, can still be very complex and
day to day operations still remain very time consuming, thus leaving little time for innovation and
extending further value-add services to the business. As such, many IT organizations are now looking
towards datacenter automation as the answer to alleviate time consuming day to day operational
overhead as well as minimize complexity.
Cisco UCS Director is a complete end-to-end management, automation and orchestration solution
supporting a wide array of both Cisco and non-Cisco data center infrastructure components. Cisco UCS
Director provides both administrative and end-user perspectives and functions, enabling IT to not only
build automation services but also extend those services in an on-demand manner to the users that need
to consume them. IT subject matter experts can collaborate upfront to quickly and easily create policies
and build Cisco UCS Director workflows which can equate to simple or complex provisioning and
configuration processes. When built, these workflows perform in exactly the same manner each and
every time they are executed. No matter whether the subject matter experts run the workflows
themselves, or whether the workflows are published to another set of users to execute. The beauty is that
the complexities, human error, and long time to value typically seen in the datacenter can be alleviated
by Cisco UCS Director workflows and on-demand services. When these services (workflows) are
created, it can be completely self-service driven, allowing IT subject matter experts to provide
provisioning and configuration capabilities to their resource consumers, on an as needed basis through
RBAC controls, while in parallel they focus on new ways to support and drive future business objectives.
Cisco UCS Director supports a wide array of use-cases across various hardware and software datacenter
components. Some example use-cases include, but are not limited tothe following:
•
Virtual machine provisioning and life cycle management
•
Network resource configuration and life cycle management
•
Storage resource configuration and life cycle management
•
Tenant infrastructure configuration
•
Application infrastructure provisioning
•
Self-service capabilities and catalogs
•
Bare metal server provisioning including operating system installation
For detailed information about Cisco UCS Director including documentation and compatibility matrices,
navigate to:
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
8
Cisco UCS Director for FlexPod with VMware vSphere and Cisco Application Centric Infrastructure
http://www.cisco.com/c/en/us/products/servers-unified-computing/ucs-director
Cisco UCS Director for FlexPod with VMware vSphere and
Cisco Application Centric Infrastructure
Cisco UCS Director is the perfect complement to FlexPod because it was specifically built from the
ground up to deliver advanced management and automation capabilities for converged infrastructures.
Cisco UCS Director natively supports all components, both physical and virtual, that together, along
with best practices, combine to form the various FlexPod architectures. These components include:the
following
•
The Cisco UCS system
•
The Cisco Nexus switch family (physical and virtual)
•
The NetApp clustered Data ONTAP storage platform
•
VMware vSphere virtual infrastructure software
•
NetApp Virtual Storage Console (VSC) for VMware vSphere
Cisco UCS Director supports all FlexPod datacenter architectures, including the newest architecture
based on VMware vSphere and Cisco ACI. The remainder of this document will focus on the deployment
and use of Cisco UCS Director as a complementary tool for the management and automation of the latest
FlexPod architecture with VMware vSphere and Cisco ACI.
Component Software Versions
In conjunction with the validated design for FlexPod with VMware vSphere and Cisco ACI, the
component software versions listed in Error! Reference source not found. were used for system
validation.
Table 1
Layer
Compute
Network
Storage
Software
Component Software Versions
Device
Cisco UCS Fabric Interconnects 6200 Series, UCS B-200
M3, UCS C-220 M3
Cisco eNIC
Version or Release
2.2(3d)
2.1.2.42
Cisco fNIC
1.6.0.5
Cisco APIC
1.0(2m)
Cisco Nexus 9000 iNX-OS
11.0(1b)
NetApp FAS 8040
Data ONTAP 8.2.1
Nexus 5596 Cluster Switches
5.2(1)N1(1)
VMware vSphere ESXi
5.5 update 2
VMware vCenter
5.5 update 2
NetApp Virtual Storage Console (VSC)
5.0
NetApp SnapDrive for Windows
7.1
NetApp SnapManager for SQL
7.1
NetApp Windows Host Utilities Kit
7.0
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
9
Cisco UCS Director Initial Deployment
Microsoft SQL Server
2012 SP2
Cisco UCS Director
5.2.0.2
Cisco UCS Director Initial Deployment
Prerequisites
As a prerequisite for performing the following Cisco UCS Director initial deployment procedures, the
expectation is that a FlexPod with Cisco Application Centric Infrastructure has been configured as per
the following published Cisco Validated Deployment Guide:
FlexPod Datacenter with VMware vSphere 5.5 Update 2 and Cisco Nexus 9000 Application Centric
Infrastructure (ACI) Deployment Guide
http://www.cisco.com/c/dam/en/us/td/docs/unified_computing/ucs/UCS_CVDs/flexpod_esxi55u2_n9k
_aci.pdf
Deployment Models
From customer to customer, no infrastructure is exactly the same. Some customers need to automate at
a very small scale, while other customers operate at a very large scale, requiring the automation of
thousands of different devices. For this reason, Cisco UCS Director supports two different types of
deployment models; Single-Node and Multi-Node (or Distributed).
•
Single-Node Deployment Model - A single instance of the Cisco UCS Director appliance is
deployed. All components and services of the Cisco UCS Director application run natively on the
single installed appliance VM.
Figure 2
Single-Node Deployment Model
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
10
Cisco UCS Director Initial Deployment
•
Multi-Node Deployment Model—Multiple instances of the Cisco UCS Director appliance are
deployed. Each instance can be given a specific role, which determines which components and
services of the Cisco UCS Director application will run on that specific node. The Cisco UCS
Director multi-node roles are as follows;
– Primary Node—runs all management and web front-end components, acting as the central
manager of the entire multi-node deployment. There can be only one primary node in a
multi-node deployment.
– Service Node(s)—essentially worker nodes. The system admin can distribute different Cisco
UCS Director system tasks across one or more different service nodes. Service nodes are
managed from the primary node. A multi-node deployment can consist of zero to many service
nodes.
– Inventory Database Node—runs only the inventory database services for the multi-node
deployment. Communicates with both the primary and service nodes. Only one inventory
database node per multi-node deployment.
– Monitoring Database Node— runs only the monitoring database services for the multi-node
deployment. Communicates with both the primary and service nodes. Only one monitoring
database node per multi-node deployment.
Figure 3
Multi-Node Deployment Model
The size of the environment to be managed and automated by Cisco UCS Director determines the best
deployment model that should be used. In regards to a multi-node deployment, customers can start out
with a minimum number of nodes and then grow the deployment to scale with their environment. For
more information on Cisco UCS Director deployment models and scalability limits, consult the
following:
Cisco UCS Director Installation and Upgrade on VMware vSphere Guide, Release 5.2
http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/ucs-director/vsphere-install-guide/5-2/b_
Installing_UCSDirector_on_vSphere_5_2.pdf
No matter which deployment model a customer chooses, the deployment of Cisco UCS Director is
simple. Cisco delivers Cisco UCS Director as a single OVF file for VMware vSphere. Both deployment
models are deployed from the same OVF file. For a single-node deployment, import a single instance of
the OVF file into VMware vSphere and configure an IP address. For a multi-node deployment, import
multiple instances of the OVF file into VMware vSphere, assign a role and configure an IP address for
each instance. In a multi-node deployment configuration, Cisco UCS Director takes care of the
coordination and communication between the different nodes.
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
11
Cisco UCS Director Initial Deployment
Note
The installation procedure provided below continues with a single-node Cisco UCS Director deployment
model. For information about deploying a multi-node Cisco UCS Director deployment model, please
consult the Cisco UCS Director Installation and Upgrade Guide on Cisco.com (direct link provided
above).
Deploy Single-Node Cisco UCS Director Appliance
To deploy a single-node Cisco UCS Director appliance virtual machine, complete the following steps:
1.
Download the Cisco UCS Director 5.2 appliance (for VMware) ZIP file from Cisco.com. A
Cisco.com login is required.
2.
Unzip the UCS Director 5.2 Appliance ZIP file to a location on your local machine.
3.
Log into the VMware vSphere Client application.
4.
Click on File and then Deploy OVF Template….
5.
Click Browse and navigate to the location of the UCS Director appliance OVF file on your local
machine. Choose the OVF file and click Open.
6.
On the Source page, click Next.
7.
On the OVF Template Details page, click Next.
8.
On the End User License Agreement page, review the agreement and click Accept. Click Next.
9.
On the Name and Location page, provide a Name for the UCS Director appliance VM and choose
an inventory location.
10. On the Host / Cluster page, choose a target VMware datacenter and cluster for deploying the UCS
Director appliance VM. Click Next.
11. On the Resource Pool page, choose the desired location for deploying the UCS Director appliance
VM. Click Next.
12. On the Storage page, choose the datastore where the UCS Director appliance VM is to be deployed.
Click Next.
13. On the Disk Format page, choose the desired disk format for the UCS Director appliance VM. The
recommended format is Thin Provision. Click Next.
14. On the Network Mapping page, map the Network 1 VM interface to the desired management
network for the UCS Director appliance VM. Click Next.
15. On the IP Address Allocation page, click Next. Note that the only available option is DHCP. A static
IP address can be configured once the UCS Director appliance VM is powered on.
16. On the Ready to Complete page, review the chosen settings and click Finish to deploy the UCS
Director appliance VM.
Assign Static IP Address to UCS Director
To assign a static IPv4 IP address to the UCS Director appliance virtual machine, complete the following
steps:
1.
Open the VMware console for the UCS Director appliance VM.
2.
Power on the UCS Director appliance VM.
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
12
Cisco UCS Director Initial Deployment
3.
The UCS Director appliance VM will start its initial boot process and load various components and
services. During the network portion, a prompt regarding assigning a static IP address will appear.
4.
Do you want to Configure static IP [y/n]? :. Type Y and hit Enter to configure a static IP address for
the UCS Director appliance VM. If DHCP is desired, Type N and hit Enter, the VM will continue to
boot normally.
5.
Do you want to configure IPv4/IPv6 pv4/v6] ? :. Type v4 and hit Enter to configure an IPv4 address
or v6 to configure an IPv6 address for the UCS Director appliance VM. (The following procedure
continues on the assumption that an IPv4 address will be provided)
6.
IP Address:. Enter the IP address for the UCS Director appliance VM.
7.
Netmask:. Enter the netmask for the UCS Director appliance VM.
8.
Gateway:. Enter the gateway IP address for the UCS Director appliance VM.
9.
Do you want to continue [y/n]? :. Review the configuration and type Y and hit Enter to continue.
10. The UCS Director appliance VM will configure the network interface with the provided
configuration and continue to boot for several minutes.
11. Personality: [1/2]?. Choose the UCS Director personality that should be loaded and configured on
this instance. As of this publication, UCS Director offers two personalities, the default full-feature
UCS Director personality as well as the UCS Director Express personality, which is focused on Big
Data/Hadoop configuration and management. Select 1 for the default UCS Director personality and
hit Enter to continue.
12. The UCS Director appliance VM will continue to boot and finish loading the necessary components
and services. This process may take a couple minutes to complete during first boot of the UCS
Director appliance VM.
13. When completed, the message To manage this VM browse to https:<ucsd_ip_address>:443/ will be
displayed on the UCS Director VM console within the VMware vSphere Client.
Initial System Configuration Guided Setup
To configure various system options such as DNS servers, NTP servers, E-mail configuration and SMTP
servers, etc., complete the following steps:
Note
1.
Open a web browser and navigate to https://<ucsd_ip_address>.
2.
The UCS Director appliance login screen should appear. The default username and password are
both admin.
3.
When logged in to the UCS Director appliance, the Guided Setup screen will automatically appear
presenting options of various guided setup processes that can be used to configure UCS Director.
Select the checkbox next to Initial System Configuration and then click Submit.
If Guided Setup does not automatically launch when logging in to UCS Director, navigate to
Administration ' Guided Setup and then select the Launch Guided Setup option.
4.
The current page presents the various configuration tasks that the Initial System Configuration
guided setup will walk through. Review the list of steps and unselect any that are not required in
your particular environment. Click Submit. (The following procedure continues on the assumption
that all tasks are selected to be completed)
5.
On the Overview page, click Next.
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
13
Cisco UCS Director Initial Deployment
6.
On the License page, click the Browse button and navigate to the UCS Director license file (.lic).
Click Open then click Upload. You can optionally choose to add the license by copying the license
file text to UCS Director, to do so select the Enter License Text option. Click Next once completed.
7.
On the Locale page, choose the appropriate Language from the drop-down list. Click Next. Note that
changes to language from English to another language will require the user to log out and log back
in after the wizard completes for changes to take effect.
8.
On the DNS Server page, review the currently configured DNS servers. Select Modify DNS Servers
to add, edit or delete DNS servers from the currently configured list. Click Next.
9.
On the Mail Server page, enter the necessary SMTP server information as well as the System IP
Address, which is the local IP address of the UCS Director appliance. Selecting Send a Test Email
will send a test email from the UCS Director appliance to the supplied email address upon clicking
Next. Click Next.
10. On the Email Address page, enter the contact email address for the currently logged in user admin.
Click Next.
11. On the NTP Server page, review the currently configured NTP servers. Select Modify NTP Servers
to add, edit or delete NTP servers from the currently configured list. Click Next.
12. On the Summary page, review the information provided in each task and it's associated status. At
this point you can optionally click Next to review Recommended Next Steps which provides
additional wizard options. For purposes of this document, click Close to close the current wizard.
Initial system setup is now complete.
Configuring User Roles
Cisco UCS Director provides the ability to create and configure user roles in order to control what
specific features and functionalities those user have permissions to perform. To modify existing user
roles as well as create new user roles, complete the following steps:
1.
In UCS Director, navigate to Administration ' System and select the User Roles tab.
2.
By default, several user roles are provided out of the box with UCS Director. To edit an existing user
role, click on the user role in the table and then click Edit.
3.
To create a new user role, click Add.
4.
On the User Role page, provide a User Role (name for the user role) as well as the Role Type. The
Role Type determines what type of UCS Director user interface (or portal) is presented to any user
with this particular user role. As of this publication, there are two role types, Admin and End User.
Optionally provide a Description as well. Click Next.
5.
On the Menu Settings page, choose which menus should be viewable by all users associated with
this particular user role. Note that the options in the Menu Settings page will change depending on
the Role Type chosen for the user role. Click Next.
6.
On the User Permissions page, choose the permissions that should be provided to all users
associated with this particular user role. For each category or operating, the user role can be
configured with no access (by not selecting Read or Write), Read-only access (by selecting only
Read) and Read-Write access (by selecting both Read and Write).
7.
When the appropriate user permissions have been set, click Submit.
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
14
Cisco UCS Director Initial Deployment
Configuring Users and Groups
The following sections detail the steps required to create users and user groups within UCS Director as
well as how to change the local administrator password.
Change Local Admin Password
It is highly recommended to change the local admin user's password from the default. To change the
admin password as well as any local users password, complete the following steps:
1.
In USC Director, navigate to Administration ' Users and Groups and select the Login Users tab.
2.
Select the admin user and choose Change Password.
3.
Enter the New Password and the Confirm Password. Both entries must be identical.
4.
Click Save.
5.
Repeat steps 2 - 4 to change the password for any locally authenticated user. For remote
authenticated users, password changes must be done through the remote authentication server itself
(for example, directly within Microsoft Active Directory, etc.).
Locally Authenticated Users and Groups
To create local user groups within the Cisco UCS Director appliance, complete the following steps:
1.
In UCS Director, navigate to Administration ' Users and Groups and select the User Groups tab.
2.
Click Add.
3.
Provide the user group Name, Contact Email for the user group and any other appropriate optional
information for the user group.
4.
(Optional) The Group Share Policy is used to configure which other existing user groups the current
user group can optionally choose to share its own resources with. This policy can be
configured/created by navigating to Administration ' Users and Groups and selecting the Group
Share Policy tab.
5.
(Optional) The Allow Resource Assignment to Users option allows for more granular control of
resource ownership within a user group. By default, this option is not selected and all resources are
owned at the user group level. If this option is selected, resources within a user group can be
assigned down to the individual user level within a specific user group.
6.
When the Add Group form is complete, click Add.
7.
Repeat steps 2 - 6 for each new user group that needs to be created.
To create local login users within the Cisco UCS Director appliance, complete the following steps:
1.
In UCS Director, navigate to Administration ' Users and Groups and select the Login Users tab.
2.
Click Add.
3.
Choose the appropriate User Role for the new user.
4.
Depending on the User Role chosen, you may also be prompted to select a User Group to associate
the new user to. The button to the right of the drop-down allows you to create a new user group as
well.
5.
Provide a Login Name, which will serve as the username for this particular user when logging into
UCS Director.
6.
Provide a Password and Confirm Password for the new user.
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
15
Cisco UCS Director Initial Deployment
7.
Provide a User Contact Email for the new user.
8.
Optionally provide other information for the new user.
9.
When the Add User form is completed, Click Add.
10. Repeat steps 2 - 9 for each new user that need to be created.
Remotely Authenticated Users and Groups
Cisco UCS Director supports both local and remote user authentication. Remote authentication is
provided through integration with services such as OpenLDAP and Microsoft Active Directory. The
following procedure should be used to integrate UCS Director with a Microsoft Active Directory
Domain through LDAP in order to sync (pull only) remote users and groups into UCS Director.
Note
As of this publication, UCS Director accesses LDAP accounts in a read-only manner. UCS Director does
not push any user or group changes or configurations to the LDAP server(s).
1.
In UCS Director, navigate to Administration ' Users and Groups and select the LDAP Integration
tab.
2.
Click the Add button to add a new LDAP integration.
3.
Provide the Account Name. Input expects arbitrary text to identify this LDAP integration versus
another LDAP integration on the same UCS Director instance.
4.
Provide the Server Type. Options are OpenLDAP and Microsoft Active Directory.
5.
Provide the Server information. Input expects either the LDAP/AD servers host name or the IP
address.
6.
Provide the Port to use for the integration. By default this option is set to 389, optionally you can
enable SSL by selecting the Enable SSL option. If SSL is enabled, the Port input will automatically
change to 636.
7.
Provide the Domain Name. Should be in standard domain format, for example ucsd.cisco.com.
8.
Provide the Username. Username used to connect to Microsoft Active Directory from the UCS
Director appliance.
9.
Provide the Password. Password for the username used to connect to Microsoft Active Directory
from the UCS Director appliance.
10. When the Add LDAP Configurations form is complete, click Next.
11. On the LDAP Search Base page, click the Select button and choose the appropriate OU(s) that UCS
Director should sync to/from. Once selected, click Submit. Note, a message may appear saying that
LDAP is not set as the preferred authentication method, click OK. This option will be set in the next
steps.
12. Navigate to Administration ' Users and Groups and select the Authentication Preferences tab.
13. Set the appropriate value from the drop-down menu for Authentication Preferences. Click Save.
Note
At this point, UCS Director is configured to sync with Microsoft Active Directory through LDAP. A
manual sync can be performed at any time by the UCS Director admin, however UCS Director also syncs
automatically with each configured LDAP account every 24 hours by default. The automatic LDAP sync
frequency can be changed from the default value using the following optional procedure.
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
16
Cisco UCS Director Initial Deployment
14. (Optional) Navigate to Administration ' System and select the System Tasks tab.
15. (Optional) In the upper right-hand corner of the System Tasks table, enter the phrase ldap into the
search box and press Enter.
16. (Optional) This should result in a short list of LDAP related system tasks being displayed. Select
the system task that corresponds to the appropriate LDAP account (referenced by the Account Name
provided when adding the LDAP account to UCSD). Click on Manage Task.
17. (Optional) Select the appropriate frequency value for Hours and click Submit.
18. (Optional) A manual sync can be performed at any time by selecting the appropriate system task and
clicking the Run Now button.
Creating a Credential Policy
In many environments it may be typical to have a common set of credentials (username and password)
used across infrastructure components of the same type. This is especially true when adding many of the
same type of infrastructure components, for example many UCS manager accounts, or many VMware
vCenter accounts. UCS Director credential policies allow the administrator to create and store these
common sets of credentials so that UCS Director can access and manage the various infrastructure
components in the environment using these policies. When adding various infrastructure component
accounts to UCS Director, these credential policies can be leveraged rather than having to enter
credentials for each added account. If passwords are updated, only the credential policy needs to be
updated, each individual account will automatically be updated based on the credential policy. If
credential policies are not configured, a username and password will need to be provided with each
managed account as it is added to UCS Director.
1.
In USC Director, navigate to Policies'Physical Infrastructure Policies'Credential Policies.
2.
Click Add.
3.
On the Account Type page, select the account type for the credential policy.
4.
Enter the appropriate information in the Add Credential Policy form and click Submit.
5.
Repeat steps 2 - 4 for each type of infrastructure component.
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
17
Cisco UCS Director Extended Deployment for FlexPod Datacenter with VMware vSphere and Cisco Application
Cisco UCS Director Extended Deployment for FlexPod
Datacenter with VMware vSphere and Cisco Application
Centric Infrastructure
Prerequisites
As a prerequisite for performing the following UCS Director extended deployment procedures, the
expectation is that the steps and prerequisites outlined in the Initial System Configuration Guided Setup
section above have been completed.
FlexPod Configuration Guided Setup
The FlexPod Configuration Guided Setup walks the user through the process of creating or selecting a
FlexPod pod within UCS Director as well as discovering and adding the various FlexPod components to
that pod. A UCS Director pod is a feature that allows components managed by UCS Director to be
logically grouped based on their function, relationship, responsibility, site, etc.. In the case of FlexPod,
the UCS Director pod refers to the components that make up the entire FlexPod converged infrastructure.
1.
In UCS Director, navigate to Administration ' Guided Setup.
2.
Double-click the FlexPod Configuration guided setup icon.
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
18
Cisco UCS Director Extended Deployment for FlexPod Datacenter with VMware vSphere and Cisco
3.
On the Overview page, click Next.
4.
On the Pod page, either select an existing Pod from the drop-down menu or select the icon to the
right of the drop-down menu to create a new Pod in UCS Director. The following assumes the
creation of a new Pod in UCS Director is necessary.
5.
In the Add POD pop up window, enter the Name for the new pod, choose the Site in which the Pod
is located, optionally provide a Description and then provide an Address for the Pod. If a Site has
not yet been created, choose the icon to the right of the Site drop-down menu to create a new Site.
The following assumes the creation of a new Site in UCS Director is necessary.
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
19
Cisco UCS Director Extended Deployment for FlexPod Datacenter with VMware vSphere and Cisco Application
6.
In the Add Site pop up window, enter a Site Name, an optional Description and a Contact Name.
Click Submit and then click OK. This should return you to the Add POD pop up window.
7.
When the Add POD pop up window form is complete, click Add and then click OK.
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
20
Cisco UCS Director Extended Deployment for FlexPod Datacenter with VMware vSphere and Cisco
8.
On the Pod page, click Next.
9.
On the Cisco UCS Manager page, enter the appropriate information to allow UCS Director to
manage the UCS system through UCS Manager. If a credential policy was created for UCS Manager
accounts, check the Use Credential Policy option and select the corresponding policy. Click Next.
10. On the NetApp page, enter the appropriate information to allow UCS Director to manage the
NetApp clustered Data ONTAP operating system. If a credential policy was created for any Data
ONTAP accounts, check the Use Credential Policy option and select the corresponding policy. Click
Next.
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
21
Cisco UCS Director Extended Deployment for FlexPod Datacenter with VMware vSphere and Cisco Application
11. On the Nexus Physical Devices page, click Skip. In this document we are configuring a FlexPod
with ACI, which does not require the Nexus Physical Device information. The entire ACI fabric will
be discovered (learned) through the APIC account, which will be added further below in the process.
Other non-ACI FlexPod configurations may require this information.
12. On the Nexus Virtual Device page, click Skip. In this document we are configuring a FlexPod with
ACI leveraging the VMware virtual distributed switch only.
13. On the VMware page, enter the appropriate information to allow UCS Director to manage the
VMware vSphere infrastructure through VMware vCenter. If a credential policy was created for
VMware vCenter accounts, check the Use Credential Policy option and select the corresponding
policy. Click Next.
14. On the Summary page, review the details that were provided and configured. At this point all
components have already been added to the selected UCS Director pod. Click Close.
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
22
Cisco UCS Director Extended Deployment for FlexPod Datacenter with VMware vSphere and Cisco
Adding the Application Policy Infrastructure Controller APIC Account
The following section details the steps required to add the Cisco Application Policy Infrastructure
Controller to the UCS Director appliance virtual machine.
1.
In UCS Director, navigate to Administration ' Physical Accounts and select the Multi-Domain
Managers tab.
2.
Click Add to add a new Multi-Domain Manager account to UCS Director.
3.
In the Add Account pop up window, choose APIC in the drop-down menu. Click Submit.
4.
In the follow-on Add Account form page, enter the appropriate information regarding your Cisco
APIC. If a credential policy was created for APIC accounts, check the Use Credential Policy option
and select the corresponding policy Click Submit and then click OK.
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
23
Cisco UCS Director Extended Deployment for FlexPod Datacenter with VMware vSphere and Cisco Application
Note
In an ACI configuration, it is typical to deploy a cluster of APIC controllers consisting of a minimum of
three APICs. However, It is only required to add a single APIC account to UCS Director. UCS Director
will discover and manage all APIC controllers through the single added APIC account.
5.
Now that the APIC cluster has been added to UCS Director, we need to add the APIC account to the
FlexPod pod. Navigate to Physical ' Network.
6.
In the left-hand pane, expand the Multi-Domain Managers tree and then select (highlight) the APIC
Accounts tree. Do not choose the actual underlying APIC account under the APIC Accounts tree.
7.
In the right-hand pane, select the APIC account and then select the Assign To Pod action button.
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
24
Cisco UCS Director Extended Deployment for FlexPod Datacenter with VMware vSphere and Cisco
8.
In the Assign To Pod pop up window, select the Pod and click Submit. Then click OK.
9.
At this point, navigate to the Converged tab. In the Site drop-down menu, choose the site at which
the FlexPod Pod is located.
10. When the Site is selected, choose the FlexPod Pod. The result should look similar to the below.
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
25
Cisco UCS Director Extended Deployment for FlexPod Datacenter with VMware vSphere and Cisco Application
Select Managed Cisco UCS Servers
In certain scenarios the administrator may not wish to allow Cisco UCS Director to managed all Cisco
UCS servers within a given Cisco UCS Manager account. The following section details the steps
required to allow the administrator to choose exactly which Cisco UCS servers should be managed by
Cisco UCS Director.
1.
In UCS Director, navigate to Physical'Compute. In the left hand pane, expand the Site, then expand
the Pod and select the UCS Manager account.
2.
On the right-hand side, select the UCS Discovered Servers tab.
3.
Click the Manage Servers option.
4.
In the Discovered Servers table, select all or the desired subset of UCS servers to be managed by
this UCS Director instance. Click Submit.
Create VLAN Pool Policy
As a prerequisite for the workflows that are highlighted in this document, one or more VLAN pools must
be configured within UCS Director. The administrator can configure the range of VLANs that UCS
Director can use by creating a VLAN Pool Policy. This VLAN Pool Policy will be used to dynamically
reserve VLANs for each tenant as the tenant is configured. In this example, we'll create a single VLAN
Pool Policy that all tenant VLANs are provisioned from. Administrators can also create multiple VLAN
Pool Policies that specify a specific range of VLANs to be used for a specific function within a tenant,
for example a specific range of VLANs to be used for tenant NFS traffic and another specific range of
VLANs to be used for tenant storage virtual machine (SVM) management traffic.
1.
In UCS Director, navigate to Policies'Virtual/Hypervisor Policies'Network and then select the
VLAN Pool Policy tab.
2.
Click Add.
3.
Select the FlexPod pod created above, provide a Policy Name as well as a VLAN Range for this
policy. Click Submit and then OK.
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
26
Cisco UCS Director Extended Deployment for FlexPod Datacenter with VMware vSphere and Cisco
Create IP Subnet Pool Policy
As part of the workflows highlighted in this document, several networks will be created for each tenant
across the FlexPod that serve various functions. One network for NFS traffic, another for SVM
management traffic and so on. Each of the tenant's networks will require a specific reserved IP address
subnet and all tenant endpoints (physical, logical or virtual resources) on those networks will need to be
assigned an IP address from that specific tenant's reserved IP subnet. This is where UCS Director IP
Subnet Pool Policies come into the picture. This feature allows the administrator to create a pool of IP
Subnets that can then be dynamically reserved to tenants as they are created during the workflow(s)
configured below. Similar to the VLAN Pool Policy, an administrator can create one or more IP Subnet
Pool Policies, for the examples in this document only a single policy is created.
1.
In UCS Director, navigate to Policies'Virtual/Hypervisor Policies'Network and then select the IP
Subnet Pool Policy tab.
2.
Click Add.
3.
Provide the Policy Name.
4.
Provide the Network Supernet Address. This is the network address of the subnet to be split into
smaller subnets. Each of these smaller subnets could then be reserved for tenants.
5.
Provide the Network Supernet Mask. This is the network subnet mask of the larger supernet that
will be split into smaller subnets.
6.
Select the Number of Subnets Required.
7.
Select the Gateway Address.
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
27
Cisco UCS Director Extended Deployment for FlexPod Datacenter with VMware vSphere and Cisco Application
Note
In the example screenshot above, we are splitting the 192.168.200.0 (Supernet Address) network into 16
(Number of Subnets Required) equal and smaller IP subnets. UCS Director will make these smaller IP
subnets available to reserve to tenants. The first address in each smaller IP subnet will be designated as
the default gateway IP address for each IP subnet. The reservable IP subnets can be seen below in the
following screenshot. To view this information, click on the IP Subnet Pool Policy and then click View
Details. This will display the available IP subnets.
Create Resource Tags
The following section details the steps required to create resource tags within UCS Director. Resource
tags can be used for various provisioning operations, however in the use cases described below, they are
used to determine a list of resources that should be used by UCS Director for provisioning. In the
following steps, a resource tag called Availability is created with values of Available and Unavailable..
1.
In UCS Director, navigate to Policies'Tag Library.
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
28
Cisco UCS Director Extended Deployment for FlexPod Datacenter with VMware vSphere and Cisco
2.
Click Create.
3.
On the Tag Details page, enter the word Availability for Name field and optionally enter a
Description. Select STRING as the Type and for the Possible Tag Values field, enter
Available,Unavailable (make sure to include the comma as well). Click Next.
4.
On the Applicability Rules page, click the green plus button to add Entities to the Taggable Entities
table.
5.
On the Add Entry to Entities page, choose Virtual Compute for the Category and select VMware
Cluster. Click Submit.
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
29
Cisco UCS Director Extended Deployment for FlexPod Datacenter with VMware vSphere and Cisco Application
6.
On the Application Rules page, click the green plus button again to add an additional Entity to the
Taggable Entities table.
7.
On the Add Entities Entry page, choose the category PHYSICAL_STORAGE and select NetApp
Aggregate. Click Submit.
8.
On the Application Rules page, the Taggable Entities table should now have two entries. Click
Submit.
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
30
Cisco UCS Director Extended Deployment for FlexPod Datacenter with VMware vSphere and Cisco
Apply Resource Tags
The following section details the steps required to apply resource tags to resources within UCS Director.
When a resource tag has been created, the administrator can then tag certain resources (i.e. NetApp
Aggregates and VMware Clusters) and use those tags to determine available resources for provisioning.
In this use case, we will tag both NetApp Aggregates and VMware Clusters to tell UCS Director which
NetApp Aggregates and which VMware Clusters should be used for automated provisioning.
1.
In UCS Director, navigate to Virtual'Compute.
2.
In the left pane, expand All Clouds and select the vCenter account.
3.
In the right pane, select the Clusters tab.
4.
In the Clusters table, select the cluster (or clusters) that should be used for tenant provisioning. This
document continues with the assumption that a single cluster will be selected.
5.
Click the Add Tags button.
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
31
Cisco UCS Director Extended Deployment for FlexPod Datacenter with VMware vSphere and Cisco Application
6.
On the Add Tags page, choose Availability for the Tag Name and AVAILABLE for the Tag Value.
Click Submit.
7.
Navigate to Physical'Storage.
8.
In the left pane, expand the appropriate site and then expand the appropriate pod. Select the
appropriate NetApp cluster account.
9.
In the right pane, select the Aggregates tab.
10. In the Aggregates table, select one or more aggregates to use for tenant provisioning. Use the Add
Tags button to add the AVAILABLE tag to the resource. Click Submit. For the use cases in this
document, two aggregates have been selected, one aggregate from NetApp Cluster Node 1 and one
aggregate from NetApp Cluster Node 2.
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
32
Cisco UCS Director Extended Deployment for FlexPod Datacenter with VMware vSphere and Cisco
Create Resource Group
Cisc UCS Director has the ability to manage various resources across many different vendor platforms.
Resource Groups is a feature that allows the infrastructure admin or system admin to easily manage
which resources can be used by the infrastructure tenants and how they can consume them. Managed
device accounts can be added into a Resource Group, which can then be mapped dynamically to a tenant
based on their application requirements, which are defined in what is called a Service Offering. UCS
Director intelligently and dynamically uses the defined Service Offering (requirements) to pair the
tenant with a Resource Group that provides all the required capabilities and capacities needed by the
tenant.
To create a new Resource Group containing the FlexPod infrastructure components, complete the
following steps:
1.
In UCS Director, navigate to Policies'Resource Groups and then select the Resource Groups tab.
2.
Click Add Pod to Resource Group. This option will allow the administrator to easily add an entire
pod to a resource group rather than having to choose device accounts individually to assign. Use the
Add button to add individual accounts to the resource group. The procedure below assumes the
addition of an entire pod to the resource group using the Add Pod to Resource Group option.
3.
In the Resource Group page, select the option to Add New Resource Group. Provide a Name and
optional Description. In the Pod selection, choose a pod to be added to the resource group. Click
Submit.
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
33
Cisco UCS Director Extended Deployment for FlexPod Datacenter with VMware vSphere and Cisco Application
Define Environment Specific Inputs
Also defined in a Resource Group are various Environment Specific Inputs. These Environment Specific
Inputs allow the infrastructure admin or system admin to define specific environment characteristics for
the chosen Resource Group. For example, information such as which VLAN Pool Policy should be used
or connectivity information such as the APIC static path for a device (physical domain) can all be
defined within a Resource Group.
Resource Groups are divided into six different classes in order to help organize the devices, environment
specific inputs and other resource group related options. The six classes are Virtual Compute, Virtual
Storage, Virtual Network, Physical Compute, Physical Storage and Physical Network.
To define the appropriate Environment Specific Inputs required for the use cases highlighted in this
document, complete the following steps:
1.
In UCS Director, navigate to Policies'Resource Groups and then select the Resource Groups tab.
2.
Highlight the appropriate existing Resource Group (created above) from the table and click the Edit
button.
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
34
Cisco UCS Director Extended Deployment for FlexPod Datacenter with VMware vSphere and Cisco
3.
On the Resource Group page, click Next.
4.
On the Virtual Compute page, the vCenter account should again be listed in the Virtual Accounts
table. Click Next.
5.
On the Virtual Storage page, the vCenter account should again be listed in the Virtual Accounts
table. Click Next.
6.
On the Virtual Network page, the vCenter account should again be listed in the Virtual Accounts
table. Click on the vCenter account and click the edit button that looks like a pencil.
7.
On the Edit Virtual Accounts Entry page, add the following items under Environment Specific
Inputs using the green plus button.
Resource Group  Virtual Network  Environment Specific Inputs
Name
Required Value
VMM Domain
[Select the VMM Domain associated with the vCenter
account]
DV Switch
[Select the required VMware Distributed Virtual Switch
associated with the selected VMM Domain]
8.
When all Environment Specific Inputs have been added to the Virtual Network section, click
Submit.
9.
On the Physical Compute page, the UCS Manager account should be listed in the Compute Accounts
table. Click Next.
10. On the Physical Storage page, the NetApp cluster account should be listed in the Storage Accounts
table. Click the NetApp cluster account and click the edit button with the pencil icon.
11. On the Edit Storage Accounts Entry page, add the following items under Environment Specific
Inputs using the green plus button.
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
35
Cisco UCS Director Extended Deployment for FlexPod Datacenter with VMware vSphere and Cisco Application
Resource Group  Physical Storage  Environment Specific Inputs
Name
Required Value
Cluster Node 1 Identity
[Select Cluster Node 1 Identity]
Cluster Node 2 Identity
[Select Cluster Node 2 Identity]
APIC vPC Static Path for Node
[Select APIC vPC Static Path for Node 1]
1
APIC vPC Static Path for Node
[Select APIC vPC Static Path for Node 2]
2
NFS IP Subnet Pool Policy
[Select IP Subnet Pool Policy]
SVM mgmt IP Subnet Pool
[Select IP Subnet Pool Policy]
Policy
iSCSI_A IP Subnet Pool Policy
[Select IP Subnet Pool Policy]
iSCSI_B IP Subnet Pool Policy
[Select IP Subnet Pool Policy]
APIC Vlan Pool for Node 1
[Select APIC VLAN Pool for Node 1 Physical Domain]
APIC Vlan Pool for Node 2
[Select APIC VLAN Pool for Node 2 Physical Domain]
NFS Vlan Pool
[Select the UCSD VLAN Pool Policy]
SVM mgmt Vlan Pool
[Select the UCSD VLAN Pool Policy]
iSCSI_A VLAN Pool
[Select the UCSD VLAN Pool Policy]
iSCSI_B VLAN Pool
[Select the UCSD VLAN Pool Policy]
12. When all Environment Specific Inputs have been added to the Physical Storage section, click
Submit.
13. Click Next.
14. On the Physical Network page, the Cisco APIC account should be listed in the Network Accounts
table. Click Submit.
Create Service Offering
As previously described, a Service Offering is a collection of requirements that will be used to match a
tenant to a Resource Group. Each Service Offering is organized into six different Service Classes which
correspond to the six different classes defined in the Resource Group, The six different Service Classes
are Virtual Compute, Virtual Storage, Virtual Network, Physical Compute, Physical Storage and
Physical Network. Within each Service Class, the infrastructure admin or system admin can define the
exact requirements from the tenant perspective. These requirements are organized into two categories,
capabilities (what capabilities the tenant requires) and capacities (what capacity does the tenant require).
To create a new Service Offering and define the six different Service Classes within the newly created
Service Offering, complete the following steps:
1.
In UCS Director, navigate to Policies'Resource Groups and then select the Service Offering tab.
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
36
Cisco UCS Director Extended Deployment for FlexPod Datacenter with VMware vSphere and Cisco
2.
Click Add.
3.
On the Service Offering - Specification page, provide a Name and optional Description for the
Service Offering. Click Next.
4.
On the Service Class page, click the green plus sign to add a new Service Class to the Service
Offering. Service Offerings contain the same six classes defined in Resource Groups as well.
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
37
Cisco UCS Director Extended Deployment for FlexPod Datacenter with VMware vSphere and Cisco Application
5.
On the Add Entry to Service Class page, provide a Name and optional Description. Ensure Resource
Allocation type for Tenant and Resource Allocation type for Application are set to Shared. Selected
Virtual Compute for the Resource Type. Under Resource Capability and Resource Capacity,
optionally set any specific parameters that are required per tenant. These two sections define
capabilities and capacities that must be available within the resource group that is used. This
procedure continues assuming the default values are accepted. Click Submit.
6.
Repeat steps 4 and 5 above to add a Service Class entry for all six class categories (Virtual Compute,
Virtual Storage, Virtual Network, Physical Compute, Physical Storage and Physical Network)
defining specific requirements in terms of capabilities and capacities needed by the tenants.
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
38
Cisco UCS Director Extended Deployment for FlexPod Datacenter with VMware vSphere and Cisco
7.
When creating the Virtual Compute and Physical Storage Service Classes, A a Resource Tag. Add
the Tag Name of Availability and a Tag Value of AVAILABLE. Again, this should only be done for
the Virtual Compute and Physical Storage Service Classes.
8.
After all six Service Class entries have been added to the Service Offering, click Submit.
Create Tenant Profile
A Tenant Profile is a template for choosing or matching a Service Offering (tenant requirements) with a
Resource Group (available resources) which can be reused across tenants with similar requirements. To
create a Tenant Profile within UCS Director, complete the following steps:
1.
In UCS Director, navigate to Policies'Resource Groups and then select the Tenant Profile tab.
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
39
Cisco UCS Director Extended Deployment for FlexPod Datacenter with VMware vSphere and Cisco Application
2.
Click Add.
3.
On the Tenant Profile page, provide a Name and optional Description. Select the Service Offering
created in the previous steps. Select Admin Selection in the Resource Group Selection dropdown
menu. Click Next.
4.
On the Resource Groups page, use the green plus button to add a Resource Group to the Resource
Group table.
5.
On the Add Entry to Resource Group page, ensure the same Service Offering is selected in the
drop-down menu and select the Resource Group from the Resource Group table. Click Submit.
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
40
Cisco UCS Director Workflow Primer
6.
Click Submit.
Cisco UCS Director Workflow Primer
This section will provide an introduction to UCS Director workflows and how they are built and
executed. This information is very important and valuable if looking to create custom workflows for
specific infrastructure operations within UCS Director. This information will also help the reader follow
along with the remainder of this document, which discusses building UCS Director workflows
pertaining to specific use-case examples.
What is a Workflow
In UCS Director, a workflow is simply a collection of specific infrastructure tasks that are constructed
in a particular order to perform a particular operation. These tasks can come in two different forms; they
can be provided as out of the box tasks as part of the task library in the installed product or they can be
custom tasks that are created by UCS Director administrators. No matter the type of task, out of the box
or custom, workflows are built using a standard process of dragging and dropping the required tasks into
the workflow pane and then mapping inputs and outputs (variables) accordingly between the tasks.
Inputs and Outputs
The mapping of inputs and outputs in a UCS Director workflow is very important. Each task has a set
of inputs that are required to perform its intended function or purpose. Being that a workflow is meant
to be built once and executed multiple times, similar to a template, UCS Director must provide a
dynamic capability for passing data specific to each workflow execution. This capability comes in the
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
41
Cisco UCS Director Use Case Overview
form of workflow variables that can be mapped to one or more specific task inputs. This variable
mapping mechanism allows for the passing and usage of information throughout the workflow, from one
task to another.
Each task input as well as each workflow variable has an attribute called an input type which specifies
the type of data that is expected for that particular input or is held within that particular workflow
variable. This input type attribute helps to ensure that the appropriate data gets mapped to the appropriate
task input or inputs and that the data is in the proper format. For example, a task that adds a VLAN to a
switch might require a task input of VLAN (among others) and the input type for that task input might
be vlan id. The vlan_id input type ensures that only integers between 0 and 4096 are passed to this
particular task input named VLAN. UCS Director will only allow you to map workflow variables with
an input type of vlan id to a task input with an input type of vlan id. The only exception to this is if the
task input requires an input type of Generic Text Input. In this case, any workflow variable of any input
type can be mapped to a task input with an input type of Generic Text Input.
There are three sources of information that can be used in a workflow and mapped to task inputs.
•
End User Input—A workflow can be configured to prompt the executing user for certain
information. This information is then transferred as workflow variables and mapped where
necessary throughout the workflow to specific task inputs. This is a dynamic source of information,
meaning that with each execution of the workflow, the data or information will most likely be
different.
•
Task Output—As each task in a workflow is completed, certain objects may have been created or
changed, etc.. As this happens, the task produces information, such as the name of that object for
example, and stores this information as one or more task outputs. These task outputs are variables
that can then be mapped to subsequent task inputs. This is another dynamic source of information
within the workflow.
•
Static Admin Input—As a workflow is built, the builder can choose where to get each and every
required task input. If the task input is not mapped to an End User Input or a Task Output from
another task, the task input must be entered as a static input. This is a static source of information,
meaning with each and every execution of the workflow, this value will stay exactly the same.
Cisco UCS Director Use Case Overview
The following sections below detail the UCS Director workflows, configurations and operations
necessary to perform an example set of use cases when managing and automating a FlexPod with Cisco
Application Infrastructure architecture. Each use case highlighted below is meant to build upon the next,
therefore the specific order in which each use case is implemented is important. The use cases
highlighted in this document are as follows:
•
Use Case 1: Tenant Infrastructure Configuration - in order for the other use cases highlighted in this
document to be completed, the tenant must be deployed and configured on the FlexPod architecture.
This use case highlights a UCS Director workflow example that can be used to deploy and configure
a tenant within the FlexPod architecture.
•
Use Case 2: Enable Tenant Infrastructure To Support Guest Attached iSCSI - after the tenant has
been deployed and configured, the tenant may require VM direct attached iSCSI storage
capabilities. This use case highlights a UCS Director workflow example that can be used to
configure the tenant infrastructure and ACI network fabric to support highly-available (two iSCSI
paths) VM direct attached iSCSI.
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
42
Cisco UCS Director Use Case Overview
•
Use Case 3: Enable Tenant Virtual Machine Provisioning - In most if not all cases, once a tenant is
provisioned, the tenant users will want to provision VMs within their tenant infrastructure. The
procedure highlighted in this use case details the steps for configuring self-service VM provisioning
for a tenant that has been deployed.
•
Use Case 4: Enable Connectivity For Virtual Machine Application Consistent Snapshots - This use
case highlights a small UCS Director example workflow which enables specific connectivity
between a VM network in which one or more application virtual machines are connected, and the
network in which the tenant's storage virtual machine (SVM) management LIF is connected. This
connectivity is required to leverage NetApp SnapDrive and SnapManager software, which enables
application virtual machine consistent data snapshots.
Cisco UCS Director Use Case Example #1: Tenant Infrastructure
Configuration
Overview
This section describes the specific use case where a new tenant is configured in the FlexPod with ACI
infrastructure. The definition of a tenant in this context is a container or grouping of resources dedicated
to a specific group of users or applications.
In this example, the tenant is provided with a dedicated vSphere NFS datastore securely provisioned
within a NetApp SVM and dedicated storage networks. A NetApp SVM securely isolates shared,
virtualized data storage and network attachment. Each SVM appears as if it were a dedicated storage
controller to the tenant. In other words, it is as if each tenant received a virtualized NetApp storage
controller.
Each SVM has a separate user authentication domain and can be managed independently by its SVM
administrator, an ideal approach to providing dedicated and secure storage resources within a
multi-tenant environment. The tenant's dedicated storage networks access the SVM storage through a
logical interface (LIF) that can be further assigned to a VLAN interface and combined with other
interfaces into failover groups for high availability. All of these tenant storage resources, networks, and
connectivity endpoints are provisioned by UCS Director leveraging ACI. Refer to NetApp Clustered
Data ONTAP 8.2.x An Introduction for more information about clustered Data ONTAP.
This section covers the expected outcome or results of this use case and also how to build a UCS Director
workflow to automate the execution of an example use case. At a high-level, this use case covers the
following operations across the FlexPod infrastructure:
Note
•
The provisioning and configuration of a tenant-dedicated NetApp SVM.
•
The configuration of the ACI, vSphere, and NetApp infrastructure needed to enable NFS datastore
connectivity from the SVM to ESXi hosts.
•
The configuration of the ACI infrastructure to instantiate a tenant-specific SVM_MGMT network.
•
The configuration of the ACI infrastructure to instantiate a tenant-specific VMNET network.
Although the use cases described in this document can be used exactly as is, they are presented as an
example of what is possible in terms of infrastructure automation with UCS Director. Please use the
use-case examples, tools, and methods in this document as needed to build the workflows and
appropriate infrastructure processes dictated by your requirements.
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
43
Cisco UCS Director Use Case Overview
Figure 4 depicts what is configured per tenant with each execution of the UCS Director workflow built
for use case example #1.
Figure 4
Tenant Infrastructure Configuration for Use Case Example #1
Table 2 provides a high-level process overview of the steps and order of operations involved in
successfully provisioning a new Tenant as per the FlexPod with ACI deployment guide. Notice not only
the sheer number of tasks involved in successfully automating this use-case, but also the number of
devices that these operations must take place on across the infrastructure. UCS Director is handling the
coordination of the tasks across all required devices as well as the passing of required information
between tasks.
Table 2
Use-case #1: Task List and Order of Operations
Operational Task
1. Get Info From Resource Group
2. Create Tenant Group
3. Get Tenant NFS VLAN
4. Get Tenant SVM MGMT VLAN
5. Create NFS VLAN Interface Node 1
6. Create NFS VLAN Interface Node 2
7. Create SVM MGMT VLAN Interface Node 1
8. Create SVM MGMT VLAN Interface Node 2
9. Edit SVM MGMT VLAN Interface MTU Size Node 1
10. Edit SVM MGMT VLAN Interface MTU Size Node 2
11. Create Tenant Storage Virtual Machine
12. Enable vStorage on Tenant SVM
13. Reserve IP Address Subnet for NFS
14. Reserve IP Address Subnet for SVM MGMT
15. Get IP Address for NFS LIF
16. Get IP Address for SVM MGMT LIF
17. Create a Flexible Volume for Tenant NFS Datastore
18. Create Cluster Export Policy Rule
19. Create Junction Path for Tenant Flexible Volume
20. Enable Deduplication on Tenant Flexible Volume
21. Create Failover Group for NFS on Node 1
22. Create Failover Group for NFS on Node 2
23. Create Failover Group for SVM MGMT on Node 1
24. Create Failover Group for SVM MGMT on Node 2
25. Create LIF for NFS
26. Create LIF for SVM MGMT
27. Set VSADMIN User Password on Tenant SVM
28. Enable VSADMIN User Account on Tenant SVM
29. Create SVM Root Volume Load Sharing Mirror on
Node 1
30. Create SVM Root Volume Load Sharing Mirror on
Node 2
Infrastructure Domain
Cisco UCS Director
Cisco UCS Director
NetApp Clustered Data ONTAP
NetApp Clustered Data ONTAP
NetApp Clustered Data ONTAP
NetApp Clustered Data ONTAP
NetApp Clustered Data ONTAP
NetApp Clustered Data ONTAP
NetApp Clustered Data ONTAP
NetApp Clustered Data ONTAP
NetApp Clustered Data ONTAP
NetApp Clustered Data ONTAP
NetApp Clustered Data ONTAP
NetApp Clustered Data ONTAP
NetApp Clustered Data ONTAP
NetApp Clustered Data ONTAP
NetApp Clustered Data ONTAP
NetApp Clustered Data ONTAP
NetApp Clustered Data ONTAP
NetApp Clustered Data ONTAP
NetApp Clustered Data ONTAP
NetApp Clustered Data ONTAP
NetApp Clustered Data ONTAP
NetApp Clustered Data ONTAP
NetApp Clustered Data ONTAP
NetApp Clustered Data ONTAP
NetApp Clustered Data ONTAP
NetApp Clustered Data ONTAP
NetApp Clustered Data ONTAP
NetApp Clustered Data ONTAP
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
44
Cisco UCS Director Use Case Overview
31. Create SnapMirror Load Sharing Relationship on
32.
33.
34.
35.
Node 1
Create SnapMirror Load Sharing Relationship on
Node 2
Initialize Load Sharing Relationship on Node 1
Initialize Load Sharing Relationship on Node 2
Create Tenant in APIC
36. Create Tenant Private Network
37. Create Tenant NFS Bridge Domain
38. Create Tenant SVM MGMT Bridge Domain
39. Create Tenant VMNET Bridge Domain
40. Create Tenant NFS Application Profile
41. Create Tenant SVM MGMT Application Profile
42. Create Tenant VMNET Application Profile
43. Create Tenant LIF NFS EPG
44. Create Tenant VMKernel NFS EPG
45. Create Tenant LIF SVM MGMT EPG
46. Create Tenant VMNET EPG
47. Create Subnet for SVM MGMT EPG
48. Add NFS VLAN to VLAN Pool for Node 1
49. Add NFS VLAN to VLAN Pool for Node 2
50. Add SVM MGMT VLAN to VLAN Pool for Node 1
51. Add SVM_MGMT VLAN to VLAN Pool for Node 2
52. Add VMM Domain to VMKernel NFS EPG
53. Add VMM Domain to VMNET EPG
54. Add Static Path for Node 1 to LIF NFS EPG
55. Add Static Path for Node 2 to LIF NFS EPG
56. Add Static Path for Node 1 to LIF SVM MGMT EPG
57. Add Static Path for Node 2 to LIF SVM MGMT EPG
58. Add NFS VMKernel Ports to ESXi Cluster Hosts
59. Create Contract for NFS
60. Create Contract Subject for NFS
61. Create NFS Contract Filter
NetApp Clustered Data ONTAP
NetApp Clustered Data ONTAP
NetApp Clustered Data ONTAP
NetApp Clustered Data ONTAP
Cisco Application Infrastructure
Controller
Cisco Application Infrastructure
Controller
Cisco Application Infrastructure
Controller
Cisco Application Infrastructure
Controller
Cisco Application Infrastructure
Controller
Cisco Application Infrastructure
Controller
Cisco Application Infrastructure
Controller
Cisco Application Infrastructure
Controller
Cisco Application Infrastructure
Controller
Cisco Application Infrastructure
Controller
Cisco Application Infrastructure
Controller
Cisco Application Infrastructure
Controller
Cisco Application Infrastructure
Controller
Cisco Application Infrastructure
Controller
Cisco Application Infrastructure
Controller
Cisco Application Infrastructure
Controller
Cisco Application Infrastructure
Controller
Cisco Application Infrastructure
Controller
Cisco Application Infrastructure
Controller
Cisco Application Infrastructure
Controller
Cisco Application Infrastructure
Controller
Cisco Application Infrastructure
Controller
Cisco Application Infrastructure
Controller
VMware vCenter Server
Cisco Application Infrastructure
Controller
Cisco Application Infrastructure
Controller
Cisco Application Infrastructure
Controller
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
45
Cisco UCS Director Use Case Overview
62. Create NFS Contract Filter Rule 1
63. Create NFS Contract Filter Rule 2
64. Create NFS Contract Filter Rule 3
65. Create NFS Contract Filter Rule 4
66. Create NFS Contract Filter Rule 5
67. Create NFS Contract Filter Rule 6
68. Add NFS Filter to Contract Subject
69. Add NFS Contract to LIF NFS EPG
70. Add NFS Contract to VMK NFS EPG
71.
72.
73.
74.
Mount Tenant NFS Datastore
Assign APIC Tenant to Group
Assign Tenant SVM to Group
Assign VMNET Distributed Port Group to Group
Cisco Application Infrastructure
Controller
Cisco Application Infrastructure
Controller
Cisco Application Infrastructure
Controller
Cisco Application Infrastructure
Controller
Cisco Application Infrastructure
Controller
Cisco Application Infrastructure
Controller
Cisco Application Infrastructure
Controller
Cisco Application Infrastructure
Controller
Cisco Application Infrastructure
Controller
VMware vCenter Server
Cisco UCS Director
Cisco UCS Director
Cisco UCS Director
User Perspective
This specific use-case and its associated UCS Director workflow, as highlighted and configured below,
is expected to be executed from the perspective of the infrastructure administrator, typically a user with
the system admin or other comparable user role in UCS Director. In this use case, this workflow is not
configured for publication to, and execution from an end-user or tenant perspective.
Prerequisites
This section details the specific prerequisites that must be in place and configured prior to building and
executing the UCS Director workflow for this specific use case:
•
FlexPod with ACI configuration in place and operational as per the Cisco CVD Deployment Guide.
•
Cisco UCS Director initial deployment must be performed. The required procedure can be found in
this document in the Cisco UCS Director Initial Deployment section.
•
UCS Director extended deployment for FlexPod must be performed. This configuration pertains to
specific steps that must be in place regarding managing a FlexPod within UCS Director. The
required procedure can be found in this document in the UCS Director Extended Deployment for
FlexPod with ACI section.
Detailed Workflow Configuration
To create new workflow, complete the following steps:
1.
In UCS Director, navigate to Policies'Orchestration and then select the Workflows tab.
2.
Click the Add Workflow button to create a new workflow. Optionally use the Import button to
import the published version of this workflow as opposed to building from scratch. This procedure
continues assuming creating a new workflow.
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
46
Cisco UCS Director Use Case Overview
3.
Provide a Workflow Name.
4.
Optionally provide a Description.
5.
Set Workflow Context to Any.
6.
Optionally select Save as Compound Task. This option will add this specific workflow as a task in
the task library therefore enabling this workflow to be nested in other workflows as a task.
7.
Under Save Options, choose an existing folder in the Select Folder dropdown menu, or choose Place
in New Folder and provide the name of the new folder.
8.
Select any optional Notifications options to notify users of workflow execution status.
9.
Click Next.
10. On the Add User Inputs page, this is where we create the form that will be presented to each user
when the workflow is executed. This form will prompt the user for specific information that can then
be mapped to task inputs throughout the workflow. The table below in the Workflow User Inputs
section provides information on the User Inputs defined for this specific use case workflow.
11. Click Next.
12. Click Submit.
Workflow User Inputs
This information can be provided when creating a new workflow on the Add User Inputs page, as seen
in the procedure above, or items can be added as workflow user inputs as tasks are added to the
workflow. On the User Input Mapping page of each task (after it is dragged into the workflow from the
task library), there is an Edit Workflow Properties button at the top of the page. This button can be used
at any time to add additional user inputs. To reiterate, these are the items that the user will be prompted
for each time the workflow is executed. This information is then generally mapped to the appropriate
task or tasks throughout the workflow for various task inputs.
Table 3 represents the User Inputs that are collected from the user each time this specific workflow is
executed. This list is provided simply as an example. Specific customer requirements may require a
larger or small number of User Inputs. This list can be customized as needed, however the information
below is what is required to fulfill this use-case as is highlighted in this document.
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
47
Cisco UCS Director Use Case Overview
Table 3
Workflow User Inputs
Input Label
Input
Description
Tenant Name
Tenant Profile
Tenant Service Offering
Tenant Contact
Information
Tenant SVM Admin
Password
Datastore Capacity
Datastore Capacity
Units
Datastrore Storage
SnapShot Policy
SVM Root Volume LS
SnapMirror Schedule
Mandator
y
Yes
Yes
Yes
Yes
gen_text_input
rgTenantProfileIdentity
ServiceOfferingName
email_address_list
Yes
password
Yes
Yes
netAppVolSize
sizeUnit
Yes
netappClusterSnapshotPolic
yIdentity
NetAppClusterCronJobIdenti
ty
Yes
Type
Admin Input
Value
Workflow Tasks and Input/Output Mappings
This section provides detailed information about the UCS Director tasks used to build an automated
workflow for executing this use case. Also Included is information regarding the order of operations
(tasks) as well as the mapping of inputs and outputs between tasks.
Get Info From Resource Group
Task Name from Task Library:
(drag and drop this task)
Tenant Onboarding Wrapper for FlexPod with ACI
Task Information
Field
Value
Task Name
Get_Info_From_Resource_Group
Task Category
Resource Group Tasks
Task Type
Tenant Onboarding Wrapper for FlexPod with ACI
Comment
Get Info From Resource Group
User Input Mapping
Input
Tenant Name (Mandatory)
Tenant profile Name (Mandatory)
Service Offering (Mandatory)
Datastore Size
Mapped




Mapped Variable
Tenant Name
Tenant Profile
Tenant Service Offering
Datastore Capacity
Select Host/Cluster (Mandatory)
CPU Resource Reservation (MHz)
(Mandatory)
Memory Resource Reservation (MB)
(Mandatory)
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
48
Cisco UCS Director Use Case Overview
Task Inputs
Input
Value
Select Host/Cluster
Cluster
CPU Resource Reservation (MHz)
0
Memory Resource Reservation (MB)
0
Create Tenant Group
Task Name from Task Library:
(drag and drop this task)
Add Group
Task Information
Field
Value
Task Name
Create_Tenant_Group
Task Category
User and Group Tasks
Task Type
Add Group
Comment
Create Tenant Group
User Input Mapping
Input
Name (Mandatory)
Mapped
Mapped Variable

Tenant Name

Tenant Contact Email Address
Description
MSP Group Name
Code
Contact Email (Mandatory)
First Name
Last Name
Phone
Address
Group Share Policy
Task Inputs
Input
Value
Description
Code
First Name
Last Name
Phone
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
49
Cisco UCS Director Use Case Overview
Address
Group Share Policy

Allow Resource Assignment To Users
Get Tenant NFS VLAN
Task Name from Task
Library:
Generate VLAN from pool
Task Information
Field
Value
Task Name
Get_Tenant_NFS_VLAN
Task Category
General Tasks
Task Type
Generate VLAN from pool
Comment
Get Tenant NFS VLAN
User Input Mapping
Input
VLAN Pool Policy (Mandatory)
Mapped

Mapped Variable
Get_Info_From_Resource_Group.NFS_VLAN_POOL
Task Inputs
Input
Task Name from Task Library:
(drag and drop this task)
Value
Generate VLAN from pool
Task Information
Field
Value
Task Name
Get_Tenant_SVM_MGMT_VLAN
Task Category
General Tasks
Task Type
Generate VLAN from pool
Comment
Get Tenant SVM_MGMT VLAN
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
50
Cisco UCS Director Use Case Overview
User Input Mapping
Input
VLAN Pool Policy (Mandatory)
Mapped

Mapped Variable
Get_Info_From_Resource_Group.SVM_MGMT_VLAN_POOL
Task Inputs
Input
Value
Create NFS VLAN Interface Node 1
Task Name from Task Library:
(drag and drop this task)
Create Cluster vLAN Interface
Task Information
Field
Value
Task Name
Create_NFS_VLAN_Interface_Node_1
Task Category
NetApp clustered Data ONTAP Tasks
Task Type
Create Cluster vLAN Interface
Comment
Create NFS VLAN Interface Node 1
User Input Mapping
Input
Port Name (Mandatory)
VLAN ID (Mandatory)
Mapped


Mapped Variable
Get_Info_From_Resource_Group.NETAPP_INTERFACEGROUP
_PRIMARY_NODE_PORT
Get_Tenant_NFS_VLAN.OUTPUT_VLAN_ID
Task Inputs
Input
Value
Create NFS VLAN Interface Node 2
Task Name from Task Library:
(drag and drop this task)
Create Cluster vLAN Interface
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
51
Cisco UCS Director Use Case Overview
Task Information
Field
Value
Task Name
Create_NFS_VLAN_Interface_Node_2
Task Category
NetApp clustered Data ONTAP Tasks
Task Type
Create Cluster vLAN Interface
Comment
Create NFS VLAN Interface Node 2
User Input Mapping
Input
Port Name (Mandatory)
VLAN ID (Mandatory)
Mapped


Mapped Variable
Get_Info_From_Resource_Group.NETAPP_INTERFACEGRO
UP_PARTNER_NODE_PORT
Get_Tenant_NFS_VLAN.OUTPUT_VLAN_ID
Task Inputs
Input
Value
Create SVM MGMT VLAN Interface Node 1
Task Name from Task Library:
(drag and drop this task)
Create Cluster vLAN Interface
Task Information
Field
Value
Task Name
Create_SVM_MGMT_VLAN_Interface_Node_1
Task Category
NetApp clustered Data ONTAP Tasks
Task Type
Create Cluster vLAN Interface
Comment
Create SVM_MGMT VLAN Interface Node 1
User Input Mapping
Input
Port Name (Mandatory)
VLAN ID (Mandatory)
Mapped


Mapped Variable
Get_Info_From_Resource_Group.NETAPP_INTERFACEGRO
UP_PRIMARY_NODE_PORT
Get_Tenant_SVM_MGMT_VLAN.OUTPUT_VLAN_ID
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
52
Cisco UCS Director Use Case Overview
Task Inputs
Input
Value
Create SVM MGMT VLAN Interface Node 2
Task Name from Task Library:
(drag and drop this task)
Create Cluster vLAN Interface
Task Information
Field
Value
Task Name
Create_SVM_MGMT_VLAN_Interface_Node_2
Task Category
NetApp clustered Data ONTAP Tasks
Task Type
Create Cluster vLAN Interface
Comment
Create SVM_MGMT VLAN Interface Node 2
User Input Mapping
Input
Port Name (Mandatory)
VLAN ID (Mandatory)
Mapped


Mapped Variable
Get_Info_From_Resource_Group.NETAPP_INTERFACEGRO
UP_PARTNER_NODE_PORT
Get_Tenant_SVM_MGMT_VLAN.OUTPUT_VLAN_ID
Task Inputs
Input
Value
Edit SVM MGMT VLAN Interface MTU Size Node 1
Task Name from Task Library:
(drag and drop this task)
Execute NetApp Cluster CLI
Task Information
Field
Value
Task Name
Edit_SVM_MGMT_VLAN_Interface_MTU_Size_Node_1
Task Category
NetApp clustered Data ONTAP Tasks
Task Type
Execute NetApp Cluster CLI
Comment
Edit SVM MGMT VLAN Interface MTU Size Node 1
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
53
Cisco UCS Director Use Case Overview
User Input Mapping
Input
Filer Identity Name (Mandatory)
Mapped

Mapped Variable
Get_Info_From_Resource_Group.NETAPP_CLUSTER_FILE
R_IDENTITY
CLI Command
Expected Output
Undo CLI Command
Task Inputs
Input
CLI Command
Value
network port modify -node
${Get_Info_From_Resource_Group.NETAPP_CLUSTER_NODE_NAME}
-port a0a-${Get_Tenant_SVM_MGMT_VLAN.OUTPUT_VLAN_ID} -mtu
1500
Edit SVM MGMT VLAN Interface MTU Size Node 2
Task Name from Task Library:
(drag and drop this task)
Execute NetApp Cluster CLI
Task Information
Field
Value
Task Name
Edit_SVM_MGMT_VLAN_Interface_MTU_Size_Node_2
Task Category
NetApp clustered Data ONTAP Tasks
Task Type
Execute NetApp Cluster CLI
Comment
Edit SVM MGMT VLAN Interface MTU Size Node 2
User Input Mapping
Input
Filer Identity Name (Mandatory)
Mapped

Mapped Variable
Get_Info_From_Resource_Group.NETAPP_CLUSTER_FILE
R_IDENTITY
CLI Command
Expected Output
Undo CLI Command
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
54
Cisco UCS Director Use Case Overview
Task Inputs
Input
CLI Command
Value
network port modify -node
${Get_Info_From_Resource_Group.NETAPP_CLUSTER_PARTNER_NOD
E_NAME} -port
a0a-${Get_Tenant_SVM_MGMT_VLAN.OUTPUT_VLAN_ID} -mtu 1500
Create Tenant Storage Virtual Machine
Task Name from Task Library:
(drag and drop this task)
Create Cluster Vserver
Task Information
Field
Value
Task Name
Create_Tenant_Storage_Virtual_Machine
Task Category
NetApp clustered Data ONTAP Tasks
Task Type
Create Cluster Vserver
Comment
Create Tenant Storage Virtual Machine
User Input Mapping
Input
Mapped


Aggregate Name (Mandatory
Vserver Name
Mapped Variable
Get_Info_From_Resource_Group.NETAPP_AGGREGATE_I
DENTITY
Tenant Name
Root Volume Name
Name Service Switch
Security Style
Snapshot Policy
Protocols
Task Inputs
Input
Value
Root Volume Name
${Tenant Name}_rootvol
Name Service Switch
file
Security Style
unix
Snapshot Policy
Protocols
NFS
NFS Service Start

FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
55
Cisco UCS Director Use Case Overview
Enable vStorage on Tenant SVM
Task Name from Task Library:
(drag and drop this task)
Execute NetApp Cluster CLI
Task Information
Field
Value
Task Name
Enable_vStorage_on_Tenant_SVM
Task Category
NetApp clustered Data ONTAP Tasks
Task Type
Execute NetApp Cluster CLI
Comment
Enable vStorage on Tenant SVM
User Input Mapping
Input
Filer Identity Name (Mandatory)
Mapped

Mapped Variable
Get_Info_From_Resource_Group.NETAPP_CLUSTER_FILE
R_IDENTITY
CLI Command
Expected Output
Undo CLI Command
Task Inputs
Input
Value
CLI Command
vserver nfs modify -vserver ${Tenant Name} -vstorage enabled
Reserve IP Address Subnet for NFS
Task Name from Task Library:
(drag and drop this task)
Get IP Subnet From IP Subnet Pool Policy
Task Information
Field
Value
Task Name
Reserve_Tenant_NFS_IP_Subnet
Task Category
General Tasks
Task Type
Get IP From IP Subnet Pool Policy
Comment
Reserve Tenant NFS IP Subnet
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
56
Cisco UCS Director Use Case Overview
User Input Mapping
Input
IP Subnet Pool Policy (Mandatory)
User Group ID (Mandatory)
Mapped


Mapped Variable
Get_Info_From_Resource_Group.NFS_IP_SUBNET_POOL_PO
LICY
Create_Tenant_Group.OUTPUT_USER_GROUP
IP Subnet Label
Task Inputs
Input
Value
IP Subnet Label
NFS
Reserve IP Address Subnet for SVM MGMT
Task Name from Task Library:
(drag and drop this task)
Get IP Subnet From IP Subnet Pool Policy
Task Information
Field
Value
Task Name
Reserve_Tenant_SVM_MGMT_IP_Subnet
Task Category
General Tasks
Task Type
Get IP From IP Subnet Pool Policy
Comment
Reserve Tenant SVM_MGMT IP Subnet
User Input Mapping
Input
IP Subnet Pool Policy (Mandatory)
User Group ID (Mandatory)
Mapped


Mapped Variable
Get_Info_From_Resource_Group.SVM_MGMT_IP_SUBNET_P
OOL_POLICY
Create_Tenant_Group.OUTPUT_USER_GROUP
IP Subnet Label
Task Inputs
Input
Value
IP Subnet Label
SVM_MGMT
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
57
Cisco UCS Director Use Case Overview
Get IP Address for NFS LIF
Task Name from Task Library:
Get IP Address From IP Subnet
(drag and drop this task)
Task Information
Field
Value
Task Name
Get_NFS_LIF_IP_Address_From_Subet
Task Category
General Tasks
Task Type
Get IP Address From IP Subnet
Comment
Get NFS LIF IP Address From Subnet
User Input Mapping
Input
Mapped
User Group ID (Mandatory)
Mapped Variable

Create_Tenant_Group.OUTPUT_USER_GROUP

Reserve_Tenant_NFS_IP_Subnet.OUTPUT_SUBNET_ID
IP Subnet Label
IP Subnet
Task Inputs
Input
Value
IP Subnet Label
Get IP Address for SVM MGMT LIF
Task Name from Task Library:
(drag and drop this task)
Get IP Address From IP Subnet
Task Information
Field
Value
Task Name
Get_SVM_MGMT_LIF_IP_Address_From_Subet
Task Category
General Tasks
Task Type
Get IP Address From IP Subnet
Comment
Get SVM_MGMT LIF IP Address From Subnet
User Input Mapping
Input
User Group ID (Mandatory)
Mapped
Mapped Variable

Create_Tenant_Group.OUTPUT_USER_GROUP

Reserve_Tenant_SVM_MGMT_IP_Subnet.OUTPUT_SUB
NET_ID
IP Subnet Label
IP Subnet
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
58
Cisco UCS Director Use Case Overview
Task Inputs
Input
Value
IP Subnet Label
Create a Flexible Volume for Tenant NFS Datastore
Task Name from Task Library:
(drag and drop this task)
Create Cluster Flexible Volume
Task Information
Field
Value
Task Name
Create_Flexible_Volume_for_Tenant_Datastore
Task Category
NetApp clustered Data ONTAP Tasks
Task Type
Create Cluster Flexible Volume
Comment
Create Flexible Volume for Tenant Datastore
User Input Mapping
Input
Mapped
Vserver Name (Mandatory)

Aggregate Name (Mandatory)

Mapped Variable
Create_Tenant_Storage_Virtual_Machine.OUTPUT_CLUSTER_
VSERVER_IDENTITY
Create_Tenant_Storage_Virtual_Machine.OUTPUT_CLUSTER_
AGGREGATE_IDENTITY
Volume Name
Volume Size (Mandatory)
Volume Size Units


Datastore Capacity

Datastore Storage SnapShot Policy
Datastore Capacity Unit
Volume Type (Mandatory)
Volume State
Security Style
Space Guarantee
Snapshot Size (%)
Snapshot Policy
Export Policy
Flexcache Origin Volume Name for type
DC (Mandatory)
Task Inputs
Input
Value
Volume Name
${Tenant Name}_datastore_1
Volume Type
RW
Volume State
online
Security Style
unix
Space Guarantee
none
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
59
Cisco UCS Director Use Case Overview
Snapshot Size (%)
0
Export Policy
Create Cluster Export Policy Rule
Task Name from Task Library:
(drag and drop this task)
Create Cluster Export Rule
Task Information
Field
Value
Task Name
Create_Cluster_Export_Policy_Rule
Task Category
NetApp clustered Data ONTAP Tasks
Task Type
Create Cluster Export Rule
Comment
Create Cluster Export Policy Rule
User Input Mapping
Input
Mapped
Vserver Name (Mandatory)

Export Policy (Mandatory)

Mapped Variable
Create_Tenant_Storage_Virtual_Machine.OUTPUT_CLUSTE
R_VSERVER_IDENTITY
Create_Flexible_Volume_for_Tenant_Datastore.OUTPUT_CL
USTER_EXPORT_POLICY_IDENTITY
Access Protocol
Client Match Spec (Mandatory)
Read Only Access Rule (Mandatory)
Read Write Access Rule (Mandatory)
Rule Index
Task Inputs
Input
Value
Access Protocol
Read Only Access Rule
NFS
${Reserve_Tenant_NFS_IP_Subnet.OUTPUT_NETWORK_IP}/${Ge
t_NFS_LIF_IP_Address_From_Subnet.SubnetMask Bitwise Value}
Sys
Read Write Access Rule
Sys
Client Match Spec
Rule Index
Create Junction Path for Tenant Flexible Volume
Task Name from Task Library:
(drag and drop this task)
Mount Cluster Volume
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
60
Cisco UCS Director Use Case Overview
Task Information
Field
Value
Task Name
Create_Junction_Path_For_Tenant_Flexible_Volume
Task Category
NetApp clustered Data ONTAP Tasks
Task Type
Mount Cluster Volume
Comment
Create Junction Path For Tenant Flexible Volume
User Input Mapping
Input
Volume Name (Mandatory)
Mapped

Mapped Variable
Create_Flexible_Volume_for_Tenant_Datastore.OUTPUT_CL
USTER_VOLUME_IDENTITY
Junction Path
Task Inputs
Input
Value
Junction Path
/${Create_Flexible_Volume_for_Tenant_Datastore.VOLUME_NAME}
Enable Deduplication on Tenant Flexible Volume
Task Name from Task Library:
(drag and drop this task)
Execute NetApp Cluster CLI
Task Information
Field
Value
Task Name
Enable_Deduplication_on_Tenant_Datastore
Task Category
NetApp clustered Data ONTAP Tasks
Task Type
Execute NetApp Cluster CLI
Comment
Enable Deduplication on Tenant Datastore
User Input Mapping
Input
Filer Identity Name (Mandatory)
Mapped
Mapped Variable
Get_Info_From_Resource_Group.NETAPP_CLUSTER_FILE
R_IDENTITY
CLI Command
Expected Output
Undo CLI Command
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
61
Cisco UCS Director Use Case Overview
Task Inputs
Input
Value
volume efficiency on -vserver ${Tenant_Name} -volume
${Tenant_Name}_datastore_1
CLI Command
Create Failover Group for NFS on Node 1
Task Name from Task Library:
Create FailOver Group
(drag and drop this task)
Task Information
Field
Value
Task Name
Create_Failover_Group_NFS_Node_1
Task Category
NetApp clustered Data ONTAP Tasks
Task Type
Create FailOver Group
Comment
Create Failover Group NFS Node 1
User Input Mapping
Input
Mapped
Mapped Variable
FailOver Group Name (Mandatory)
Create_NFS_VLAN_Interface_Node_1.OUTPUT_CLUS
TER_ALL_PORT_NAMES

Port (Mandatory)
Task Inputs
Input
Value
FailOver Group Name
${Tenant Name}-nfs-${Get_Tenant_NFS_VLAN.OUTPUT_VLAN_ID}
Create Failover Group for NFS on Node 2
Task Name from Task Library:
(drag and drop this task)
Create FailOver Group
Task Information
Field
Value
Task Name
Create_Failover_Group_NFS_Node_2
Task Category
NetApp clustered Data ONTAP Tasks
Task Type
Create FailOver Group
Comment
Create Failover Group NFS Node 2
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
62
Cisco UCS Director Use Case Overview
User Input Mapping
Input
Mapped
Mapped Variable
FailOver Group Name (Mandatory)
Create_NFS_VLAN_Interface_Node_2.OUTPUT_CLUS
TER_ALL_PORT_NAMES

Port (Mandatory)
Task Inputs
Input
Value
FailOver Group Name
${Tenant Name}-nfs-${Get_Tenant_NFS_VLAN.OUTPUT_VLAN_ID}
Create Failover Group for SVM MGMT on Node 1
Task Name from Task Library:
(drag and drop this task)
Create FailOver Group
Task Information
Field
Value
Task Name
Create_Failover_Group_SVM_MGMT_Node_1
Task Category
NetApp clustered Data ONTAP Tasks
Task Type
Create FailOver Group
Comment
Create Failover Group SVM_MGMT Node 1
User Input Mapping
Input
Mapped
Mapped Variable
FailOver Group Name (Mandatory)
Port (Mandatory)

Create_SVM_MGMT_VLAN_Interface_Node_1.OUTP
UT_CLUSTER_ALL_PORT_NAMES
Task Inputs
Input
FailOver Group Name
Value
${Tenant
Name}-svm-mgmt-${Get_Tenant_SVM_MGMT_VLAN.OUTPUT_VLAN_ID}
Create Failover Group for SVM MGMT on Node 2
Task Name from Task Library:
(drag and drop this task)
Create FailOver Group
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
63
Cisco UCS Director Use Case Overview
Task Information
Field
Value
Task Name
Create_Failover_Group_SVM_MGMT_Node_2
Task Category
NetApp clustered Data ONTAP Tasks
Task Type
Create FailOver Group
Comment
Create Failover Group SVM_MGMT Node 2
User Input Mapping
Input
Mapped
Mapped Variable
FailOver Group Name (Mandatory)
Port (Mandatory)
Create_SVM_MGMT_VLAN_Interface_Node_2.OUTP
UT_CLUSTER_ALL_PORT_NAMES

Task Inputs
Input
FailOver Group Name
Value
${Tenant
Name}-svm-mgmt-${Get_Tenant_SVM_MGMT_VLAN.OUTPUT_VLAN_ID}
Create LIF for NFS
Task Name from Task Library:
(drag and drop this task)
Create Cluster Logical Interface
Task Information
Field
Value
Task Name
Create_NFS_LIF
Task Category
NetApp clustered Data ONTAP Tasks
Task Type
Create Cluster Logical Interface
Comment
Create NFS LIF
User Input Mapping
Input
Mapped
Mapped Variable
Role (Mandatory)
Vserver Name (Mandatory)

Home Node (Mandatory)

Create_Tenant_Storage_Virtual_Machine.OUTPUT_CLUS
TER_VSERVER_IDENTITY
Get_Info_From_Resource_Group.NETAPP_NODE_IDENT
ITY
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
64
Cisco UCS Director Use Case Overview
Home Port (Mandatory)

Create_NFS_VLAN_Interface_Node_1.OUTPUT_CLUSTE
R_PORT_NAME


Get_NFS_LIF_IP_Address_From_Subnet.IPAddress

Create_Failover_Group_NFS_Node_1.OUTPUT_CLUSTE
R_FAIL_OVER_GROUP_NAME
Logical Interface Name
IP Address
Subnetmask (Mandatory)
Get_NFS_LIF_IP_Address_From_Subnet.SubnetMask
Failover Policy
Use Failover Group
Failover Group Name (Mandatory)
Task Inputs
Input
Value
Role
Data
Allowed Protocols
NFS
Logical Interface Name
LIF_NFS
Failover Policy
nextavail
Use Failover Group
enabled
Create LIF for SVM MGMT
Task Name from Task Library:
(drag and drop this task)
Create Cluster Logical Interface
Task Information
Field
Value
Task Name
Create_SVM_MGMT_LIF
Task Category
NetApp clustered Data ONTAP Tasks
Task Type
Create Cluster Logical Interface
Comment
Create SVM_MGMT LIF
User Input Mapping
Input
Mapped
Mapped Variable
Role (Mandatory)
Vserver Name (Mandatory)

Home Node (Mandatory)

Home Port (Mandatory)

Create_Tenant_Storage_Virtual_Machine.OUTPUT_CLUS
TER_VSERVER_IDENTITY
Get_Info_From_Resource_Group.NETAPP_NODE_IDENT
ITY
Create_SVM_MGMT_VLAN_Interface_Node_1.OUTPUT
_CLUSTER_PORT_NAME
Logical Interface Name
IP Address

Subnetmask (Mandatory)

Get_SVM_MGMT_LIF_IP_Address_From_Subnet.IPAddr
ess
Get_SVM_MGMT_LIF_IP_Address_From_Subnet.Subnet
Mask
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
65
Cisco UCS Director Use Case Overview
Failover Policy
Use Failover Group

Failover Group Name (Mandatory)
Create_Failover_Group_SVM_MGMT_Node_1.OUTPUT_
CLUSTER_FAIL_OVER_GROUP_NAME
Task Inputs
Input
Value
Role
Data
Allowed Protocols
Logical Interface Name
LIF_SVM_MGMT
Failover Policy
nextavail
Use Failover Group
enabled
Set VSADMIN User Password on Tenant SVM
Task Name from Task Library:
Modify Vserver User
(drag and drop this task)
Task Information
Field
Value
Task Name
Set_SVM_VSADMIN_Account_Password
Task Category
NetApp clustered Data ONTAP Tasks
Task Type
Modify Vserver User
Comment
Set SVM VSADMIN Account Password
User Input Mapping
Input
Mapped
Vserver Name (Mandatory)

Mapped Variable
Create_Tenant_Storage_Virtual_Machine.OUTPUT_CLUS
TER_VSERVER_IDENTITY

Tenant SVM Admin Password
UserName
Password
Task Inputs
Input
Value
UserName
vsadmin
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
66
Cisco UCS Director Use Case Overview
Enable VSADMIN User Account on Tenant SVM
Task Name from Task Library:
Enable Vserver User
(drag and drop this task)
Task Information
Field
Value
Task Name
Enable_Tenant_SVM_VSADMIN_Account
Task Category
NetApp clustered Data ONTAP Tasks
Task Type
Modify Vserver User
Comment
Enable Tenant SVM VSADMIN Account
User Input Mapping
Input
Mapped

Vserver Name (Mandatory)
Mapped Variable
Create_Tenant_Storage_Virtual_Machine.OUTPUT_CLUS
TER_VSERVER_IDENTITY
UserName
Task Inputs
Input
Value
UserName
vsadmin
Create SVM Root Volume Load Sharing Mirror on Node 1
Task Name from Task Library:
Create Cluster Flexible Volume
(drag and drop this task)
Task Information
Field
Value
Task Name
Create_SVM_Rootvol_Load_Sharing_Mirror_Node_1
Task Category
NetApp clustered Data ONTAP Tasks
Task Type
Create Cluster Flexible Volume
Comment
Create SVM Rootvol Load Sharing Mirror Node 1
User Input Mapping
Input
Vserver Name (Mandatory)
Mapped

Mapped Variable
Create_Tenant_Storage_Virtual_Machine.OUTPUT_CLUSTER_VSER
VER_IDENTITY
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
67
Cisco UCS Director Use Case Overview
Aggregate Name (Mandatory)

Get_Info_From_Resource_Group.NETAPP_AGGREGATE_IDENTITY
Volume Name
Volume Size (Mandatory)
Volume Size Units
Volume Type
Volume State
Security Style
Space Guarantee
Snapshot Size (%)
Snapshot Policy
Export Policy
Flexcache Origin Volume Name
for type DC (Mandatory)
Task Inputs
Input
Value
Volume Name
rootvol_m01
Volume Size
1
Volume Size Units
GB
Volume Type
DP
Volume State
online
Security Style
unix
Space Guarantee
none
Snapshot Size (%)
0
Snapshot Policy
Export Policy
Create SVM Root Volume Load Sharing Mirror on Node 2
Task Name from Task Library:
(drag and drop this task)
Create Cluster Flexible Volume
Task Information
Field
Value
Task Name
Create_SVM_Rootvol_Load_Sharing_Mirror_Node_2
Task Category
NetApp clustered Data ONTAP Tasks
Task Type
Create Cluster Flexible Volume
Comment
Create SVM Rootvol Load Sharing Mirror Node 2
User Input Mapping
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
68
Cisco UCS Director Use Case Overview
Input
Mapped
Vserver Name (Mandatory)

Aggregate Name (Mandatory)

Mapped Variable
Create_Tenant_Storage_Virtual_Machine.OUTPUT_CLUSTER_VSER
VER_IDENTITY
Get_Info_From_Resource.NETAPP_CLUSTER_PARTNER_AGGREG
ATE_IDENTITY
Volume Name
Volume Size (Mandatory)
Volume Size Units
Volume Type
Volume State
Security Style
Space Guarantee
Snapshot Size (%)
Snapshot Policy
Export Policy
Flexcache Origin Volume Name
for type DC (Mandatory)
Task Inputs
Input
Value
Volume Name
rootvol_m02
Volume Size
1
Volume Size Units
GB
Volume Type
DP
Volume State
online
Security Style
unix
Space Guarantee
none
Snapshot Size (%)
0
Snapshot Policy
Export Policy
Create SnapMirror Load Sharing Relationship on Node 1
Task Name from Task Library:
(drag and drop this task)
Create SnapMirror Relationship
Task Information
Field
Value
Task Name
Create_SnapMirror_LS_Relationship_Node_1
Task Category
NetApp clustered Data ONTAP Tasks
Task Type
Create SnapMirror Relationship
Comment
Create SnapMirror LS Relationship Node 1
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
69
Cisco UCS Director Use Case Overview
User Input Mapping
Input
Destination Volume (Mandatory)
Mapped

Mapped Variable
Create_SVM_Rootvol_Load_Sharing_Mirror_Node_1.OUTPUT_CLUS
TER_VOLUME_IDENTITY

Create_Tenant_Storage_Virtual_Machine.OUTPUT_CLUSTER_VOLU
ME_IDENTITY

SVM Root Volume LS SnapMirror Schedule
Relationship Type
Source Volume (Mandatory)
Policy
Schedule
Maximum Transfer Rate
Task Inputs
Input
Value
Relationship Type
Load Sharing
Policy
Maximum Transfer Rate kbps
Create SnapMirror Load Sharing Relationship on Node 2
Task Name from Task Library:
Create SnapMirror Relationship
(drag and drop this task)
Task Information
Field
Value
Task Name
Create_SnapMirror_LS_Relationship_Node_2
Task Category
NetApp clustered Data ONTAP Tasks
Task Type
Create SnapMirror Relationship
Comment
Create SnapMirror LS Relationship Node 2
User Input Mapping
Input
Destination Volume (Mandatory)
Mapped

Mapped Variable
Create_SVM_Rootvol_Load_Sharing_Mirror_Node_2.OUTPUT_CLUS
TER_VOLUME_IDENTITY

Create_Tenant_Storage_Virtual_Machine.OUTPUT_CLUSTER_VOLU
ME_IDENTITY

SVM Root Volume LS SnapMirror Schedule
Relationship Type
Source Volume (Mandatory)
Policy
Schedule
Maximum Transfer Rate
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
70
Cisco UCS Director Use Case Overview
Task Inputs
Input
Value
Relationship Type
Load Sharing
Policy
Maximum Transfer Rate kbps
Initialize Load Sharing Relationship on Node 1
Task Name from Task Library:
(drag and drop this task)
Actions on SnapMirror Relationship
Task Information
Field
Value
Task Name
Initialize_LS_Relationship_Node_1
Task Category
NetApp clustered Data ONTAP Tasks
Task Type
Actions on SnapMirror Relationship
Comment
Initialize LS Relationship Node 1
User Input Mapping
Input
Select SnapMirror Relationship
(Mandatory
Select Action Type
Mapped

Mapped Variable
Create_SnapMirror_LS_Relationship_Node_1.OUTPUT_CLUST
ER_SNAPMIRROR_RELATIONSHIP_IDENTITY
Transfer Priority
Maximum Transfer Rate (kbps)
Task Inputs
Input
Value
Select Action Type
Initialize
Initialize Load Sharing Relationship on Node 2
Task Name from Task Library:
(drag and drop this task)
Actions on SnapMirror Relationship
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
71
Cisco UCS Director Use Case Overview
Task Information
Field
Value
Task Name
Initialize_LS_Relationship_Node_2
Task Category
NetApp clustered Data ONTAP Tasks
Task Type
Actions on SnapMirror Relationship
Comment
Initialize LS Relationship Node 2
User Input Mapping
Input
Select SnapMirror Relationship
(Mandatory
Select Action Type
Mapped

Mapped Variable
Create_SnapMirror_LS_Relationship_Node_2.OUTPUT_CLUST
ER_SNAPMIRROR_RELATIONSHIP_IDENTITY
Transfer Priority
Maximum Transfer Rate (kbps)
Task Inputs
Input
Value
Select Action Type
Initialize
Create Tenant in APIC
Task Name from Task Library:
(drag and drop this task)
Create APIC Tenant
Task Information
Field
Value
Task Name
Create_APIC_Tenant
Task Category
Cisco APIC Tasks
Task Type
Create APIC Tenant
Comment
Create APIC Tenant
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
72
Cisco UCS Director Use Case Overview
User Input Mapping
Input
Mapped
APIC Account Name (Mandatory)
Tenant Name (Mandatory)


Mapped Variable
Get_Info_From_Resource_Group.APIC_ACCOUNT
Tenant Name
Tenant Description
Tenant Alias
Tenant Tags
Monitoring Policy
Security Domains
Task Inputs
Input
Value
Description
Alias
Tags
Monitoring Policy
Security Domains
all
Create Tenant Private Network
Task Name from Task Library:
(drag and drop this task)
Create Private Network
Task Information
Field
Value
Task Name
Create_Tenant_Private_Network
Task Category
Cisco APIC Tasks
Task Type
Create Private Network
Comment
Create Tenant Private Network
User Input Mapping
Input
Tenant Name (Mandatory)
Private Network Name (Mandatory)
Mapped


Mapped Variable
Create_APIC_Tenant.TENANT_IDENTITY
Tenant Name
Policy Enforcement
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
73
Cisco UCS Director Use Case Overview
Private Network Description
BGP Timers
OSPF Timers
Monitoring Policy
Task Inputs
Input
Value
Policy Enforcement
Private Network Description
BGP Timers
OSPF Timers
Monitoring Policy
Create Tenant NFS Bridge Domain
Task Name from Task Library:
(drag and drop this task)
Create Tenant Bridge Domain
Task Information
Field
Value
Task Name
Create_Tenant_NFS_Bridge_Domain
Task Category
Cisco APIC Tasks
Task Type
Create Tenant Bridge Domain
Comment
Create Tenant NFS Bridge Domain
User Input Mapping
Input
Tenant Name (Mandatory)
Mapped
Mapped Variable

Create_APIC_Tenant.TENANT_IDENTITY

Create_Tenant_Private_Network.PRIVATE_NETWORK_I
DENTITY
Bridge Domain Name (Mandatory)
Description
Network
Forwarding
L2 Unknown Unicast
Unknown Multicast Flooding
MacAddress
IGMP Snoop Policy
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
74
Cisco UCS Director Use Case Overview
Associated L3 Out
L3 Out for Route Profile
Monitoring Policy
Task Inputs
Input
Value
Bridge Domain Name
bd-NFS
Description
Network
Forwarding
Customize
L2 Unknown Unicast
Unknown Multicast
Flooding
ARP Flooding
Flood
Unicast Routing
Flood


Custom MacAddress
IGMP Snoop Policy
default
Associated L3 Out
L3 Out for Route Profile
Monitoring Policy
Create Tenant SVM MGMT Bridge Domain
Task Name from Task Library:
(drag and drop this task)
Create Tenant Bridge Domain
Task Information
Field
Value
Task Name
Create_Tenant_SVM_MGMT_Bridge_Domain
Task Category
Cisco APIC Tasks
Task Type
Create Tenant Bridge Domain
Comment
Create Tenant SVM_MGMT Bridge Domain
User Input Mapping
Input
Tenant Name (Mandatory)
Mapped

Mapped Variable
Create_APIC_Tenant.TENANT_IDENTITY
Bridge Domain Name (Mandatory)
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
75
Cisco UCS Director Use Case Overview
Description

Network
Create_Tenant_Private_Network.PRIVATE_NETWORK_I
DENTITY
Forwarding
L2 Unknown Unicast
Unknown Multicast Flooding
MacAddress
IGMP Snoop Policy
Associated L3 Out
L3 Out for Route Profile
Monitoring Policy
Task Inputs
Input
Value
Bridge Domain Name
bd-SVM_MGMT
Description
Forwarding
Customize
L2 Unknown Unicast
Unknown Multicast
Flooding
ARP Flooding
Flood
Unicast Routing
Flood


Custom MacAddress
IGMP Snoop Policy
default
Associated L3 Out
L3 Out for Route Profile
Monitoring Policy
Create Tenant VMNET Bridge Domain
Task Name from Task Library:
(drag and drop this task)
Create Tenant Bridge Domain
Task Information
Field
Value
Task Name
Create_Tenant_VMNET_Bridge_Domain
Task Category
Cisco APIC Tasks
Task Type
Create Tenant Bridge Domain
Comment
Create Tenant VMNET Bridge Domain
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
76
Cisco UCS Director Use Case Overview
User Input Mapping
Input
Mapped
Tenant Name (Mandatory)
Mapped Variable

Create_APIC_Tenant.TENANT_IDENTITY

Create_Tenant_Private_Network.PRIVATE_NETWORK_I
DENTITY
Bridge Domain Name (Mandatory)
Description
Network
Forwarding
L2 Unknown Unicast
Unknown Multicast Flooding
MacAddress
IGMP Snoop Policy
Associated L3 Out
L3 Out for Route Profile
Monitoring Policy
Task Inputs
Input
Value
Bridge Domain Name
bd-VMNET
Description
Forwarding
Customize
L2 Unknown Unicast
Unknown Multicast
Flooding
ARP Flooding
Flood
Unicast Routing
Flood


Custom MacAddress
IGMP Snoop Policy
default
Associated L3 Out
L3 Out for Route Profile
Monitoring Policy
Create Tenant NFS Application Profile
Task Name from Task Library:
(drag and drop this task)
Create Tenant Application Profile
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
77
Cisco UCS Director Use Case Overview
Task Information
Field
Value
Task Name
Create_NFS_Application_Profile
Task Category
Cisco APIC Tasks
Task Type
Create Tenant Application Profile
Comment
Create NFS Application Profile
User Input Mapping
Input
Mapped

Tenant Name (Mandatory)
Mapped Variable
Create_APIC_Tenant.TENANT_IDENTITY
Application Profile (Mandatory)
Description
Alias
Tags
QoS
Monitoring Policy
Task Inputs
Input
Value
Application Profile
NFS
Description
Alias
Tags
QoS
unspecified
Monitoring Policy
default
Create Tenant SVM MGMT Application Profile
Task Name from Task Library:
(drag and drop this task)
Create Tenant Application Profile
Task Information
Field
Value
Task Name
Create_SVM_MGMT_Application_Profile
Task Category
Cisco APIC Tasks
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
78
Cisco UCS Director Use Case Overview
Task Type
Create Tenant Application Profile
Comment
Create SVM_MGMT Application Profile
User Input Mapping
Input
Mapped

Tenant Name (Mandatory)
Mapped Variable
Create_APIC_Tenant.TENANT_IDENTITY
Application Profile (Mandatory)
Description
Alias
Tags
QoS
Monitoring Policy
Task Inputs
Input
Value
Application Profile
SVM_MGMT
Description
Alias
Tags
QoS
unspecified
Monitoring Policy
default
Create Tenant VMNET Application Profile
Task Name from Task Library:
(drag and drop this task)
Create Tenant Application Profile
Task Information
Field
Value
Task Name
Create_VMNET_Application_Profile
Task Category
Cisco APIC Tasks
Task Type
Create Tenant Application Profile
Comment
Create VMNET Application Profile
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
79
Cisco UCS Director Use Case Overview
User Input Mapping
Input
Mapped

Tenant Name (Mandatory)
Mapped Variable
Create_APIC_Tenant.TENANT_IDENTITY
Application Profile (Mandatory)
Description
Alias
Tags
QoS
Monitoring Policy
Task Inputs
Input
Value
Application Profile
VMNET
Description
Alias
Tags
QoS
unspecified
Monitoring Policy
default
Create Tenant LIF NFS EPG
Task Name from Task Library:
(drag and drop this task)
Create EPG
Task Information
Field
Value
Task Name
Create_LIF_NFS_EPG
Task Category
Cisco APIC Tasks
Task Type
Create EPG
Comment
Create LIF NFS EPG
User Input Mapping
Input
Application Profile Name (Mandatory)
Mapped

Mapped Variable
Create_NFS_Application_Profile.TENANT_APPLN_PROF
ILE_IDENTITY
EPG Name
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
80
Cisco UCS Director Use Case Overview
EPG Description
Alias
Tags
QoS Class
Custom QoS

Bridge Domain
Create_Tenant_NFS_Bridge_Domain.TENANT_BRIDGE_
DOMAIN_IDENTITY
Monitoring Policy
Task Inputs
Input
Value
EPG Name
LIF_NFS
EGP Description
Alias
Tags
QoS
unspecified
Custom QoS
Monitoring Policy
default
Create Tenant VMKernel NFS EPG
Task Name from Task Library:
(drag and drop this task)
Create EPG
Task Information
Field
Value
Task Name
Create_VMK_NFS_EPG
Task Category
Cisco APIC Tasks
Task Type
Create EPG
Comment
Create VMK NFS EPG
User Input Mapping
Input
Application Profile Name (Mandatory)
Mapped

Mapped Variable
Create_NFS_Application_Profile.TENANT_APPLN_PROF
ILE_IDENTITY
EPG Name
EPG Description
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
81
Cisco UCS Director Use Case Overview
Alias
Tags
QoS Class
Custom QoS

Bridge Domain
Create_Tenant_NFS_Bridge_Domain.TENANT_BRIDGE_
DOMAIN_IDENTITY
Monitoring Policy
Task Inputs
Input
Value
EPG Name
VMK_NFS
EGP Description
Alias
Tags
QoS
unspecified
Custom QoS
Monitoring Policy
default
Create Tenant LIF SVM MGMT EPG
Task Name from Task Library:
(drag and drop this task)
Create EPG
Task Information
Field
Value
Task Name
Create_LIF_SVM_MGMT_EPG
Task Category
Cisco APIC Tasks
Task Type
Create EPG
Comment
Create LIF SVM_MGMT EPG
User Input Mapping
Input
Application Profile Name (Mandatory)
Mapped

Mapped Variable
Create_SVM_MGMT_Application_Profile.TENANT_APP
LN_PROFILE_IDENTITY
EPG Name
EPG Description
Alias
Tags
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
82
Cisco UCS Director Use Case Overview
QoS Class
Custom QoS

Bridge Domain
Create_Tenant_SVM_MGMT_Bridge_Domain.TENANT_
BRIDGE_DOMAIN_IDENTITY
Monitoring Policy
Task Inputs
Input
Value
EPG Name
LIF_SVM_MGMT
EGP Description
Alias
Tags
QoS
unspecified
Custom QoS
Monitoring Policy
default
Create Tenant VMNET EPG
Task Name from Task Library:
(drag and drop this task)
Create EPG
Task Information
Field
Value
Task Name
Create_VMNET_EPG
Task Category
Cisco APIC Tasks
Task Type
Create EPG
Comment
Create VMNET EPG
User Input Mapping
Input
Application Profile Name (Mandatory)
Mapped

Mapped Variable
Create_VMNET_Application_Profile.TENANT_APPLN_P
ROFILE_IDENTITY
EPG Name
EPG Description
Alias
Tags
QoS Class
Custom QoS
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
83
Cisco UCS Director Use Case Overview

Bridge Domain
Create_Tenant_VMNET_Bridge_Domain.TENANT_BRID
GE_DOMAIN_IDENTITY
Monitoring Policy
Task Inputs
Input
Value
EPG Name
VMNET
EGP Description
Alias
Tags
QoS
unspecified
Custom QoS
Monitoring Policy
default
Create Subnet for SVM MGMT EPG
Task Name from Task Library:
(drag and drop this task)
Create Subnet To EPG
Task Information
Field
Value
Task Name
Create_Subnet_Gateway_for_SVM_MGMT_EPG
Task Category
Cisco APIC Tasks
Task Type
Create Subnet To EPG
Comment
Create Subnet Gateway for SVM_MGMT EPG
User Input Mapping
Input
Mapped
EPG (Mandatory)

Gateway IP (Address)(Mandatory)

Gateway IP (Prefix)(Mandatory)

Mapped Variable
Create_LIF_SVM_MGMT_EPG.TENANT_EPG_IDENTIT
Y
Reserve_Tenant_SVM_MGMT_IP_Subnet.OUTPUT_GAT
EWAY_IP
Get_SVM_MGMT_LIF_IP_Address_From_Subnet.Subnet
Mask Bitwise Value
Description
L3 Out for Route Prefix
Route Profile
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
84
Cisco UCS Director Use Case Overview
Task Inputs
Input
Value
Shared Subnet
Public Subnet
Private Subnet

Description
Subnet Control (Querier IP)
L3 Out for Route Prefix
Route Profile
Add NFS VLAN to VLAN Pool for Node 1
Task Name from Task Library:
Add VLAN Range To VLAN Pool
(drag and drop this task)
Task Information
Field
Value
Task Name
Add_NFS_VLAN_To_VLAN_Pool_Node_1
Task Category
Cisco APIC Tasks
Task Type
Add VLAN Range To VLAN Pool
Comment
Add NFS VLAN To VLAN Pool Node 1
User Input Mapping
Input
Mapped



VLAN Pool Name (Mandatory)
Range From (Mandatory)
Range To (Mandatory)
Mapped Variable
Get_Info_From_Resource_Pool.OUTPUT_APIC_VLAN_P
OOL_NODE1
Get_Tenant_NFS_VLAN.OUTPUT_VLAN_ID
Get_Tenant_NFS_VLAN.OUTPUT_VLAN_ID
Task Inputs
Input
Value
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
85
Cisco UCS Director Use Case Overview
Add NFS VLAN to VLAN Pool for Node 2
Task Name from Task Library:
Add VLAN Range To VLAN Pool
(drag and drop this task)
Task Information
Field
Value
Task Name
Add_NFS_VLAN_To_VLAN_Pool_Node_2
Task Category
Cisco APIC Tasks
Task Type
Add VLAN Range To VLAN Pool
Comment
Add NFS VLAN To VLAN Pool Node 2
User Input Mapping
Input
Mapped
Mapped Variable
Get_Info_From_Resource_Pool.OUTPUT_APIC_VLAN_P
OOL_NODE2
Get_Tenant_NFS_VLAN.OUTPUT_VLAN_ID



VLAN Pool Name (Mandatory)
Range From (Mandatory)
Range To (Mandatory)
Get_Tenant_NFS_VLAN.OUTPUT_VLAN_ID
Task Inputs
Input
Value
Add SVM MGMT VLAN to VLAN Pool for Node 1
Task Name from Task Library:
(drag and drop this task)
Add VLAN Range To VLAN Pool
Task Information
Field
Value
Task Name
Add_SVM_MGMT_VLAN_To_VLAN_Pool_Node_1
Task Category
Cisco APIC Tasks
Task Type
Add VLAN Range To VLAN Pool
Comment
Add SVM_MGMT VLAN To VLAN Pool Node 1
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
86
Cisco UCS Director Use Case Overview
User Input Mapping
Input
Mapped
Mapped Variable
Get_Info_From_Resource_Pool.OUTPUT_APIC_VLAN_P
OOL_NODE1
Get_Tenant_SVM_MGMT_VLAN.OUTPUT_VLAN_ID



VLAN Pool Name (Mandatory)
Range From (Mandatory)
Range To (Mandatory)
Get_Tenant_SVM_MGMT_VLAN.OUTPUT_VLAN_ID
Task Inputs
Input
Value
Add SVM_MGMT VLAN to VLAN Pool for Node 2
Task Name from Task Library:
Add VLAN Range To VLAN Pool
(drag and drop this task)
Task Information
Field
Value
Task Name
Add_SVM_MGMT_VLAN_To_VLAN_Pool_Node_2
Task Category
Cisco APIC Tasks
Task Type
Add VLAN Range To VLAN Pool
Comment
Add SVM_MGMT VLAN To VLAN Pool Node 2
User Input Mapping
Input
Mapped



VLAN Pool Name (Mandatory)
Range From (Mandatory)
Range To (Mandatory)
Mapped Variable
Get_Info_From_Resource_Pool.OUTPUT_APIC_VLAN_P
OOL_NODE2
Get_Tenant_SVM_MGMT_VLAN.OUTPUT_VLAN_ID
Get_Tenant_SVM_MGMT_VLAN.OUTPUT_VLAN_ID
Task Inputs
Input
Value
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
87
Cisco UCS Director Use Case Overview
Add VMM Domain to VMKernel NFS EPG
Task Name from Task Library:
Add Domain to EPG
(drag and drop this task)
Task Information
Field
Value
Task Name
Add_VMM_Domain_to_VMK_NFS_EPG
Task Category
Cisco APIC Tasks
Task Type
Add Domain To EPG
Comment
Add VMM Domain to VMK_NFS EPG
User Input Mapping
Input
Mapped


EPG (Mandatory)
Domain Profile (Mandatory)
Mapped Variable
Create_VMK_NFS_EPG.TENANT_EPG_IDENTITY
Get_Infro_From_Resource_Group.VMM_DOMAIN_PROF
ILE_IDENTITY
Deploy Immediacy
Resolution Immediacy
Task Inputs
Input
Value
Deploy Immediacy
immediate
Resolution Immediacy
immediate
Add VMM Domain to VMNET EPG
Task Name from Task Library:
(drag and drop this task)
Add Domain to EPG
Task Information
Field
Value
Task Name
Add_VMM_Domain_to_VMNET_EPG
Task Category
Cisco APIC Tasks
Task Type
Add Domain To EPG
Comment
Add VMM Domain to VMNET EPG
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
88
Cisco UCS Director Use Case Overview
User Input Mapping
Input
Mapped


EPG (Mandatory)
Domain Profile (Mandatory)
Mapped Variable
Create_VMNET_EPG.TENANT_EPG_IDENTITY
Get_Infro_From_Resource_Group.VMM_DOMAIN_PROF
ILE_IDENTITY
Deploy Immediacy
Resolution Immediacy
Task Inputs
Input
Value
Deploy Immediacy
immediate
Resolution Immediacy
immediate
Add Static Path for Node 1 to LIF NFS EPG
Task Name from Task Library:
(drag and drop this task)
Add Static Path to EPG
Task Information
Field
Value
Task Name
Add_Static_Path_to_LIF_NFS_EPG_Node_1
Task Category
Cisco APIC Tasks
Task Type
Add Static Path To EPG
Comment
Add Static Path to LIF_NFS EPG Node 1
User Input Mapping
Input
EPG (Mandatory)
Mapped
Mapped Variable

Create_LIF_NFS_EPG.TENANT_EPG_IDENTITY


Get_Info_From_Resource_Group.vPC_STATIC_PATH_FO
R_NODE1
Get_Tenant_NFS_VLAN.OUTPUT_VLAN_ID
Path Type (Mandatory)
Path (Mandatory)
Encapsulation (Mandatory)
Deployment Immediacy (Mandatory)
Mode (Mandatory)
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
89
Cisco UCS Director Use Case Overview
Task Inputs
Input
Value
Path Type
Virtual Port Channel
Deployment Immediacy
immediate
Mode
Tagged
Add Static Path for Node 2 to LIF NFS EPG
Task Name from Task Library:
Add Static Path to EPG
(drag and drop this task)
Task Information
Field
Value
Task Name
Add_Static_Path_to_LIF_NFS_EPG_Node_2
Task Category
Cisco APIC Tasks
Task Type
Add Static Path To EPG
Comment
Add Static Path to LIF_NFS EPG Node 2
User Input Mapping
Input
Mapped
EPG (Mandatory)
Mapped Variable

Create_LIF_NFS_EPG.TENANT_EPG_IDENTITY


Get_Info_From_Resource_Group.vPC_STATIC_PATH_FO
R_NODE2
Get_Tenant_NFS_VLAN.OUTPUT_VLAN_ID
Path Type (Mandatory)
Path (Mandatory)
Encapsulation (Mandatory)
Deployment Immediacy (Mandatory)
Mode (Mandatory)
Task Inputs
Input
Value
Path Type
Virtual Port Channel
Deployment Immediacy
immediate
Mode
Tagged
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
90
Cisco UCS Director Use Case Overview
Add Static Path for Node 1 to LIF SVM MGMT EPG
Task Name from Task Library:
Add Static Path to EPG
(drag and drop this task)
Task Information
Field
Value
Task Name
Add_Static_Path_to_LIF_SVM_MGMT_EPG_Node_1
Task Category
Cisco APIC Tasks
Task Type
Add Static Path To EPG
Comment
Add Static Path to LIF_SVM_MGMT EPG Node 1
User Input Mapping
Input
Mapped
EPG (Mandatory)

Mapped Variable
Create_LIF_SVM_MGMT_EPG.TENANT_EPG_IDENTIT
Y


Get_Info_From_Resource_Group.vPC_STATIC_PATH_FO
R_NODE1
Get_Tenant_SVM_MGMT_VLAN.OUTPUT_VLAN_ID
Path Type (Mandatory)
Path (Mandatory)
Encapsulation (Mandatory)
Deployment Immediacy (Mandatory)
Mode (Mandatory)
Task Inputs
Input
Value
Path Type
Virtual Port Channel
Deployment Immediacy
immediate
Mode
Tagged
Add Static Path for Node 2 to LIF SVM MGMT EPG
Task Name from Task Library:
(drag and drop this task)
Add Static Path to EPG
Task Information
Field
Value
Task Name
Add_Static_Path_to_LIF_SVM_MGMT_EPG_Node_2
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
91
Cisco UCS Director Use Case Overview
Task Category
Cisco APIC Tasks
Task Type
Add Static Path To EPG
Comment
Add Static Path to LIF_SVM_MGMT EPG Node 2
User Input Mapping
Input
Mapped
EPG (Mandatory)

Mapped Variable
Create_LIF_SVM_MGMT_EPG.TENANT_EPG_IDENTIT
Y


Get_Info_From_Resource_Group.vPC_STATIC_PATH_FO
R_NODE2
Get_Tenant_SVM_MGMT_VLAN.OUTPUT_VLAN_ID
Path Type (Mandatory)
Path (Mandatory)
Encapsulation (Mandatory)
Deployment Immediacy (Mandatory)
Mode (Mandatory)
Task Inputs
Input
Value
Path Type
Virtual Port Channel
Deployment Immediacy
immediate
Mode
Tagged
Create ESXi VMkernel Interfaces
Task Name from Task Library:
(drag and drop this task)
Add VMkernel Interfaces (custom)
Task Information
Field
Value
Task Name
Create_ESXi_VMkernel_Interfaces
Task Category
Custom Tasks
Task Type
Add VMkernel Interfaces (custom)
Comment
Create ESXi VMkernel Interfaces
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
92
Cisco UCS Director Use Case Overview
User Input Mapping
Input
Mapped
Mapped Variable
Select Host/Cluster (Mandatory)
Select Cluster (Mandatory)

Get_Info_From_Resource_Group.OUTPUT_VMWARE_C
LUSTER_IDENTITY

Add_VMM_Domain_to_VMK_EPG.VMWARE_DVSWIT
CH_PORTGROUP_IDENTITY

Reserve_Tenant_NFS_IP_Subnet.OUTPUT_SUBNET_ID
Select Host Nodes (Mandatory)
DVPortGroup Name (Mandatory)
Network Type (Mandatory)
IP Subnet (Mandatory)
MTU Size
Task Inputs
Input
Value
Select Host/Cluster
Cluster
Network Type
IPv4
MUT Size
9000
Enable vMotion
Create Contract for NFS
Task Name from Task Library:
(drag and drop this task)
Create Contract
Task Information
Field
Value
Task Name
Create_Tenant_NFS_Contract
Task Category
Cisco APIC Tasks
Task Type
Create Contract
Comment
Create Tenant NFS Contract
User Input Mapping
Input
Tenant Name (Mandatory)
Mapped

Mapped Variable
Create_APIC_Tenant.TENANT_IDENTITY
Contract Name
Contract Description
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
93
Cisco UCS Director Use Case Overview
Scope (Mandatory)
Priority (Mandatory)
Task Inputs
Input
Value
Contract Name
NFS
Contract Description
Scope
application-profile
Priority
unspecified
Create Contract Subject for NFS
Task Name from Task Library:
(drag and drop this task)
Create Contract Subject
Task Information
Field
Value
Task Name
Create_Tenant_NFS_Contract_Subject
Task Category
Cisco APIC Tasks
Task Type
Create Contract Subject
Comment
Create Tenant NFS Contract Subject
User Input Mapping
Input
Contract Name (Mandatory)
Mapped

Mapped Variable
Create_Tenant_NFS_Contract.TENANT_CONTRACT_ID
ENTITY
Type
Contract Subject Name (Mandatory)
Contract Subject Description
Reverse Filter Ports
Apply Both Directions
Service Graph
QoS
In Term Service Graph
In Term QoS
Out Term Service Graph
Out Term QoS
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
94
Cisco UCS Director Use Case Overview
Task Inputs
Input
Value
Type
Normal
Contract Subject Name
NFS
Contract Subject Description
Reverse Filter Ports
Apply Both Directions


Service Graph
QoS
unspecified
Create NFS Contract Filter
Task Name from Task Library:
Create Tenant Filter
(drag and drop this task)
Task Information
Field
Value
Task Name
Create_NFS_Contract_Filter
Task Category
Cisco APIC Tasks
Task Type
Create Tenant Filter
Comment
Create NFS Contract Filter
User Input Mapping
Input
Mapped

Tenant Name (Mandatory)
Mapped Variable
Create_APIC_Tenant.TENANT_IDENTITY
Filter Name (Mandatory)
Description
Task Inputs
Input
Value
Filter Name
Allow_NFS
Description
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
95
Cisco UCS Director Use Case Overview
Create NFS Contract Filter Rule 1
Task Name from Task Library:
Create Tenant Filter Rule
(drag and drop this task)
Task Information
Field
Value
Task Name
Create_NFS_Contract_Filter_Rule_1
Task Category
Cisco APIC Tasks
Task Type
Create Tenant Filter Rule
Comment
Create NFS Contract Filter Rule 1
User Input Mapping
Input
Mapped

Filter Name (Mandatory)
Mapped Variable
Create_NFS_Contract_Filter.TENANT_FILTER_IDENTIT
Y
Filter Rule Name (Mandatory)
Description
Ethernet Type (Mandatory)
ARP Flag
IP Protocol
Source Port Start
Source Port Start Custom (Mandatory)
Source Port End
Source Port End Custom (Mandatory)
Destination Port Start
Destination Port Start Custom (Mandatory)
Destination Port End
Destination Port End Custom (Mandatory)
Task Inputs
Input
Value
Filter Rule Name
tcp_111
Description
Ethernet Type
IP
ARP Flag
UNSPECIFIED
IP Protocol
TCP
Allow Fragment
Source Port Start
UNSPECIFIED
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
96
Cisco UCS Director Use Case Overview
Source Port End
UNSPECIFIED
Destination Port Start
Destination Port Start
Custom
Destination Port End
Destination Port End
Custom
TCP Session Rule
CUSTOM
111
CUSTOM
111
Unspecified
Create NFS Contract Filter Rule 2
Task Name from Task Library:
(drag and drop this task)
Create Tenant Filter Rule
Task Information
Field
Value
Task Name
Create_NFS_Contract_Filter_Rule_2
Task Category
Cisco APIC Tasks
Task Type
Create Tenant Filter Rule
Comment
Create NFS Contract Filter Rule 2
User Input Mapping
Input
Filter Name (Mandatory)
Mapped

Mapped Variable
Create_NFS_Contract_Filter.TENANT_FILTER_IDENTIT
Y
Filter Rule Name (Mandatory)
Description
Ethernet Type (Mandatory)
ARP Flag
IP Protocol
Source Port Start
Source Port Start Custom (Mandatory)
Source Port End
Source Port End Custom (Mandatory)
Destination Port Start
Destination Port Start Custom (Mandatory)
Destination Port End
Destination Port End Custom (Mandatory)
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
97
Cisco UCS Director Use Case Overview
Task Inputs
Input
Value
Filter Rule Name
tcp_635
Description
Ethernet Type
IP
ARP Flag
UNSPECIFIED
IP Protocol
TCP
Allow Fragment
Source Port Start
UNSPECIFIED
Source Port End
UNSPECIFIED
Destination Port Start
Destination Port Start
Custom
Destination Port End
Destination Port End
Custom
TCP Session Rule
CUSTOM
635
CUSTOM
635
Unspecified
Create NFS Contract Filter Rule 3
Task Name from Task Library:
(drag and drop this task)
Create Tenant Filter Rule
Task Information
Field
Value
Task Name
Create_NFS_Contract_Filter_Rule_3
Task Category
Cisco APIC Tasks
Task Type
Create Tenant Filter Rule
Comment
Create NFS Contract Filter Rule 3
User Input Mapping
Input
Filter Name (Mandatory)
Mapped

Mapped Variable
Create_NFS_Contract_Filter.TENANT_FILTER_IDENTIT
Y
Filter Rule Name (Mandatory)
Description
Ethernet Type (Mandatory)
ARP Flag
IP Protocol
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
98
Cisco UCS Director Use Case Overview
Source Port Start
Source Port Start Custom (Mandatory)
Source Port End
Source Port End Custom (Mandatory)
Destination Port Start
Destination Port Start Custom (Mandatory)
Destination Port End
Destination Port End Custom (Mandatory)
Task Inputs
Input
Value
Filter Rule Name
tcp_2049
Description
Ethernet Type
IP
ARP Flag
UNSPECIFIED
IP Protocol
TCP
Allow Fragment
Source Port Start
UNSPECIFIED
Source Port End
UNSPECIFIED
Destination Port Start
Destination Port Start
Custom
Destination Port End
Destination Port End
Custom
TCP Session Rule
CUSTOM
2049
CUSTOM
2049
Unspecified
Create NFS Contract Filter Rule 4
Task Name from Task Library:
(drag and drop this task)
Create Tenant Filter Rule
Task Information
Field
Value
Task Name
Create_NFS_Contract_Filter_Rule_4
Task Category
Cisco APIC Tasks
Task Type
Create Tenant Filter Rule
Comment
Create NFS Contract Filter Rule 4
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
99
Cisco UCS Director Use Case Overview
User Input Mapping
Input
Mapped

Filter Name (Mandatory)
Mapped Variable
Create_NFS_Contract_Filter.TENANT_FILTER_IDENTIT
Y
Filter Rule Name (Mandatory)
Description
Ethernet Type (Mandatory)
ARP Flag
IP Protocol
Source Port Start
Source Port Start Custom (Mandatory)
Source Port End
Source Port End Custom (Mandatory)
Destination Port Start
Destination Port Start Custom (Mandatory)
Destination Port End
Destination Port End Custom (Mandatory)
Task Inputs
Input
Value
Filter Rule Name
udp_111
Description
Ethernet Type
IP
ARP Flag
UNSPECIFIED
IP Protocol
UDP
Allow Fragment
Source Port Start
UNSPECIFIED
Source Port End
UNSPECIFIED
Destination Port Start
Destination Port Start
Custom
Destination Port End
Destination Port End
Custom
TCP Session Rule
CUSTOM
111
CUSTOM
111
Unspecified
Create NFS Contract Filter Rule 5
Task Name from Task Library:
(drag and drop this task)
Create Tenant Filter Rule
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
100
Cisco UCS Director Use Case Overview
Task Information
Field
Value
Task Name
Create_NFS_Contract_Filter_Rule_5
Task Category
Cisco APIC Tasks
Task Type
Create Tenant Filter Rule
Comment
Create NFS Contract Filter Rule 5
User Input Mapping
Input
Mapped

Filter Name (Mandatory)
Mapped Variable
Create_NFS_Contract_Filter.TENANT_FILTER_IDENTIT
Y
Filter Rule Name (Mandatory)
Description
Ethernet Type (Mandatory)
ARP Flag
IP Protocol
Source Port Start
Source Port Start Custom (Mandatory)
Source Port End
Source Port End Custom (Mandatory)
Destination Port Start
Destination Port Start Custom (Mandatory)
Destination Port End
Destination Port End Custom (Mandatory)
Task Inputs
Input
Value
Filter Rule Name
udp_635
Description
Ethernet Type
IP
ARP Flag
UNSPECIFIED
IP Protocol
UDP
Allow Fragment
Source Port Start
UNSPECIFIED
Source Port End
UNSPECIFIED
Destination Port Start
Destination Port Start
Custom
Destination Port End
CUSTOM
635
CUSTOM
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
101
Cisco UCS Director Use Case Overview
Destination Port End
Custom
TCP Session Rule
635
Unspecified
Create NFS Contract Filter Rule 6
Task Name from Task Library:
Create Tenant Filter Rule
(drag and drop this task)
Task Information
Field
Value
Task Name
Create_NFS_Contract_Filter_Rule_6
Task Category
Cisco APIC Tasks
Task Type
Create Tenant Filter Rule
Comment
Create NFS Contract Filter Rule 6
User Input Mapping
Input
Mapped

Filter Name (Mandatory)
Mapped Variable
Create_NFS_Contract_Filter.TENANT_FILTER_IDENTIT
Y
Filter Rule Name (Mandatory)
Description
Ethernet Type (Mandatory)
ARP Flag
IP Protocol
Source Port Start
Source Port Start Custom (Mandatory)
Source Port End
Source Port End Custom (Mandatory)
Destination Port Start
Destination Port Start Custom (Mandatory)
Destination Port End
Destination Port End Custom (Mandatory)
Task Inputs
Input
Value
Filter Rule Name
udp_2049
Description
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
102
Cisco UCS Director Use Case Overview
Ethernet Type
IP
ARP Flag
UNSPECIFIED
IP Protocol
UDP
Allow Fragment
Source Port Start
UNSPECIFIED
Source Port End
UNSPECIFIED
Destination Port Start
Destination Port Start
Custom
Destination Port End
Destination Port End
Custom
TCP Session Rule
CUSTOM
2049
CUSTOM
2049
Unspecified
Add NFS Filter to Contract Subject
Task Name from Task Library:
Add Filter To Contract Subject
(drag and drop this task)
Task Information
Field
Value
Task Name
Add_NFS_Filter_to_Contract_Subject
Task Category
Cisco APIC Tasks
Task Type
Add Filter To Contract Subject
Comment
Add NFS Filter to Contract Subject
User Input Mapping
Input
Mapped


Contract Subject (Mandatory)
Filter (Mandatory)
Mapped Variable
Create_Tenant_NFS_Contract_Subject.TENANT_CONTR
ACT_SUBJECT_IDENTITY
Create_Tenant_NFS_Filter.TENANT_FILTER_IDENTITY
Filter For Consumer To Provider
Filter For Provider To Consumer
Task Inputs
Input
Value
Apply Both Directions

FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
103
Cisco UCS Director Use Case Overview
Add NFS Contract to LIF NFS EPG
Task Name from Task Library:
Add Contract To EPG
(drag and drop this task)
Task Information
Field
Value
Task Name
Add_NFS_Contract_to_LIF_NFS_EPG
Task Category
Cisco APIC Tasks
Task Type
Add Contract To EPG
Comment
Add NFS Contract to LIF_NFS EPG
User Input Mapping
Input
Mapped
EPG (Mandatory)
Mapped Variable

Create_LIF_NFS_EPG.TENANT_EPG_IDENTITY

Create_Tenant_NFS_Contract.TENANT_CONTRACT_ID
ENTITY
Contract Type (Mandatory)
Contract (Mandatory)
QoS (Mandatory)
Task Inputs
Input
Value
Contract Type
Provided Contract
QoS
unspecified
Add NFS Contract to VMK NFS EPG
Task Name from Task Library:
(drag and drop this task)
Add Contract To EPG
Task Information
Field
Value
Task Name
Add_NFS_Contract_to_VMK_NFS_EPG
Task Category
Cisco APIC Tasks
Task Type
Add Contract To EPG
Comment
Add NFS Contract to VMK_NFS EPG
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
104
Cisco UCS Director Use Case Overview
User Input Mapping
Input
Mapped
EPG (Mandatory)
Mapped Variable

Create_VMK_NFS_EPG.TENANT_EPG_IDENTITY

Create_Tenant_NFS_Contract.TENANT_CONTRACT_ID
ENTITY
Contract Type (Mandatory)
Contract (Mandatory)
QoS (Mandatory)
Task Inputs
Input
Value
Contract Type
Consumed Contract
QoS
unspecified
Mount Tenant NFS Datastore
Task Name from Task Library:
(drag and drop this task)
Associate Cluster Volume as NFS Datastore
Task Information
Field
Value
Task Name
Mount_Tenant_NFS_Datastore
Task Category
NetApp clustered Data ONTAP Tasks
Task Type
Associate Cluster Volume as NFS Datastore
Comment
Mount Tenant NFS Datastore
User Input Mapping
Input
LIF Identity (Mandatory)
Mapped

Mapped Variable
Create_NFS_LIF.OUTPUT_CLUSTER_LOGICAL_INF_ID
ENTITY
Target Resource Type (Mandatory)
Hostnode (Mandatory)
VMware Cluster Identity (Mandatory)

NFS Path (Mandatory)

Datastore Name

Get_Info_From_Resource_Group.OUTPUT_VMWARE_CL
USTER_IDENTITY
Create_Junction_Path_For_Tenant_Flexible_Volume.OUTP
UT_CLUSTER_VOLUME_JUNCTION_PATH
Create_Flexible_Volume_for_Tenant_Datastore.VOLUME_
NAME
Access Mode (Mandatory)
Success Criteria
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
105
Cisco UCS Director Use Case Overview
Task Inputs
Input
Value
Target Resource Type
Cluster
Access Mode
Read/Write
Success Criteria
Mount successful on all the Hosts
Create Tenant VM Resource Pool
Task Name from Task Library:
(drag and drop this task)
Create Resource Pool
Task Information
Field
Value
Task Name
Create_Tenant_VM_Resource_Pool
Task Category
VMware Host Tasks
Task Type
Create Resource Pool
Comment
Create Tenant VM Resrouce Pool
User Input Mapping
Input
Parent Resource Pool (Mandatory)
Resource Pool Name (Mandatory)
Mapped


Mapped Variable
Get_Info_From_Resource_Group.OUTPUT_VMWARE_RE
SOURCE_POOL_IDENTITY
Tenant Name
CPU Resource Shares (Mandatory)
New CPU Resource Share (Mandatory)
CPU Resource Reservation (MHz)
(Mandatory)
CPU Expandable Reservation
CPU Resource Limit (MHz) (Mandatory)
CPU Resource Unlimited
Memory Resource Shares (Mandatory)
New Memory Resource Share (Mandatory)
Memory Resource Reservation (MB)
(Mandatory)
Memory Expandable Reservation
Memory Resource Limit (MB) (Mandatory)
Memory Resource Unlimited
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
106
Cisco UCS Director Use Case Overview
Task Inputs
Input
Value
CPU Resource Shares
CPU Resource Reservation
(MHz)
CPU Expandable
Reservation
CPU Resource Unlimited
Normal
Memory Resource Shares
Memory Resource
Reservation (MB)
Memory Expandable
Reservation
Memory Resource
Unlimited
0


Normal
0


Assign Resource Pool To Group
Task Name from Task Library:
Assign Resource Pool To Group
(drag and drop this task)
Task Information
Field
Value
Task Name
Assign_Resource_Pool_To_Group
Task Category
VMware Host Tasks
Task Type
Assign Resource Pool to Group
Comment
Assign Resource Pool To Group
User Input Mapping
Input
Mapped


Resource Pool (Mandatory)
User Group ID (Mandatory)
Mapped Variable
Create_Tenant_VM_Resource_Pool.RESOURCE_POOL_ID
ENTITY
Create_Tenant_Group.OUTPUT_GROUP_ID
Comments
Task Inputs
Input
Value
Assign To Users

Comments
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
107
Cisco UCS Director Use Case Overview
Assign APIC Tenant to Group
Task Name from Task Library:
Assign APIC Tenant to Group
(drag and drop this task)
Task Information
Field
Value
Task Name
Assign_APIC_Tenant_to_Group
Task Category
Cisco APIC Tasks
Task Type
Assign APIC Tenant to Group
Comment
Assign APIC Tenant to Group
User Input Mapping
Input
Mapped


Tenant Name (Mandatory)
User Group ID (Mandatory)
Mapped Variable
Create_APIC_Tenant.TENANT_IDENTITY
Create_Tenant_Group.OUTPUT_GROUP_ID
Comments
Task Inputs
Input
Value
Assign To Users

Comments
Assign Tenant SVM To Group
Task Name from Task Library:
(drag and drop this task)
Assign Vserver to Group
Task Information
Field
Value
Task Name
Assign_Tenant_SVM_To_Group
Task Category
User and Group Tasks
Task Type
Assign Vserver to Group
Comment
Assign Tenant SVM to Group
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
108
Cisco UCS Director Use Case Overview
User Input Mapping
Input
Mapped


Vserver Name (Mandatory)
User Group ID (Mandatory)
Mapped Variable
Create_Tenant_Storage_Virtual_Machine.OUTPUT_CLUST
ER_VSERVER_IDENTITY
Create_Tenant_Group.OUTPUT_GROUP_ID
Comments
Task Inputs
Input
Value
Assign To Users

Comments
Assign VMNET Distributed Port Group to Group
Task Name from Task Library:
Assign DV Port Group to Group
(drag and drop this task)
Task Information
Field
Value
Task Name
Assign_VMNET_Distributed_Port_Group_to_Group
Task Category
VMware Network Tasks
Task Type
Assign DV Port Group to Group
Comment
Assign VMNET Distributed Port Group to Group
User Input Mapping
Input
Mapped
dvPortGroup Name (Mandatory)
User Group ID (Mandatory)


Mapped Variable
Add_VMM_Domain_to_VMNET_EPG.VMWARE_DVSWI
TCH_PORTGROUP_IDENTITY
Create_Tenant_Group.OUTPUT_GROUP_ID
Task Inputs
Input
Value
Assign To Users

FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
109
Cisco UCS Director Use Case Overview
Allocate Tenant Resources
Task Name from Task Library:
(drag and drop this task)
Tenant Resource Allocation
Task Information
Field
Value
Task Name
Allocate_Resources_To_Tenant
Task Category
Resource Group Tasks
Task Type
Tenant Resource Allocation
Comment
Allocate Resources To Tenant
User Input Mapping
Input
Mapped
Mapped Variable



Tenant Name
Get_Info_From_Resource_Group.RESOURCEGROUP_NA
ME
Tenant Service Offering

Get_Info_From_Resource_Group.VMWARE_ACCOUNT_N
AME
vmWare Cluster

Resource Pool

DV Switch


Get_Info_From_Resource_Group.OUTPUT_VMWARE_CL
USTER_IDENTITY
Create_Tenant_VM_Resource_Pool.RESOURCE_POOL_ID
ENTITY
Get_Info_From_Resource_Group..VMWARE_DV_SWITCH
_NAME
Mount_Tenant_Datastore.DATASTORE_IDENTITY
Add_VMM_Domain_to_VMNET_EPG.VMWARE_DVSWI
TCH_PORTGROUP_IDENTITY
Tenant (Mandatory)
Resource Group (Mandatory)
Service Offering
Container
vCenter
Host
Hosts
Data Store
DV Port Group
Service Profile
Service Profiles
Service Profile Template
Server Pool
Server
NetApp Cluster vServer

Create_Tenant_Storage_Virtual_Machine.OUTPUT_CLUST
ER_VSERVER_IDENTITY
Aggregate Name
Filer Name
Raid Group Name
Storage Pool
NetApp VLAN
VMM Domain VLAN
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
110
Cisco UCS Director Use Case Example #2: Enable Tenant Infrastructure for Guest Attached iSCSI
APIC Account Name
Device Package
Task Inputs
Input
Value
Container
VMware Host
Hosts
dvSwitch Name
Datastore Name
Service Profile
Service Profiles
Service Profile Templates
Server Pool
Server
Servers
Aggregate Name
Filer Name
RAID Group Name for New
LUN
Storage Pool for New LUN
NetApp LUN
VMM Domain VLAN
Apic Account Name
Device Package
Cisco UCS Director Use Case Example #2: Enable Tenant
Infrastructure for Guest Attached iSCSI
Overview
This section covers the specific use case of configuring the new tenant infrastructure provisioned in use
case example #1 to support the iSCSI protocol for direct VM storage attachment. iSCSI storage is
provisioned from within the tenant's dedicated NetApp SVM and is accessed over tenant-dedicated
iSCSI networks. This example provisions two iSCSI network paths for high availability. In this context,
“direct VM storage attachment” means that the VM guest operating system has access to and controls
the mounting and management of iSCSI storage directly. This use case does not use raw device mapping
(RDM).
At a high-level, this use case covers the following operations across the FlexPod infrastructure:
•
The configuration of iSCSI service on the tenant-dedicated NetApp SVM.
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
111
Cisco UCS Director Use Case Example #2: Enable Tenant Infrastructure for Guest Attached iSCSI
Note
•
The provisioning and configuration of a tenant-specific iSCSI_A fabric across the ACI, vSphere and
NetApp infrastructure
•
The provisioning and configuration of a tenant-specific iSCSI_B fabric across the ACI, vSphere and
NetApp infrastructure
Although the use cases described in this document can be used exactly as is, they are presented as
examples of what infrastructure automation is possible with UCS Director. Use the use-case examples,
tools, and methods from this document to build the appropriate workflows and infrastructure processes
dictated by your requirements.
Figure 5 illustrates what is configured per tenant with each execution of the UCS Director workflow
built for use case example #2.
Figure 5
Tenant Infrastructure Configuration for Use Case Example #2
Table 4 provides a high-level process overview of the steps and order of operations required to
successfully configure the tenant infrastructure to support the iSCSI protocol. Notice both the large
number of tasks needed to automate this use case and also the number of devices that these operations
take place on across the infrastructure. UCS Director handles the coordination of these tasks across all
of the required devices and also the passing of required information between tasks.
Table 4
Use-Case Example #2: Task List and Order of Operations
Get Tenant iSCSI_A VLAN
Get Tenant iSCSI_B VLAN
Reserve IP Address Subnet for iSCSI_A
Reserve IP Address Subnet for iSCSI_B
Create VLAN Interface for iSCSI_A on Node 1
Create VLAN Interface for iSCSI_A on Node 2
Create VLAN Interface for iSCSI_B on Node 1
Create VLAN Interface for iSCSI_B on Node 2
Get IP Address for iSCSI_A LIF From Subnet
Node 1
10. Get IP Address for iSCSI_A LIF From Subnet
Node 2
11. Get IP Address for iSCSI_B LIF From Subnet
Node 1
12. Get IP Address for iSCSI_B LIF From Subnet
Node 2
1.
2.
3.
4.
5.
6.
7.
8.
9.
Cisco UCS Director
Cisco UCS Director
Cisco UCS Director
Cisco UCS Director
NetApp Clustered Data ONTAP
NetApp Clustered Data ONTAP
NetApp Clustered Data ONTAP
NetApp Clustered Data ONTAP
Cisco UCS Director
Cisco UCS Director
Cisco UCS Director
Cisco UCS Director
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
112
Cisco UCS Director Use Case Example #2: Enable Tenant Infrastructure for Guest Attached iSCSI
13.
14.
15.
16.
17.
18.
19.
Create LIF for iSCSI_A on Node 1
Create LIF for iSCSI_A on Node 2
Create LIF for iSCSI_B on Node 1
Create LIF for iSCSI_B on Node 2
Enable iSCSI Protocol on Tenant SVM
Create iSCSI Service on Tenant SVM
Create Tenant iSCSI_A Bridge Domain
20. Create Tenant iSCSI_B Bridge Domain
21. Create Tenant iSCSI_A Application Profile
22. Create Tenant iSCSI_B Application Profile
23. Create Tenant LIF iSCSI_A EPG
24. Create Tenant LIF iSCSI_B EPG
25. Create Tenant VM iSCSI_A EPG
26. Create Tenant VM iSCSI_B EPG
27. Add iSCSI_A VLAN to VLAN Pool
28. Add iSCSI_B VLAN to VLAN Pool
29. Add Static Path to LIF iSCSI_A EPG
30. Add Static Path to LIF iSCSI_B EPG
31. Add VMM Domain to VM iSCSI_A EPG
32. Add VMM Domain to VM iSCSI_B EPG
33. Create Contract for iSCSI_A
34. Create Contract for iSCSI_B
35. Create Contract Subject for iSCSI_A
36. Create Contract Subject for iSCSI_B
37. Create iSCSI Contract Filter
38. Create iSCSI Contract Filter Rule
39. Add iSCSI Filter to iSCSI_A Contract Subject
40. Add iSCSI Filter to iSCSI_B Contract Subject
41. Add iSCSI_A Contract to LIF iSCSI_A EPG
42. Add iSCSI_A Contract to VM iSCSI_A EPG
43. Add iSCSI_B Contract to LIF iSCSI_B EPG
44. Add iSCSI_B Contract to VM iSCSI_B EPG
45. Assign iSCSI_A Distributed Port Group to Group
46. Assign iSCSI_B Distributed Port Group to Group
NetApp Clustered Data ONTAP
NetApp Clustered Data ONTAP
NetApp Clustered Data ONTAP
NetApp Clustered Data ONTAP
NetApp Clustered Data ONTAP
NetApp Clustered Data ONTAP
Cisco Application Policy Infrastructure
Controller
Cisco Application Policy Infrastructure
Controller
Cisco Application Policy Infrastructure
Controller
Cisco Application Policy Infrastructure
Controller
Cisco Application Policy Infrastructure
Controller
Cisco Application Policy Infrastructure
Controller
Cisco Application Policy Infrastructure
Controller
Cisco Application Policy Infrastructure
Controller
Cisco Application Policy Infrastructure
Controller
Cisco Application Policy Infrastructure
Controller
Cisco Application Policy Infrastructure
Controller
Cisco Application Policy Infrastructure
Controller
Cisco Application Policy Infrastructure
Controller
Cisco Application Policy Infrastructure
Controller
Cisco Application Policy Infrastructure
Controller
Cisco Application Policy Infrastructure
Controller
Cisco Application Policy Infrastructure
Controller
Cisco Application Policy Infrastructure
Controller
Cisco Application Policy Infrastructure
Controller
Cisco Application Policy Infrastructure
Controller
Cisco Application Policy Infrastructure
Controller
Cisco Application Policy Infrastructure
Controller
Cisco Application Policy Infrastructure
Controller
Cisco Application Policy Infrastructure
Controller
Cisco Application Policy Infrastructure
Controller
Cisco Application Policy Infrastructure
Controller
Cisco UCS Director
Cisco UCS Director
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
113
Cisco UCS Director Use Case Example #2: Enable Tenant Infrastructure for Guest Attached iSCSI
User Perspective
This specific workflow, as configured below, should be executed from the perspective of the
infrastructure administrator, typically a user with the system admin or other comparable user role in UCS
Director. In this use case, this workflow is not configured for publication to, and execution from an
end-user or tenant perspective.
Prerequisites
This section details the specific prerequisites that must be in place and configured prior to building and
executing the UCS Director workflow for this specific use case.
•
FlexPod withACI configuration in place and operational as per the Cisco CVD Deployment Guide.
•
UCS Director initial deployment must be performed. The required procedure can be found in this
document in the UCS Director Initial Deployment section.
•
UCS Director extended deployment for FlexPod must be performed. This configuration pertains to
specific steps that must be in place regarding managing a FlexPod within UCS Director. The
required procedure can be found in this document in the UCS Director Extended Deployment for
FlexPod with ACI section.
•
Use-case example #1 (above) workflow to create a new Tenant must be configured and have been
executed, resulting in one ore more existing Tenants within the infrastructure. Use-case example #2
will build upon Use-case example #1.
Detailed Workflow Configuration
Create a New Workflow
To create a new workflow, complete the following steps:
1.
In UCS Director, navigate to Policies'Orchestration and then select the Workflows tab.
2.
Click the Add Workflow button to create a new workflow. Optionally use the Import button to
import the published version of this workflow as apposed to building from scratch. This procedure
continues assuming creating a new workflow.
3.
Provide a Workflow Name.
4.
Optionally provide a Description.
5.
Set Workflow Context to Any.
6.
Optionally select Save as Compound Task. This option will add this specific workflow as a task in
the task library therefore enabling this workflow to be nested in other workflows as a task.
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
114
Cisco UCS Director Use Case Example #2: Enable Tenant Infrastructure for Guest Attached iSCSI
7.
Under Save Options, choose an existing folder in the Select Folder dropdown menu, or choose Place
in New Folder and provide the name of the new folder.
8.
Select any optional Notifications options to notify users of workflow execution status.
9.
Click Next.
10. On the Add User Inputs page, this is where we create the form that will be presented to each user
when the workflow is executed. This form can prompt the user for specific information that can then
be mapped to task inputs throughout the workflow. The table below provides information on the
User Inputs defined for this specific use case.
11. Click Next.
12. Click Submit.
Workflow User Inputs
This information can be provided when creating a new workflow on the Add User Inputs page, as seen
in the procedure above, or items can be added as workflow user inputs as tasks are added to the
workflow. On the User Input Mapping page of each task (after it is dragged into the workflow from the
task library), there is an Edit Workflow Properties button at the top of the page. This button can be used
at any time to add additional user inputs. To reiterate, these are the items that the user will be prompted
for each time the workflow is executed. This information is then generally mapped to the appropriate
task or tasks throughout the workflow for various task inputs.
Table 5 lists the User Inputs that are collected from the user each time this specific workflow is executed.
This list is provided simply as an example. Specific customer requirements may require a larger or small
number of User Inputs. This list can be customized as needed, however the information below is what
is required to fulfill this use-case as is highlighted in this document.
Table 5
Input Label
User Group
Tenant SVN
APIC Tenant
APIC Tenant
Private
Network
Tenant Name
Tenant Service
Offering
Tenant Profile
User Inputs
Input
Description
Mandator
y
Yes
Yes
Yes
Yes
Type
userGroup
netappClusterVServerIdentity
ApicDeviceTenantIdentity
ApicDeviceTenantPrivateNetworkIdentit
y
Yes
Yes
gen_text_input
ServiceOfferingName
Yes
rgTenantProfileIdentity
Admin Input
Value
Workflow Tasks and Input/Output Mappings
This section provides information on the UCS Director tasks used to build an automated workflow for
executing this use case. Also Included is information regarding the order of operations (tasks) as well as
the mapping of inputs and outputs between tasks.
Get Info From Resource Group
Task Name from Task Library:
(drag and drop this task)
Tenant Onboarding Wrapper for FlexPod with ACI
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
115
Cisco UCS Director Use Case Example #2: Enable Tenant Infrastructure for Guest Attached iSCSI
Task Information
Field
Value
Task Name
Get_Info_From_Resource_Group
Task Category
Resource Group Tasks
Task Type
Tenant Onboarding Wrapper for FlexPod with ACI
Comment
Get Info From Resource Group
User Input Mapping
Input
Mapped



Tenant Name (Mandatory)
Tenant profile Name (Mandatory)
Service Offering (Mandatory)
Mapped Variable
Tenant Name
Tenant Profile
Tenant Service Offering
Datastore Size
Select Host/Cluster (Mandatory)
CPU Resource Reservation (MHz)
(Mandatory)
Memory Resource Reservation (MB)
(Mandatory)
Task Inputs
Input
Value
Datastore Size
0
Select Host/Cluster
Cluster
CPU Resource Reservation (MHz)
0
Memory Resource Reservation (MB)
0
Get Tenant iSCSI_A VLAN
Task Name from Task Library:
(drag and drop this task)
Generate VLAN from pool
Task Information
Field
Value
Task Name
Get_Tenant_iSCSI_A_VLAN
Task Category
General Tasks
Task Type
Generate VLAN from pool
Comment
Get Tenant iSCSI_A VLAN
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
116
Cisco UCS Director Use Case Example #2: Enable Tenant Infrastructure for Guest Attached iSCSI
User Input Mapping
Input
VLAN Pool Policy (Mandatory)
Mapped

Mapped Variable
Get_Info_From_Resource_Group.ISCSI_A_VLAN_POOL_POLI
CY_NAME
Task Inputs
Input
Value
Get Tenant iSCSI_B VLAN
Task Name from Task Library:
(drag and drop this task)
Generate VLAN from pool
Task Information
Field
Value
Task Name
Get_Tenant_iSCSI_B_VLAN
Task Category
General Tasks
Task Type
Generate VLAN from pool
Comment
Get Tenant iSCSI_B VLAN
User Input Mapping
Input
VLAN Pool Policy (Mandatory)
Mapped

Mapped Variable
Get_Info_From_Resource_Group.ISCSI_B_VLAN_POOL_POLI
CY_NAME
Task Inputs
Input
Value
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
117
Cisco UCS Director Use Case Example #2: Enable Tenant Infrastructure for Guest Attached iSCSI
Reserve IP Address Subnet for iSCSI_A
Task Name from Task Library:
(drag and drop this task)
Get IP Subnet From IP Subnet Pool Policy
Task Information
Field
Value
Task Name
Reserve_iSCSI_A_IP_Subnet
Task Category
General Tasks
Task Type
Get IP From IP Subnet Pool Policy
Comment
Reserve iSCSI_A IP Subnet
User Input Mapping
Input
Mapped


IP Subnet Pool Policy (Mandatory)
User Group ID (Mandatory)
Mapped Variable
Get_Info_From_Resource_Group.OUTPUT_ISCSI_A_IP_SUBN
ET_POOL_POLICY
User Group
IP Subnet Label
Task Inputs
Input
Value
IP Subnet Label
iSCSI_A
Reserve IP Address Subnet for iSCSI_B
Task Name from Task Library:
(drag and drop this task)
Get IP Subnet From IP Subnet Pool Policy
Task Information
Field
Value
Task Name
Reserve_iSCSI_B_IP_Subnet
Task Category
General Tasks
Task Type
Get IP From IP Subnet Pool Policy
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
118
Cisco UCS Director Use Case Example #2: Enable Tenant Infrastructure for Guest Attached iSCSI
Comment
Reserve iSCSI_B IP Subnet
User Input Mapping
Input
IP Subnet Pool Policy (Mandatory)
User Group ID (Mandatory)
Mapped


Mapped Variable
Get_Info_From_Resource_Group.OUTPUT_ISCSI_A_IP_SUBN
ET_POOL_POLICY
User Group
IP Subnet Label
Task Inputs
Input
Value
IP Subnet Label
iSCSI_B
Create VLAN Interface for iSCSI_A on Node 1
Task Name from Task Library:
(drag and drop this task)
Create Cluster vLAN Interface
Task Information
Field
Value
Task Name
Create_VLAN_Interface_For_iSCSI_A_Node_1
Task Category
NetApp clustered Data ONTAP Tasks
Task Type
Create Cluster vLAN Interface
Comment
Create VLAN Interface For iSCSI_A Node 1
User Input Mapping
Input
Port Name (Mandatory)
VLAN ID
Mapped


Mapped Variable
Get_Info_From_Resource_Group.NETAPP_INTERFACEGROU
P_PRIMARY_NODE_PORT
Get_Tenant_iSCSI_A_VLAN.OUTPUT_VLAN_ID
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
119
Cisco UCS Director Use Case Example #2: Enable Tenant Infrastructure for Guest Attached iSCSI
Task Inputs
Input
Value
Create VLAN Interface for iSCSI_A on Node 2
Task Name from Task Library:
(drag and drop this task)
Create Cluster vLAN Interface
Task Information
Field
Value
Task Name
Create_VLAN_Interface_For_iSCSI_A_Node_2
Task Category
NetApp clustered Data ONTAP Tasks
Task Type
Create Cluster vLAN Interface
Comment
Create VLAN Interface For iSCSI_A Node 2
User Input Mapping
Input
Port Name (Mandatory)
VLAN ID
Mapped


Mapped Variable
Get_Info_From_Resource_Group.NETAPP_INTERFACEGROU
P_PARTNER_NODE_PORT
Get_Tenant_iSCSI_A_VLAN.OUTPUT_VLAN_ID
Task Inputs
Input
Value
Create VLAN Interface for iSCSI_B on Node 1
Task Name from Task Library:
(drag and drop this task)
Create Cluster vLAN Interface
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
120
Cisco UCS Director Use Case Example #2: Enable Tenant Infrastructure for Guest Attached iSCSI
Task Information
Field
Value
Task Name
Create_VLAN_Interface_For_iSCSI_B_Node_1
Task Category
NetApp clustered Data ONTAP Tasks
Task Type
Create Cluster vLAN Interface
Comment
Create VLAN Interface For iSCSI_B Node 1
User Input Mapping
Input
Port Name (Mandatory)
VLAN ID
Mapped


Mapped Variable
Get_Info_From_Resource_Group.NETAPP_INTERFACEGROU
P_PRIMARY_NODE_PORT
Get_Tenant_iSCSI_B_VLAN.OUTPUT_VLAN_ID
Task Inputs
Input
Value
Create VLAN Interface for iSCSI_B on Node 2
Task Name from Task Library:
(drag and drop this task)
Create Cluster vLAN Interface
Task Information
Field
Value
Task Name
Create_VLAN_Interface_For_iSCSI_B_Node_2
Task Category
NetApp clustered Data ONTAP Tasks
Task Type
Create Cluster vLAN Interface
Comment
Create VLAN Interface For iSCSI_B Node 2
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
121
Cisco UCS Director Use Case Example #2: Enable Tenant Infrastructure for Guest Attached iSCSI
User Input Mapping
Mapped
Input


Port Name (Mandatory)
VLAN ID
Mapped Variable
Get_Info_From_Resource_Group.NETAPP_INTERFACEGROU
P_PARTNER_NODE_PORT
Get_Tenant_iSCSI_B_VLAN.OUTPUT_VLAN_ID
Task Inputs
Input
Value
Get IP Address for iSCSI_A LIF From Subnet Node 1
Task Name from Task Library:
Get IP Address From IP Subnet
(drag and drop this task)
Task Information
Field
Value
Task Name
Get_iSCSI_A_LIF_IP_Address_From_Subnet_Node_1
Task Category
General Tasks
Task Type
Get IP Address From IP Subnet
Comment
Get iSCSI_A LIF IP Address From Subnet Node 1
User Input Mapping
Input
Mapped
User Group ID (Mandatory)
Mapped Variable

User Group

Reserve_iSCSI_A_IP_Subnet.OUTPUT_SUBNET_ID
IP Subnet Label
IP Subnet
Task Inputs
Input
Value
IP Subnet Label
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
122
Cisco UCS Director Use Case Example #2: Enable Tenant Infrastructure for Guest Attached iSCSI
Get IP Address for iSCSI_A LIF From Subnet Node 2
Task Name from Task Library:
Get IP Address From IP Subnet
(drag and drop this task)
Task Information
Field
Value
Task Name
Get_iSCSI_A_LIF_IP_Address_From_Subnet_Node_2
Task Category
General Tasks
Task Type
Get IP Address From IP Subnet
Comment
Get iSCSI_A LIF IP Address From Subnet Node 2
User Input Mapping
Input
Mapped
User Group ID (Mandatory)
Mapped Variable

User Group

Reserve_iSCSI_A_IP_Subnet.OUTPUT_SUBNET_ID
IP Subnet Label
IP Subnet
Task Inputs
Input
Value
IP Subnet Label
Get IP Address for iSCSI_B LIF From Subnet Node 1
Task Name from Task Library:
(drag and drop this task)
Get IP Address From IP Subnet
Task Information
Field
Value
Task Name
Get_iSCSI_B_LIF_IP_Address_From_Subnet_Node_1
Task Category
General Tasks
Task Type
Get IP Address From IP Subnet
Comment
Get iSCSI_B LIF IP Address From Subnet Node 1
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
123
Cisco UCS Director Use Case Example #2: Enable Tenant Infrastructure for Guest Attached iSCSI
User Input Mapping
Input
Mapped
User Group ID (Mandatory)
Mapped Variable

User Group

Reserve_iSCSI_B_IP_Subnet.OUTPUT_SUBNET_ID
IP Subnet Label
IP Subnet
Task Inputs
Input
Value
IP Subnet Label
Get IP Address for iSCSI_B LIF From Subnet Node 2
Task Name from Task Library:
Get IP Address From IP Subnet
(drag and drop this task)
Task Information
Field
Value
Task Name
Get_iSCSI_B_LIF_IP_Address_From_Subnet_Node_2
Task Category
General Tasks
Task Type
Get IP Address From IP Subnet
Comment
Get iSCSI_B LIF IP Address From Subnet Node 2
User Input Mapping
Input
Mapped
User Group ID (Mandatory)
Mapped Variable

User Group

Reserve_iSCSI_B_IP_Subnet.OUTPUT_SUBNET_ID
IP Subnet Label
IP Subnet
Task Inputs
Input
Value
IP Subnet Label
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
124
Cisco UCS Director Use Case Example #2: Enable Tenant Infrastructure for Guest Attached iSCSI
Create LIF for iSCSI_A on Node 1
Task Name from Task Library:
Create Cluster Logical Interface
(drag and drop this task)
Task Information
Field
Value
Task Name
Create_iSCSI_A_LIF_Node_1
Task Category
NetApp clustered Data ONTAP Tasks
Task Type
Create Cluster Logical Interface
Comment
Create iSCSI_A LIF Node 1
User Input Mapping
Input
Mapped
Mapped Variable
Role (Mandatory)
Home Node (Mandatory)


Home Port (Mandatory)

Vserver Name (Mandatory)
Tenant SVM
Get_Info_From_Resource_Group.NETAPP_NODE_IDENT
ITY
Create_VLAN_Interface_For_iSCSI_A_Node_1.OUTPUT_
CLUSTER_PORT_NAME
Logical Interface Name
IP Address

Subnetmask (Mandatory)

Get_iSCSI_A_LIF_IP_Address_From_Subnet_Node_1.IPA
ddress
Get_iSCSI_A_LIF_IP_Address_From_Subnet_Node_1.Sub
netMask
Failover Policy
Use Failover Group
Task Inputs
Input
Value
Role
Data
Allowed Protocols
iSCSI
Logical Interface Name
LIF_iSCSI_A_01
Failover Policy
disabled
Use Failover Group
disabled
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
125
Cisco UCS Director Use Case Example #2: Enable Tenant Infrastructure for Guest Attached iSCSI
Create LIF for iSCSI_A on Node 2
Task Name from Task Library:
Create Cluster Logical Interface
(drag and drop this task)
Task Information
Field
Value
Task Name
Create_iSCSI_A_LIF_Node_2
Task Category
NetApp clustered Data ONTAP Tasks
Task Type
Create Cluster Logical Interface
Comment
Create iSCSI_A LIF Node 2
User Input Mapping
Input
Mapped
Mapped Variable
Role (Mandatory)
Home Node (Mandatory)


Home Port (Mandatory)

Vserver Name (Mandatory)
Tenant SVM
Get_Info_From_Resource_Group.NETAPP_CLUSTER_PA
RTNER_NODE_IDENTITY
Create_VLAN_Interface_For_iSCSI_A_Node_2.OUTPUT_
CLUSTER_PORT_NAME
Logical Interface Name
IP Address

Subnetmask (Mandatory)

Get_iSCSI_A_LIF_IP_Address_From_Subnet_Node_2.IPA
ddress
Get_iSCSI_A_LIF_IP_Address_From_Subnet_Node_2.Sub
netMask
Failover Policy
Use Failover Group
Task Inputs
Input
Value
Role
Data
Allowed Protocols
iSCSI
Logical Interface Name
LIF_iSCSI_A_02
Failover Policy
disabled
Use Failover Group
disabled
Create LIF for iSCSI_B on Node 1
Task Name from Task Library:
(drag and drop this task)
Create Cluster Logical Interface
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
126
Cisco UCS Director Use Case Example #2: Enable Tenant Infrastructure for Guest Attached iSCSI
Task Information
Field
Value
Task Name
Create_iSCSI_B_LIF_Node_1
Task Category
NetApp clustered Data ONTAP Tasks
Task Type
Create Cluster Logical Interface
Comment
Create iSCSI_B LIF Node 1
User Input Mapping
Input
Mapped
Mapped Variable
Role (Mandatory)
Home Node (Mandatory)


Home Port (Mandatory)

Vserver Name (Mandatory)
Tenant SVM
Get_Info_From_Resource_Group.NETAPP_NODE_IDENT
ITY
Create_VLAN_Interface_For_iSCSI_B_Node_1.OUTPUT_
CLUSTER_PORT_NAME
Logical Interface Name
IP Address

Subnetmask (Mandatory)

Get_iSCSI_B_LIF_IP_Address_From_Subnet_Node_1.IPA
ddress
Get_iSCSI_B_LIF_IP_Address_From_Subnet_Node_1.Sub
netMask
Failover Policy
Use Failover Group
Task Inputs
Input
Value
Role
Data
Allowed Protocols
iSCSI
Logical Interface Name
LIF_iSCSI_B_01
Failover Policy
disabled
Use Failover Group
disabled
Create LIF for iSCSI_B on Node 2
Task Name from Task Library:
(drag and drop this task)
Create Cluster Logical Interface
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
127
Cisco UCS Director Use Case Example #2: Enable Tenant Infrastructure for Guest Attached iSCSI
Task Information
Field
Value
Task Name
Create_iSCSI_B_LIF_Node_2
Task Category
NetApp clustered Data ONTAP Tasks
Task Type
Create Cluster Logical Interface
Comment
Create iSCSI_B LIF Node 2
User Input Mapping
Input
Mapped
Mapped Variable
Role (Mandatory)
Home Node (Mandatory)


Home Port (Mandatory)

Vserver Name (Mandatory)
Tenant SVM
Get_Info_From_Resource_Group.NETAPP_CLUSTER_PA
RTNER_NODE_IDENTITY
Create_VLAN_Interface_For_iSCSI_B_Node_2.OUTPUT_
CLUSTER_PORT_NAME
Logical Interface Name
IP Address

Subnetmask (Mandatory)

Get_iSCSI_B_LIF_IP_Address_From_Subnet_Node_2.IPA
ddress
Get_iSCSI_B_LIF_IP_Address_From_Subnet_Node_2.Sub
netMask
Failover Policy
Use Failover Group
Task Inputs
Input
Value
Role
Data
Allowed Protocols
iSCSI
Logical Interface Name
LIF_iSCSI_B_02
Failover Policy
disabled
Use Failover Group
disabled
Enable iSCSI Protocol on Tenant SVM
Task Name from Task Library:
(drag and drop this task)
Create Cluster iSCSI Service
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
128
Cisco UCS Director Use Case Example #2: Enable Tenant Infrastructure for Guest Attached iSCSI
Task Information
Field
Value
Task Name
Enable_iSCSI_Protocol_On_Tenant_SVM
Task Category
NetApp clustered Data ONTAP Tasks
Task Type
Modify Cluster Vserver
Comment
Enable iSCSI Protocol On Tenant SVM
User Input Mapping
Input
Mapped

Vserver Name (Mandatory)
Mapped Variable
Tenant SVM
Name Mapping Switch
Max. Volume Limit
Aggregate List
Snapshot Policy
Protocols
Task Inputs
Input
Value
Name Service Switch
file
Name Mapping Switch
file
Max. Volume Limit
Aggregate List
Snapshot Policy
Protocols
NFS, iSCSI
Create iSCSI Service on Tenant SVM
Task Name from Task Library:
(drag and drop this task)
Create Cluster iSCSI Service
Task Information
Field
Value
Task Name
Create_SVM_iSCSI_Service
Task Category
NetApp clustered Data ONTAP Tasks
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
129
Cisco UCS Director Use Case Example #2: Enable Tenant Infrastructure for Guest Attached iSCSI
Task Type
Create Cluster iSCSI Service
Comment
Create SVM iSCSI Service
User Input Mapping
Input
Mapped

Vserver Name (Mandatory)
Mapped Variable
Tenant SVM
Alias Name
ISCSI Target Node Name
Start
Task Inputs
Input
Value
Alias Name
ISCSI Target Node Name
Create Tenant iSCSI_A Bridge Domain
Task Name from Task Library:
(drag and drop this task)
Create Tenant Bridge Domain
Task Information
Field
Value
Task Name
Create_Tenant_iSCSI_A_Bridge_Domain
Task Category
Cisco APIC Tasks
Task Type
Create Tenant Bridge Domain
Comment
Create Tenant iSCSI_A Bridge Domain
User Input Mapping
Input
Tenant Name (Mandatory)
Mapped
Mapped Variable

APIC Tenant

APIC Tenant Private Network
Bridge Domain Name (Mandatory)
Description
Network
Forwarding
L2 Unknown Unicast
Unknown Multicast Flooding
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
130
Cisco UCS Director Use Case Example #2: Enable Tenant Infrastructure for Guest Attached iSCSI
MacAddress
IGMP Snoop Policy
Associated L3 Out
L3 Out for Route Profile
Monitoring Policy
Task Inputs
Input
Value
Bridge Domain Name
bd-iSCSI_A
Description
Forwarding
Customize
L2 Unknown Unicast
Unknown Multicast
Flooding
ARP Flooding
Flood
Unicast Routing
Flood


Custom MacAddress
IGMP Snoop Policy
default
Associated L3 Out
L3 Out for Route Profile
Monitoring Policy
Create Tenant iSCSI_B Bridge Domain
Task Name from Task Library:
(drag and drop this task)
Create Tenant Bridge Domain
Task Information
Field
Value
Task Name
Create_Tenant_iSCSI_B_Bridge_Domain
Task Category
Cisco APIC Tasks
Task Type
Create Tenant Bridge Domain
Comment
Create Tenant iSCSI_B Bridge Domain
User Input Mapping
Input
Tenant Name (Mandatory)
Mapped

Mapped Variable
APIC Tenant
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
131
Cisco UCS Director Use Case Example #2: Enable Tenant Infrastructure for Guest Attached iSCSI
Bridge Domain Name (Mandatory)
Description

Network
APIC Tenant Private Network
Forwarding
L2 Unknown Unicast
Unknown Multicast Flooding
MacAddress
IGMP Snoop Policy
Associated L3 Out
L3 Out for Route Profile
Monitoring Policy
Task Inputs
Input
Value
Bridge Domain Name
bd-iSCSI_B
Description
Forwarding
Customize
L2 Unknown Unicast
Unknown Multicast
Flooding
ARP Flooding
Flood
Unicast Routing
Flood


Custom MacAddress
IGMP Snoop Policy
default
Associated L3 Out
L3 Out for Route Profile
Monitoring Policy
Create Tenant iSCSI_A Application Profile
Task Name from Task Library:
(drag and drop this task)
Create Tenant Application Profile
Task Information
Field
Value
Task Name
Create_Tenant_iSCSI_A_Application_Profile
Task Category
Cisco APIC Tasks
Task Type
Create Tenant Application Profile
Comment
Create Tenant iSCSI_A Application Profile
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
132
Cisco UCS Director Use Case Example #2: Enable Tenant Infrastructure for Guest Attached iSCSI
User Input Mapping
Input
Mapped

Tenant Name (Mandatory)
Mapped Variable
APIC Tenant
Application Profile (Mandatory)
Description
Alias
Tags
QoS
Monitoring Policy
Task Inputs
Input
Value
Application Profile
iSCSI_A
Description
Alias
Tags
QoS
unspecified
Monitoring Policy
default
Create Tenant iSCSI_B Application Profile
Task Name from Task Library:
(drag and drop this task)
Create Tenant Application Profile
Task Information
Field
Value
Task Name
Create_Tenant_iSCSI_B_Application_Profile
Task Category
Cisco APIC Tasks
Task Type
Create Tenant Application Profile
Comment
Create Tenant iSCSI_B Application Profile
User Input Mapping
Input
Tenant Name (Mandatory)
Mapped

Mapped Variable
APIC Tenant
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
133
Cisco UCS Director Use Case Example #2: Enable Tenant Infrastructure for Guest Attached iSCSI
Application Profile (Mandatory)
Description
Alias
Tags
QoS
Monitoring Policy
Task Inputs
Input
Value
Application Profile
iSCSI_B
Description
Alias
Tags
QoS
unspecified
Monitoring Policy
default
Create Tenant LIF iSCSI_A EPG
Task Name from Task Library:
(drag and drop this task)
Create EPG
Task Information
Field
Value
Task Name
Create_LIF_iSCSI_A_EPG
Task Category
Cisco APIC Tasks
Task Type
Create EPG
Comment
Create LIF iSCSI_A EPG
User Input Mapping
Input
Application Profile Name (Mandatory)
Mapped

Mapped Variable
Create_Tenant_iSCSI_A_Application_Profile.TENANT_A
PPLN_PROFILE_IDENTITY
EPG Name
EPG Description
Alias
Tags
QoS Class
Custom QoS
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
134
Cisco UCS Director Use Case Example #2: Enable Tenant Infrastructure for Guest Attached iSCSI

Bridge Domain
Create_Tenant_iSCSI_A_Bridge_Domain.TENANT_BRID
GE_DOMAIN_IDENTITY
Monitoring Policy
Task Inputs
Input
Value
EPG Name
LIF_iSCSI_A
EGP Description
Alias
Tags
QoS
unspecified
Custom QoS
Monitoring Policy
default
Create Tenant LIF iSCSI_B EPG
Task Name from Task Library:
(drag and drop this task)
Create EPG
Task Information
Field
Value
Task Name
Create_LIF_iSCSI_B_EPG
Task Category
Cisco APIC Tasks
Task Type
Create EPG
Comment
Create LIF iSCSI_B EPG
User Input Mapping
Input
Application Profile Name (Mandatory)
Mapped

Mapped Variable
Create_Tenant_iSCSI_B_Application_Profile.TENANT_AP
PLN_PROFILE_IDENTITY

Create_Tenant_iSCSI_B_Bridge_Domain.TENANT_BRID
GE_DOMAIN_IDENTITY
EPG Name
EPG Description
Alias
Tags
QoS Class
Custom QoS
Bridge Domain
Monitoring Policy
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
135
Cisco UCS Director Use Case Example #2: Enable Tenant Infrastructure for Guest Attached iSCSI
Task Inputs
Input
Value
EPG Name
LIF_iSCSI_B
EGP Description
Alias
Tags
QoS
unspecified
Custom QoS
Monitoring Policy
default
Create Tenant VM iSCSI_A EPG
Task Name from Task Library:
(drag and drop this task)
Create EPG
Task Information
Field
Value
Task Name
Create_VM_iSCSI_A_EPG
Task Category
Cisco APIC Tasks
Task Type
Create EPG
Comment
Create VM iSCSI_A EPG
User Input Mapping
Input
Application Profile Name (Mandatory)
Mapped

Mapped Variable
Create_Tenant_iSCSI_A_Application_Profile.TENANT_A
PPLN_PROFILE_IDENTITY

Create_Tenant_iSCSI_A_Bridge_Domain.TENANT_BRID
GE_DOMAIN_IDENTITY
EPG Name
EPG Description
Alias
Tags
QoS Class
Custom QoS
Bridge Domain
Monitoring Policy
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
136
Cisco UCS Director Use Case Example #2: Enable Tenant Infrastructure for Guest Attached iSCSI
Task Inputs
Input
Value
EPG Name
VM_iSCSI_A
EGP Description
Alias
Tags
QoS
unspecified
Custom QoS
Monitoring Policy
default
Create Tenant VM iSCSI_B EPG
Task Name from Task Library:
(drag and drop this task)
Create EPG
Task Information
Field
Value
Task Name
Create_VM_iSCSI_B_EPG
Task Category
Cisco APIC Tasks
Task Type
Create EPG
Comment
Create VM iSCSI_B EPG
User Input Mapping
Input
Application Profile Name (Mandatory)
Mapped

Mapped Variable
Create_Tenant_iSCSI_B_Application_Profile.TENANT_AP
PLN_PROFILE_IDENTITY

Create_Tenant_iSCSI_B_Bridge_Domain.TENANT_BRID
GE_DOMAIN_IDENTITY
EPG Name
EPG Description
Alias
Tags
QoS Class
Custom QoS
Bridge Domain
Monitoring Policy
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
137
Cisco UCS Director Use Case Example #2: Enable Tenant Infrastructure for Guest Attached iSCSI
Task Inputs
Input
Value
EPG Name
VM_iSCSI_B
EGP Description
Alias
Tags
QoS
unspecified
Custom QoS
Monitoring Policy
default
Add iSCSI_A VLAN to VLAN Pool
Task Name from Task Library:
Add VLAN Range To VLAN Pool
(drag and drop this task)
Task Information
Field
Value
Task Name
Add_iSCSI_A_VLAN_To_VLAN_Pool
Task Category
Cisco APIC Tasks
Task Type
Add VLAN Range To VLAN Pool
Comment
Add iSCSI_A VLAN To VLAN Pool
User Input Mapping
Input
Mapped



VLAN Pool Name (Mandatory)
Range From (Mandatory)
Range To (Mandatory)
Mapped Variable
Get_Info_From_Resource_Group.OUTPUT_APIC_VLAN_
POOL_NODE1
Get_Tenant_iSCSI_A_VLAN.OUTPUT_VLAN_ID
Get_Tenant_iSCSI_A_VLAN.OUTPUT_VLAN_ID
Task Inputs
Input
Value
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
138
Cisco UCS Director Use Case Example #2: Enable Tenant Infrastructure for Guest Attached iSCSI
Add iSCSI_B VLAN to VLAN Pool
Task Name from Task Library:
Add VLAN Range To VLAN Pool
(drag and drop this task)
Task Information
Field
Value
Task Name
Add_iSCSI_B_VLAN_To_VLAN_Pool
Task Category
Cisco APIC Tasks
Task Type
Add VLAN Range To VLAN Pool
Comment
Add iSCSI_B VLAN To VLAN Pool
User Input Mapping
Input
Mapped



VLAN Pool Name (Mandatory)
Range From (Mandatory)
Range To (Mandatory)
Mapped Variable
Get_Info_From_Resource_Group.OUTPUT_APIC_VLAN_
POOL_NODE2
Get_Tenant_iSCSI_B_VLAN.OUTPUT_VLAN_ID
Get_Tenant_iSCSI_B_VLAN.OUTPUT_VLAN_ID
Task Inputs
Input
Value
Add Static Path to LIF iSCSI_A EPG
Task Name from Task Library:
(drag and drop this task)
Add Static Path to EPG
Task Information
Field
Value
Task Name
Add_Static_Path_to_LIF_iSCSI_A_EPG
Task Category
Cisco APIC Tasks
Task Type
Add Static Path To EPG
Comment
Add Static Path to LIF iSCSI_A EPG
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
139
Cisco UCS Director Use Case Example #2: Enable Tenant Infrastructure for Guest Attached iSCSI
User Input Mapping
Input
Mapped
EPG (Mandatory)
Mapped Variable

Create_LIF_iSCSI_A_EPG.TENANT_EPG_IDENTITY


Get_Info_From_Resource_Group.vPC_STATIC_PATH_FO
R_NODE1
Get_Tenant_iSCSI_A_VLAN.OUTPUT_VLAN_ID
Path Type (Mandatory)
Path (Mandatory)
Encapsulation (Mandatory)
Deployment Immediacy (Mandatory)
Mode (Mandatory)
Task Inputs
Input
Value
Path Type
Virtual Port Channel
Deployment Immediacy
immediate
Mode
Tagged
Add Static Path to LIF iSCSI_B EPG
Task Name from Task Library:
(drag and drop this task)
Add Static Path to EPG
Task Information
Field
Value
Task Name
Add_Static_Path_to_LIF_iSCSI_B_EPG
Task Category
Cisco APIC Tasks
Task Type
Add Static Path To EPG
Comment
Add Static Path to LIF iSCSI_B EPG
User Input Mapping
Input
EPG (Mandatory)
Mapped
Mapped Variable

Create_LIF_iSCSI_B_EPG.TENANT_EPG_IDENTITY


Get_Info_From_Resource_Group.vPC_STATIC_PATH_FO
R_NODE2
Get_Tenant_iSCSI_B_VLAN.OUTPUT_VLAN_ID
Path Type (Mandatory)
Path (Mandatory)
Encapsulation (Mandatory)
Deployment Immediacy (Mandatory)
Mode (Mandatory)
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
140
Cisco UCS Director Use Case Example #2: Enable Tenant Infrastructure for Guest Attached iSCSI
Task Inputs
Input
Value
Path Type
Virtual Port Channel
Deployment Immediacy
immediate
Mode
Tagged
Add VMM Domain to VM iSCSI_A EPG
Task Name from Task Library:
Add Domain to EPG
(drag and drop this task)
Task Information
Field
Value
Task Name
Add_VMM_Domain_to_VM_iSCSI_A_EPG
Task Category
Cisco APIC Tasks
Task Type
Add Domain To EPG
Comment
Add VMM Domain to VM iSCSI_A EPG
User Input Mapping
Input
Mapped


EPG (Mandatory)
Domain Profile (Mandatory)
Mapped Variable
Create_VM_iSCSI_A_EPG.TENANT_EPG_IDENTITY
Get_Info_From_Resource_Group.VMM_DOMAIN_PROFI
LE_IDENTITY
Deploy Immediacy
Resolution Immediacy
Task Inputs
Input
Value
Deploy Immediacy
immediate
Resolution Immediacy
immediate
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
141
Cisco UCS Director Use Case Example #2: Enable Tenant Infrastructure for Guest Attached iSCSI
Add VMM Domain to VM iSCSI_B EPG
Task Name from Task Library:
Add Domain to EPG
(drag and drop this task)
Task Information
Field
Value
Task Name
Add_VMM_Domain_to_VM_iSCSI_B_EPG
Task Category
Cisco APIC Tasks
Task Type
Add Domain To EPG
Comment
Add VMM Domain to VM iSCSI_B EPG
User Input Mapping
Input
Mapped
Mapped Variable


EPG (Mandatory)
Domain Profile (Mandatory)
Create_VM_iSCSI_B_EPG.TENANT_EPG_IDENTITY
Get_Info_From_Resource_Group.VMM_DOMAIN_PROFI
LE_IDENTITY
Deploy Immediacy
Resolution Immediacy
Task Inputs
Input
Value
Deploy Immediacy
immediate
Resolution Immediacy
immediate
Create Contract for iSCSI_A
Task Name from Task Library:
(drag and drop this task)
Create Contract
Task Information
Field
Value
Task Name
Create_Tenant_iSCSI_A_Contract
Task Category
Cisco APIC Tasks
Task Type
Create Contract
Comment
Create Tenant iSCSI_A Contract
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
142
Cisco UCS Director Use Case Example #2: Enable Tenant Infrastructure for Guest Attached iSCSI
User Input Mapping
Input
Mapped
Mapped Variable

Tenant Name (Mandatory)
APIC Tenant
Contract Name
Contract Description
Scope (Mandatory)
Priority (Mandatory)
Task Inputs
Input
Value
Contract Name
iSCSI_A
Contract Description
Scope
application-profile
Priority
unspecified
Create Contract for iSCSI_B
Task Name from Task Library:
(drag and drop this task)
Create Contract
Task Information
Field
Value
Task Name
Create_Tenant_iSCSI_B_Contract
Task Category
Cisco APIC Tasks
Task Type
Create Contract
Comment
Create Tenant iSCSI_B Contract
User Input Mapping
Input
Tenant Name (Mandatory)
Mapped

Mapped Variable
APIC Tenant
Contract Name
Contract Description
Scope (Mandatory)
Priority (Mandatory)
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
143
Cisco UCS Director Use Case Example #2: Enable Tenant Infrastructure for Guest Attached iSCSI
Task Inputs
Input
Value
Contract Name
iSCSI_B
Contract Description
Scope
application-profile
Priority
unspecified
Create Contract Subject for iSCSI_A
Task Name from Task Library:
(drag and drop this task)
Create Contract Subject
Task Information
Field
Value
Task Name
Create_Tenant_iSCSI_A_Contract_Subject
Task Category
Cisco APIC Tasks
Task Type
Create Contract Subject
Comment
Create Tenant iSCSI_A Contract Subject
User Input Mapping
Input
Contract Name (Mandatory)
Mapped

Mapped Variable
Create_Tenant_iSCSI_A_Contract.TENANT_CONTRACT
_IDENTITY
Type
Contract Subject Name (Mandatory)
Contract Subject Description
Reverse Filter Ports
Apply Both Directions
Service Graph
QoS
In Term Service Graph
In Term QoS
Out Term Service Graph
Out Term QoS
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
144
Cisco UCS Director Use Case Example #2: Enable Tenant Infrastructure for Guest Attached iSCSI
Task Inputs
Input
Value
Type
Normal
Contract Subject Name
iSCSI_A
Contract Subject Description
Reverse Filter Ports
Apply Both Directions


Service Graph
QoS
unspecified
Create Contract Subject for iSCSI_B
Task Name from Task Library:
(drag and drop this task)
Create Contract Subject
Task Information
Field
Value
Task Name
Create_Tenant_iSCSI_B_Contract_Subject
Task Category
Cisco APIC Tasks
Task Type
Create Contract Subject
Comment
Create Tenant iSCSI_B Contract Subject
User Input Mapping
Input
Contract Name (Mandatory)
Mapped

Mapped Variable
Create_Tenant_iSCSI_B_Contract.TENANT_CONTRACT
_IDENTITY
Type
Contract Subject Name (Mandatory)
Contract Subject Description
Reverse Filter Ports
Apply Both Directions
Service Graph
QoS
In Term Service Graph
In Term QoS
Out Term Service Graph
Out Term QoS
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
145
Cisco UCS Director Use Case Example #2: Enable Tenant Infrastructure for Guest Attached iSCSI
Task Inputs
Input
Value
Type
Normal
Contract Subject Name
iSCSI_B
Contract Subject Description
Reverse Filter Ports
Apply Both Directions


Service Graph
QoS
unspecified
Create iSCSI Contract Filter
Task Name from Task Library:
Create Tenant Filter
(drag and drop this task)
Task Information
Field
Value
Task Name
Create_iSCSI_Contract_Filter
Task Category
Cisco APIC Tasks
Task Type
Create Tenant Filter
Comment
Create iSCSI Contract Filter
User Input Mapping
Input
Mapped

Tenant Name (Mandatory)
Mapped Variable
APIC Tenant
Filter Name (Mandatory)
Description
Task Inputs
Input
Value
Filter Name
Allow_iSCSI
Description
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
146
Cisco UCS Director Use Case Example #2: Enable Tenant Infrastructure for Guest Attached iSCSI
Create iSCSI Contract Filter Rule
Task Name from Task Library:
Create Tenant Filter Rule
(drag and drop this task)
Task Information
Field
Value
Task Name
Create_iSCSI_Contract_Filter_Rule
Task Category
Cisco APIC Tasks
Task Type
Create Tenant Filter Rule
Comment
Create iSCSI Contract Filter Rule
User Input Mapping
Input
Mapped

Filter Name (Mandatory)
Mapped Variable
Create_iSCSI_Contract_Filter.TENANT_FILTER_IDENTI
TY
Filter Rule Name (Mandatory)
Description
Ethernet Type (Mandatory)
ARP Flag
IP Protocol
Source Port Start
Source Port Start Custom (Mandatory)
Source Port End
Source Port End Custom (Mandatory)
Destination Port Start
Destination Port Start Custom (Mandatory)
Destination Port End
Destination Port End Custom (Mandatory)
Task Inputs
Input
Value
Filter Rule Name
tcp_3260
Description
Ethernet Type
IP
ARP Flag
UNSPECIFIED
IP Protocol
TCP
Allow Fragment
Source Port Start
UNSPECIFIED
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
147
Cisco UCS Director Use Case Example #2: Enable Tenant Infrastructure for Guest Attached iSCSI
Source Port End
UNSPECIFIED
Destination Port Start
Destination Port Start
Custom
Destination Port End
Destination Port End
Custom
TCP Session Rule
CUSTOM
3260
CUSTOM
3260
Unspecified
Add iSCSI Filter to iSCSI_A Contract Subject
Task Name from Task Library:
Add Filter To Contract Subject
(drag and drop this task)
Task Information
Field
Value
Task Name
Add_iSCSI_Filter_to_iSCSI_A_Contract_Subject
Task Category
Cisco APIC Tasks
Task Type
Add Filter To Contract Subject
Comment
Add iSCSI Filter to iSCSI_A Contract Subject
User Input Mapping
Input
Mapped
Contract Subject (Mandatory)

Filter (Mandatory)

Mapped Variable
Create_Tenant_iSCSI_A_Contract_Subject.TENANT_CON
TRACT_SUBJECT_IDENTITY
Create_iSCSI_Contract_Filter.TENANT_FILTER_IDENTI
TY
Filter For Consumer To Provider
Filter For Provider To Consumer
Task Inputs
Input
Value
Apply Both Directions

Add iSCSI Filter to iSCSI_B Contract Subject
Task Name from Task Library:
(drag and drop this task)
Add Filter To Contract Subject
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
148
Cisco UCS Director Use Case Example #2: Enable Tenant Infrastructure for Guest Attached iSCSI
Task Information
Field
Value
Task Name
Add_iSCSI_Filter_to_iSCSI_B_Contract_Subject
Task Category
Cisco APIC Tasks
Task Type
Add Filter To Contract Subject
Comment
Add iSCSI Filter to iSCSI_B Contract Subject
User Input Mapping
Input
Mapped
Contract Subject (Mandatory)

Filter (Mandatory)

Mapped Variable
Create_Tenant_iSCSI_B_Contract_Subject.TENANT_CON
TRACT_SUBJECT_IDENTITY
Create_iSCSI_Contract_Filter.TENANT_FILTER_IDENTI
TY
Filter For Consumer To Provider
Filter For Provider To Consumer
Task Inputs
Input
Value
Apply Both Directions

Add iSCSI_A Contract to LIF iSCSI_A EPG
Task Name from Task Library:
(drag and drop this task)
Add Contract To EPG
Task Information
Field
Value
Task Name
Add_iSCSI_A_Contract_to_LIF_iSCSI_A_EPG
Task Category
Cisco APIC Tasks
Task Type
Add Contract To EPG
Comment
Add iSCSI_A Contract to LIF iSCSI_A EPG
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
149
Cisco UCS Director Use Case Example #2: Enable Tenant Infrastructure for Guest Attached iSCSI
User Input Mapping
Input
Mapped
EPG (Mandatory)
Mapped Variable

Create_LIF_iSCSI_A_EPG.TENANT_EPG_IDENTITY

Create_Tenant_iSCSI_A_Contract.TENANT_CONTRACT
_IDENTITY
Contract Type (Mandatory)
Contract (Mandatory)
QoS (Mandatory)
Task Inputs
Input
Value
Contract Type
Provided Contract
QoS
unspecified
Add iSCSI_A Contract to VM iSCSI_A EPG
Task Name from Task Library:
(drag and drop this task)
Add Contract To EPG
Task Information
Field
Value
Task Name
Add_iSCSI_A_Contract_to_VM_iSCSI_A_EPG
Task Category
Cisco APIC Tasks
Task Type
Add Contract To EPG
Comment
Add iSCSI_A Contract to VM iSCSI_A EPG
User Input Mapping
Input
EPG (Mandatory)
Mapped
Mapped Variable

Create_VM_iSCSI_A_EPG.TENANT_EPG_IDENTITY

Create_Tenant_iSCSI_A_Contract.TENANT_CONTRACT
_IDENTITY
Contract Type (Mandatory)
Contract (Mandatory)
QoS (Mandatory)
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
150
Cisco UCS Director Use Case Example #2: Enable Tenant Infrastructure for Guest Attached iSCSI
Task Inputs
Input
Value
Contract Type
Consumed Contract
QoS
unspecified
Add iSCSI_B Contract to LIF iSCSI_B EPG
Task Name from Task Library:
Add Contract To EPG
(drag and drop this task)
Task Information
Field
Value
Task Name
Add_iSCSI_B_Contract_to_LIF_iSCSI_B_EPG
Task Category
Cisco APIC Tasks
Task Type
Add Contract To EPG
Comment
Add iSCSI_B Contract to LIF iSCSI_B EPG
User Input Mapping
Input
Mapped
EPG (Mandatory)
Mapped Variable

Create_LIF_iSCSI_B_EPG.TENANT_EPG_IDENTITY

Create_Tenant_iSCSI_B_Contract.TENANT_CONTRACT
_IDENTITY
Contract Type (Mandatory)
Contract (Mandatory)
QoS (Mandatory)
Task Inputs
Input
Value
Contract Type
Provided Contract
QoS
unspecified
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
151
Cisco UCS Director Use Case Example #2: Enable Tenant Infrastructure for Guest Attached iSCSI
Add iSCSI_B Contract to VM iSCSI_B EPG
Task Name from Task Library:
Add Contract To EPG
(drag and drop this task)
Task Information
Field
Value
Task Name
Add_iSCSI_B_Contract_to_VM_iSCSI_B_EPG
Task Category
Cisco APIC Tasks
Task Type
Add Contract To EPG
Comment
Add iSCSI_B Contract to VM iSCSI_B EPG
User Input Mapping
Input
Mapped
EPG (Mandatory)
Mapped Variable

Create_VM_iSCSI_B_EPG.TENANT_EPG_IDENTITY

Create_Tenant_iSCSI_B_Contract.TENANT_CONTRACT
_IDENTITY
Contract Type (Mandatory)
Contract (Mandatory)
QoS (Mandatory)
Task Inputs
Input
Value
Contract Type
Consumed Contract
QoS
unspecified
Assign iSCSI_A Distributed Port Group to Group
Task Name from Task Library:
(drag and drop this task)
Assign DV Port Group to Group
Task Information
Field
Value
Task Name
Assign_iSCSI_A_Distributed_Port_Group_to_Group
Task Category
VMware Network Tasks
Task Type
Assign DV Port Group to Group
Comment
Assign iSCSI_A Distributed Port Group to Group
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
152
Cisco UCS Director Use Case Example #2: Enable Tenant Infrastructure for Guest Attached iSCSI
User Input Mapping
Input
Mapped
dvPortGroup Name (Mandatory)
User Group ID (Mandatory)


Mapped Variable
Add_VMM_Domain_to_VM_iSCSI_A_EPG.VMWARE_D
VSWITCH_PORTGROUP_IDENTITY
User Group
Task Inputs
Input
Value
Assign To Users

Assign iSCSI_B Distributed Port Group to Group
Task Name from Task Library:
Assign DV Port Group to Group
(drag and drop this task)
Task Information
Field
Value
Task Name
Assign_iSCSI_B_Distributed_Port_Group_to_Group
Task Category
VMware Network Tasks
Task Type
Assign DV Port Group to Group
Comment
Assign iSCSI_B Distributed Port Group to Group
User Input Mapping
Input
Mapped
dvPortGroup Name (Mandatory)
User Group ID (Mandatory)


Mapped Variable
Add_VMM_Domain_to_VM_iSCSI_B_EPG.VMWARE_D
VSWITCH_PORTGROUP_IDENTITY
User Group
Task Inputs
Input
Value
Assign To Users

FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
153
Cisco UCS Director Use Case Example #3: Enable Tenant Virtual Machine Provisioning
Cisco UCS Director Use Case Example #3: Enable Tenant
Virtual Machine Provisioning
Overview
This use case covers the self-service ability of tenant users to provision virtual machines from their
individual end-user portal. As part of this use case, the system administrator configures VM provisioning
capability for a specific tenant and then publishes that capability to the tenant user group. The prior use
cases illustrate the provisioning of a secure, dedicated tenant vSphere datastore hosted within the
tenant's NetApp SVM and attached with dedicated storage networking. In this configuration, any VM
provisioned on behalf of the tenant will be placed in this secure datastore, and its storage networking
will also be securely separated from other tenant environments.
User Perspective
The specific use case configured as follows spans two different user perspectives. First, the
infrastructure administrator or system administrator completes the following procedures to enable VM
provisioning for a specific tenant. At that point, tenant users can access their specific end-user portal and
execute the capabilities (VM provisioning) that have been published to them by the infrastructure
administrator.
Prerequisites
•
FlexPod with ACI configuration must be in place and operational in accordance with the Cisco CVD
Deployment Guide.
•
You must perform the initial deployment of UCS Director. The required procedure can be found in
the section UCS Director Initial Deployment.
•
You must perform UCS Director extended deployment for FlexPod. This configuration contains
specific steps to manage a FlexPod system within UCS Director. The procedure can be found in the
section UCS Director Extended Deployment for FlexPod with ACI.
•
You must configure and execute the use case example #1 workflow to create a new tenant, resulting
in one or more existing tenants within the infrastructure. Use case example #2 builds upon use case
example #1.
Create Tenant IP Pool For Virtual Machines
To create a tenant IP pool for virtual machines, complete the following steps:
1.
In UCS Director, navigate to Policies'Virtual/Hypervisor Policies'Network and then select the Static
IP Pool Policy tab.
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
154
Cisco UCS Director Use Case Example #3: Enable Tenant Virtual Machine Provisioning
2.
Click Add.
3.
On the Static IP Policy Information page, provide a Policy Name, optional Policy Description and
use the green plus icon to add one or more IP ranges into the static IP Pool policy. This IP Pool
Policy will be specific to this tenant and will be used to reserve IP addresses for this tenant's VMs
on the tenant VMNET network.
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
155
Cisco UCS Director Use Case Example #3: Enable Tenant Virtual Machine Provisioning
4.
Click Submit.
Configure Tenant VMNET Gateway IP Address
In order for tenant VM traffic on the VMNET network (VMNET EPG) to be potentially connected to
other EPGs, for example the tenant SVM_MGMT EPG or possibly even a layer3 boundary outside of
the ACI environment, an APIC subnet (Gateway IP Address) must be created.
To set the APIC subnet (Gateway IP Address) on the tenant VMNET EPG, complete the following steps:
1.
In the Cisco Application Policy Infrastructure Controller (APIC), navigate to the Tenants tab, select
ALL Tenants in the upper left corner and then double-click the appropriate tenant.
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
156
Cisco UCS Director Use Case Example #3: Enable Tenant Virtual Machine Provisioning
2.
When the tenant specific information tree appears in the left hand pane, expand Application Profiles,
then expand VMNET, then expand Application EPGs, and finally expand EPG VMNET.
3.
Click the Subnets folder under EPG VMNET and in the right hand pane, click Actions and select
Create EPG Subnet.
4.
On the Create EPG Subnet page, enter the default gateway IP address and subnet mask. The default
gateway IP address and subnet mask should be identical to the information provided in the above
section Creating a Tenant IP Pool for Virtual Machines. Select Private Subnet for the Scope option.
Leave all other options set at their defaults (blank). Click Submit. The default gateway is now
configured for the tenant VMNET network.
vDC Creation Guided Setup
The following procedure guides the reader through setting up a Virtual Datacenter or vDC, which is a
prerequisite for providing the capability of VM provisioning to tenants or end-users. A vDC is
essentially a collection of policies (compute, network, storage, system, etc.) that define the scope of
resources as well as other information that can be used during the VM provisioning process.
To create a vDC, complete the following steps:
1.
In UCS Director, navigate to Administration>Guided Setup and double-click the vDC Creation
guided setup wizard or highlight the vDC Creation option and choose Launch.
2.
On the Overview page, click Next.
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
157
Cisco UCS Director Use Case Example #3: Enable Tenant Virtual Machine Provisioning
3.
On the vDC General Information page, provide a vDC Name, choose the Group Name, choose
VMware as the Cloud Type and choose the vCenter account name for the Cloud Name. Click Next.
4.
On the Approvers and Contacts page, add any option approvers and configure any of the optional
approval settings. Click Next. Optional choose Skip if no approvals are required.
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
158
Cisco UCS Director Use Case Example #3: Enable Tenant Virtual Machine Provisioning
5.
On the vDC Creation page, choose an existing System Policy if one has already been configured. If
a System Policy has not been created, use the green plus icon to create a new System Policy. A
System Policy defines information and rules about the cloned Virtual Machines. It provides rule sets
for the VM hostname and VM label in vCenter as well as information regarding Windows setup and
domain parameters, etc. The System Policy is very important and essential to VM provisioning. This
procedure continues on the assumption of creating a new Service Policy. Click the green plus icon
to the right of System Policy.
6.
On the System Policy Information page, fill in the appropriate information for the required fields.
For more information one ach field as well as syntax for variables used in Host Name Template and
other fields, refer to the UCS Director Administration Guide on Cisco.com. When created, this
System Policy can be reused for other tenants, depending on the information provided. When
completed, click Submit.
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
159
Cisco UCS Director Use Case Example #3: Enable Tenant Virtual Machine Provisioning
7.
Back on the vDC Creation page, select the newly created System Policy. Click the green plus icon
to the right of Compute Policy to create a new tenant Compute Policy.
8.
On the Add Computing Policy page, provide a Policy Name, choose the scope of where this tenant's
VMs will be provisioned using the Hose Node/Cluster Scope, Resource Pool, ESX Type and ESX
Version options. Optionally set any additional Filter Conditions which will fine tune the placement
of tenant VMs. Enabling Override Template allows the administrator to decide what the CPU and
memory allocation of the provisioned (cloned) virtual machines will look like. Disabling this option
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
160
Cisco UCS Director Use Case Example #3: Enable Tenant Virtual Machine Provisioning
copies the template VM CPU and memory configuration. Enabling the Resizing of VM option
allows the tenant users to resize the CPU and memory for a given VM after the VM is provisioned.
This option does not effect the CPU and memory at the time of provisioning. When complete, click
Submit.
9.
On the Network Policy Information page, provide a Policy Name and add VM Networks to the
network policy. The VM Networks define which virtual networks the provisioned VMs for this
tenant have access to. In some cases the tenant may be given the option to choose from a list of
vNICs to add to a provisioned VM. To enable user selection of vNICs, choose the Allow end user
to select optional NICs. Use the green plus icon next to VM Networks to add a new tenant network
to the network policy. Note that each VM Network in the table equates to an interface that will be
added to each provisioned VM using this network policy.
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
161
Cisco UCS Director Use Case Example #3: Enable Tenant Virtual Machine Provisioning
10. On the Add Entry to VM Networks page, enter a NIC Alias (name) for this vNIC. Other options are
available if required. Add Port Groups to this vNIC. Choose the tenant VMNET IP Pool Policy to
assign an IP Address for the virtual machine VMNET network interface. Only one port group is
required unless the Allow end user to choose port groups option is enabled, in which case more than
one port group can be defined for this vNIC. Click Submit.
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
162
Cisco UCS Director Use Case Example #3: Enable Tenant Virtual Machine Provisioning
Note
Optionally add other vNICs to the network policy. For example additional vNICs could be added for the
tenant iSCSI_A and iSCSI_B port groups as well to connect the VM directly to the iSCSI fabrics.
11. Click Submit on the Network Policy Information page.
12. On the vDC Creation page, choose the green plus icon to the right of Storage Policy.
13. On the System Disk Policy page, enter a Policy Name. Under System Disk Scope section, choose
the options to narrow the scope of where the tenant's virtual machines will be provisioned from a
datastore perspective. Choose the tenant's datastore within this scope. Additional options are
provided to fine tune the datastore selection and configuration under the Storage Options and
Resizing Options for VM lifecycle sections. Click Next.
14. On the Additional Disk Policies page, Click Submit.
15. On the vDC Creation page, all required fields should now be selected. For more information on the
remaining non-mandatory options, please consult the UCS Director Administration Guide on
Cisco.com. Click Next.
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
163
Cisco UCS Director Use Case Example #3: Enable Tenant Virtual Machine Provisioning
16. On the Summary page, review and click Close.
Catalog Creation
The following procedure will guide the reader through the steps to publish a VM provisioning capability
for Catalog Item to an user group or tenant.
To create a catalog, complete the following steps:
1.
In UCS Director, navigate to Policies'Catalog. Click Add to add a new catalog item for the tenant.
2.
The Add Catalog box will appear, for the Catalog Type choose Standard.
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
164
Cisco UCS Director Use Case Example #3: Enable Tenant Virtual Machine Provisioning
Note
3.
On the Basic Information page, provide a Catalog Name and optional Catalog Description. Choose
the Catalog Icon that will show in the tenant catalog. Enable Applied to all groups to add this catalog
to every group (tenant), or use the Selected Groups button to choose specific groups to publish to.
Select the Cloud Name (vCenter Server account) and the Image (VM Template in vCenter). Click
Next.
4.
On the Application Details page, click Next.
5.
On the User credentials page, click Next.
6.
On the Customization page, ensure Automatic Guest Customization is enabled. Click Next.
7.
On the VM Access page, click Next.
8.
On the Summary page, review and click Submit.
Tenant users can now log in and view the Catalog from their end-user portal. Users that belong to the
group to which the catalog item was published will now have the capability to provision a VM based on
the procedure followed above. For more information on this procedure as well as more detail on the
various options and features, please consult the UCS Director Administration Guide on Cisco.com.
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
165
Cisco UCS Director Use Case Example #4: Enable Connectivity for Virtual Machine Application-Consistent
The Tenant user can now log into and view the Catalog from their end-user portal. Users that belong to
the group to which the catalog item was published will now have the capability to provision a VM within
their specific tenant resources. For more information on this procedure as well as more detail on the
various options and features, please consult the UCS Director Administration Guide on Cisco.com.
Cisco UCS Director Administration Guide, Release 5.2
http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/ucs-director/administration-guide/5-2/b_
Cisco_UCSD_Admin_Guide_52.html
Cisco UCS Director Use Case Example #4: Enable
Connectivity for Virtual Machine Application-Consistent
Snapshots
Overview
When a tenant can provision VMs, those VMs are typically intended to run business critical applications.
Therefore, such tenants often need to take granular storage level snapshots of the consistent application
state to ensure that important application data is backed up and, in most cases, replicated. This use case
adds the required tenant connectivity through the APIC fabric and across tenant resources to enable the
use of NetApp SnapDrive and SnapManager software.
SnapDrive is installed in a physical or VM operating system and enables the machine administrator to
provision and manage storage resources within their environment. SnapManager is also installed in a
physical or virtual machine operating system and leverages SnapDrive to provide application-aware data
protection. SnapManager products are available for popular applications, and these products are
integrated with application-specific data protection mechanisms.
To achieve an application-consistent snapshot, SnapManager interacts with the application itself to
prepare it for backup and then coordinates with SnapDrive to execute the snapshot within Data ONTAP.
SnapManager can also coordinate replication of snapshot data (using NetApp SnapMirror data
replication software) to another NetApp storage destination for secondary or cascaded backups.
As illustrated in Figure 6, this use case requires that the application VM running SnapDrive must be able
to communicate with the tenant-specific SVM. This use case configures a new tenant contract that
enables snap-related traffic between the tenant VMNET network (EPG) and the tenant LIF SVM MGMT
network (EPG) and thus facilitates communication between SnapDrive and the SVM.
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
166
Cisco UCS Director Use Case Example #4: Enable Connectivity for Virtual Machine Application-Consistent
Figure 6
Tenant Infrastructure Configuration for Use Case Example #4
Table 6 provides a high-level process overview of the steps and order of operations involved in enabling
the connectivity required for application-consistent snapshots with SnapDrive and SnapManager.
Table 6
Use Case Example #4: Task List and Order of Operations
Operational Tasks
1. Create Tenant Snap Contract
2. Create Tenant Snap Contract Subject
3. Create Snap Contract Filter
4. Create Snap Contract Filter Rule 1
5. Create Snap Contract Filter Rule 2
6. Create Snap Contract Filter Rule 3
7. Add Snap Filter to Snap Contract Subject
8. Add Snap Contract to LIF_SVM_MGMT_EPG
9. Add Snap Contract to VMNET EPG
10. Install Microsoft iSCSI Initiator (Manual Task)
11. Install and Configure NetApp SnapDrive (Manual
Task)
12. Install and Configure NetApp SnapManager
(Manual Task)
Infrastructure Domain
Cisco Application Infrastructure Controller
Cisco Application Infrastructure Controller
Cisco Application Infrastructure Controller
Cisco Application Infrastructure Controller
Cisco Application Infrastructure Controller
Cisco Application Infrastructure Controller
Cisco Application Infrastructure Controller
Cisco Application Infrastructure Controller
Cisco Application Infrastructure Controller
Application Virtual Machine(s)
Application Virtual Machine(s)
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
167
Cisco UCS Director Use Case Example #4: Enable Connectivity for Virtual Machine Application-Consistent
User Perspective
The specific workflow configured as follows is executed from the perspective of the infrastructure
administrator, typically a user with the system administrator or other comparable user role in UCS
Director. In this use case, workflow is not configured for publication to and execution from an end-user
or tenant perspective. Once the following short workflow is configured and executed by the system
administrator for a tenant, the individual tenant users can install SnapDrive, and the appropriate
connectivity is in place for SnapDrive to communicate with the tenant SVM as required by SnapDrive.
Prerequisites
•
FlexPod with ACI configuration must be in place and operational as indicated in the Cisco CVD
Deployment Guide.
•
You must perform initial deployment of UCS Director. This procedure is described in the section
UCS Director Initial Deployment.
•
You must perform UCS Director extended deployment for FlexPod. This configuration contains
specific steps for the management of a FlexPod system within UCS Director. This procedure can be
found in the section UCS Director Extended Deployment for FlexPod with ACI.
•
You must configure and execute the use case example #1 workflow to create one or more tenants in
the infrastructure.
•
You must configure and execute the use case example #2 workflow so that the tenant infrastructure
supports guest-attached iSCSI.
•
You must configure use case example #3 to allow tenant VM provisioning.
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
168
Cisco UCS Director Use Case Example #4: Enable Connectivity for Virtual Machine Application-Consistent
Detailed Workflow Configuration
Create New Workflow
To create a new workflow, complete the following steps:
1.
In UCS Director, navigate to Policies'Orchestration and then select the Workflows tab.
2.
Click the Add Workflow button to create a new workflow. Optionally use the Import button to
import the published version of this workflow as opposed to building from scratch. This procedure
continues assuming creating a new workflow.
3.
Provide a Workflow Name.
4.
Optionally provide a Description.
5.
Set Workflow Context to Any.
6.
Optionally select Save as Compound Task. This option will add this specific workflow as a task in
the task library therefore enabling this workflow to be nested in other workflows as a task.
7.
Under Save Options, choose an existing folder in the Select Folder dropdown menu, or choose Place
in New Folder and provide the name of the new folder.
8.
Select any optional Notifications options to notify users of workflow execution status.
9.
Click Next.
10. On the Add User Inputs page, this is where we create the form that will be presented to each user
when the workflow is executed. This form can prompt the user for specific information that can then
be mapped to task inputs throughout the workflow. The table below provides information on the
User Inputs defined for this specific use case.
11. Click Next.
12. Click Submit.
Workflow User Inputs
This information can be provided when creating a new workflow on the Add User Inputs page, as seen
in the procedure above, or items can be added as workflow user inputs as tasks are added to the
workflow. On the User Input Mapping page of each task (after it is dragged into the workflow from the
task library), there is an Edit Workflow Properties button at the top of the page. This button can be used
at any time to add additional user inputs. To reiterate, these are the items that the user will be prompted
for each time the workflow is executed. This information is then generally mapped to the appropriate
task or tasks throughout the workflow for various task inputs.
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
169
Cisco UCS Director Use Case Example #4: Enable Connectivity for Virtual Machine Application-Consistent
Table 7 represents the User Inputs that are collected from the user each time this specific workflow is
executed. This list is provided simply as an example. Specific customer requirements may require a
larger or small number of User Inputs. This list can be customized as needed, however the information
below is what is required to fulfill this use-case as is highlighted in this document.
Table 7
User Inputs
Input Label
APIC Tenant
SVM_MGMT EPG
VMNET EPG
Input
Description
Mandator
y
Yes
Yes
Yes
Type
ApicDeviceTenantidentity
ApicDeviceTenantEPGIdentity
ApicDeviceTenantEPGIdentity
Admin Input
Value
Workflow Tasks and Input/Output Mappings
This section provides information on the UCS Director tasks used to build an automated workflow for
executing this use case. Also Included is information regarding the order of operations (tasks) as well as
the mapping of inputs and outputs between tasks.
Create Contract for Snap
Task Name from Task Library:
(drag and drop this task)
Create Contract
Task Information
Field
Value
Task Name
Create_Tenant_Snap_Contract
Task Category
Cisco APIC Tasks
Task Type
Create Contract
Comment
Create Tenant Snap Contract
User Input Mapping
Input
Tenant Name (Mandatory)
Mapped

Mapped Variable
APIC Tenant
Contract Name
Contract Description
Scope (Mandatory)
Priority (Mandatory)
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
170
Cisco UCS Director Use Case Example #4: Enable Connectivity for Virtual Machine Application-Consistent
Task Inputs
Input
Value
Contract Name
Snap
Contract Description
Scope
tenant
Priority
unspecified
Create Contract Subject for Snap
Task Name from Task Library:
(drag and drop this task)
Create Contract Subject
Task Information
Field
Value
Task Name
Create_Tenant_Snap_Contract_Subject
Task Category
Cisco APIC Tasks
Task Type
Create Contract Subject
Comment
Create Tenant Snap Contract Subject
User Input Mapping
Input
Contract Name (Mandatory)
Mapped

Mapped Variable
Create_Tenant_Snap_Contract.TENANT_CONTRACT_ID
ENTITY
Type
Contract Subject Name (Mandatory)
Contract Subject Description
Reverse Filter Ports
Apply Both Directions
Service Graph
QoS
In Term Service Graph
In Term QoS
Out Term Service Graph
Out Term QoS
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
171
Cisco UCS Director Use Case Example #4: Enable Connectivity for Virtual Machine Application-Consistent
Task Inputs
Input
Value
Type
Normal
Contract Subject Name
Snap
Contract Subject Description
Reverse Filter Ports
Apply Both Directions


Service Graph
QoS
unspecified
Create Snap Contract Filter
Task Name from Task Library:
Create Tenant Filter
(drag and drop this task)
Task Information
Field
Value
Task Name
Create_Snap_Contract_Filter
Task Category
Cisco APIC Tasks
Task Type
Create Tenant Filter
Comment
Create Snap Contract Filter
User Input Mapping
Input
Mapped

Tenant Name (Mandatory)
Mapped Variable
APIC Tenant
Filter Name (Mandatory)
Description
Task Inputs
Input
Value
Filter Name
Allow_Snap
Description
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
172
Cisco UCS Director Use Case Example #4: Enable Connectivity for Virtual Machine Application-Consistent
Create Snap Contract Filter Rule 1
Task Name from Task Library:
Create Tenant Filter Rule
(drag and drop this task)
Task Information
Field
Value
Task Name
Create_Snap_Contract_Filter_Rule_1
Task Category
Cisco APIC Tasks
Task Type
Create Tenant Filter Rule
Comment
Create Snap Contract Filter Rule 1
User Input Mapping
Input
Mapped

Filter Name (Mandatory)
Mapped Variable
Create_Snap_Contract_Filter.TENANT_FILTER_IDENTIT
Y
Filter Rule Name (Mandatory)
Description
Ethernet Type (Mandatory)
ARP Flag
IP Protocol
Source Port Start
Source Port Start Custom (Mandatory)
Source Port End
Source Port End Custom (Mandatory)
Destination Port Start
Destination Port Start Custom (Mandatory)
Destination Port End
Destination Port End Custom (Mandatory)
Task Inputs
Input
Value
Filter Rule Name
tcp_443
Description
Ethernet Type
IP
ARP Flag
UNSPECIFIED
IP Protocol
TCP
Allow Fragment
Source Port Start
UNSPECIFIED
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
173
Cisco UCS Director Use Case Example #4: Enable Connectivity for Virtual Machine Application-Consistent
Source Port End
UNSPECIFIED
Destination Port Start
HTTPS
Destination Port End
HTTPS
TCP Session Rule
Unspecified
Create Snap Contract Filter Rule 2
Task Name from Task Library:
Create Tenant Filter Rule
(drag and drop this task)
Task Information
Field
Value
Task Name
Create_Snap_Contract_Filter_Rule_2
Task Category
Cisco APIC Tasks
Task Type
Create Tenant Filter Rule
Comment
Create Snap Contract Filter Rule 2
User Input Mapping
Input
Mapped

Filter Name (Mandatory)
Mapped Variable
Create_Snap_Contract_Filter.TENANT_FILTER_IDENTIT
Y
Filter Rule Name (Mandatory)
Description
Ethernet Type (Mandatory)
ARP Flag
IP Protocol
Source Port Start
Source Port Start Custom (Mandatory)
Source Port End
Source Port End Custom (Mandatory)
Destination Port Start
Destination Port Start Custom (Mandatory)
Destination Port End
Destination Port End Custom (Mandatory)
Task Inputs
Input
Value
Filter Rule Name
tcp_808
Description
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
174
Cisco UCS Director Use Case Example #4: Enable Connectivity for Virtual Machine Application-Consistent
Ethernet Type
IP
ARP Flag
UNSPECIFIED
IP Protocol
TCP
Allow Fragment
Source Port Start
UNSPECIFIED
Source Port End
UNSPECIFIED
Destination Port Start
Destination Port Start
Custom
Destination Port End
Destination Port End
Custom
TCP Session Rule
CUSTOM
808
CUSTOM
808
Unspecified
Create Snap Contract Filter Rule 3
Task Name from Task Library:
(drag and drop this task)
Create Tenant Filter Rule
Task Information
Field
Value
Task Name
Create_Snap_Contract_Filter_Rule_3
Task Category
Cisco APIC Tasks
Task Type
Create Tenant Filter Rule
Comment
Create Snap Contract Filter Rule_3
User Input Mapping
Input
Filter Name (Mandatory)
Mapped

Mapped Variable
Create_Snap_Contract_Filter.TENANT_FILTER_IDENTIT
Y
Filter Rule Name (Mandatory)
Description
Ethernet Type (Mandatory)
ARP Flag
IP Protocol
Source Port Start
Source Port Start Custom (Mandatory)
Source Port End
Source Port End Custom (Mandatory)
Destination Port Start
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
175
Cisco UCS Director Use Case Example #4: Enable Connectivity for Virtual Machine Application-Consistent
Destination Port Start Custom (Mandatory)
Destination Port End
Destination Port End Custom (Mandatory)
Task Inputs
Input
Value
Filter Rule Name
tcp_4095
Description
Ethernet Type
IP
ARP Flag
UNSPECIFIED
IP Protocol
TCP
Allow Fragment
Source Port Start
UNSPECIFIED
Source Port End
UNSPECIFIED
Destination Port Start
Destination Port Start
Custom
Destination Port End
Destination Port End
Custom
TCP Session Rule
CUSTOM
4095
CUSTOM
4095
UNSPECIFIED
Add Snap Filter to Snap Contract Subject
Task Name from Task Library:
(drag and drop this task)
Add Filter To Contract Subject
Task Information
Field
Value
Task Name
Add_Snap_Filter_to_Snap_Contract_Subject
Task Category
Cisco APIC Tasks
Task Type
Add Filter To Contract Subject
Comment
Add iSCSI Filter to iSCSI_A Contract Subject
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
176
Cisco UCS Director Use Case Example #4: Enable Connectivity for Virtual Machine Application-Consistent
User Input Mapping
Input
Mapped
Contract Subject (Mandatory)

Filter (Mandatory)

Mapped Variable
Create_Tenant_iSCSI_A_Contract_Subject.TENANT_CON
TRACT_SUBJECT_IDENTITY
Create_Snap_Contract_Filter.TENANT_FILTER_IDENTIT
Y
Filter For Consumer To Provider
Filter For Provider To Consumer
Task Inputs
Input
Value
Apply Both Directions

Add Snap Contract to LIF SVM_MGMT EPG
Task Name from Task Library:
(drag and drop this task)
Add Contract To EPG
Task Information
Field
Value
Task Name
Add_Snap_Contract_to_LIF_SVM_MGMT_EPG
Task Category
Cisco APIC Tasks
Task Type
Add Contract To EPG
Comment
Add Snap Contract to LIF SVM_MGMT EPG
User Input Mapping
Input
EPG (Mandatory)
Mapped
Mapped Variable

SVM_MGMT EPG

Create_Tenant_Snap_Contract.TENANT_CONTRACT_ID
ENTITY
Contract Type (Mandatory)
Contract (Mandatory)
QoS (Mandatory)
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
177
Cisco UCS Director Use Case Example #4: Enable Connectivity for Virtual Machine Application-Consistent
Task Inputs
Input
Value
Contract Type
Provided Contract
QoS
UNSPECIFIED
Add Snap Contract to VMNET EPG
Task Name from Task Library:
Add Contract To EPG
(drag and drop this task)
Task Information
Field
Value
Task Name
Add_Snap_Contract_to_VMNET_EPG
Task Category
Cisco APIC Tasks
Task Type
Add Contract To EPG
Comment
Add Snap Contract to VMNET EPG
User Input Mapping
Input
Mapped
EPG (Mandatory)
Mapped Variable

VMNET EPG

Create_Tenant_Snap_Contract.TENANT_CONTRACT_ID
ENTITY
Contract Type (Mandatory)
Contract (Mandatory)
QoS (Mandatory)
Task Inputs
Input
Value
Contract Type
Consumed Contract
QoS
unspecified
NetApp SnapDrive Software
When the above workflow has been executed for the tenant, the necessary ports are allowed between
tenant SnapDrive instances and the tenant SVM. At this point, NetApp SnapDrive can then be installed
and used to create and map new guest attached LUNs to the application virtual machines as well as
initiate snapshots of the application data residing on the attached LUNs. These functions can be managed
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
178
Cisco UCS Director Use Case Example #4: Enable Connectivity for Virtual Machine Application-Consistent
through the SnapDrive user interface on the application VM itself, rather than having to log into the
tenant SVM to create and map new storage and initiate snapshots. NetApp® SnapDrive® for Windows®
(SDW) helps you to perform storage provisioning tasks and manage data in Microsoft Windows
environments. You can run SnapDrive software on Windows hosts in either a physical or a virtual
environment. SnapDrive software integrates with Windows Volume Manager so that storage systems can
serve as virtual storage devices for application data in Windows Server® 2008 R2 and later. It can also
be used to provision storage for Windows virtual machines hosted on ESX® hypervisors.
SnapDrive for Windows supports the following features in clustered Data ONTAP® environments:
•
Enables online storage configuration, LUN expansion, and streamlined management
•
Integrates Data ONTAP Snapshot™ technology with Microsoft VSS framework, which enables
creating point-in-time images of data stored on LUNs
•
Integrates with Microsoft remote VSS framework to perform backup and restore of SMB 3.0 shares
hosted on NetApp storage systems running clustered Data ONTAP 8.2
•
Enables support on Microsoft cluster configurations
•
Supports iSCSI, FC, and FCoE on Windows and VMware® environments
•
Supports virtual Fibre Channel adapters for guest virtual machines in Windows Server 2012
environments.
•
Supports RDM, VMDK over NFS, and VMFS datastores in VMware environments
•
Supports LUN migration with VMware vMotion®, SRM, and DRS functionalities
•
Works in conjunction with SnapMirror® software to facilitate disaster recovery from either
asynchronously or synchronously mirrored destination volumes
•
Enables SnapVault® integration natively within SnapManager® for SQL Server and SnapManager
for Hyper-V
•
Supports Data ONTAP PowerShell cmdlets to execute SAN and SMB workflows
The following sections provide a high-level sample overview of the NetApp SnapDrive installation and
configuration procedure. NetApp recommends referring to the NetApp SnapDrive documentation for
further guidance and information on the individual options and features provided during installation and
configuration.
NetApp SnapDrive Installation
To install NetApp SnapDrive, complete the following steps:
1.
On the application VM, locate and run the NetApp SnapDrive executable as the Administrator user.
2.
On the Welcome to the SnapDrive Installation page, click Next.
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
179
Cisco UCS Director Use Case Example #4: Enable Connectivity for Virtual Machine Application-Consistent
3.
On the SnapDrive License page, choose the SnapDrive license option that best fits your
environment. This example assumes a Per Storage System license. Click Next.
4.
On the Customer Information page, enter a User Name and an Organization. Click Next.
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
180
Cisco UCS Director Use Case Example #4: Enable Connectivity for Virtual Machine Application-Consistent
5.
On the Destination Folder page, keep the default install path or use the Change… button to select
an alternate install path. Click Next.
6.
On the Set Firewall Rules page, click the checkbox to Enable SnapDrive to communicate through
the Windows Firewal. Click Next.
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
181
Cisco UCS Director Use Case Example #4: Enable Connectivity for Virtual Machine Application-Consistent
7.
On the VirtualCenter or ESX Server Web Service Console page, leave the Enable VirtualCenter or
ESX Server Settings checkbox unchecked. Click Next.
8.
On the Virtual Storage Console Details page, leave the Virtual Storage Console Details checkbox
unchecked. Click Next.
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
182
Cisco UCS Director Use Case Example #4: Enable Connectivity for Virtual Machine Application-Consistent
9.
Note
On the SnapDrive Service Credentials page, enter the local user Account (username) and Password
that SnapDrive should use for installed services. This user account should be a member of the local
Administrators user group. In this example we have created a local user named snapuser with
administrative rights on the local machine.
Be sure to add the Account (username) in DOMAIN\USERNAME notation, installation will fail if not
entered in this format.
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
183
Cisco UCS Director Use Case Example #4: Enable Connectivity for Virtual Machine Application-Consistent
10. On the SnapDrive Web Service Configuration page, keep the default port settings. Click Next.
11. On the Preferred Storage System IP Address page, select Enable preferred storage system IP
Address. Provide a Storage System Name and the IP Address of the lif_svm_mgmt LIF on the tenant
storage virtual machine for the Preferred IP Address. Click Next.
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
184
Cisco UCS Director Use Case Example #4: Enable Connectivity for Virtual Machine Application-Consistent
12. On the Transport Protocol Default Settings page, choose the appropriate transport protocol and
provide the User Name and Password if required for the chosen transport protocol. It is highly
recommended to choose HTTPS as the transport protocol. This procedure continues with the HTTPS
option enabled. Click Next.
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
185
Cisco UCS Director Use Case Example #4: Enable Connectivity for Virtual Machine Application-Consistent
13. On the Unified Manager Configuration page, click Next.
14. On the Ready to Install the SnapDrive Application page, click Install.
15. The installation should now complete successfully, click Finish.
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
186
Cisco UCS Director Use Case Example #4: Enable Connectivity for Virtual Machine Application-Consistent
NetApp SnapDrive Configuration
When SnapDrive has been installed on the application virtual machine, it can then be used to create and
map new LUNs on storage to the virtual machine. The following provides a high-level example of such
a procedure. Again it is highly recommended to refer directly to the NetApp documentation for specific
installation and configuration instructions as well as more detail information on the options and features
of NetApp SnapDrive.
To configure NetApp SnapDrive, complete the following steps:
1.
Open NetApp SnapDrive, which should now be installed on the VM.
2.
When SnapDrive is open, expand the tree in the left-hand pane and right-click on iSCSI
Management. Then choose Establish Session.
3.
The Welcome to the Create iSCSI Session Wizard will open. Click Next.
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
187
Cisco UCS Director Use Case Example #4: Enable Connectivity for Virtual Machine Application-Consistent
4.
On the Provide Storage System Identification page, provide the Storage System Name as the IP
Address of the tenant storage virtual machine lif_svm_mgmt (This is the SVM management LIF)
LIF. Click Next.
5.
On the Provide iSCSI HBA page, select the initiator for the iSCSI_A fabric from the top list and
select the corresponding target for the iSCSI_A fabric. Click Next.
6.
On the Completing the iSCSI session Wizard page, click Finish.
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
188
Cisco UCS Director Use Case Example #4: Enable Connectivity for Virtual Machine Application-Consistent
NetApp SnapManager Software
NetApp SnapManager software is a software suite that works in conjunction with NetApp SnapDrive
software to schedule and prepare applications and their data for the creation of storage snapshots.
SnapManager facilitates communication and coordination between SnapDrive and the business-critical
application in question. Each version of SnapManager (SnapManager for SQL, SnapManager for Oracle,
SnapManager for Exchange, and so on) is specifically developed to support and integrate a specific
application. SnapManager thus serves as a link between an application, the application data, and
SnapDrive. SnapManager works with an application to ensure the application and application data are
in a known good state prior to informing SnapDrive to initiate a snapshot on the tenant SVM.
The installation and configuration of SnapManager is outside of the scope of this document. For more
information on the various versions of SnapManager, refer to the NetApp SnapManager Software page.
Detailed installation and configuration procedures for all versions of SnapDrive and SnapManager
software are available at the NetApp Support site. You can also refer to the NetApp Technical Library
for SnapDrive and SnapManager Best Practices.
The following guides should be used when setting up SnapDrive for Windows and SnapManager for
SQL in a NetApp clustered Data ONTAP environment.
Note
•
SnapDrive 7.0 for Windows for Clustered Data ONTAP 8.2 - Best Practices Guide
•
Microsoft SQL Server and SnapManager 7.1 for SQL server - Best Practices Guide
•
Microsoft SQL Server and SnapManager for SQL Deployment Guide
The guides listed above are version specific, so follow the guides appropriate for your environment.
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
189
Appendix
Appendix
Reference Documentation Links
FlexPod References
FlexPod on Cisco Design Zone
http://www.cisco.com/c/en/us/solutions/enterprise/data-center-designs-cloud-computing/fpplatforms.html
FlexPod Datacenter with VMware vSphere 5.5 Update 1 and Cisco Nexus 9000 Application Centric
Infrastructure (ACI) Design Guide
http://www.cisco.com/c/dam/en/us/td/docs/unified_computing/ucs/UCS_CVDs/flexpod_esxi55u2_n9k_aci
_design.pdf
FlexPod Datacenter with VMware vSphere 5.5 Update 1 and Cisco Nexus 9000 Application Centric
Infrastructure (ACI) Deployment Guide
http://www.cisco.com/c/dam/en/us/td/docs/unified_computing/ucs/UCS_CVDs/flexpod_esxi55u2_n9k_aci.
pdf
Cisco References
Cisco UCS Director Landing Page
http://www.cisco.com/c/en/us/products/servers-unified-computing/ucs-director
NetApp References
NetApp SnapManager Software Landing Page
http://www.netapp.com/us/products/management-software/snapmanager
NetApp Clustered Data ONTAP 8.2.x Technical Report
http://www.netapp.com/us/media/tr-3982.pdf
NetApp Technical Library
http://www.netapp.com/us/library/index.aspx
Firewall and Contract Port Information
NetApp NFS Traffic
Port Number
111 (tcp/udp)
2049 (tcp/udp)
635 (tcp/udp)
Port Description
Portmapper
NFS
Mountd
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
190
Appendix
NetApp iSCSI Traffic
Port Number
3260 (tcp)
Port Description
iSCSI por for mounting iSCSI LUNs
NetApp SnapDrive And SnapManager
Port Number
443 (tcp)
808 (tcp)
4095 (tcp)
Port Description
HTTPS (on Storage System to receive ZAPI requests)
TCP.NET protocol communication of WCF based web services.
SnapDrive for Windows, SnapManager for Hyper-V, SnapManager
for Exchange, SnapManager for SQL all have WCF based Web
services.
SnapDrive Web services HTTPS endpoint
FlexPod Datacenter with VMware vSphere, Cisco UCS Director, Cisco Nexus 9000, Cisco Application Centric Infrastructure (ACI)
191
Download