Skip to main content
Element Software
A newer release of this product is available.

Enable virtual volumes

Contributors netapp-revathid netapp-pcarriga netapp-dbagwell
PDFs

You must manually enable vSphere Virtual Volumes (VVols) functionality through the NetApp Element software. The Element software system comes with VVols functionality disabled by default, and it is not automatically enabled as part of a new installation or upgrade. Enabling the VVols feature is a one-time configuration task.

What you'll need

  • The cluster must be running Element 9.0 or later.

  • The cluster must be connected to an ESXi 6.0 or later environment that is compatible with VVols.

  • If you are using Element 11.3 or later, the cluster must be connected to an ESXi 6.0 update 3 or later environment.

Important Enabling vSphere Virtual Volumes functionality permanently changes the Element software configuration. You should only enable VVols functionality if your cluster is connected to a VMware ESXi VVols-compatible environment. You can disable the VVols feature and restore the default settings only by returning the cluster to the factory image, which deletes all data on the system.
Steps

  1. Select Clusters > Settings.

  2. Find the cluster-specific settings for Virtual Volumes.

  3. Click Enable Virtual Volumes.

  4. Click Yes to confirm the Virtual Volumes configuration change.

    The VVols tab appears in the Element UI.

    Note When VVols functionality is enabled, the SolidFire cluster starts the VASA Provider, opens port 8444 for VASA traffic, and creates protocol endpoints that can be discovered by vCenter and all ESXi hosts.

  5. Copy the VASA Provider URL from the Virtual Volumes (VVols) settings in Clusters > Settings. You will use this URL to register the VASA Provider in vCenter.

  6. Create a storage container in VVols > Storage Containers.

    Note You must create at least one storage container so that VMs can be provisioned to a VVol datastore.

  7. Select VVols > Protocol Endpoints.

  8. Verify that a protocol endpoint has been created for each node in the cluster.

    Note Additional configuration tasks are required in vSphere. See the VMware vSphere Virtual Volumes for SolidFire Storage Configuration Guide to register the VASA Provider in vCenter, create and manage VVol datastores, and manage storage based on policies.

Find more information

VMware vSphere Virtual Volumes for SolidFire Storage Configuration Guide