NFS 4.1 Datastores using Custom NFS TCP/IP Stack become inaccessible after upgrading to ESXi 8.0.2
searchcancel
NFS 4.1 Datastores using Custom NFS TCP/IP Stack become inaccessible after upgrading to ESXi 8.0.2
book
Article ID: 380337
calendar_today
Updated On: 02-25-2025
Products
VMware vSphere ESXiVMware vSphere ESXi 8.0
Issue/Introduction
Datastores that were using Custom NFS TCP/IP Stack with NFS 4.1 to isolate traffic to a specific Virtual NIC (vmk) for use with applications such as OpenStack become inaccessible after upgrade to ESXi 8.0.2.
Environment
vSphere ESXi 8.0.x
Cause
This is expected as Custom TCP/IP stack for NFS is unavailable from 8.0.
Resolution
With ESXi 8.0, vmkportbind feature was introduced. We may utilize this to bind the NFS traffic to specific NIC.
Procedure
To specify VMkernel adapters while mounting a new NFS 4.1 volume on the ESXi host, use the following command: