Installation and User Guide - NetApp

OnCommand® Cloud Manager 3.0

Installation and User GuideFor Volume Management

September 2016 | [email protected]

Contents

Deciding whether to use this guide ............................................................. 4Product 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 ..................................... 10Preparing 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 ................................................. 19Launching a Cloud Manager instance in a standard AWS region ............................. 19

Installing Cloud Manager on an existing Linux host ................................................ 20

Setting up OnCommand Cloud Manager ................................................ 22Registering for support .............................................................................................. 25

Managing NFS volumes ............................................................................. 27Logging 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 ............................................................... 34Updating Cloud Manager to the latest version ........................................ 35Copyright information ............................................................................... 36Trademark information ............................................................................. 37How to send comments about documentation and receive update

notifications ............................................................................................ 38Index ............................................................................................................. 39

Table of Contents | 3

Deciding whether to use this guide

The OnCommand Cloud Manager Installation and User Guide for Volume Management describeshow to install and use Cloud Manager in the Volume View. This view provides an interface for userswho simply want to create volumes and do not want to manage storage systems, and are comfortablewith 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 theStorage System View:

For instructions, see the OnCommand Cloud Manager 3.0 Installation and Setup Guide for StorageSystem Management and the OnCommand Cloud Manager 3.0 Storage System Management Guide.

4

https://library.netapp.com/ecm/ecm_download_file/ECMLP2484721



Product overview

OnCommand Cloud Manager provides simplified management of cloud storage environments builton NetApp. You can use Cloud Manager to manage data across your hybrid cloud, which includesfull control of ONTAP Cloud systems, or you can simply provision volumes and let Cloud Managerhandle the rest.

When you set up Cloud Manager, you can choose between two management views: the StorageSystem 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, ONTAPCloud 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 CloudManager handles the rest: it deploys ONTAP Cloud systems as needed and it automatically makescapacity allocation decisions as volumes grow. This view gives you the benefits of enterprise-classstorage 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 systemand data replication to and from ONTAP clusters:

5

How the Volume View worksThe Volume View simplifies storage management: you specify the NFS volume that you need andCloud Manager creates ONTAP Cloud systems and makes storage capacity decisions as volumesgrow.

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 volumeson 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 Managerinteracts with the storage system and its underlying storage (the box on the right).

How an ONTAP Cloud HA configuration provides non-disruptive 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 storagetakeover and giveback processes.

Note: The mediator instance runs the Linux operating system on a t2.micro instance and usesone EBS magnetic disk that is approximately 8 GB.

6 | OnCommand Cloud Manager 3.0 Installation and User Guide

• Three floating IP addresses that can move between nodes, which enables storage failover for NFSand 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 mirroredto the partner.

When takeover occurs in a NAS configuration, the node's floating IP address that clients use toaccess data moves to the other node.

The following image depicts storage takeover in a NAS configuration. If node 2 goes down, thefloating IP address for node 2 moves to node 1.

Product overview | 7

After the node reboots, the partner must resync data before it can return the storage. The time that ittakes 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 samenumber of disks to both nodes, creates a mirrored aggregate, and then creates the new volume. Forexample, if two disks are required for the volume, Cloud Manager allocates two disks per node for atotal of four disks.

Storage configurations

You can use an ONTAP Cloud HA pair as an active-active configuration, in which both nodes servedata to clients, or as an active-passive configuration, in which the passive node responds to datarequests 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 StorageSystem View.

Performance expectations for an ONTAP Cloud HA configuration

An ONTAP Cloud HA configuration synchronously replicates data between nodes, which consumesnetwork bandwidth. As a result, you can expect the following performance in comparison to a single-node ONTAP Cloud configuration:

• For HA configurations that serve data from only one node, read performance is comparable to theread 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 readperformance of a single-node configuration, and write performance is the same or higher.

NetApp Technical Report 4383: Performance Characterization of ONTAP Cloud with ApplicationWorkloads

Client access to storage in an HA pair

