A quick post about VAAI, NetApp and VMware. I was messing around with VAAI and installing the NetApp plugin for NFS in my VCAP test environment. This is a pretty simple process and can be automatically deployed via the NetApp VSC, if installed. Since I’m working on making sure I can do this from the CLI, think VCAP-DCA5, I’m practicing doing it from there. I’m using the NetApp Simulator, which is probably the best thing that NetApp could have done for its customers. Simply amazing piece of software that offers nearly all the functionality of a NetApp filer.
I placed the NetApp_bootbank_NetAppNasPlugin_1.0-018.vib on a datastore so that I could access it from the CLI
Easy stuff, nothing new here. Now let’s get this thing installed from the CLI
Looks like we got it. Reboot the host and we’re golden. Check vCenter to see if our Hardware Acceleration is working.
Hmmm, not working as it should. Let’s check to make sure the vib is showing up in the vib list.
Yeah we got it there. What could be the problem? Well, let’s check the NetApp to see the NFS options.
Ah ha! There’s our problem right there. There’s a few options not enabled. These have to be enabled to allow VAAI functions on the NetApp for NFS datastores. So let’s enable them
Now that it’s enabled, let’s go check our vCenter and NFS datastores again. A quick rescan of the datastores and we’re working as intended.
Or we can check it from the CLI, since we’re concerned about knowing how to check this from there anyway
EDIT – So I was building a new controller out in the lab and I confirmed Mike’s assumption. The need for ‘options nfs.v4.enable on’ is only a requirement using the version of the NetApp simulator that I’m using. This option is NOT required for a real set of controllers.