Archivo de la etiqueta: nfsv4 esx

NFSv4 y ESXi, de verdad de la buena

Currently, there are three versions of NFS. NFS version 2 (NFSv2) is older and is widely supported. NFS version 3 (NFSv3) supports safe asynchronous writes and a more robust error handling than NFSv2; it also supports 64-bit file sizes and offsets, allowing clients to access more than 2Gb of file data.

NFS version 4 (NFSv4) works through firewalls and on the Internet, no longer requires an rpcbind service, supports ACLs, and utilizes stateful operations. Red Hat Enterprise Linux 6 supports NFSv2, NFSv3, and NFSv4 clients. When mounting a file system via NFS, Red Hat Enterprise Linux uses NFSv4 by default, if the server supports it.

All versions of NFS can use Transmission Control Protocol (TCP) running over an IP network, with NFSv4 requiring it. NFSv2 and NFSv3 can use the User Datagram Protocol (UDP) running over an IP network to provide a stateless network connection between the client and server.

When using NFSv2 or NFSv3 with UDP, the stateless UDP connection (under normal conditions) has less protocol overhead than TCP. This can translate into better performance on very clean, non-congested networks. However, because UDP is stateless, if the server goes down unexpectedly, UDP clients continue to saturate the network with requests for the server. In addition, when a frame is lost with UDP, the entire RPC request must be retransmitted; with TCP, only the lost frame needs to be resent. For these reasons, TCP is the preferred protocol when connecting to an NFS server.

The mounting and locking protocols have been incorporated into the NFSv4 protocol. The server also listens on the well-known TCP port 2049. As such, NFSv4 does not need to interact with rpcbind[2], lockd, and rpc.statd daemons. The rpc.mountd daemon is still required on the NFS server to set up the exports, but is not involved in any over-the-wire operations.

NAS4Free soporta NFSv4, pero se ha de activar usando el checkbox. Sólo se podrán conectar los ESXi 6.0 o superiores.
Cómo activar NFSv4 en FreeBSD 9.1:


NFSv4 y ESXi

ESXi 5.5 no soporta NFSv4. Sólo NFSv3, el cual va por UDP.

ESX 6.0 sí soporta NFSv4.1:
If you are using NFS storage for VMs (either on a hardware NAS box or hosted on a VM) with your ESXi hosts then you might be interested in the new support for NFS version 4.1. Version 4.1 has superior new features (state management, improved locking, Kerberos authentication) and can be much more efficient and performant than 3.0 (which was exclusively supported with ESXi 5.x), but that depends very much on the client implementation. Time and the performance tests to come will tell how much you can gain from it with ESXi.

NAS4Free soporta NFSv4, pero se ha de activar usando el checkbox. Sólo se podrán conectar los ESXi 6.0 o superiores.

Guías de buenas práctica spara conectar ESXi a NFS:

NFS Best Practices – Part 1: Networking

NFS Best Practices – Part 2: Advanced Settings

Con ESXi 6.0 y NFSv4 ya se puede hacer un balanceo de carga accediendo al NFS por varias IPs. Antes todo el datastore NFS se comunicaba por una única conexión TCP/IP. En el NAS4Free podríamos usar LAACP para que pueda ser accedido por dos ips distintas:

Multipathing and Load-balancing:
Now onto the improvements. NFS v4.1 introduces better performance and availability through load balancing and multipathing. Note that this is not pNFS (parallel NFS). pNFS support is not in vSphere 6.0.
Setup NFSv4.1 datastoreIn the server(s) field, add a comma separate list of IP addresses for the server if you wish to use load-balancing and multipathing.