Skip to main content
Cloud Volumes ONTAP
AWS
  • Amazon Web Services
  • Google Cloud
  • Microsoft Azure
  • All cloud providers

Supported default configurations for Cloud Volumes ONTAP

Contributors netapp-manini netapp-rlithman netapp-bcammett netapp-driley
PDFs

Understanding how Cloud Volumes ONTAP is configured by default can help you set up and administer your systems, especially if you are familiar with ONTAP because the default setup for Cloud Volumes ONTAP is different than ONTAP.

Default setup

  • BlueXP creates one data-serving storage VM when it deploys Cloud Volumes ONTAP. Some configurations support additional storage VMs. Learn more about managing storage VMs.

    Starting with the BlueXP 3.9.5 release, logical space reporting is enabled on the initial storage VM. When space is reported logically, ONTAP reports the volume space such that all the physical space saved by the storage efficiency features are also reported as used. For information about inline storage efficiency features, refer to the knowledge base article KB: What Inline Storage Efficiency features are supported with CVO?

  • BlueXP automatically installs the following ONTAP feature licenses on Cloud Volumes ONTAP:

    • CIFS

    • FlexCache

    • FlexClone

    • iSCSI

    • Multi-tenant Encryption Key Management (MTEKM), starting with Cloud Volumes ONTAP 9.12.1 GA

    • NetApp Volume Encryption (only for bring your own license (BYOL) or registered pay-as-you-go (PAYGO) systems)

    • NFS

    • ONTAP S3

      Starting with Cloud Volumes ONTAP 9.11.0 in AWS

    • SnapMirror

    • SnapRestore

    • SnapVault

  • Several network interfaces are created by default:

    • A cluster management LIF

    • An intercluster LIF

    • An SVM management LIF on single node systems in AWS

    • A node management LIF

    • An iSCSI data LIF

    • A CIFS and NFS data LIF

      Note LIF failover is disabled by default for Cloud Volumes ONTAP due to cloud provider requirements. Migrating a LIF to a different port breaks the external mapping between IP addresses and network interfaces on the instance, making the LIF inaccessible.

  • Cloud Volumes ONTAP sends configuration backups to the Connector using HTTP.

    The backups are accessible from http://ipaddress/occm/offboxconfig/ where ipaddress is the IP address of the Connector host.

    You can use the backups for reconfiguring your Cloud Volumes ONTAP system. For more information about configuration backups, refer to the ONTAP documentation.

  • BlueXP sets a few volume attributes differently than other management tools (ONTAP System Manager or the ONTAP CLI, for example).

    The following table lists the volume attributes that BlueXP sets differently from the defaults:

    Attribute Value set by BlueXP

    Autosize mode

    grow

    Maximum autosize

    1,000 percent

    Note The BlueXP Organization or Account admin can modify this value from the Settings page.

    Security style

    NTFS for CIFS volumes
    UNIX for NFS volumes

    Space guarantee style

    none

    UNIX permissions (NFS only)

    777

    For information about these attributes, refer to ONTAP volume create man page.

Internal disks for system data

In addition to the storage for user data, BlueXP also purchases cloud storage for system data.

AWS

  • Three disks per node for boot, root, and core data:

    • 47 GiB io1 disk for boot data

    • 140 GiB gp3 disk for root data

    • 540 GiB gp2 disk for core data

  • For HA pairs:

    • Two st1 EBS volumes for the mediator instance, one of approximately 8 GiB as root disk, and one of 4 GiB as data disk

    • One 140 GiB gp3 disk in each node to contain a copy of the root data of the other node

      Note In some zones, the available EBS disk type can only be gp2.

  • One EBS snapshot for each boot disk and root disk

    Note Snapshots are created automatically upon reboot.

  • When you enable data encryption in AWS using the Key Management Service (KMS), the boot and root disks for Cloud Volumes ONTAP are encrypted, as well. This includes the boot disk for the mediator instance in an HA pair. The disks are encrypted using the CMK that you select when you create the working environment.

Tip In AWS, NVRAM is on the boot disk.

Where the disks reside

BlueXP lays out the storage as follows:

  • Boot data resides on a disk attached to the instance or virtual machine.

    This disk, which contains the boot image, is not available to Cloud Volumes ONTAP.

  • Root data, which contains the system configuration and logs, resides in aggr0.

  • The storage virtual machine (SVM) root volume resides in aggr1.

  • Data volumes also reside in aggr1.