Skip to main content
ONTAP tools for VMware vSphere 10.1

Prepare to deploy ONTAP tools for VMware vSphere

Contributors
PDFs

You should be aware of the basic storage backend requirements, application requirements, and license requirements before you begin deploying ONTAP tools for VMware vSphere. Plan your deployment in advance and decide how you want to configure ONTAP tools for VMware vSphere in your environment.

Preparing for deployment

Following are ONTAP tools for VMware vSphere requirements before proceeding with the deployment:

  1. Configure and set up your vCenter Server environment.

  2. Download the .ova file.

  3. (Optional) Used for automation user - Gather the Postman collections JSON file provided by NetApp.

  4. Parent vCenter Server Credentials to deploy the OVA. Parent vCenter Server password should not contain these special characters($, ', ")

  5. Make sure the host or the resource pool where the OVA is deployed has the minimum resources mentioned in the Prerequisites for deploying ONTAP tools for VMware vSphere section.

  6. The login credentials for your vCenter Server instance to which the ONTAP tools for VMware vSphere will connect to post deployment for registration.

  7. Delete the browser cache.

  8. For non-HA deployment, you need three free IP addresses - one free IP address for load balancer and one free IP address for the Kubernetes control plane and one IP address for node. For HA deployment, along with these three IP addresses you'll need two more IP addresses for second and third nodes. Host names should be mapped to the free IP addresses on the DNS before assigning. All the five IP addresses should be on the same VLAN that is selected for deployment.

  9. Content library template once uploaded should not be deleted post deployment as it will be used during reboots.

  10. In a multi-vCenter deployment where Custom CA certificates are mandatory, map the Domain Name on which the certificate is issued to the Virtual IP address. Perform a nslookup check on the domain name to check whether the domain is getting resolved to the intended IP address. The certificates should be created with domain name and IP address of the load balancer IP address.

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

  12. NTP Server which is provided to the vCenter Server for time sync.

  13. Static IP address Configuration details for the Node or VM where the OVA is being deployed (Mandatory) and other details.

    1. vCenter Server hostname (vCenter where the OVA is deployed)

    2. vCenter Server username (vCenter where the OVA is deployed)

    3. vCenter Server password (vCenter where the OVA is deployed)

    4. Resource pool

    5. Data LIF (IPv4/IPv6)

    6. Management LIF

    7. ONTAP username

    8. ONTAP password

    9. SVM name

    10. Protocol

    11. Virtual IP addresses for the Kubernetes control plane.

    12. HA / NON-HA drop down

    13. List of hostnames

    14. IP addresses (string)

    15. Content library name

    16. OVF template name

    17. IPv6 gateway (optional)