Clients should access volumes by using the floating IP address of the node on which the volumeresides. If clients access a volume using the floating IP address of the partner node, traffic goesbetween both nodes, which reduces performance.

Important: If you move a volume between nodes in an HA pair, you should remount the volumeby using the floating IP address of the other node. Otherwise, you can experience reducedperformance. If clients support NFSv4 referrals or folder redirection for CIFS, you can enablethose features on the ONTAP Cloud systems to avoid remounting the volume. For details, seeONTAP documentation.


http://www.netapp.com/us/media/tr-4383.pdf

http://www.netapp.com/us/media/tr-4383.pdf

You can easily identify the correct IP address from Cloud Manager:

Cloud Manager REST APIsCloud Manager includes REST APIs that enable software developers to automate the management ofNetApp 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 theAPI 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 Manager3.0 API Developer Guide.

Product overview | 9

https://library.netapp.com/ecmdocs/ECMLP2484728/html/index.html

https://library.netapp.com/ecmdocs/ECMLP2484728/html/index.html

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.

10

Preparing for installation and setup

Before you install and set up Cloud Manager, you must prepare your environment and understand theinformation that you need for installation and setup.

Steps

1. Prepare your AWS environment on page 11Your AWS environment must meet a few requirements so that Cloud Manager and ONTAP Cloudoperate correctly in AWS.

2. Review Cloud Manager requirements on page 16You must verify support for your configuration, which includes host requirements, web browserrequirements, EC2 instance requirements, and so on. Most of this information is available in theNetAppInteroperability Matrix; however, because you might not have a NetApp Support Sitelogin, a minimum amount of information is provided to get you started.

3. Gather information for installation and setup on page 18You need to enter information about your environment when you install and set up CloudManager. You can use a worksheet to collect the information that you need.

Preparing your AWS environmentYour AWS environment must meet a few requirements so that Cloud Manager and ONTAP Cloudoperate 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 HAconfigurations 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

11

http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_Subnets.html

http://docs.aws.amazon.com/general/latest/gr/aws_service_limits.html

http://aws.amazon.com/about-aws/whats-new/2014/06/19/amazon-ec2-service-limits-report-now-available/

http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-key-pairs.html

https://aws.amazon.com/marketplace/pp/B011KEZ734

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 Cloudsoftware.

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 byusing 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 allowoutbound Internet access to enable communication between Cloud Manager and AWS services, toenable 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 VPCAWS Documentation: NAT

• Note the following about providing Internet access for NetApp AutoSupport, which is atroubleshooting 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 HTTPStraffic 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 tosupport.netapp.com.

• If you plan to install Cloud Manager in one subnet and create volumes in another subnet, thenthere must be a route between those subnets.

• If you install Cloud Manager in a private subnet, the web browser from which you access CloudManager 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, anInternet gateway that connects the VPC to the internet, and a NAT device that enables outboundInternet traffic from the private subnet:


http://aws.amazon.com/marketplace/pp/B01H4LVJ84

http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_Scenarios.html

http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_Internet_Gateway.html

http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/vpc-nat.html

http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_NAT_Instance.html

AWS networking requirements for ONTAP Cloud HA configurations

Additional AWS networking requirements apply to ONTAP Cloud HA configurations. You shouldreview these requirements before you create an HA volume because you must enter the networkingdetails in Cloud Manager.

Availability Zones

To ensure high availability of your data, you must use a dedicated Availability Zone for each ONTAPCloud instance and the mediator instance, which provides a communication channel between the HApair. Using the same Availability Zone for more than one instance is not supported. It does notprovide 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 assistwith storage failover.

Floating IP addresses

ONTAP Cloud HA configurations use floating IP addresses for storage failover between nodes whenusing NFS and CIFS. You must specify three floating IP addresses that are outside of the CIDRblocks for all VPCs in the AWS region where you deploy the HA configuration. You can think of thefloating 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, andone is for NFS/CIFS data on node 2.

