Skip to main content
Cloud Manager 3.7
A newer release of this product is available.

Default configurations

Contributors netapp-bcammett

Details about how Cloud Manager and Cloud Volumes ONTAP are configured by default can help you administer the systems.

Default configuration for Cloud Manager on Linux

If you need to troubleshoot Cloud Manager or your Linux host, it might help to understand how Cloud Manager is configured.

  • If you deployed Cloud Manager from NetApp Cloud Central (or directly from a cloud provider's marketplace), note the following:

    • In AWS, the user name for the EC2 Linux instance is ec2-user.

    • The operating system for the Cloud Manager image is Red Hat Enterprise Linux 7.4 (HVM).

      The operating system does not include a GUI. You must use a terminal to access the system.

  • The Cloud Manager installation folder resides in the following location:

    /opt/application/netapp/cloudmanager

  • Log files are contained in the following folder:

    /opt/application/netapp/cloudmanager/log

  • The Cloud Manager service is named occm.

  • The occm service is dependent on the MySQL service.

    If the MySQL service is down, then the occm service is down too.

  • Cloud Manager installs the following packages on the Linux host, if they are not already installed:

    • 7Zip

    • AWSCLI

    • Java

    • Kubectl

    • MySQL

    • Tridentctl

    • Wget

Default configuration for Cloud Volumes ONTAP

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.

  • Cloud Volumes ONTAP is available as a single-node system in AWS, Azure, and GCP, and as an HA pair in AWS and Azure.

  • Cloud Manager creates one data-serving SVM when it deploys Cloud Volumes ONTAP. Using multiple data-serving SVMs is not supported.

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

    • CIFS

    • FlexCache

    • FlexClone

    • iSCSI

    • NetApp Volume Encryption (only for BYOL or registered 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 Azure, single node systems in AWS, and optionally on HA systems in multiple AWS Availability Zones

    • 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 EC2 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 Cloud Manager using HTTPS.

    When logged in to Cloud Manager, the backups are accessible from https://ipaddress/occm/offboxconfig/

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

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

    Attribute Value set by Cloud Manager

    Autosize mode

    grow

    Maximum autosize

    1,000 percent

    Note The 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

    See the volume create man page for information about these attributes.

Boot and root data for Cloud Volumes ONTAP

In addition to the storage for user data, Cloud Manager also purchases cloud storage for boot and root data on each Cloud Volumes ONTAP system.

AWS

  • Two General Purpose SSD disks:

    • One 140 GB disk for root data (one per node)

    • 9.6 and later: One 86 GB disk for boot data (one per node)

    • 9.5 and earlier: One 45 GB disk for boot data (one per node)

  • One EBS snapshot for each boot disk and root disk

  • For HA pairs, one EBS volume for the Mediator instance, which is approximately 8 GB

Azure (single node)

  • Two Premium SSD disks:

    • One 90 GB disk for boot data

    • One 140 GB disk for root data

  • One Azure snapshot for each boot disk and root disk

Azure (HA pairs)

  • Two 90 GB Premium SSD disks for the boot volume (one per node)

  • Two 140 GB Premium Storage page blobs for the root volume (one per node)

  • Two 128 GB Standard HDD disks for saving cores (one per node)

  • One Azure snapshot for each boot disk and root disk

GCP

  • One 10 GB Standard persistent disk for boot data

  • One 64 GB Standard persistent disk for root data

  • One 500 GB Standard persistent disk for NVRAM

  • One 216 GB Standard persistent disk for saving cores

  • One GCP snapshot each for the boot disk and root disk

Where the disks reside

Cloud Manager 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.

Encryption

Boot and root disks are always encrypted in Azure and Google Cloud Platform because encryption is enabled by default in those cloud providers.

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.