Installation and User Guide

OnCommand Cloud Manager 3.0 Installation and User Guide For Volume Management September 2016 215-11109_B0 doccomments@netapp.com

Table of Contents 3 Contents Deciding whether to use this guide... 4 Product overview... 5 How the Volume View works... 6 How an ONTAP Cloud HA configuration provides non-disruptive operations... 6 How storage works in an ONTAP Cloud HA pair... 8 Cloud Manager REST APIs... 9 Installation and volume management workflow... 10 Preparing for installation and setup... 11 Preparing your AWS environment... 11 AWS networking requirements... 12 AWS networking requirements for ONTAP Cloud HA configurations... 13 Granting AWS permissions to Cloud Manager... 15 Cloud Manager software requirements... 16 Installation and setup worksheet... 18 Installing OnCommand Cloud Manager... 19 Launching a Cloud Manager instance in a standard AWS region... 19 Installing Cloud Manager on an existing Linux host... 20 Setting up OnCommand Cloud Manager... 22 Registering for support... 25 Managing NFS volumes... 27 Logging in to Cloud Manager... 27 How Cloud Manager allocates cloud resources... 28 How ONTAP Cloud licenses impact available capacity and allocation of AWS resources... 29 Creating NFS volumes... 30 Mounting volumes to Linux hosts... 32 Cloning volumes... 32 Managing data access to volumes... 32 Deleting volumes... 33 Viewing and modifying AWS resources... 33 Changing the management view... 34 Updating Cloud Manager to the latest version... 35 Copyright information... 36 Trademark information... 37 How to send comments about documentation and receive update notifications... 38 Index... 39

4 Deciding whether to use this guide The OnCommand Cloud Manager Installation and User Guide for Volume Management describes how to install and use Cloud Manager in the Volume View. This view provides an interface for users who simply want to create volumes and do not want to manage storage systems, and are comfortable with Cloud Manager making capacity allocation decisions. The following image shows the Volume View in Cloud Manager: If you want full control of ONTAP Cloud systems, you should install and use Cloud Manager in the Storage System View: For instructions, see the OnCommand Cloud Manager 3.0 Installation and Setup Guide for Storage System Management and the OnCommand Cloud Manager 3.0 Storage System Management Guide.

5 Product overview OnCommand Cloud Manager provides simplified management of cloud storage environments built on NetApp. You can use Cloud Manager to manage data across your hybrid cloud, which includes full control of ONTAP Cloud systems, or you can simply provision volumes and let Cloud Manager handle the rest. When you set up Cloud Manager, you can choose between two management views: the Storage System View and the Volume View. Storage System View You can use Cloud Manager in this view to have full control of ONTAP Cloud systems: Configure and launch ONTAP Cloud instances in Amazon Web Services (AWS) Provision NFS and CIFS storage Replicate data across a hybrid cloud environment: between on-premises ONTAP clusters, ONTAP Cloud systems, and NetApp Private Storage for Cloud configurations Manage ONTAP Cloud systems as needed, which includes capacity allocation decisions, simplified upgrades, cost monitoring, and several other tasks Volume View The Volume View enables you to simply specify the NFS volume that you need and then Cloud Manager handles the rest: it deploys ONTAP Cloud systems as needed and it automatically makes capacity allocation decisions as volumes grow. This view gives you the benefits of enterprise-class storage in the cloud with very little storage management. Where to deploy Cloud Manager Cloud Manager can run in AWS or in your network. Cloud Manager must run in the AWS GovCloud (US) region if you want to launch ONTAP Cloud instances in AWS GovCloud (US). Note: The Volume View is not supported in the AWS GovCloud (US) region. The following image shows Cloud Manager running in AWS and managing an ONTAP Cloud system and data replication to and from ONTAP clusters:

6 OnCommand Cloud Manager 3.0 Installation and User Guide How the Volume View works The Volume View simplifies storage management: you specify the NFS volume that you need and Cloud Manager creates ONTAP Cloud systems and makes storage capacity decisions as volumes grow. The following image shows how you interact with Cloud Manager in the Volume View: 1. You create NFS volumes. 2. Cloud Manager launches ONTAP Cloud instances in AWS for new volumes or it creates volumes on existing instances. It also purchases physical EBS storage for the volumes. 3. You make the volumes available to your hosts and applications. 4. Cloud Manager makes capacity allocation decisions as your volumes grow. This means that you simply need to interact with volumes (the box on the left), while Cloud Manager interacts with the storage system and its underlying storage (the box on the right). How an ONTAP Cloud HA configuration provides nondisruptive operations An ONTAP Cloud HA configuration ensures high availability of your data in case of software, storage, and networking failures. HA components An ONTAP Cloud HA configuration includes the following components: Two ONTAP Cloud systems (nodes) whose data is synchronously mirrored between each other. A mediator instance that provides a communication channel between the nodes to assist in storage takeover and giveback processes. Note: The mediator instance runs the Linux operating system on a t2.micro instance and uses one EBS magnetic disk that is approximately 8 GB.

