Table of ContentsView in Frames

Installing VASA Provider for clustered Data ONTAP

You deploy the VASA Provider for clustered Data ONTAP virtual appliance on an ESXi host. After the VASA Provider virtual appliance is installed, you must register it with Virtual Storage Console for VMware vSphere.

Before you begin

VASA Provider does not support direct-connect Storage Virtual Machines (SVMs, formerly known as Vservers) or qtree datastores.

Steps

  1. Download the OVA file for NetApp VASA Provider for clustered Data ONTAP OVA from the NetApp Support Site.
  2. Save the OVA file to a local or network location that is accessible to your VMware vSphere Web Client.
  3. From the vSphere Web Client Home page, click VMs and Templates.
    Screen shot: VMs and Templates selected on the vSphere Web Client Home page.
  4. Right-click the datacenter where you want to deploy the VASA Provider software.
    The Actions - Datacenter list appears.
  5. Select the option Deploy OVF template.

    This opens a wizard that steps you through the process of installing the VASA Provider software. Follow the instructions provided on each page of the wizard.

    Some points to keep in mind include the following:

    Page/Field Explanation
    Select source Specify either the URL to the VASA Provider software or browse to location where you downloaded the software.

    You can install VASA Provider from a URL; however, the installation is usually faster if you download the software to your local machine.

    Note: If you download the software and the download process changes the file extension from .ova to .tar, you must rename the file to change the extension back to .ova.
    Accept EULAs Click Accept even though no EULA appears.

    The EULA was displayed and had to be accepted before you were able to download the software from the VASA Provider for Clustered Data ONTAP Download page.

    This screen provides information about the steps you must perform to complete the installation after you set up the VASA Provider virtual appliance. These steps include the following:

    • Powering on the virtual appliances by clicking the Console tab in the vCenter client.
      Note: You can check the option in the wizard to do this automatically.
    • Watching the console output for final instructions and your virtual appliance URL.
    Select name and folder Provide both a name that allows you to easily identify the virtual appliance and a location for the virtual appliance.

    The location can be either a folder or a datacenter.

    Select a resource Specify where you will deploy VASA Provider.

    This can be either a cluster, host, vApp, or resource pool.

    Select storage Specify both the virtual disk format and the location where you want to store files for the deployed template from the list of available datastores.

    You can use a VM Storage Policy if your environment is configured for that.

    The wizard displays a list of datastores that the destination resource you selected in the previous page can access.

    Setup networks From the available networks shown, select the ones that you want to use with the deployed template.

    The network you select must be accessible to all the components you are working with, including VSC.

    Note: IPv6 is not supported.
    Customize template If you are using DHCP, leave these fields blank.

    Otherwise, you can specify properties to customize the deployment information for VASA Provider.

    If you choose to provide custom settings, you must supply values for all the fields on this page. You cannot supply information for some fields and leave the rest blank.

    In addition, you must have created a DNS entry for VASA Provider before you enter information on this page.

    Ready to complete (Recommended) Select Power on after deployment.

    Review your settings. If you need to change something, go back to that page in the wizard.

  6. Monitor the status of the Deploy OVF Template operation in the Recent Tasks pane.
    When the operation completes, verify the application status. The status will continue to say that it is initializing the DB until you log in and log out. The status changes to vpserver is running and waiting for vSphere registration.
  7. After your deployment completes, open a virtual console to VASA Provider from the vCenter Server.

    If the new VASA Provider does not power on automatically, click its name in the Recent Tasks pane. When it opens, use the Actions menu to power it on and then launch the console.

    Note: When you are working within the console, your mouse disappears. To get it back, press Ctrl-Alt.

    The application status is updated every 60 seconds; however, the display does not update unless you press Enter.

  8. If you do not have VMware Tools installed, click OK at the Install VMware Tools dialog box.

    This image is explained by the surrounding text.
    1. From the console, select VM > Guest > Install/Upgrade VMware Tools and press Enter.


      This image is explained by the surrounding text.

    2. The VMWare Tools wizard starts. Follow the prompts.
  9. At the VM Settings option, select Remove tools disk and press Enter.
    Pressing Enter causes VASA Provider to reboot.
  10. Specify a password for the maint account (maintenance) user and the vpserver account.
    Recommended: Use different passwords for the two accounts. You use the vpserver account password to register VASA Provider with VSC.
    VASA Provider then generates the certificates it requires and displays the login screen.

    The Application Status should state the following: vpserver is running and waiting for vSphere registration.

After you finish

You must open VSC and register the VASA Provider server on the VSC Configuration page. You must supply the IP address for VASA Provider and the vpserver password. Do not use the vCenter Manage > Storage Provider page to register VASA Provider.