Note: If you use SnapDrive for Windows or SnapCenter with an ONTAP Cloud HA pair, a floatingIP address is also required for the SVM management LIF. You must create this LIF after youlaunch the HA pair.

Preparing for installation and setup | 13

The following example shows the relationship between floating IP addresses and the VPCs in anAWS region. While the floating IP addresses are outside the CIDR blocks for all VPCs, they areroutable to subnets through route tables.

You must manually enter the floating IP addresses in Cloud Manager when you create an ONTAPCloud HA working environment. Cloud Manager allocates the IP addresses to the HA pair when itlaunches the system.

Route tables

After you specify the floating IP addresses in Cloud Manager, you must select the route tables thatshould include routes to the floating IP addresses. This enables client access to the ONTAP CloudHA pair.

If you have just one route table for the subnets in your VPC (the main route table), then CloudManager automatically adds the floating IP addresses to that route table. If you have more than oneroute table, it is very important to select the correct route tables. Otherwise, some clients might nothave access to the ONTAP Cloud HA pair.

For example, you might have two subnets that are associated with different route tables. If you selectroute table A, but not route table B, then clients in the subnet associated with route table A can accessthe 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 managementinterface. Therefore, external routing is not available. If you want to use NetApp management toolswith 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 anactive-passive configuration:


http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_Route_Tables.html

Granting AWS permissions to Cloud Manager

Cloud Manager needs permissions to perform actions in AWS. The Cloud Manager IAM policydefines the AWS actions and resources that Cloud Manager is allowed to use. You must grant thepermissions defined in the IAM policy by associating an IAM role with the Cloud Manager instanceor 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 anyoperations that Cloud Manager cannot perform. For example, if you do not provide permissions todelete 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 CloudManager instance when you launch it in AWS. Before you launch the instance, you must create anIAM 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.


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 CloudManager IAM policy.

3. Create an IAM role with the role type Amazon EC2 and attach the policy that you created in theprevious step.

Result

You now have an IAM role that you can associate with the Cloud Manager instance when you launchit in AWS.

After you finish

When you launch the Cloud Manager instance in a standard AWS region, you must choose CustomLaunch to launch the instance from the EC2 console. Launching from the EC2 console enables youto 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 userswhen 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 IAMpolicy.

About this task

If you create a Cloud Manager user and enter access keys for an AWS root account user, then thatuser 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 CloudManager 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, youmust specify the AWS access keys for those IAM users.

Cloud Manager software requirementsYou must verify support for your configuration, which includes host requirements, web browserrequirements, EC2 instance requirements, and so on. Most of this information is available in theNetApp Interoperability Matrix; however, because you might not have a NetApp Support Site login, aminimum 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 forsupported Cloud Manager configurations.


https://mysupport.netapp.com/cloudontap/iampolicies

https://mysupport.netapp.com/cloudontap/iampolicies

http://docs.aws.amazon.com/IAM/latest/UserGuide/ManagingPolicies.html

http://mysupport.netapp.com/matrix

EC2 instance requirements

Cloud Manager is supported on the t2.medium and m3.medium instance types. Cloud Manager canrun 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 minimumrequirements:

Component Requirement

Hypervisor A bare metal or hosted hypervisor that is certified to run Red HatEnterprise Linux

Red Hat Solution: Which hypervisors are certified to run Red HatEnterprise Linux?

Operating system Red Hat Enterprise Linux 7.1 or 7.2

CPU 2.27 GHz or higher with two cores

RAM 4 GB

Free disk space 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 areavailable. 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 CloudManager.

There is a potential conflict with port 3306. If another instance of MySQL is running on the host, ituses 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 cannotchange the default port for the MySQL database. If you change the HTTP and HTTPS ports, youmust 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.


https://access.redhat.com/certified-hypervisors

https://access.redhat.com/certified-hypervisors

http://mysupport.netapp.com/matrix

• Specify the port when you enter the URL to the Cloud Manager web console.

Installation and setup worksheetYou 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 Your value

Instance type

Virtual Private Cloud

Subnet

