Skip to main content
ONTAP tools for VMware vSphere 10.2

Deploy ONTAP tools for VMware vSphere

Contributors netapp-jani
PDFs

You can deploy ONTAP tools for VMware vSphere in two configurations:

  • Non-HA single-node configuration

  • HA configuration

Non-HA single-node configuration

You can deploy a non-HA single-node configuration in either a small or medium configuration.

  • The small non-HA configuration contains 8 CPUs and 16 GB RAM.

  • Medium non-HA configuration contains 12 CPUs and 24 GB RAM.

Before you begin

Make sure the network route is present. Storage data network must be accessible from VM management network. For example, log in to ONTAP > run the command network route create -vserver <SVM> -destination 0.0.0.0/0 -gateway <gateway_ip>

Steps

  1. Download the .zip file that contains binaries (.ova) and signed certificates for ONTAP tools for VMware vSphere from the NetApp Support Site.

  2. Log in to the vSphere server.

  3. Navigate to the resource pool that you have created or to the cluster or to the host where you want to deploy the OVA.

  4. Right-click the required location and select Deploy OVF template…​.

    Note Do not deploy ONTAP tools for VMware vSphere virtual machine on a vVols datastore that it manages.

  5. Select the OVA file either through the URL for the .ova file or browse to the folder where the .ova file is saved, and then click Next.

  6. Select a computer resource and click Next.

  7. Review the details of the template and click Next.

  8. Read and accept the license agreement.

  9. Select the deployment configuration and click Next.

    The advanced deployment options use Trident as a dynamic storage provisioner for ONTAP to create volumes and the easy deployment uses local storage to create volumes.

  10. Select the storage for the configuration and the disk files and click Next.

  11. Select the destination network for each source network and click Next.

  12. In the Customize template, enter the required details and click Next

    • When SVM scope is enabled you should have already enabled SVM support with management IP address.

    • The information provided here is validated for proper patterns during installation process. In case of discrepancy, an error message is displayed on the web console, and you are prompted to correct any incorrect information provided.

    • Host names must consist of uppercase letters (A-Z), lowercase letters (a-z), digits (0-9), or the hyphen (-) special character. If you want to configure dual stack, specify the host name mapped to IPv6 address.

      Note Pure IPV6 is not supported. Mixed mode is supported with VLAN having both IPv6 and IPv4 addresses.

  13. Review the details in the Ready to complete window, select Finish.

    As the deployment task gets created, the progress is shown in the vSphere task bar.

  14. Power on the VM after the completion of the task.

HA configuration

You can configure HA three nodes in either small, medium, or large configurations. HA deployment uses Trident to store the services data.

  • Small HA three nodes contain 8 CPUs and 16 GB RAM per node.

  • Medium HA three nodes contain 12 CPUs and 24 GB RAM per node.

  • Large HA three nodes contain 16 CPUs and 32 GB RAM per node.

Before you begin

This task gives you instructions on how to install HA three nodes in small, medium, or high configurations.

Creating the content library is a mandatory prerequisite step for deploying HA three nodes configuration. A content library in VMware is a container object which stores VM templates, vApp templates, and other types of files. Deployment with content library provides you with a seamless experience as it is not dependent on the network connectivity.

Note You should store the content library on a shared datastore, such that all hosts in a cluster can access it. You need to create a content library to store the OVA before deploying the OVA in HA configuration.
Note Content library template once uploaded should not be deleted post deployment, as it will be used during reboots.

Create the content library using the following steps:

  1. Download the .zip file that contains binaries (.ova) and signed certificates for ONTAP tools for VMware vSphere from the NetApp Support Site.

  2. Log in to the vSphere client using https://vcenterip/ui

  3. Select the horizontal ellipses next to vSphere client and select Content library.

  4. Select Create on the right of the page.

  5. Provide a name for the library and create the content library.

  6. Navigate to the content library you created.

  7. Select Actions in the right of the page and select Import item and import the OVA file.

Note For more information, refer to Creating and Using Content Library blog.

Make sure you have imported your OVA into your content library. Keep the name of the content library and the library item name that you have given to your OVA item handy.

Note Before proceeding with the deployment, set the cluster's Distributed Resource Scheduler (DRS) on the inventory to 'Conservative' during the installation of ONTAP tools. This ensures that VM's do not migrate during the installation.

Steps

  1. Download the .zip file that contains binaries (.ova) and signed certificates for ONTAP tools for VMware vSphere from the NetApp Support Site.

  2. Log in to the vSphere server.

  3. Navigate to the resource pool that you have created or to the cluster or to the host where you want to deploy the OVA.

  4. Right-click the required location and select Deploy OVF template…​.

    Note Do not deploy ONTAP tools for VMware vSphere virtual machine on a vVols datastore that it manages.

  5. Select the OVA file either through the URL for the .ova file or browse to the folder where the .ova file is saved, and then click Next.

  6. To deploy ONTAP tools for VMware vSphere from content library:

    1. Go to your content library and click on the library item that you want to deploy.

    2. Click on Actions > New VM from this template

  7. Select a computer resource and click Next.

  8. Review the details of the template and click Next.

  9. Read and accept the license agreement and click Next.

  10. Select the deployment configuration and click Next.

  11. Select the storage for the configuration and the disk files and click Next.

  12. Select the destination network for each source network and click Next.

  13. In the Customize template window, fill in the required fields and click Next.

    • In HA mode of deployment, do not rename the VM names after the deployment.

    • When SVM scope is enabled you should have already enabled SVM support with management IP address.

    • The information provided here is validated for proper patterns during installation process. In case of discrepancy, an error message is displayed on the web console, and you are prompted to correct any incorrect information provided.

    • Host names must consist of uppercase letters (A-Z), lowercase letters (a-z), digits (0-9), or the hyphen (-) special character. If you want to configure dual stack, specify the host name mapped to IPv6 address.

      Note Pure IPV6 is not supported. Mixed mode is supported with VLAN having both IPv6 and IPv4 addresses.

  14. Review the details in the Ready to complete window, select Finish.

    As the deployment task gets created, the progress is shown in the vSphere task bar.

  15. Power on the VM after the completion of the task.

You can track the progress of the installation within the VM's web console.

In case of any discrepancies in the values entered in the OVF form, a dialog box will prompt you to take corrective action. Make the necessary changes within the dialog box, utilizing the tab button to navigate and select "OK." You have three attempts to rectify any issues. If issues persist after three attempts, the installation process will cease, and it is recommended to retry the installation on a fresh VM.