Product overview 7 Three floating IP addresses that can move between nodes, which enables storage failover for NFS and CIFS. Note: One floating IP address is for cluster management, one is for NFS/CIFS data on node 1, and one is for NFS/CIFS data on node 2. The following image shows the relationship between these components: Each of these components must be deployed properly in AWS. AWS networking requirements for ONTAP Cloud HA configurations on page 13 Storage takeover and giveback If a node goes down, the other node can serve data for its partner to provide continued data service. Clients can access the same data from the partner node because the data was synchronously mirrored to the partner. When takeover occurs in a NAS configuration, the node's floating IP address that clients use to access data moves to the other node. The following image depicts storage takeover in a NAS configuration. If node 2 goes down, the floating IP address for node 2 moves to node 1.

8 OnCommand Cloud Manager 3.0 Installation and User Guide After the node reboots, the partner must resync data before it can return the storage. The time that it takes to resync data depends on how much data was changed while the node was down. RPO and RTO An ONTAP Cloud HA configuration maintains high availability of your data as follows: The recovery point objective (RPO) is 0 seconds. Your data is transactionally consistent with no data loss. The recovery time objective (RTO) is 60 seconds. In the event of an outage, data should be available in 60 seconds or less. How storage works in an ONTAP Cloud HA pair Unlike an ONTAP cluster, storage in an ONTAP Cloud HA pair is not shared between nodes. Instead, data is synchronously mirrored between the nodes so that the data is available in the event of failure. Storage allocation When you create a new volume and additional disks are required, Cloud Manager allocates the same number of disks to both nodes, creates a mirrored aggregate, and then creates the new volume. For example, if two disks are required for the volume, Cloud Manager allocates two disks per node for a total of four disks. Storage configurations You can use an ONTAP Cloud HA pair as an active-active configuration, in which both nodes serve data to clients, or as an active-passive configuration, in which the passive node responds to data requests only if it has taken over storage for the active node. Note: You can set up an active-active configuration only when using Cloud Manager in the Storage System View. Performance expectations for an ONTAP Cloud HA configuration An ONTAP Cloud HA configuration synchronously replicates data between nodes, which consumes network bandwidth. As a result, you can expect the following performance in comparison to a singlenode ONTAP Cloud configuration: For HA configurations that serve data from only one node, read performance is comparable to the read performance of a single-node configuration, whereas write performance is lower. For HA configurations that serve data from both nodes, read performance is higher than the read performance of a single-node configuration, and write performance is the same or higher. NetApp Technical Report 4383: Performance Characterization of ONTAP Cloud with Application Workloads Client access to storage in an HA pair Clients should access volumes by using the floating IP address of the node on which the volume resides. If clients access a volume using the floating IP address of the partner node, traffic goes between both nodes, which reduces performance. Important: If you move a volume between nodes in an HA pair, you should remount the volume by using the floating IP address of the other node. Otherwise, you can experience reduced performance. If clients support NFSv4 referrals or folder redirection for CIFS, you can enable those features on the ONTAP Cloud systems to avoid remounting the volume. For details, see ONTAP documentation.

Product overview 9 You can easily identify the correct IP address from Cloud Manager: Cloud Manager REST APIs Cloud Manager includes REST APIs that enable software developers to automate the management of NetApp storage in the cloud. There is an API for every action that is available from the user interface. Cloud Manager provides interactive API documentation using the Swagger interface. A link to the API documentation is available in the lower-right corner of the console: You can also find an overview, examples, and an API reference in the OnCommand Cloud Manager 3.0 API Developer Guide.

10 Installation and volume management workflow Before you can start creating volumes for your applications, you need to prepare your environment, install Cloud Manager, and then set it up.

11 Preparing for installation and setup Before you install and set up Cloud Manager, you must prepare your environment and understand the information that you need for installation and setup. Steps 1. Prepare your AWS environment on page 11 Your AWS environment must meet a few requirements so that Cloud Manager and ONTAP Cloud operate correctly in AWS. 2. Review Cloud Manager requirements on page 16 You must verify support for your configuration, which includes host requirements, web browser requirements, EC2 instance requirements, and so on. Most of this information is available in the NetAppInteroperability Matrix; however, because you might not have a NetApp Support Site login, a minimum amount of information is provided to get you started. 3. Gather information for installation and setup on page 18 You need to enter information about your environment when you install and set up Cloud Manager. You can use a worksheet to collect the information that you need. Preparing your AWS environment Your AWS environment must meet a few requirements so that Cloud Manager and ONTAP Cloud operate correctly in AWS. Before you begin You should be familiar with Virtual Private Clouds (VPCs) and subnets. AWS Documentation: Your VPC and Subnets Steps 1. Set up a VPC that includes one or more subnets that have outbound Internet access. For a list of requirements and tips, see AWS networking requirements on page 12. If you want to create HA volumes, see AWS networking requirements for ONTAP Cloud HA configurations on page 13. 2. Grant the required permissions so that Cloud Manager can perform operations in AWS. Granting AWS permissions to Cloud Manager on page 15 3. Depending on your storage needs, request an increase to default AWS limits. By default, AWS limits accounts to 20 instances and 20 TB of EBS storage. Amazon Web Services (AWS) Documentation: AWS Service Limits Amazon Web Services (AWS): Amazon EC2 Service Limits Report Now Available 4. If you want to launch Cloud Manager in AWS, create an EC2 key pair if you do not have one. AWS Documentation: Amazon EC2 Key Pairs 5. Subscribe to ONTAP Cloud in AWS: a. Go to the AWS Marketplace pages for ONTAP Cloud: AWS Marketplace: ONTAP Cloud for AWS