EC2 key pair


Installing OnCommand Cloud Manager

You can install the Cloud Manager software by launching a Cloud Manager instance in Amazon WebServices (AWS) or by installing Cloud Manager on an existing Linux host. The standard method is tolaunch 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 AWSregion

You can use the Cloud Manager AMI from the AWS Marketplace to launch an EC2 instance in astandard AWS region (a region other than the AWS GovCloud (US) region). This gives you access tothe 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-ClickLaunch option, the public subnet must be already enabled to automatically assign public IPaddresses.Amazon Web Services (AWS) Documentation: IP Addressing in Your VPCOtherwise, 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 StorageSystem View.

3. Depending on how you want to grant AWS permissions to Cloud Manager, launch the instancefrom the 1-Click Launch tab or the Custom Launch tab:

Choice Steps

You do not want to associatethe instance with an IAMrole. You want to specifyAWS keys for the CloudManager user account.

a. On the 1-Click Launch tab, specify settings for the instance. Note thefollowing:

• 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 rulesrequired by Cloud Manager.

b. Click Accept Terms and Launch with 1-Click.

19

http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-key-pairs.html

http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/vpc-ip-addressing.html

https://aws.amazon.com/marketplace/pp/B018REK8QG

Choice Steps

You want to associate theinstance with an IAM role.

a. On the Custom Launch tab, click Launch with EC2 Console foryour region.

b. Choose an instance type.The t2.medium instance type is recommended.

c. Select a VPC, subnet, IAM role, and other configuration options thatmeet 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 Managerinstance: SSH, HTTP, and HTTPS.

g. Click Launch.

Result

AWS launches the software with the specified settings. The Cloud Manager instance and softwareshould 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 hostYou 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 CloudManager 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 fromNetApp 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 AWSDocumentation: Connecting to Your Linux Instance Using SSH.

2. Assign permissions to execute the script.


http://mysupport.netapp.com/NOW/cgi-bin/software

http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AccessingInstancesLinux.html

http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AccessingInstancesLinux.html

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 theHTTP and HTTPS ports when prompted.

If you change the HTTP and HTTPS ports, you must ensure that users can access the CloudManager 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

Installing OnCommand Cloud Manager | 21

Setting up OnCommand Cloud Manager

The Cloud Manager Setup wizard appears when you access the web console for the first time. Thewizard 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 CloudManager 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 theconfiguration of the Cloud Manager host. For example, if Cloud Manager is installed in AWS andthe instance does not have a public IP address, you must enter a private IP address from a host inAWS 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 theHTTPS 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, choosewhether to enable automatic updates, read and approve the End User License Agreement, andthen click Create.

The following table describes fields for which you might need guidance:

22

Field Description

Email Address Your user name is your email address. Cloud Manager does not sendemails to this address.

AWS Credentials If you did not associate Cloud Manager with an IAM role, you mustspecify your AWS credentials so Cloud Manager can perform AWSoperations.

Granting AWS permissions to Cloud Manager on page 15

Automaticallyupdate CloudManager to thelatest version

You should enable this field to make sure that you are running the latestversion. Cloud Manager automatically installs minor updates at 12:00midnight if no operations are running. Major updates (for example, 3.0 to4.0) are not automatically installed. You must manually update CloudManager when a new major version is available.

4. On the Create New Volume page, select a volume type:

Option Description

Create Volume Creates a volume attached to a single AWS instance.

Create HA volume Creates a volume attached to a single AWS instance and mirrored toanother instance to provide high availability in case of failures. Press theInfo icon to see additional details about the instances required for an HAvolume.

5. If you chose Create Volume, specify details for your first volume, and then click Create.


Field Description

Size The maximum size for the initial volume is 17.2 TB.

Thin provisioning is automatically enabled on the volume, which enablesyou to create a volume that is bigger than the physical storage currentlyavailable to it. Instead of preallocating storage space, space is allocated toeach volume as data is written.

