Deploying ONTAP Select v1.0.1

Deploying ONTAP Select
November 2019 | SL10579 Version 1.0.1

TABLE OF CONTENTS
1 Introduction...................................................................................................................................... 3
1.1 Lab Objectives........................................................................................................................... 3
1.2 Prerequisites.............................................................................................................................. 3
2 Lab Environment............................................................................................................................. 4
3 Lab Activities................................................................................................................................... 5
3.1 ONTAP Select CLI Deployment................................................................................................ 5
3.2 ONTAP Select Verification and Configuration...................................................................... 11
3.3 ONTAP Select GUI Deployment............................................................................................. 26
4 References......................................................................................................................................38
5 Version History.............................................................................................................................. 39

2 © 2019 NetApp, Inc. All rights reserved. NetApp Proprietary
1 Introduction
ONTAP Select delivers enterprise storage services via ONTAP instances running on vSphere ESX or KVM
hypervisors. Single-node, 2-node HA, and 4-node HA configurations are supported. This lab will focus on
demonstrating how to create a single-node ONTAP cluster using the ONTAP Select Deploy utility.
1.1 Lab Objectives

The lab includes the following activities:
• Use the ONTAP Select Deploy virtual machine to create a single-node ONTAP cluster
• Verify cluster creation and access via OnCommand System Manager
1.2 Prerequisites
Familiarity with the concepts of clustered Data ONTAP is helpful, but not required to demonstrate the ONTAP
Select Deploy utility.

2 Lab Environment
The following diagram illustrates the environment for this lab.
This environment contains a minimal VMware vSphere configuration with a single hypervisor. The ONTAP Select
Deploy VM is already unpacked and running in the environment. Using the utility on this VM, you can create an
ONTAP cluster.
The Lab Host Credentials table provides a list of the servers and storage controller nodes in the lab, along with
their IP address.
Figure 2-1:
Table 1: Lab Host Credentials
Hostname Description IP Address(es) Username Password

Windows 2012R2
JUMPHOST 192.168.0.5 DEMO\Administrator Netapp1!
Remote Access host
VMware vCenter
VC1 192.168.0.31 DEMO\Administrator Netapp1!
Server v6.0
ESX1 VMware ESXi server 192.168.0.51 root Netapp1!
v6.0
Active Directory
DC1 192.168.0.253 DEMO\Administrator Netapp1!
Server

3 Lab Activities
• ONTAP Select CLI Deployment on page 5
• ONTAP Select Verification and Configuration on page 11
• ONTAP Select GUI Deployment on page 26
3.1 ONTAP Select CLI Deployment

NetApp’s software defined offering is helping pioneer the emerging software defined storage area by bringing
enterprise class storage management features to the software defined datacenter. ONTAP Select is a critical
component of the NetApp Data Fabric vision, allowing customers to run Data ONTAP management services on
commodity hardware. This product is targeted at remote office and software defined datacenter implementations.
This exercise will focus on creating a single-node ONTAP Select cluster after describing the unique licensing and
components of the ONTAP Select solution.
3.1 Licensing
In addition to hardware flexibility, ONTAP Select 9 offers a different licensing model. Capacity licenses are
available in 1TB increments up to 100TB per node. The capacity used is calculated on raw capacity. Actual
usable capacity can be higher when storage efficiencies are utilized.
For testing and evaluation purposes, ONTAP Select 9 nodes can be deployed with an evaluation license. The
following features are available on each ONTAP Select 9 node:
• NFS
• CIFS
• iSCSI
• FlexClone
• SnapRestore
• SnapVault
• SnapMirror
3.1 Components
The ONTAP Select 9 solution has two major components:
• ONTAP Select Deploy
The Deploy utility is packaged as an OVA. Once imported, this Linux based virtual appliance provides
both a graphical and command line interface for creating, managing, and destroying ONTAP Select 9
nodes.
• ONTAP Select 9 Node
ONTAP Select 9 is supported in single-node, two-node HA, and four-node HA configurations. The
single-node configuration allows for an ONTAP instance with minimal resources while relying on
SnapMirror or other data protection configurations to keep redundant copies of the data. The two-node
and four-node HA configurations utilize Aggregate mirroring between the nodes so that the storage
remains both redundant and highly available.
Note: As with all software defined storage (SDS), some of the architectural details exist in an
abstraction layer below the SDS. This requires careful consideration regarding hypervisor node
placement, RAID hardware, etc. These details are noted during the graphical UI installation of a
node, and are expressed in further detail in the deployment guides. These resources are linked
to in the References section of this guide.

