To take advantage of multipathing benefits offered by trunking, you need a set of LIFs – referred to as a trunking group – that are associated with the SVM containing a trunking-enabled NFS server. The LIFs in a trunking group must have home ports on the same node of the cluster, and they must reside on those home ports. It is a best practice that all LIFs in a trunking group are members of the same failover group.

ONTAP supports up to 16 trunked connections per node from a given client.

When a client mounts exports from a trunking-enabled server, they specify a number of IP addresses for LIFs in a trunking group. After the client connects to the first LIF, additional LIFs are only added to the NFSv4.1 session and used for trunking if they conform to trunking group requirements. The client then distributes NFS operations over the multiple connections based on their own algorithm (such as round-robin).

For best performance, you should configure trunking in an SVM that is dedicated to providing multipath exports, not single-path exports. That is, you should only enable trunking on a NFS server in an SVM whose exports are provided to trunking-enabled clients only.

The ONTAP NFSv4.1 server supports trunking with any client capable of NFSv4.1 session trunking.

The following clients have been tested with ONTAP 9.14.1:

Beginning with ONTAP 9.8, nconnect functionality is available by default when NFSv4.1 is enabled. On nconnect-capable clients, a single NFS mount can have multiple TCP connections (up to 16) over a single LIF.

In contrast, trunking is multipathing functionality, which provides multiple TCP connections over multiple LIFs. If you have the ability to employ additional NICs in your environment, trunking provides increased parallelism and performance beyond the capability of nconnect.

Learn more about nconnect.