Step1 Check the Health status of the Link Aggregation:

uemcli -d 10.0.0.1 -u Local/admin -p Password123# /net/la show -detail

1: ID = la0_SPA
SP = SPA
Ports = eth2_SPA,eth3_SPA
Health state = OK (5)

2: ID = la0_SPB
SP = SPB
Ports = eth2_SPB,eth3_SPB
Health state = OK (5)

Step2 Ensure the Network Interface for NFS is correctly configured:
uemcli -d 10.0.0.1 -u Local/admin -p Password123# /net/if show -detail

ID = if_2
Port = eth2_SPA
VLAN ID = 0
IPv4 mode = static
IPv4 address = 10.0.0.11
IPv4 subnet mask = 255.255.255.0
IPv4 gateway = 10.0.0.254
MAC address = 08:00:00:00:00:00
SP = SPA

Step3 Check the Health Status and MTU Value set on the Ports:
uemcli -d 10.0.0.1 -u Local/admin -p Password123# /net/port show

ID = eth2_SPA
Role = frontend
SP = SPA
Supported types = iscsi, net
MTU size = 9000
Speed = 1 Gbps
Health state = OK (5)
Aggregated port ID = la0_SPA

ID = eth3_SPB
Role = frontend
SP = SPB
Supported types = iscsi, net
MTU size = 9000
Speed = 1 Gbps
Health state = OK (5)
Aggregated port ID = la0_SPB

For a more detailed analysis of Frontend|Backend:
uemcli -d 10.0.0.1 -u Local/admin -p Password123# /net/port -role frontend show -detail

Step4 Check if Jumbo MTU is set correctly on Cisco SW’s:
SwitchA#show system mtu
If change required then issue command: system mtu jumbo 9198
Save and then reload

Step5 Check Shared folder for enabled NFS and Interface ID
uemcli -d 10.0.0.1 -u Local/admin -p Password123# /net/nas/server show

ID = file_server_2
Name = NFS_01
Health state = OK (5)
SP = SPA
CIFS enabled = no
NFS enabled = yes
Interface = if_2

Step6 Run a PING Test from the VNXe NFS Interface if_2 to ESXi NFS IP & VMKPing from ESXi NFS vmk to VNXe Server
Gather ESXi Host details:
uemcli -d 10.0.0.1 -u Local/admin -p Password#123 /remote/host show -detail

ID = 1003
Name = ESXi_01
Type = host
Address = 10.0.0.50
OS type = esx

Ping the vmkernel of the ESXi host to ensure proper connectivity:
uemcli -d 10.0.0.1 -u Local/admin -p Password123# /net/util ping -srcIf if_2 -addr 10.0.0.50
Operation completed successfully.
Ping the NFS Server from the vmkernel of the ESXi host:
vmkping -s 8972 -d 10.0.0.11

Failure here will normally imply a networking configuration issue – Verify subnets, vlan’s and any firewall configs are correct.

Step7 Check the status and details of the NFS Datastore
uemcli -d 10.0.0.1 -u Local/admin -p Password123# /stor/prov/vmware/nfs show -detail
ID = app_1
Name = NFS-01
Health state = OK (5)
Health details = "The component is operating normally. No action is required."
Server = file_server_2
Storage pool = NFS-01
Size = 858993459200 (800.0G)
Size used = 241740808192 (225.1G)
Maximum size = 4417404272640 (4.0T)
Thin provisioning enabled = no
Cached = no
Current allocation = 858993459200 (800.0G)
Protection size = 42949672960 (40.0G)
Protection size used = 0
Maximum protection size = 17592184995840 (16.0T)
Protection current allocation = 0
Auto-adjust protection size = yes
Local path = /NFS_01
Export path = /NFS_01
Default access = na
Root hosts = 1003[10.0.0.50]
Replication destination = no
Deduplication enabled = no
Creation time = 2014-06-11 09:55:00
Last modified time = 2014-06-11 09:55:00

Step8 For any Firewall in-place ensure the following port is open:
2049 – TCP/UDP – NFS – Required for NFS

Step9 Add the NFS file system manually to the ESXi host:
Log on to vCenter or the ESX host click on the ESXi host, from the Configuration tab choose Storage and Add storage:
1. Enter the IP address of the NFS server – 10.0.0.11
2. Enter the Folder name which is the mount point from VNXe – /NFS-01
3. Enter the datastore name that vCenter/ESXi will use to present as – NFS-01