12 OnCommand Cloud Manager 3.0 Installation and User Guide AWS Marketplace: ONTAP Cloud for AWS - High Availability b. Review the terms, and then click Accept. You cannot create volumes from Cloud Manager unless you subscribe to the ONTAP Cloud software. AWS networking requirements You must set up your AWS networking so that Cloud Manager can create volumes. Virtual Private Cloud (VPC) setup The easiest way to set up your AWS networking is to choose one of the common VPC scenarios by using the VPC wizard. AWS Documentation: VPC Wizard Scenarios for Amazon VPC Subnets and internet access You can choose whether the subnets in your VPC are public or private, but they must allow outbound Internet access to enable communication between Cloud Manager and AWS services, to enable software upgrades, and to enable technical support from NetApp for your volumes. You can enable Internet access by using an Internet gateway, NAT device, VPN, or proxy server. AWS Documentation: Adding an Internet Gateway to Your VPC AWS Documentation: NAT Note the following about providing Internet access for NetApp AutoSupport, which is a troubleshooting tool that proactively monitors the health of your storage: If you use a NAT instance, you must define an inbound security group rule that allows HTTPS traffic from the private subnet to the Internet. AWS Documentation: NAT Instances If you use a VPN, routing and firewall policies must allow AWS HTTP/HTTPS traffic to support.netapp.com. If you plan to install Cloud Manager in one subnet and create volumes in another subnet, then there must be a route between those subnets. If you install Cloud Manager in a private subnet, the web browser from which you access Cloud Manager must have a connection to that AWS subnet. Security groups You do not need to create security groups because Cloud Manager does that for you. Example setup The following example shows Cloud Manager in a public subnet, volumes in a private subnet, an Internet gateway that connects the VPC to the internet, and a NAT device that enables outbound Internet traffic from the private subnet:

Preparing for installation and setup 13 AWS networking requirements for ONTAP Cloud HA configurations Additional AWS networking requirements apply to ONTAP Cloud HA configurations. You should review these requirements before you create an HA volume because you must enter the networking details in Cloud Manager. Availability Zones To ensure high availability of your data, you must use a dedicated Availability Zone for each ONTAP Cloud instance and the mediator instance, which provides a communication channel between the HA pair. Using the same Availability Zone for more than one instance is not supported. It does not provide high availability for all the required protection scenarios. If your region does not have three Availability Zones, try to request more from AWS. Outbound Internet access The mediator instance must have outbound Internet access so it can communicate with AWS to assist with storage failover. Floating IP addresses ONTAP Cloud HA configurations use floating IP addresses for storage failover between nodes when using NFS and CIFS. You must specify three floating IP addresses that are outside of the CIDR blocks for all VPCs in the AWS region where you deploy the HA configuration. You can think of the floating IP addresses as a logical subnet that is outside of the VPCs in your region. Note: One floating IP address is for cluster management, one is for NFS/CIFS data on node 1, and one is for NFS/CIFS data on node 2. Note: If you use SnapDrive for Windows or SnapCenter with an ONTAP Cloud HA pair, a floating IP address is also required for the SVM management LIF. You must create this LIF after you launch the HA pair.

14 OnCommand Cloud Manager 3.0 Installation and User Guide The following example shows the relationship between floating IP addresses and the VPCs in an AWS region. While the floating IP addresses are outside the CIDR blocks for all VPCs, they are routable to subnets through route tables. You must manually enter the floating IP addresses in Cloud Manager when you create an ONTAP Cloud HA working environment. Cloud Manager allocates the IP addresses to the HA pair when it launches the system. Route tables After you specify the floating IP addresses in Cloud Manager, you must select the route tables that should include routes to the floating IP addresses. This enables client access to the ONTAP Cloud HA pair. If you have just one route table for the subnets in your VPC (the main route table), then Cloud Manager automatically adds the floating IP addresses to that route table. If you have more than one route table, it is very important to select the correct route tables. Otherwise, some clients might not have access to the ONTAP Cloud HA pair. For example, you might have two subnets that are associated with different route tables. If you select route table A, but not route table B, then clients in the subnet associated with route table A can access the HA pair, but clients in the subnet associated with route table B cannot access the HA pair. Amazon Web Services (AWS) Documentation: Route Tables Connection to NetApp management tools ONTAP Cloud HA configurations use a private, floating IP address for the cluster management interface. Therefore, external routing is not available. If you want to use NetApp management tools with ONTAP Cloud HA configurations, they must be part of the same routing domain. Example configuration The following image shows an optimal ONTAP Cloud HA configuration in AWS operating as an active-passive configuration:

Preparing for installation and setup 15 Granting AWS permissions to Cloud Manager Cloud Manager needs permissions to perform actions in AWS. The Cloud Manager IAM policy defines the AWS actions and resources that Cloud Manager is allowed to use. You must grant the permissions defined in the IAM policy by associating an IAM role with the Cloud Manager instance or by specifying AWS access keys for each Cloud Manager user account. If you provide any fewer than the permissions defined in the IAM policy, then you must perform any operations that Cloud Manager cannot perform. For example, if you do not provide permissions to delete AWS resources, then you must delete those resources yourself. Choices Setting up an IAM role for the Cloud Manager instance on page 15 Granting permissions to IAM users on page 16 Setting up an IAM role for the Cloud Manager instance You can grant AWS permissions to Cloud Manager by associating an IAM role with the Cloud Manager instance when you launch it in AWS. Before you launch the instance, you must create an IAM policy and attach it to an IAM role. About this task You cannot associate an IAM role with an already running instance of Cloud Manager.

