Ping the IP address of the NFS export from the ESXi host. Use the Direct Console User Interface (DCUI) to test connectivity from the ESXi host or enable the ESXi shell and use the vmkping command.
Check the physical cabling. Check if the link lights are showing a connected state on the physical interfaces on the ESXi host, the Ethernet switches, and the NFS server.
Check to see if the VLANs have been configured correctly. Check if you have properly configured the same VLAN on the host, the switch, and the interface(s) that will be used on your NFS server.
Check if the IP routing is correct and functional. Check for the IP addresses on the VMkernel adapter and the interface(s) that will be used on the NFS server. Make sure they are on the same subnet. Even though, strictly speaking, it is possible to route NFS traffic, it is not a recommended practice since it adds additional latency on the router. Not recommended in vSphere environments.
Are there any firewalls blocking the NFS traffic ? The ping could succeed but you will not be able to mount the NFS datastore if a firewall is blocking the path. The general recommendation is to avoid firewalls in the data path whenever possible, to reduce additional latency.
Check if Jumbo frames are configured. If you are using Jumbo frames you should have them configured on the VMkernel adapter, the vDistributed Switch, on all physical switches along the data path, and on the NFS server as well.
Check if there is any problem with root access from the ESXi host to the NFS export.
Check the physical cabling. Check if the link lights are showing a connected state on the physical interfaces on the ESXi host, the Ethernet switches, and the NFS server.
Check to see if the VLANs have been configured correctly. Check if you have properly configured the same VLAN on the host, the switch, and the interface(s) that will be used on your NFS server.
Check if the IP routing is correct and functional. Check for the IP addresses on the VMkernel adapter and the interface(s) that will be used on the NFS server. Make sure they are on the same subnet. Even though, strictly speaking, it is possible to route NFS traffic, it is not a recommended practice since it adds additional latency on the router. Not recommended in vSphere environments.
Are there any firewalls blocking the NFS traffic ? The ping could succeed but you will not be able to mount the NFS datastore if a firewall is blocking the path. The general recommendation is to avoid firewalls in the data path whenever possible, to reduce additional latency.
Check if Jumbo frames are configured. If you are using Jumbo frames you should have them configured on the VMkernel adapter, the vDistributed Switch, on all physical switches along the data path, and on the NFS server as well.
Check if there is any problem with root access from the ESXi host to the NFS export.
No comments:
Post a Comment