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

Supported default configurations for Cloud Volumes ONTAP

Contributors netapp-manini
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

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

    Beginning with the 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?

  • The Console 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

    • SnapMirror

    • SnapRestore

    • SnapVault

  • Several network interfaces are created by default:

    • A cluster management LIF

    • An intercluster LIF

    • An SVM management LIF on HA systems in Google Cloud

    • A node management LIF

      In Google Cloud, this LIF is combined with the intercluster 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 Console agent using HTTP.

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

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

  • The Console 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 set differently from the defaults:

    Attribute Value that the Console configures

    Autosize mode

    grow

    Maximum autosize

    1,000 percent

    Note The 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, the Console also purchases cloud storage for system data.

Google Cloud (single node)

  • One 10 GiB SSD persistent disk for boot data

  • One 64 GiB SSD persistent disk for root data

  • One 500 GiB SSD persistent disk for NVRAM

  • One 315 GiB Standard persistent disk for saving cores

  • Snapshots for boot and root data

    Note Snapshots are created automatically upon reboot.

  • Boot and root disks are encrypted by default.

Google Cloud (HA pair)

  • Two 10 GiB SSD persistent disks for boot data

  • Four 64 GiB SSD persistent disk for root data

  • Two 500 GiB SSD persistent disk for NVRAM

  • Two 315 GiB Standard persistent disk for saving cores

  • One 10 GiB Standard persistent disk for mediator data

  • One 10 GiB Standard persistent disk for mediator boot data

  • Snapshots for boot and root data

    Note Snapshots are created automatically upon reboot.

  • Boot and root disks are encrypted by default.

Where the disks reside

Storage layout:

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