AWS Disk Type General Purpose (SSD) disks are a good choice when performance is moreimportant than cost (the data is frequently accessed). Magnetic disks are agood choice when cost is more important than performance (the data isinfrequently accessed). For details about EBS performance, see AmazonWeb Services (AWS) Documentation: EBS Volume Types.

In addition to cost and performance, you should take maximum storagecapacity into consideration. The EBS raw capacity limit is higher forGeneral Purpose (SSD) disks than it is for Magnetic disks.

How ONTAP Cloud licenses impact available capacity and allocation ofAWS resources on page 29

The following image shows the Create Volume page filled out:

Setting up OnCommand Cloud Manager | 23

http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSVolumeTypes.html


6. If you chose Create HA volume, specify details for the volume and then click Create.


Field Description






Location You should choose a VPC that includes three subnets in three separateAvailability Zones.

AWS networking requirements for ONTAP Cloud HA configurations onpage 13

Nodes andMediator

If possible, Cloud Manager chooses separate Availability Zones for eachinstance because it is the optimal configuration.

Floating IP The IP addresses must be outside of the CIDR block for all VPCs in theregion.


Route Table If you have more than one route table, it is very important to select thecorrect route tables. Otherwise, some clients might not have access to theONTAP Cloud HA pair.



The following image shows the Nodes and Mediator page. Each instance is in a separateAvailability Zone.





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 itlaunches in AWS.The password must be at least eight characters and must contain at least one English letter andone 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 NetAppsupport 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 moretags, if needed.Cloud Manager adds the tags to the resources that it allocates in AWS. Tags enable you tocategorize your AWS resources.

c. Click Save.

Result

Cloud Manager is now set up and you can create additional volumes, as needed. The initial volumeshould be ready in approximately 25 minutes because Cloud Manager must launch ONTAP Cloud inAWS.

After you finish

Register for support.

Registering for supportYou must enter your NetApp Support Site credentials in Cloud Manager before you can get helpfrom NetApp technical support. Entering your credentials registers the ONTAP Cloud systems thathost your volumes for support.

Steps

1. In the upper right of the Cloud Manager console, click the menu, and then select SupportRegistration.

Setting up OnCommand Cloud Manager | 25

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 thenenter your credentials in Cloud Manager.

Result

All existing and future ONTAP Cloud systems that host your volumes are now registered for support.


Managing NFS volumes

You can create, mount, clone, delete, and manage access to NFS volumes using the Cloud Manageruser interface or by using the Cloud Manager APIs.

Related references

Cloud Manager REST APIs on page 9

Logging in to Cloud ManagerYou can log in to Cloud Manager from any web browser that has a connection to the Cloud Managerhost.

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 theconfiguration of the Cloud Manager host. For example, if Cloud Manager is installed in AWS andthe instance does not have a public IP address, you must enter a private IP address from a host inAWS 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 theHTTPS 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.

27

How Cloud Manager allocates cloud resourcesCloud 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 anONTAP 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 Cloudinstances or on new ONTAP Cloud instances. Cloud Manager can create a volume on an existinginstance if the instance's AWS location and disk type match the requested volume, and if there isenough 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, justlike it did for the initial volume.

NetApp storage efficiency features and storage costs

Cloud Manager automatically enables NetApp storage efficiency features on all volumes. Theseefficiencies 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 physicalstorage pool. Instead of preallocating storage space, storage space is allocated dynamicallyto each volume as data is written.

Deduplication

Improves efficiency by locating identical blocks of data and replacing them withreferences to a single shared block. This technique reduces storage capacity requirementsby 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 volumeon primary, secondary, and archive storage.

With these features enabled, you might see a difference between your allocated capacity and thepurchased AWS capacity, which can result in storage cost savings.


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 originalset 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 thatsupports 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 andallocation of AWS resources