3.1 Lab Exercise Goals
• Define the information needed to create a single-node cluster.
• Use the CLI interface to create an ONTAP Select 9 cluster.
Note: Continue with the rest of the sections of this lab guide, and return to the following steps at the end.
This will allow the time (30 minutes) needed for the node creation to finish.
• Use System Manager to configure the new cluster to serve out a CIFS share.
• Destroy the cluster and start a new cluster creation with the GUI interface.
Note: While this last step will show the GUI steps to create a cluster, there are limitations of this
demonstration lab environment that prevent GUI cluster creations from completing.
3.1 Define the information needed to create a single-node cluster

The following information is necessary for the creation of an ONTAP Select 9 node:
1. Review the following table. This information is required for creating an ONTAP Select cluster.
Table 2: Cluster create command variables
Item Value Notes

ONTAP cluster name cluster3
Admin account password Netapp1!
Cluster management IP 192.168.0.103 This is the IP address for the
cluster management LIF. The
netmask and gateway are also
needed for this interface. In this
example, use 255.255.255.0
and 192.168.0.1 respectively as
shown below.
ONTAP image version 9.6 The current environment offers
version 9.6.
Cluster node name cluster3-01 This can be any desired
hostname; however, it is often
helpful to include the cluster
name and a node number.
Node management IP 192.168.0.113 The IP address for the node
management LIF.
Hypervisor Node IP(s) or 192.168.0.51 The IP of the hypervisor where
FQDN(s) the cluster node(s) will be
deployed. If creating a two or
four node HA cluster, this is
a space separated list of IP
addresses or FQDNs.
Note: The IP or Name
used here should match
how the systems are
referenced from within
vCenter.
DNS IP(s) 192.168.0.253 The IP of the DNS server(s). If

more than one host is specified,

Item Value Notes
this is a space separated list of
IP addresses or FQDNs.
DNS search domain(s) demo.netapp.com The domain names to be used
for domain searches when
a non-qualified hostname is
used. If more than one domain
is specified, this is a space
separated list of domain names.
NTP server IP(s) 192.168.0.1 The IP of the NTP time
server(s). If more than one host
is specified, this is a space
separated list of IP addresses or
FQDNs.
Management network port group ONTAP-external This is the vSphere port group
where the ONTAP management
LIFs are connected.
Data network port group ONTAP-external This is the vSphere port group
where the cluster data LIFs
will connect. It is common to
use the same port group as
defined for management (above);
however, an extra port group is
possible for separating data and
management traffic.
Internal network port group n/a for this single-node This is the vSphere port group
demonstration where ONTAP cluster networking
is connected. Since this is only
used with the 2-node HA and 4-
node HA configurations, it will not
be used in this demonstration.
3.1 Use the CLI interface to create an ONTAP Select 9 cluster

There are three CLI commands used to create the cluster. These commands define the hypervisor host(s)
that a cluster node can be deployed on, configure the hypervisor(s), and create the cluster node(s) on those
hypervisor(s).
1. Open PuTTY.
2. Select the ONTAP Select Deploy VM saved session.
3. Click Open.

2
Figure 3-1:
4. Login as the admin user.

5. Enter Netapp1! for the password.

4
5
Figure 3-2:
6. First, add the credential needed to access vCenter (using Netapp1! as the password):
(ONTAPdeploy) credential add -hostname vc1.demo.netapp.com -type vcenter -username

"administrator@vsphere.local"
Password for administrator@vsphere.local:
Credential add for host vc1.demo.netapp.com is successful
7. Use the following command to register the hypervisor to be used for creating the ONTAP node:
Note: Multiple hypervisors are allowed; however, this example will use a single host.
(ONTAPdeploy) host register -name 192.168.0.51 -hypervisor-type ESX -mgmt-server

vc1.demo.netapp.com
The job for "host register" has been submitted with request-id 21.
8. To monitor the progress of the previous command, use the command referenced in the output from the
previous step:
Note: The request-id may differ from what is shown in this guide. Be sure to use the request-id
shown in the output from the previous command.
Note: This host register command can take up to 5 minutes to complete.
(ONTAPdeploy) job monitor -request-id 21

[Request 21 (success)]: Host "192.168.0.51" registered successfully.

