Valentin Hamburger

VVol's with HNAS - How it works

Blog Post created by Valentin Hamburger Employee on Dec 17, 2015

Get started with VVols for HNAS


My colleague Christian Hess and I are working together on enabling VVols with vSphere 6.0 and HNAS. In this

article we want to share the basic steps to configure and get started with that awesome piece of technology. While

you might find all of this in the respective manual, we just want to give a brief and quick overview how to get started.

Christian will focus on the HNAS configuration bits and I will focus on the respective actions to take in vCenter to make

everything work.



Configure HNAS


You have to have either an HNAS 4060, 4080 or 4100 with firmware version 12.3 or higher in order to use VVol's.


IP settings / Interface Settings

This section is not actually VVol specific, but it makes sense to have a look if everything is configured like it should in your HNAS from a networking
standpoint. It is important to understand that HDS differentiates between three types of interfaces in an HNAS system:

  • An administration interface, which is an EVS of the type "admin services"

  • A data traffic interface also called "EVS" of the type "File services"

  • An SMU management interace


Why are we mention this? Simply because it is important to connect the VASA provider to the right interface. Otherwise the VASA provider

will not establish a connection with the HNAS system and will give you a "wrong credentials" exception.


Create the VVol Export

In the HNAS administration interface make sure to create an NFS export for the use with VMware VVols. It is very similar to a standard NFS
export but you need to follow these three rules:

Screen Shot 2015-12-15 at 15.36.12.png


  1. Make the export name and the path exactly the same as the File System

      name e.g.: FS1_VMware

  2. Format it to make the space instantly available

  3. Make sure to include this FS options: *(rw,no_root_squash)


That's it - you have created your VVol enabled file system and successfully exported it.





Configure vCenter 6



You all probably know by now that you need to have vSphere version 6.0 (at least) to support VVols for any kind of storage.

Also you need to have the latest and greatest VASA provider from your storage vendor. In our case that is the VP-f (for HNAS) in version 3.2

You can download the Hitachi VASA provider from VMware's solution exchange here. Make sure it is the most recent version. The VASA

provider from HDS is provided as OVA (Open Virtual Appliance). It is very easy to import into your Management cluster. Just follow the typical
questions you get during an OVA deploy (IP address or DHCP, DNS, Gateway, etc) and have it deployed in minutes.


Configure the VASA appliance

Once you have deployed the VP-f (VASA Provider for file) OVA you need to configure it to talk to your HNAS.



Go to your VP-f URL like https://my.vp.local:8843

(Default) username: admin

(Default) password: nasadmin

Screen Shot 2015-12-15 at 15.15.59.png
2.Switch the VASA provider into Maintenance Mode to unlock its configuration
3.Click on "Manage Hardware" to add the IP and credentials of your HNAS system. Make sure to add the admin interface here, otherwise the config window will give you an error.
4.Once the HNAS system is added correctly, click on "done" to return to the main screen.

Click on "Manage Storage Containers" and configure the VVol container.

Make sure to create the storage container using a decent size. A storage Container
can span multiple filesystem exports.

6.Exit the maintenance mode
7.ou are done configuring the VASA provider


Add the VASA Provider to vCenter



In the vCenter web client click on vCenter and than on the "Manage" tab

Screen Shot 2015-12-15 at 16.18.40.png

On the far right click on the "Storage Providers"


Click the "add storage provider" icon


Add the following credentials for the VP-f appliance

URL: https://your-vp-f.local:8843/version.xml

(Default) admin

(Default) nasadmin


Click "OK" and wait until vCenter finishes adding the storage provider

6.Once it is done you should see the VASA provider in the list


Adding the VVol datastore

Screen Shot 2015-12-15 at 16.32.11.png

Eureka, you have successfully prepared the environment for using VVols with HNAS. To continue, you need to add a VVol
datastore to use it on any ESXi host in the cluster. ( or globally - but we follow VMware's best practices and make it available on a per cluster basis)


  1. In the web client right-click on your cluster and choose "Storage -> New Datastore"
  2. At "Type" select VVOL as option for the datastore and click next
  3. You should now see the storage container we have created earlier
  4. Make sure it is selected and click next/finish to add the datastore.


That's it, now you have a brand new VVol datastore to use. No mount point definitions, no NFS credentials - as easy as pie.


Start using your new VVol datastore for VMs and enjoy the simplicity with HNAS and VMware VVols.


Stay tuned for additional articles focusing on storage capabilities when using HNAS and VVols.