When you use Cloud Manager in the Volume View, it might prompt you to change an underlyingAWS resource to increase available capacity. That underlying AWS resource is an ONTAP Cloudinstance. You might want to know more about ONTAP Cloud licenses to understand how they impactavailable 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 theEC2 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 Standardinstance, depending on the initial volume size. As the volumes in those instances grow, CloudManager might prompt you to make an AWS instance change which means it needs to upgrade theinstance's license to Standard or Premium. Upgrading increases the EBS raw capacity limit, whichallows 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 volumefor an ONTAP Cloud Premium instance.

Managing NFS volumes | 29

http://www.netapp.com/us/technology/storage-efficiency

Note: Cloud Manager does not launch ONTAP Cloud BYOL instances in the Volume View. Youshould use Cloud Manager in the Storage System View if you purchased an ONTAP Cloud license.

Creating NFS volumesYou can use Cloud Manager to create NFS volumes that provide enterprise-class features on top ofEBS storage.

Steps

1. In the Volumes tab, click Create New Volume.

2. On the Create New Volume page, select a volume type:

Option Description

Create Volume Creates a volume attached to a single AWS instance.

Create HA volume Creates a volume attached to a single AWS instance and mirrored toanother instance to provide high availability in case of failures. Click theInfo icon to see additional details about the instances required for an HAvolume.

3. If you chose Create Volume, specify details for your first volume, and then click Create.


Field Description






The following image shows the Create Volume page filled out:




4. If you chose Create HA volume, specify details for the volume, and then click Create.


Field Description






Location You should choose a VPC that includes three subnets in three separateAvailability Zones.


Nodes andMediator

If possible, Cloud Manager chooses separate Availability Zones for eachinstance because it is the supported and optimal configuration.

Floating IP The IP addresses must be outside of the CIDR block for all VPCs in theregion.


Route Table If you have more than one route table, it is very important to select thecorrect route tables. Otherwise, some clients might not have access to theONTAP Cloud HA pair.



The following image shows the Nodes and Mediator page. Each instance is in a separateAvailability Zone.





Result

Cloud Manager creates the volume on an existing system or on a new system. If a new system isrequired, creating the volume can take approximately 25 minutes.

After you finish

Mount the volume to hosts.

Mounting volumes to Linux hostsAfter 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 thenclick Mount.

2. Click Copy.

3. On your Linux hosts, modify the copied text by changing the destination directory, and then enterthe command to mount the volume.

Cloning volumesIf you need an instantaneous copy of your data without using a lot of disk space, you can create aclone of an existing volume. The cloned volume is a writable, point-in-time copy that is space-efficient because it uses a small amount of space for metadata, and then only consumes additionalspace as data is changed or added.

Steps

1. In the Volumes tab, place your mouse cursor over the volume, select the menu icon, and thenclick 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 volumesWhen you create a volume, Cloud Manager makes the volume available to all EC2 instances in theVPC in which the volume was created. You can modify this default value if you need to restrict dataaccess to the volume.

Steps

1. In the Volumes tab, place your mouse cursor over the volume, select the menu icon, and thenclick Manage Access.

2. Modify the volume access list, and then click Save.


Deleting volumesYou 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 thenclick Delete.

2. Click Delete to confirm that you want to delete the volume.

Viewing and modifying AWS resourcesWhen you create a new volume, Cloud Manager allocates the AWS instances and EBS storagerequired 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 availableactions:


Changing the management view

Cloud Manager provides two management views for its graphical interface: the Storage System Viewfor managing storage systems across a hybrid cloud and the Volume View for creating volumeswithout having to manage storage systems. You can switch between these views, but those instancesshould 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 OnCommandCloud 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 defaultname for each instance includes the date and time that Cloud Manager created the instance (forexample, “COT_17_44_40_Mar_17_16”).

• It is possible to create additional user accounts in the Storage System View. However, only a useraccount with the Cloud Manager Admin role can access the Volume View.

34



Updating Cloud Manager to the latest version

You should enable automatic updates to Cloud Manager, but you can always do a manual updatedirectly from the web console. Cloud Manager obtains the software update from a NetApp-owned S3bucket in AWS.

Before you begin

