English

Modifying Cloud Volumes ONTAP systems

Contributors netapp-bcammett Download PDF of this page

You might need to change the configuration of Cloud Volumes ONTAP systems as your storage needs change. For example, you can change between pay-as-you-go configurations, change the instance or VM type, and more.

Changing the instance or machine type for Cloud Volumes ONTAP

You can choose from several instance or machine types when you launch Cloud Volumes ONTAP in AWS, Azure, or GCP. You can change the instance or machine type at any time if you determine that it is undersized or oversized for your needs.

About this task
  • Automatic giveback must be enabled on a Cloud Volumes ONTAP HA pair (this is the default setting). If it isn’t, then the operation will fail.

  • Changing the instance or machine type affects cloud provider service charges.

  • The operation restarts Cloud Volumes ONTAP.

    For single node systems, I/O is interrupted.

    For HA pairs, the change is nondisruptive. HA pairs continue to serve data.

    Cloud Manager gracefully changes one node at a time by initiating takeover and waiting for give back. NetApp’s QA team tested both writing and reading files during this process and didn’t see any issues on the client side. As connections changed, we did see retries on the I/O level, but the application layer overcame these short "re-wire" of NFS/CIFS connections.
Steps
  1. From the working environment, click the menu icon, and then click Change license or instance for AWS, Change license or VM for Azure, or Change license or machine for GCP.

  2. If you are using a pay-as-you-go configuration, you can optionally choose a different license.

  3. Select an instance or machine type, select the check box to confirm that you understand the implications of the change, and then click OK.

Result

Cloud Volumes ONTAP reboots with the new configuration.

Changing between pay-as-you-go configurations

After you launch pay-as-you-go Cloud Volumes ONTAP systems, you can change between the Explore, Standard, and Premium configurations at any time by modifying the license. Changing the license increases or decreases the raw capacity limit and enables you to choose from different AWS instance types or Azure virtual machine types.

In GCP, a single machine type is available for each pay-as-you-go configuration. You can’t choose between different machine types.
About this task

Note the following about changing between pay-as-you-go licenses:

  • The operation restarts Cloud Volumes ONTAP.

    For single node systems, I/O is interrupted.

    For HA pairs, the change is nondisruptive. HA pairs continue to serve data.

  • Changing the instance or machine type affects cloud provider service charges.

Steps
  1. From the working environment, click the menu icon, and then click Change license or instance for AWS, Change license or VM for Azure, or Change license or machine for GCP.

  2. Select a license type and an instance type or machine type, select the check box to confirm that you understand the implications of the change, and then click OK.

Result

Cloud Volumes ONTAP reboots with the new license, instance type or machine type, or both.

Moving to an alternate Cloud Volumes ONTAP configuration

If you want to switch between a pay-as-you-go subscription and a BYOL subscription or between a single Cloud Volumes ONTAP system and an HA pair, then you need to deploy a new system and then replicate data from the existing system to the new system.

Steps
  1. Create a new Cloud Volumes ONTAP working environment.

  2. Set up one-time data replication between the systems for each volume that you must replicate.

  3. Terminate the Cloud Volumes ONTAP system that you no longer need by deleting the original working environment.

Changing write speed to normal or high

Cloud Manager enables you to choose a write speed setting for Cloud Volumes ONTAP, except for high availability (HA) pairs in Google Cloud. The default write speed is normal. You can change to high write speed if fast write performance is required for your workload. Before you change the write speed, you should understand the differences between the normal and high settings.

About this task
  • Ensure that operations such as volume or aggregate creation are not in progress.

  • Be aware that this change restarts Cloud Volumes ONTAP.

Steps
  1. From the working environment, click the menu icon, and then click Advanced > Writing Speed.

  2. Select Normal or High.

    If you choose High, then you’ll need to read the "I understand…​" statement and confirm by checking the box.

  3. Click Save, review the confirmation message, and then click Proceed.

Modifying the storage VM name

Cloud Manager automatically names the single storage VM (SVM) that it creates for Cloud Volumes ONTAP. You can modify the name of the SVM if you have strict naming standards. For example, you might want the name to match how you name the SVMs for your ONTAP clusters.

But if you created any additional SVMs for Cloud Volumes ONTAP, then you can’t rename the SVMs from Cloud Manager. You’ll need to do so directly from Cloud Volumes ONTAP by using System Manager or the CLI.

Steps
  1. From the working environment, click the menu icon, and then click Information.

  2. Click the edit icon to the right of the storage VM name.

    Screen shot: Shows the SVM Name field and the edit icon that you must click to modify the SVM name.

  3. In the Modify SVM Name dialog box, change the name, and then click Save.

Changing the password for Cloud Volumes ONTAP

Cloud Volumes ONTAP includes a cluster admin account. You can change the password for this account from Cloud Manager, if needed.

You should not change the password for the admin account through System Manager or the CLI. The password will not be reflected in Cloud Manager. As a result, Cloud Manager cannot monitor the instance properly.
Steps
  1. From the working environment, click the menu icon, and then click Advanced > Set password.

  2. Enter the new password twice and then click Save.

    The new password must be different than one of the last six passwords that you used.

Changing the network MTU for c4.4xlarge and c4.8xlarge instances

By default, Cloud Volumes ONTAP is configured to use 9,000 MTU (also called jumbo frames) when you choose the c4.4xlarge instance or the c4.8xlarge instance in AWS. You can change the network MTU to 1,500 bytes if that is more appropriate for your network configuration.

About this task

A network maximum transmission unit (MTU) of 9,000 bytes can provide the highest maximum network throughput possible for specific configurations.

9,000 MTU is a good choice if clients in the same VPC communicate with the Cloud Volumes ONTAP system and some or all of those clients also support 9,000 MTU. If traffic leaves the VPC, packet fragmentation can occur, which degrades performance.

A network MTU of 1,500 bytes is a good choice if clients or systems outside of the VPC communicate with the Cloud Volumes ONTAP system.

Steps
  1. From the working environment, click the menu icon and then click Advanced > Network Utilization.

  2. Select Standard or Jumbo Frames.

  3. Click Change.

Changing route tables associated with HA pairs in multiple AWS AZs

You can modify the AWS route tables that include routes to the floating IP addresses for an HA pair. You might do this if new NFS or CIFS clients need to access an HA pair in AWS.

Steps
  1. From the working environment, click the menu icon and then click Information.

  2. Click Route Tables.

  3. Modify the list of selected route tables and then click Save.

Result

Cloud Manager sends an AWS request to modify the route tables.