9. Issue the following command to configure the new cluster3 to contain a single ONTAP node:
(ONTAPdeploy) cluster create -name cluster3 -node-count 1

Cluster "cluster3" created successfully.
10. This command will configure the IP settings for cluster3's cluster management interface (LIF):
(ONTAPdeploy) cluster modify -name cluster3 -mgmt-ip 192.168.0.103 -netmask 255.255.255.0 -

gateway 192.168.0.1 -dns-servers 192.168.0.253 -dns-domain demo.netapp.com
Cluster "cluster3" was successfully modified.
11. ONTAP Select can be deployed in a small, medium, or large configuration. The following command
configures the cluster3 node to use the small configuration:
Note: Do not change the instance-type in the command below as this lab has been created to
include only the resources required for the small instance type.
(ONTAPdeploy) node modify -name cluster3-01 -cluster-name cluster3 -host-name 192.168.0.51 -

instance-type small -passthrough-disks false
Node "cluster3-01" was successfully modified.
12. In a previous step, you configured the IP settings for the cluster management interface. This command
is used to configure the node mangagement interface for the cluster3-01 node:
(ONTAPdeploy) node modify -name cluster3-01 -cluster-name cluster3 -mgmt-ip 192.168.0.113 -

management-networks ONTAP-external -data-networks ONTAP-external
Node "cluster3-01" was successfully modified.
13. The last step prior to deployment is to assign a vSphere datastore for use when creating this new
ONTAP node. Run the following command to assign the esx1data datastore for use with the
cluster3-01 node:
(ONTAPdeploy) node storage pool attach -name esx1data -cluster-name cluster3 -node-name
cluster3-01 -capacity-limit 500GB
Storage pool "esx1data" was attached to node "cluster3-01" successfully.
14. Now that all of the configuration details are defined, it's time to deploy the cluster with the following
command:
Note: Use Netapp1! for the password here as well to keep things consistent and easy to
remember during this demonstration.
(ONTAPdeploy) cluster deploy -name cluster3

Create password for ONTAP admin:
Retype new password:
The job for "cluster deploy" has been submitted with request-id 48. To monitor its progress,
use the command "job monitor -request-id 48".
15. To monitor the progress of the cluster creation, use the command referenced in the output from the
previous step:
Note: The request-id may differ from what is shown in this guide. Be sure to use the request-id
shown in the output from the previous command.
Note: The message below indicates the cluster creation will take up to two hours. In this
environment, the creation should complete in ~30 minutes. When you see the final message
indicating the cluster is ready for use, continue to the next step.
(ONTAPdeploy) job monitor -request-id 48

[Request 48 (running)]: Deployment request for cluster "cluster3" accepted.
[Request 48 (running)]: Creating cluster nodes. This operation may take up to two hours,
depending on the response time of the virtualization environment.
...
...
...
[Request 48 (running)]: All nodes in the cluster are responding to ping requests.
[Request 48 (success)]: Cluster "cluster3" is deployed and ready for use.

16. To see detailed information about this new cluster, run the following command:
(ONTAPdeploy) cluster show -name cluster3 -detailed

+---------------------+--------------------------------------+
| Field | Value |
+---------------------+--------------------------------------+
| Name | cluster3 |
| State | powered_on |
| IP | 192.168.0.103 |
| ONTAP Version | 9.6.0 |
| Node Count | 1 |
| Gateway | 192.168.0.1 |
| Netmask | 255.255.255.0 |
| MTU | - |
| Eval | True |
| ONTAP Image Version | 9.6P2 |
| DNS Info DNS IPs | 192.168.0.253 |
| DNS Info Domains | demo.netapp.com |
| NTP Servers | - |
| ID | 40119464-eba2-11e9-b54a-005056ae6f9e |
| Last Refresh | - |
+---------------------+--------------------------------------+
Now that the software-defined ONTAP Select cluster has been created, you can use and manage this cluster
just like any other NetApp ONTAP system. The following section will review what has been created via the
OnCommand System Manager interface.
3.2 ONTAP Select Verification and Configuration

This section builds on the actions of the first section where you initiated an ONTAP Select cluster creation through
the Deploy VM's CLI. The cluster should be built and accessible at this point. You will validate this to be true, and
work with the new cluster through the same System Manager that is used for NetApp FAS controllers. Finally, you
will use the Deploy utility's GUI to view the cluster that was created, destroy that cluster, and start the creation of
a new cluster.
3.2 Verfiy the new cluster configuration in vCenter

1. To view the ONTAP Select node that was provisioned, open Chrome.
2. Click on the vSphere web client bookmark.
Note: This lab uses self-signed certs, so you need to click the advanced and proceed to.... links
in Chrome as you first connect.
3. Enter username administrator@vsphere.local, and password Netapp1!.
4. Click Login

2
Figure 3-3:
5. Select VMs and Templates.

7
Figure 3-4:
6. Select the ONTAP node VM named cluster3-01.

7. Select the Summary tab and note the IP address is 192.168.0.103. This address will be used in the next
section.
Note: This is the VM containing the single-cluster node you created. Feel free to investigate the
underlying network connections, VM resources, etc.

9
Figure 3-5:
3.2 Use OnCommand System Manager to configure the new cluster to serve out
a CIFS share
Now that the cluster is online, it can be managed with any of the standard NetApp ONTAP management tools.
This example excercise will setup CIFS using System Manager just as you would on a NetApp FAS system.
1. To access System Manager, open a new Chrome tab.
2. Navigate to https://192.168.0.103.
3. Enter username admin, and password Netapp1!.
4. Click Sign In.

1
Figure 3-6:
5. To create a data aggregate, drop down the Storage section.

6. Drop down the Aggregates & Disks section.
7. Select Aggregates.
8. Click Create.

8
Figure 3-7:
9. Enter aggr1 for the “Name”.

10. Click Submit.

9
10
Figure 3-8:
11. To create a Storage Virtual Machine, click SVMs.

12. Click Create.

12
11
Figure 3-9:
13. Enter an “SVM Name” of svm1.

14. Select the “Data Protocols” checkbox to enable CIFS on this SVM.
15. Click Submit & Continue.

13
14
15
Figure 3-10:
16. To configure the SVM's data LIF, click the drop down menu and select Without a subnet.

16
Figure 3-11:
17. Enter the following details as shown, and click OK:

• “IP Address:” 192.168.0.151.
• “Netmask or Prefix:” 255.255.255.0.

17
Figure 3-12:
18. Click Browse... to assign a port for the data LIF.

19. Expand cluster3-1.
20. Select the e0a port.
21. Click OK.

19
20
18
21
Figure 3-13:
22. To configure CIFS, enter the values as shown and click Submit & Continue:
• “CIFS Server Name:” svm1
• “Active Directory:” demo.netapp.com
• “Administrator Name:” administrator
• “Administrator Password:” Netapp1!
• “Share Name:” share1
• “Size:” 20GB

21
Figure 3-14:
23. Enter Netapp1! for the password, and enter Netapp1! once more to confirm.
24. Click Submit & Continue.

23
24
Figure 3-15:
25. Click OK to close the confirmation.

25
Figure 3-16:
26. To test the new CIFS share out, open Explorer.

27. Navigate to \\192.168.0.151\share1.
Note: From here, it's just another ONTAP cluster! Feel free to perform other tasks using
System Manager or CLI. You will find the operational functionality to be just what you expect
from ONTAP. The other NetApp management tools like OnCommand Unified Manager,
Performance Manager, etc. also work with the ONTAP Select clusters.

27
26
Figure 3-17:
3.2 Use Cases for ONTAP Select

Remote/Branch Office (ROBO)
Whether a single-node is used for local data access, or an HA pair with mirrored aggregates, the ROBO solution
can be easily SnapMirrored back to an ONTAP instance (SDS or FAS) in a central datacenter.
Private Cloud
An entire application stack from the application server, to the database server, to the ONTAP storage node can
be provisioned with cloud automation frameworks.
3.3 ONTAP Select GUI Deployment
3.3 Destroy the cluster and start a new cluster creation with the GUI interface
In this section, you will delete cluster3 and use the following steps to create another ONTAP Select node, this
time using the web GUI interface. Please note that this demonstration environment has limitations that prevent
this cluster creation from reliably completing . Even with this limitation, the following steps will show how the same
cluster3 from above would be created using this GUI.
1. To connect to the web GUI for ONTAP Select Deploy, open a new Chrome tab.
2. Navigate to https://192.168.0.109.

3. Enter the user name admin, and password Netapp1!, and click Sign In.
1
2
Figure 3-18:
4. Click the gear icon for cluster3, and select Take Offline.

4
Figure 3-19:
5. Click Yes to confirm taking the cluster offline.