You should have reviewed the OnCommand Cloud Manager Release Notes to identify newrequirements and changes in support.

About this task

The software update takes a few minutes. Cloud Manager will not be available during the update.

Steps

1. Check whether a new version is available by looking at the lower-right corner of the console:

2. If a new version is available, click Timeline to determine whether any tasks are in progress.

If any tasks are in progress, wait for them to finish before you proceed to the next step.

3. In the lower-right of the console, click New version available.

4. On the Cloud Manager Software Update page, click Update next to the version that you want.

5. Complete the confirmation dialog box, and then click OK:

a. Keep the option to download a backup because you can use it to restore your Cloud Managerconfiguration, if necessary.

b. Read the terms and conditions, and then select the I read and approve the terms andconditions (EULA) check box.

6. When prompted, save the Cloud Manager backup.

Result

Cloud Manager starts the update process. You can log in to the console after a few minutes.

35

Copyright information

Copyright © 1994–2016 NetApp, Inc. All rights reserved. Printed in the U.S.

No part of this document covered by copyright may be reproduced in any form or by any means—graphic, electronic, or mechanical, including photocopying, recording, taping, or storage in anelectronic retrieval system—without prior written permission of the copyright owner.

Software derived from copyrighted NetApp material is subject to the following license anddisclaimer:

THIS SOFTWARE IS PROVIDED BY NETAPP "AS IS" AND WITHOUT ANY EXPRESS ORIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE,WHICH ARE HEREBY DISCLAIMED. IN NO EVENT SHALL NETAPP BE LIABLE FOR ANYDIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIALDAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTEGOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING INANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THEPOSSIBILITY OF SUCH DAMAGE.

NetApp reserves the right to change any products described herein at any time, and without notice.NetApp assumes no responsibility or liability arising from the use of products described herein,except as expressly agreed to in writing by NetApp. The use or purchase of this product does notconvey a license under any patent rights, trademark rights, or any other intellectual property rights ofNetApp.

The product described in this manual may be protected by one or more U.S. patents, foreign patents,or pending applications.

RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by the government is subject torestrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and ComputerSoftware clause at DFARS 252.277-7103 (October 1988) and FAR 52-227-19 (June 1987).

36

Trademark information

NetApp, the NetApp logo, Go Further, Faster, AltaVault, ASUP, AutoSupport, Campaign Express,Cloud ONTAP, Clustered Data ONTAP, Customer Fitness, Data ONTAP, DataMotion, Fitness, FlashAccel, Flash Cache, Flash Pool, FlashRay, FlexArray, FlexCache, FlexClone, FlexPod, FlexScale,FlexShare, FlexVol, FPolicy, GetSuccessful, LockVault, Manage ONTAP, Mars, MetroCluster,MultiStore, NetApp Insight, OnCommand, ONTAP, ONTAPI, RAID DP, RAID-TEC, SANtricity,SecureShare, Simplicity, Simulate ONTAP, Snap Creator, SnapCenter, SnapCopy, SnapDrive,SnapIntegrator, SnapLock, SnapManager, SnapMirror, SnapMover, SnapProtect, SnapRestore,Snapshot, SnapValidator, SnapVault, StorageGRID, Tech OnTap, Unbound Cloud, and WAFL andother names are trademarks or registered trademarks of NetApp, Inc., in the United States, and/orother countries. All other brands or products are trademarks or registered trademarks of theirrespective holders and should be treated as such. A current list of NetApp trademarks is available onthe web.

http://www.netapp.com/us/legal/netapptmlist.aspx

37

http://www.netapp.com/us/legal/netapptmlist.aspx

How to send comments about documentation andreceive update notifications

You can help us to improve the quality of our documentation by sending us your feedback. You canreceive automatic notification when production-level (GA/FCS) documentation is initially released orimportant changes are made to existing production-level documents.

If you have suggestions for improving this document, send us your comments by email.

[email protected]

To help us direct your comments to the correct division, include in the subject line the product name,version, and operating system.

