NFS datastores with NetApp

[tomaddox]

Hi, everyone,

We've traditionally used Fibre Channel datastores, but we're trying to move towards using NFS-based datastores hosted by a NetApp filer. What I would ideally like to do is have a separate set of network interfaces dedicated to NFS access. What I'm running into, however, is that I can't figure out how to designate a particular VMKernel interface for NFS storage traffic. What is the best way to tell ESX/ESXi 4.1 to only use a particular interface/vSwitch/dvSwitch/portgroup/whatever for NFS storage?

Thanks,

Tom

[weinstein5]

Best way is to put the vmkernel port and NFS ports on the same network segment/vlan - 

[vmroyale]

Hello.

I absolutely agree here - isolate it.  Also, check out NetApp TR-3428 for tons of great information about setting this up.

Good Luck!

[tomaddox]

David Weinstein wrote:

Best way is to put the vmkernel port and NFS ports on the same network segment/vlan - 

Agreed, and that's the ultimate goal. What I'd like to do in the meantime is have the storage ports on the VLAN that will ultimate host the NFS network, yet be able to talk to the NetApp, which resides on a different network. As a workaround, I guess I can put the NFS interfaces on the NetApp's network segment, so I'll give that a shot. Is there no other way of guaranteeing which interface will be used, though? The hosts will have multiple routable interfaces (one for the Service Console and one for NFS, at the very least), so I would hate to have the traffic go out the wrong interface.

[chriswahl]

IP storage traffic will always choose the vmkernel port on the same subnet as the NFS storage. Barring that, it will go out the gateway. There is no way to pin IP storage to a specific vmkernel port.

I've written an article on NFS on VMware that may help:

http://wahlnetwork.wordpress.com/2011/06/08/a-look-at-nfs-on-vmware/

[EdWilts]

I would hate to have the traffic go out the wrong interface.

The best way I've found to do this is to dedicate an IP address on the filer (or vfiler) for your storage traffic.  This should be enabled with jumbo frames on your filer anyway.  Tell your network guys you don't want this routed at all.  Then assign an IP address to your ESXi host on the same subnet.  The *only* way you'll be able to get to the filer is to use the right interface - there's going to be no guessing.

Make absolutely, positively sure you mount the datastores by the exact same name on all hosts.

Make sure all of your VMDKs follow the guest alignment best practices.

And if you haven't been following the announcements today, NetApp just announced VSC 2.1.1.  http://communities.netapp.com/community/netapp-blogs/virtualization/blog/2011/09/08/netapp-virtual-s....  Personally, I have low expectations and just hope it sucks less

[titaniumlegs]

TR-3428 is really about VI3.  For 4.0, please see TR-3749. TR for 5.0 is in the works.

[tomaddox]

Ed Wilts wrote:

And if you haven't been following the announcements today, NetApp just announced VSC 2.1.1.  http://communities.netapp.com/community/netapp-blogs/virtualization/blog/2011/09/08/netapp-virtual-s....  Personally, I have low expectations and just hope it sucks less

Ha, that would be nice. If they fixed some of the more obvious bugs, that would be a step forward. Thanks for the info.