Modifying Cloud Volumes ONTAP systems Edit on GitHub Request doc changes

Installing license files on Cloud Volumes ONTAP BYOL systems

If Cloud Manager cannot obtain a BYOL license file from NetApp, you can obtain the file yourself and then manually upload the file to Cloud Manager so it can install the license on the Cloud Volumes ONTAP system.

Steps
  1. Go to the NetApp License File Generator and log in using your NetApp Support Site credentials.

  2. Enter your password, choose your product (either NetApp Cloud Volumes ONTAP BYOL for AWS, NetApp Cloud Volumes ONTAP BYOL for Azure, or NetApp Cloud Volumes ONTAP BYOL HA for AWS), enter the serial number, confirm that you have read and accepted the privacy policy, and then click Submit.

    Example

    Screen shot: Shows an example of the NetApp License File Generator web page filled out

  3. Choose whether you want to receive the serialnumber.NLF JSON file through email or direct download.

  4. In Cloud Manager, select the Cloud Volumes ONTAP BYOL working environment.

  5. In the Storage pane, click the menu icon, and then click License.

  6. Click Upload License File.

  7. Click Upload and then select the file.

Result

Cloud Manager installs the new license file on the Cloud Volumes ONTAP system.

Changing the instance or virtual machine type for Cloud Volumes ONTAP

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

About this task
  • 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 virtual machine type affects AWS or Azure service charges.

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

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

  3. Select an instance or virtual 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 EC2 instance types or Azure virtual 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 virtual machine type affects AWS or Azure service charges.

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

  2. Select a license type and an instance type or virtual 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 virtual machine type, or both.

Moving to an alternate Cloud Volumes ONTAP configuration

If you want to move between a pay-as-you-go subscription and a BYOL subscription or between a single Cloud Volumes ONTAP system and an HA pair, you can 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. If you chose a pay-as-you-go license and the tenant does not have a NetApp Support Site account assigned to it, manually register the systems with NetApp.

    Support from NetApp is included with Cloud Volumes ONTAP. To activate support, you must first register the system with NetApp.

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

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

Modifying the storage virtual machine name

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

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

  2. Click the edit icon to the right of the SVM 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, modify the SVM 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

You can modify the 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 the HA pair.

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.