If you want to be notified automatically when production-level documentation is released orimportant changes are made to existing production-level documents, follow Twitter account@NetAppDoc.

You can also contact us in the following ways:

• NetApp, Inc., 495 East Java Drive, Sunnyvale, CA 94089 U.S.

• Telephone: +1 (408) 822-6000

• Fax: +1 (408) 822-4501

• Support telephone: +1 (888) 463-8277

38

mailto:[email protected]

Index

A

about this guidedeciding whether to use 4

access, volumesmanaging 32

Amazon Web Servicesconsiderations for choosing disk types 30granting permissions to IAM users 16how Cloud Manager allocates resources in 28launching Cloud Manager in standard region 19networking requirements for Cloud Manager 12preparing your environment 11setting up an IAM role 15

APIsoverview of 9

audiencefor this guide 4

AWSSee Amazon Web Services

C

Chromesupported versions 16

clones, volumecreating 32

Cloud ManagerSee OnCommand Cloud Manager

commentshow to send feedback about documentation 38

consolelogging in to Cloud Manager 27

CPUrequired for Cloud Manager 16

D

data access, volumesmanaging 32

disk spacerequired for Cloud Manager 16

disk typesconsiderations for choosing 30

documentationhow to receive automatic notification of changes to38how to send feedback about 38

E

EBS storageraw capacity limit 29viewing 33

EC2 instance typesper ONTAP Cloud license 29

F

feedbackhow to send comments about documentation 38

Firefoxsupported versions 16

G

General Purpose (SSD) diskswhat they are 30

H

HA configurationsbest practices 13how storage works 8how they work 6requirements 13

high availabilitySee HA configurations

hosts, Linuxinstalling OnCommand Cloud Manager on existing20

I

IAM rolessetting up for Cloud Manager 15

IAM usersgranting permissions to 16

informationhow to send feedback about improvingdocumentation 38

installationgathering information for 18preparing for OnCommand Cloud Manager 11worksheets 18

installing OnCommand Cloud Manageron existing Linux hosts 20workflow 10

instanceschanging the type of 33turning off 33turning on 33

Internet Explorersupported versions 16

L

licensesONTAP Cloud 29

Linux hostsinstalling OnCommand Cloud Manager on existing20

logging into Cloud Manager 27

Index | 39

M

Magnetic diskswhat they are 30

management viewschanging 34

N

NFS volumescreating 30

O

OnCommand Cloud ManagerAWS networking requirements for 12EC2 instance requirements 16granting AWS permissions to 15host requirements 16how it allocates resources 28how the Volume View works 6information needed to launch in AWS 18installation and volume management workflow 10installing on an existing Linux host 20launching in AWS 19logging in 27preparing for installation and setup 11setting up 22setting up an IAM role for 15supported web browsers 16updating to the latest version 35what it is 5

ONTAP CloudHA best practices 13HA configuration overview 6HA configuration requirements 13HA storage overview 8licenses 29registering for support 25

operating systemrequired for Cloud Manager 16

P

permissionsgranting to IAM users 16

R

RAMrequired for Cloud Manager 16

requirementsOnCommand Cloud Manager 16

S

security groups

requirements for Cloud Manager 12setup

preparing for OnCommand Cloud Manager 11workflow 10

storagehow it works in an HA pair 8

Storage System Viewswitching to 34

subnetsrequirements for Cloud Manager 12

suggestionshow to send feedback about documentation 38

supportregistering for 25

T

Twitterhow to receive automatic notification ofdocumentation changes 38

U

updatesupdating Cloud Manager to the latest version 35

V

views, managementswitching between 34

Virtual Private Cloudsrequirements for Cloud Manager 12

volume managementworkflow 10

volume sizeconsiderations for specifying 30

Volume Viewhow it works 6switching to 34

volumescloning 32deleting 33license impact on maximum size 29managing data access 32mounting 32

volumes, NFScreating 30

W

web browserssupported versions 16

worksheetsinstallation and setup 18


Documents

Installation and User Guide - NetApp