16 OnCommand Cloud Manager 3.0 Installation and User Guide Steps 1. Download the Cloud Manager IAM policy from the following location: NetApp OnCommand Cloud Manager: AWS IAM Policy 2. From the IAM console, create your own policy by copying and pasting the text from the Cloud Manager IAM policy. 3. Create an IAM role with the role type Amazon EC2 and attach the policy that you created in the previous step. Result You now have an IAM role that you can associate with the Cloud Manager instance when you launch it in AWS. After you finish When you launch the Cloud Manager instance in a standard AWS region, you must choose Custom Launch to launch the instance from the EC2 console. Launching from the EC2 console enables you to associate the IAM role with the Cloud Manager instance. Granting permissions to IAM users You can grant AWS permissions to Cloud Manager by specifying AWS access keys for IAM users when you create Cloud Manager user accounts. Before you create the Cloud Manager user accounts, you must grant the required permissions to those IAM users by using the Cloud Manager IAM policy. About this task If you create a Cloud Manager user and enter access keys for an AWS root account user, then that user already has the required permissions. Steps 1. Download the Cloud Manager IAM policy from the following location: NetApp OnCommand Cloud Manager: AWS IAM Policy 2. From the IAM console, create your own policy by copying and pasting the text from the Cloud Manager IAM policy. 3. Attach the policy to IAM users or groups. AWS Documentation: Managing IAM Policies Result IAM users now have the required permissions. When you create Cloud Manager user accounts, you must specify the AWS access keys for those IAM users. Cloud Manager software requirements You must verify support for your configuration, which includes host requirements, web browser requirements, EC2 instance requirements, and so on. Most of this information is available in the NetApp Interoperability Matrix; however, because you might not have a NetApp Support Site login, a minimum amount of information is provided to get you started. If you have a NetApp Support Site login, go to the NetApp Interoperability Matrix Tool to search for supported Cloud Manager configurations.

Preparing for installation and setup 17 EC2 instance requirements Cloud Manager is supported on the t2.medium and m3.medium instance types. Cloud Manager can run on other EC2 instance types, but they are not supported. Host requirements To run Cloud Manager on an existing host, the physical or virtual machine must meet minimum requirements: Component Hypervisor Requirement A bare metal or hosted hypervisor that is certified to run Red Hat Enterprise Linux Red Hat Solution: Which hypervisors are certified to run Red Hat Enterprise Linux? Operating system Red Hat Enterprise Linux 7.1 or 7.2 CPU RAM Free disk space 2.27 GHz or higher with two cores 4 GB 50 GB Web browser requirements You must access the Cloud Manager console from a supported web browser: Web browser Minimum supported version Google Chrome 48 Microsoft Edge 20 Microsoft Internet Explorer 11 Mozilla Firefox 43 For the full list of supported web browser versions, see the NetApp Interoperability Matrix Tool. Port requirements Before you install Cloud Manager on an existing host, you must verify that the following ports are available. If other services are using these ports, Cloud Manager installation fails. Port Purpose 80 Provides HTTP access to the Cloud Manager web console. 443 Provides HTTPS access to the Cloud Manager web console. 3306 Used by a MySQL database that stores Cloud Manager data. 8080 Used by the Simplicator service, which is an API proxy for Cloud Manager. There is a potential conflict with port 3306. If another instance of MySQL is running on the host, it uses port 3306 by default. You must change the port that the existing MySQL instance uses. You can change the default HTTP and HTTPS ports when you install Cloud Manager. You cannot change the default port for the MySQL database. If you change the HTTP and HTTPS ports, you must ensure that users can access the Cloud Manager web console from a remote host: In AWS, modify the instance's security group to allow inbound connections through the ports.

18 OnCommand Cloud Manager 3.0 Installation and User Guide Specify the port when you enter the URL to the Cloud Manager web console. Installation and setup worksheet You need to enter information about your environment when you install and set up Cloud Manager. You can use a worksheet to collect the information that you need. Information needed to launch the Cloud Manager instance in AWS Information Instance type Virtual Private Cloud Subnet EC2 key pair Your value

