7 Responses

  1. Collin C MacMillan
    Collin C MacMillan at |

    Chris:

    Application support is another reason: it’s also important to point out support exceptions when dealing with routed NFS:

    Notably:

    In an L3 environment the following additional restrictions are applicable:

    1. The environment does not support VMware Site Recovery Manager.
    2. The environment supports only NFS protocol. Do not use other storage protocols such as FCoE over the same physical network.
    3. The NFS traffic in this environment does not support IPv6.
    4. The NFS traffic in this environment can be routed only over a LAN. Other environments such as WAN are not supported.
    5. The environment does not support Distributed Virtual Switch (DVS).

    See: http://blogs.vmware.com/vsphere/2012/06/vsphere-50-u1-now-supports-routed-nfs-storage-access.html

    Cheers,

    Reply
  2. Didier Pironet (@dpironet)
    Didier Pironet (@dpironet) at |

    Great write up! I also like the NFS on vSphere series. I found you diagram very useful to explain customers the concept of hop count for instance.
    Thx,
    Didier

    Reply
  3. Jonathan Frappier
    Jonathan Frappier at |

    Reblogged this on Jonathan Frappier's Blog.

    Reply
  4. Jim Millard
    Jim Millard at |

    I get having a vmkernel port group on the same VLAN, but how do you keep the routed connection from being chosen, instead? What if you ALSO have your NFS on the same VLAN as iSCSI (eg, NAS box, so you’ve already got 2x port/nic for iSCSI binding), and you’d like to be more deterministic about connectivity between host & NFS among the 3 vmkernel ports?

    Reply
  5. Best Practice for configuring VMware VMkernel ports for NFS traffic | Atlantis Computing Blog

    […] is a really useful link from Chris Wahl on The necessity for nfs vmkernel ports explained that has in-depth information and some cool graphical representations of what your NFS traffic […]

Share your point of view!