5
Figure 3-20:
6. Wait ~2 minutes for the cluster to become offline, then click the Refresh button.
7. The yellow warning and gear icon should become available. If they are not visible as shown, wait another
minute and refresh again. Once it becomes available, click the gear icon and select Delete.

6
Figure 3-21:
8. Click Yes to confirm the cluster deletion.

Note: The cluster deletion will also take ~5 minutes. Wait until cluster3 no longer shows in
the display before continuing.

8
Figure 3-22:
9. Click Refresh after ~5 minutes and confirm that cluster3 no longer shows before continuing.
10. Once cluster3 is deleted, click Create Cluster.

9
10
Figure 3-23:
11. Enter the following information in the fields as shown:

• “Cluster Name:” cluster3.
• “Cluster Size:” Single node cluster.
• "Configuration:" ESX.
• “ONTAP Image:” 9.6P2.
• “IPv4 Address:” 192.168.0.103.
• “Netmask:” 255.255.255.0.
• “Gateway:” 192.168.0.1.
• “Domain Names:” demo.netapp.com.
• “Server IP Addresses:” 192.168.0.253.
• “NTP Server:” 192.168.0.1.
12. Click Done.

11
12
Figure 3-24:
13. Scroll down to the Node Setup section and fill in the following values:
• "Licenses:" Evaluation Mode
• "Hosts:" 192.168.0.51
• "Management Network:" ONTAP-external
• "Data Network1:" ONTAP-external
• "Data Network2:" ONTAP-internal

13
Figure 3-25:
14. Scroll down to the Storage section, fill in the following values:
• "Storage Pool Capacity:" 500 GB.
• "Storage Pool (cluster3-01):" esx1data.
15. Click Done.

14
15
Figure 3-26:
16. Click Next.

16
Figure 3-27:
17. Enter Netapp1! for the password and confirm by typing it in a second time.
Note:
The Create Cluster button would be the last step in the process, but there is no need to select
it now because the limitations of this demonstration environment prevent successful creation of
the cluster. In a real-world scenario (without nested virtualization like we have here)... you would
have the choice of creating clusters through the CLI, or the GUI.

17
Figure 3-28:

4 References
The following references were used in writing this lab guide.
• ONTAP Select:
• Licensing:
https://library.netapp.com/ecmdocs/ECMLP2600453/html/GUID-C75CB811-8326-4A20-
A2CD-D26303746D06.html
• Quick Start Guide:
https://library.netapp.com/ecm/ecm_download_file/ECMLP2761659
• Technical Report:
http://www.netapp.com/us/media/tr-4517.pdf

5 Version History
Version Date Document Version History
1.0.0 October 2019 Initial Release
1.0.1 November 2019 Minor guide updates

Refer to the Interoperability Matrix Tool (IMT) on the NetApp Support site to validate that the exact
product and feature versions described in this document are supported for your specific environment.
The NetApp IMT defines the product components and versions that can be used to construct
configurations that are supported by NetApp. Specific results depend on each customer's installation in
accordance with published specifications.
NetApp provides no representations or warranties regarding the accuracy, reliability, or serviceability of any
information or recommendations provided in this publication, or with respect to any results that may be obtained
by the use of the information or observance of any recommendations provided herein. The information in this
document is distributed AS IS, and the use of this information or the implementation of any recommendations or
techniques herein is a customer’s responsibility and depends on the customer’s ability to evaluate and integrate
them into the customer’s operational environment. This document and the information contained herein may be
used solely in connection with the NetApp products discussed in this document.
®
Go further, faster
© 2019NetApp, Inc. All rights reserved. No portions of this document may be reproduced without prior written consent
of NetApp, Inc. Specifications are subject to change without notice. NetApp, the NetApp logo, Data ONTAP®,
ONTAP®, OnCommand®, SANtricity®, FlexPod®, SnapCenter®, and SolidFire® are trademarks or registered
trademarks of NetApp, Inc. in the United States and/or other countries. All other brands or products are trademarks or
registered trademarks of their respective holders and should be treated as such.

Deploying ONTAP Select v1.0.1

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Deploying ONTAP Select v1.0.1

Uploaded by

Copyright:

Available Formats

Deploying ONTAP Select

November 2019 | SL10579 Version 1.0.1

1.1 Lab Objectives........................................................................................................................... 3

3.1 ONTAP Select CLI Deployment................................................................................................ 5

3.2 ONTAP Select Verification and Configuration...................................................................... 11

3.3 ONTAP Select GUI Deployment............................................................................................. 26