19 Installing OnCommand Cloud Manager You can install the Cloud Manager software by launching a Cloud Manager instance in Amazon Web Services (AWS) or by installing Cloud Manager on an existing Linux host. The standard method is to launch a Cloud Manager instance in AWS using the AMI. Choices Launching a Cloud Manager instance in a standard AWS region on page 19 Installing Cloud Manager on an existing Linux host on page 20 Launching a Cloud Manager instance in a standard AWS region You can use the Cloud Manager AMI from the AWS Marketplace to launch an EC2 instance in a standard AWS region (a region other than the AWS GovCloud (US) region). This gives you access to the Cloud Manager software, which is automatically installed on the instance. Before you begin You must have an EC2 key pair. AWS uses the key pair to secure the instance's login information. Amazon Web Services (AWS) Documentation: Amazon EC2 Key Pairs If you want to assign a public IP address to the Cloud Manager instance and use the AWS 1-Click Launch option, the public subnet must be already enabled to automatically assign public IP addresses. Amazon Web Services (AWS) Documentation: IP Addressing in Your VPC Otherwise, you must use the Manual Launch option to assign a public IP address to the instance. Steps 1. Go to the Cloud Manager page on the AWS Marketplace. AWS Marketplace: OnCommand Cloud Manager 2. Keep the default delivery method (Single AMI), and then click Continue. You should use the advanced delivery methods only when using Cloud Manager in the Storage System View. 3. Depending on how you want to grant AWS permissions to Cloud Manager, launch the instance from the 1-Click Launch tab or the Custom Launch tab: Choice You do not want to associate the instance with an IAM role. You want to specify AWS keys for the Cloud Manager user account. Steps a. On the 1-Click Launch tab, specify settings for the instance. Note the following: The t2.medium instance type is recommended. Under security group, select Create new based on seller settings to create a pre-defined security group that includes the rules required by Cloud Manager. b. Click Accept Terms and Launch with 1-Click.

20 OnCommand Cloud Manager 3.0 Installation and User Guide Choice You want to associate the instance with an IAM role. Steps a. On the Custom Launch tab, click Launch with EC2 Console for your region. b. Choose an instance type. The t2.medium instance type is recommended. c. Select a VPC, subnet, IAM role, and other configuration options that meet your requirements. d. Keep the default storage options. e. Enter tags for the instance, if desired. f. Specify the required connection methods for the Cloud Manager instance: SSH, HTTP, and HTTPS. g. Click Launch. Result AWS launches the software with the specified settings. The Cloud Manager instance and software should be running in approximately five minutes. After you finish Log in to Cloud Manager by using a web browser and complete the Setup wizard. Related tasks Setting up OnCommand Cloud Manager on page 22 Installing Cloud Manager on an existing Linux host You can install the Cloud Manager software on an existing Linux host in your network or in AWS. This is an alternative to running Cloud Manager on a new AWS instance launched from the Cloud Manager AMI. About this task Root privileges are not required to install Cloud Manager. Cloud Manager installs the AWS command line tools (awscli) to enable recovery procedures from NetApp support. If you receive a message that installing the awscli failed, you can safely ignore the message. Cloud Manager can operate successfully without the tools. Steps 1. Download the software from the NetApp Support Site, and then copy it to the Linux host. NetApp Downloads: Software For help with connecting and copying the file to an EC2 instance in AWS, see AWS Documentation: Connecting to Your Linux Instance Using SSH. 2. Assign permissions to execute the script.

Installing OnCommand Cloud Manager 21 Example chmod +x OnCommandCloudManager-V3.0.0.sh 3. Run the installation script:./oncommandcloudmanager-v3.0.0.sh [silent] [proxy=ipaddress] [proxyport=port] [proxyuser=user_name] [proxypwd=password] silent runs the installation without prompting you for information. proxy is required if the Cloud Manager host is behind a proxy server. proxyport is the port for the proxy server. proxyuser is the user name for the proxy server, if basic authentication is required. proxypwd is the password for the user name that you specified. 4. Unless you specified the silent parameter, type Y to continue the script, and then enter the HTTP and HTTPS ports when prompted. If you change the HTTP and HTTPS ports, you must ensure that users can access the Cloud Manager web console from a remote host: In AWS, modify the instance's security group to allow inbound connections through the ports. Specify the port when you enter the URL to the Cloud Manager web console. Result Cloud Manager is now installed. At the end of the installation, the Cloud Manager service (occm) restarts twice if you specified a proxy server. After you finish Log in to Cloud Manager using a web browser, and then complete the Setup wizard. Related tasks Setting up OnCommand Cloud Manager on page 22

22 Setting up OnCommand Cloud Manager The Cloud Manager Setup wizard appears when you access the web console for the first time. The wizard enables you to create a user account and your first volume. About this task If you recently launched a Cloud Manager instance in Amazon Web Services (AWS), the Cloud Manager console should be available a few minutes after the AWS instance starts. Steps 1. Open a web browser and enter the following URL: https://ipaddress:port You need to use this URL each time that you log in to Cloud Manager. ipaddress can be localhost, a private IP address, or a public IP address, depending on the configuration of the Cloud Manager host. For example, if Cloud Manager is installed in AWS and the instance does not have a public IP address, you must enter a private IP address from a host in AWS that has a connection to the Cloud Manager host. port is required if you changed the default HTTP (80) or HTTPS (443) ports. For example, if the HTTPS port was changed to 8443, you would enter https://ipaddress:8443 After you enter the URL, the Cloud Manager Setup wizard appears: 2. Click Volume View. 3. On the Create your user account page, specify details to create your user account, choose whether to enable automatic updates, read and approve the End User License Agreement, and then click Create. The following table describes fields for which you might need guidance:

Setting up OnCommand Cloud Manager 23 Field Email Address AWS Credentials Automatically update Cloud Manager to the latest version Description Your user name is your email address. Cloud Manager does not send emails to this address. If you did not associate Cloud Manager with an IAM role, you must specify your AWS credentials so Cloud Manager can perform AWS operations. Granting AWS permissions to Cloud Manager on page 15 You should enable this field to make sure that you are running the latest version. Cloud Manager automatically installs minor updates at 12:00 midnight if no operations are running. Major updates (for example, 3.0 to 4.0) are not automatically installed. You must manually update Cloud Manager when a new major version is available. 4. On the Create New Volume page, select a volume type: Option Create Volume Create HA volume Description Creates a volume attached to a single AWS instance. Creates a volume attached to a single AWS instance and mirrored to another instance to provide high availability in case of failures. Press the Info icon to see additional details about the instances required for an HA volume. 5. If you chose Create Volume, specify details for your first volume, and then click Create. The following table describes fields for which you might need guidance: Field Size AWS Disk Type Description The maximum size for the initial volume is 17.2 TB. Thin provisioning is automatically enabled on the volume, which enables you to create a volume that is bigger than the physical storage currently available to it. Instead of preallocating storage space, space is allocated to each volume as data is written. General Purpose (SSD) disks are a good choice when performance is more important than cost (the data is frequently accessed). Magnetic disks are a good choice when cost is more important than performance (the data is infrequently accessed). For details about EBS performance, see Amazon Web Services (AWS) Documentation: EBS Volume Types. In addition to cost and performance, you should take maximum storage capacity into consideration. The EBS raw capacity limit is higher for General Purpose (SSD) disks than it is for Magnetic disks. How ONTAP Cloud licenses impact available capacity and allocation of AWS resources on page 29 The following image shows the Create Volume page filled out:

24 OnCommand Cloud Manager 3.0 Installation and User Guide 6. If you chose Create HA volume, specify details for the volume and then click Create. The following table describes fields for which you might need guidance: Field Size AWS Disk Type Location Nodes and Mediator Floating IP Route Table Description The maximum size for the initial volume is 17.2 TB. Thin provisioning is automatically enabled on the volume, which enables you to create a volume that is bigger than the physical storage currently available to it. Instead of preallocating storage space, space is allocated to each volume as data is written. General Purpose (SSD) disks are a good choice when performance is more important than cost (the data is frequently accessed). Magnetic disks are a good choice when cost is more important than performance (the data is infrequently accessed). For details about EBS performance, see Amazon Web Services (AWS) Documentation: EBS Volume Types. In addition to cost and performance, you should take maximum storage capacity into consideration. The EBS raw capacity limit is higher for General Purpose (SSD) disks than it is for Magnetic disks. How ONTAP Cloud licenses impact available capacity and allocation of AWS resources on page 29 You should choose a VPC that includes three subnets in three separate Availability Zones. AWS networking requirements for ONTAP Cloud HA configurations on page 13 If possible, Cloud Manager chooses separate Availability Zones for each instance because it is the optimal configuration. The IP addresses must be outside of the CIDR block for all VPCs in the region. AWS networking requirements for ONTAP Cloud HA configurations on page 13 If you have more than one route table, it is very important to select the correct route tables. Otherwise, some clients might not have access to the ONTAP Cloud HA pair. AWS networking requirements for ONTAP Cloud HA configurations on page 13 Amazon Web Services (AWS) Documentation: Route Tables The following image shows the Nodes and Mediator page. Each instance is in a separate Availability Zone.

Setting up OnCommand Cloud Manager 25 7. On the ONTAP Cloud Password dialog box, specify a password and tags: a. Enter the password that Cloud Manager should set for each ONTAP Cloud system that it launches in AWS. The password must be at least eight characters and must contain at least one English letter and one number. The password cannot contain non-english letters or the user account name (admin). You need to use this password if you want to access storage systems directly, or if NetApp support personnel needs to help you recover your storage. b. Click Add AWS tag to storage system, enter a key and an optional value, and then add more tags, if needed. Cloud Manager adds the tags to the resources that it allocates in AWS. Tags enable you to categorize your AWS resources. c. Click Save. Result Cloud Manager is now set up and you can create additional volumes, as needed. The initial volume should be ready in approximately 25 minutes because Cloud Manager must launch ONTAP Cloud in AWS. After you finish Register for support. Registering for support You must enter your NetApp Support Site credentials in Cloud Manager before you can get help from NetApp technical support. Entering your credentials registers the ONTAP Cloud systems that host your volumes for support. Steps 1. In the upper right of the Cloud Manager console, click the menu, and then select Support Registration.

26 OnCommand Cloud Manager 3.0 Installation and User Guide 2. Enter your NetApp Support Site user name and password, and then click Register. If you do not have a NetApp Support Site account, follow the link to create an account, and then enter your credentials in Cloud Manager. Result All existing and future ONTAP Cloud systems that host your volumes are now registered for support.

27 Managing NFS volumes You can create, mount, clone, delete, and manage access to NFS volumes using the Cloud Manager user interface or by using the Cloud Manager APIs. Related references Cloud Manager REST APIs on page 9 Logging in to Cloud Manager You can log in to Cloud Manager from any web browser that has a connection to the Cloud Manager host. Steps 1. Open a web browser and enter the following URL: https://ipaddress:port ipaddress can be localhost, a private IP address, or a public IP address, depending on the configuration of the Cloud Manager host. For example, if Cloud Manager is installed in AWS and the instance does not have a public IP address, you must enter a private IP address from a host in AWS that has a connection to the Cloud Manager host. port is required if you changed the default HTTP (80) or HTTPS (443) ports. For example, if the HTTPS port was changed to 8443, you would enter https://ipaddress:8443 After you enter the URL, the Cloud Manager log in screen appears: 2. Enter your email address and password, and then click Log in.

28 OnCommand Cloud Manager 3.0 Installation and User Guide How Cloud Manager allocates cloud resources Cloud Manager allocates cloud resources for you when you create volumes using the Volume View. You should understand how Cloud Manager allocates resources to set cost expectations. Allocation of cloud resources for the initial volume When you create your first volume, Cloud Manager launches an ONTAP Cloud instance or an ONTAP Cloud HA pair in AWS and purchases Amazon EBS storage for the volume: The size of the initial volume determines the EC2 instance type and the number of EBS disks. Allocation of cloud resources for additional volumes When you create additional volumes, Cloud Manager creates the volumes on existing ONTAP Cloud instances or on new ONTAP Cloud instances. Cloud Manager can create a volume on an existing instance if the instance's AWS location and disk type match the requested volume, and if there is enough space. If Cloud Manager creates a volume on an existing instance, it purchases the required EBS storage, which can be 1 TB or larger disks, depending on the requested volume size. If Cloud Manager creates a volume on a new instance, it purchases one to six 1 TB EBS disks, just like it did for the initial volume. NetApp storage efficiency features and storage costs Cloud Manager automatically enables NetApp storage efficiency features on all volumes. These efficiencies can reduce the total amount of storage that you need: Thin provisioning Presents more logical storage to hosts or users than you actually have in your physical storage pool. Instead of preallocating storage space, storage space is allocated dynamically to each volume as data is written. Deduplication Improves efficiency by locating identical blocks of data and replacing them with references to a single shared block. This technique reduces storage capacity requirements by eliminating redundant blocks of data that reside in the same volume. Compression Reduces the physical capacity required to store data by compressing data within a volume on primary, secondary, and archive storage. With these features enabled, you might see a difference between your allocated capacity and the purchased AWS capacity, which can result in storage cost savings.

Managing NFS volumes 29 Capacity allocation decisions that Cloud Manager automatically handles Cloud Manager purchases additional EBS disks as capacity thresholds are exceeded. This happens as your volumes grow. Cloud Manager deletes unused sets of EBS disks if the disks contain no volumes for 12 hours. Cloud Manager moves volumes between sets of disks to avoid capacity issues. In some cases, this requires purchasing additional EBS disks. It also frees space on the original set of disks for new and existing volumes. Actions that require your approval Cloud Manager prompts you for approval if it needs to upgrade to an ONTAP Cloud license that supports a higher EBS raw capacity limit. You are prompted because it requires a reboot, during which I/O is interrupted. Cloud Manager prompts you to delete ONTAP Cloud instances that contain no volumes. Related information NetApp Storage Efficiency: Overview How ONTAP Cloud licenses impact available capacity and allocation of AWS resources When you use Cloud Manager in the Volume View, it might prompt you to change an underlying AWS resource to increase available capacity. That underlying AWS resource is an ONTAP Cloud instance. You might want to know more about ONTAP Cloud licenses to understand how they impact available capacity and allocation of AWS resources. ONTAP Cloud is available in three pay-as-you-go configurations: Explore, Standard, and Premium. When you use Cloud Manager in the Volume View, upgrading an ONTAP Cloud license affects the EC2 instance type and EBS raw capacity limit: License EC2 instance type EBS raw capacity limit Explore r3.xlarge 2 TB Standard m4.2xlarge 10 TB Premium r3.2xlarge Single node systems: 368 TB for SSD 46 TB for Magnetic Per node in an HA pair: 360 TB for SSD 45 TB for Magnetic When Cloud Manager launches an ONTAP Cloud system, it launches an Explore or Standard instance, depending on the initial volume size. As the volumes in those instances grow, Cloud Manager might prompt you to make an AWS instance change which means it needs to upgrade the instance's license to Standard or Premium. Upgrading increases the EBS raw capacity limit, which allows your volumes to grow. Upgrading licenses also impacts the maximum size of the volumes that you can create. For example, you can create a volume up to 34.3 TB for an ONTAP Cloud Standard instance or a 137.5 TB volume for an ONTAP Cloud Premium instance.

30 OnCommand Cloud Manager 3.0 Installation and User Guide Note: Cloud Manager does not launch ONTAP Cloud BYOL instances in the Volume View. You should use Cloud Manager in the Storage System View if you purchased an ONTAP Cloud license. Creating NFS volumes You can use Cloud Manager to create NFS volumes that provide enterprise-class features on top of EBS storage. Steps 1. In the Volumes tab, click Create New Volume. 2. On the Create New Volume page, select a volume type: Option Create Volume Create HA volume Description Creates a volume attached to a single AWS instance. Creates a volume attached to a single AWS instance and mirrored to another instance to provide high availability in case of failures. Click the Info icon to see additional details about the instances required for an HA volume. 3. If you chose Create Volume, specify details for your first volume, and then click Create. The following table describes fields for which you might need guidance: Field Size AWS Disk Type Description The maximum size for the initial volume is 17.2 TB. Thin provisioning is automatically enabled on the volume, which enables you to create a volume that is bigger than the physical storage currently available to it. Instead of preallocating storage space, space is allocated to each volume as data is written. General Purpose (SSD) disks are a good choice when performance is more important than cost (the data is frequently accessed). Magnetic disks are a good choice when cost is more important than performance (the data is infrequently accessed). For details about EBS performance, see Amazon Web Services (AWS) Documentation: EBS Volume Types. In addition to cost and performance, you should take maximum storage capacity into consideration. The EBS raw capacity limit is higher for General Purpose (SSD) disks than it is for Magnetic disks. How ONTAP Cloud licenses impact available capacity and allocation of AWS resources on page 29 The following image shows the Create Volume page filled out:

Managing NFS volumes 31 4. If you chose Create HA volume, specify details for the volume, and then click Create. The following table describes fields for which you might need guidance: Field Size AWS Disk Type Location Nodes and Mediator Floating IP Route Table Description The maximum size for the initial volume is 17.2 TB. Thin provisioning is automatically enabled on the volume, which enables you to create a volume that is bigger than the physical storage currently available to it. Instead of preallocating storage space, space is allocated to each volume as data is written. General Purpose (SSD) disks are a good choice when performance is more important than cost (the data is frequently accessed). Magnetic disks are a good choice when cost is more important than performance (the data is infrequently accessed). For details about EBS performance, see Amazon Web Services (AWS) Documentation: EBS Volume Types. In addition to cost and performance, you should take maximum storage capacity into consideration. The EBS raw capacity limit is higher for General Purpose (SSD) disks than it is for Magnetic disks. How ONTAP Cloud licenses impact available capacity and allocation of AWS resources on page 29 You should choose a VPC that includes three subnets in three separate Availability Zones. AWS networking requirements for ONTAP Cloud HA configurations on page 13 If possible, Cloud Manager chooses separate Availability Zones for each instance because it is the supported and optimal configuration. The IP addresses must be outside of the CIDR block for all VPCs in the region. AWS networking requirements for ONTAP Cloud HA configurations on page 13 If you have more than one route table, it is very important to select the correct route tables. Otherwise, some clients might not have access to the ONTAP Cloud HA pair. AWS networking requirements for ONTAP Cloud HA configurations on page 13 Amazon Web Services (AWS) Documentation: Route Tables The following image shows the Nodes and Mediator page. Each instance is in a separate Availability Zone.

32 OnCommand Cloud Manager 3.0 Installation and User Guide Result Cloud Manager creates the volume on an existing system or on a new system. If a new system is required, creating the volume can take approximately 25 minutes. After you finish Mount the volume to hosts. Mounting volumes to Linux hosts After you create a volume, you should mount it to your hosts so that they can access the volume. Steps 1. In the Volumes tab, place your mouse cursor over the volume, select the menu icon, and then click Mount. 2. Click Copy. 3. On your Linux hosts, modify the copied text by changing the destination directory, and then enter the command to mount the volume. Cloning volumes If you need an instantaneous copy of your data without using a lot of disk space, you can create a clone of an existing volume. The cloned volume is a writable, point-in-time copy that is spaceefficient because it uses a small amount of space for metadata, and then only consumes additional space as data is changed or added. Steps 1. In the Volumes tab, place your mouse cursor over the volume, select the menu icon, and then click Clone. 2. Modify the name of the cloned volume, if needed, and then click Clone. Result Cloud Manager creates a new volume that is a clone of an existing volume. Managing data access to volumes When you create a volume, Cloud Manager makes the volume available to all EC2 instances in the VPC in which the volume was created. You can modify this default value if you need to restrict data access to the volume. Steps 1. In the Volumes tab, place your mouse cursor over the volume, select the menu icon, and then click Manage Access. 2. Modify the volume access list, and then click Save.

Managing NFS volumes 33 Deleting volumes You can delete volumes that you no longer need. Steps 1. In the Volumes tab, place your mouse cursor over the volume, select the menu icon, and then click Delete. 2. Click Delete to confirm that you want to delete the volume. Viewing and modifying AWS resources When you create a new volume, Cloud Manager allocates the AWS instances and EBS storage required for that volume. If required, you can view details about AWS instances and EBS storage, change instance types, and turn instances off and on. Steps 1. Click AWS Resources. The list of AWS instances displays. You can view details such as instance type, AWS location, and the volumes attached to the instance. 2. If required, select the menu icon next to the Status column, and then choose one of the available actions:

34 Changing the management view Cloud Manager provides two management views for its graphical interface: the Storage System View for managing storage systems across a hybrid cloud and the Volume View for creating volumes without having to manage storage systems. You can switch between these views, but those instances should be rare because a single view should meet your needs. Steps 1. In the upper right of the Cloud Manager console, click the menu, and then select View Selection. 2. On the View Selection page, select Storage System View, and then click Switch. Result Cloud Manager switches to the Storage System View. For help using this view, see the OnCommand Cloud Manager 3.0 Storage System Management Guide. Here are a few tips when using the Storage System View: The volumes that you created are hosted by one or more ONTAP Cloud instances. The default name for each instance includes the date and time that Cloud Manager created the instance (for example, COT_17_44_40_Mar_17_16 ). It is possible to create additional user accounts in the Storage System View. However, only a user account with the Cloud Manager Admin role can access the Volume View.