An administrator created an SVM for a VMware vSphere 6.5 cluster. For the SVM, the NFS protocol was enabled. Data LIFs were configured with jumbo frames.
The nfs01 volume was created and mounted as junction path / nfs01. A VMware export policy that allowed all the hosts of the cluster was applied to the SVM.
However, the hosts are unable to mount the volume.
In this scenario, what caused the problem?
In this scenario, the most likely cause of the problem is that the maximum transmission unit (MTU) was not set properly on the ESXi hosts. Jumbo frames require a specific MTU size, typically 9000 bytes, to be configured consistently across all devices in the network path, including the ESXi hosts. If the MTU is not set correctly, it can prevent proper communication and result in the hosts being unable to mount the NFS volume.
ans is C
Answer is D https://library.netapp.com/ecmdocs/ECMP1552554/html/GUID-0FBEAE29-31B4-4922-80D9-92F59C929C7B.html
it's D
any Kb reference on this?
The answer is C, It is true that an export policy must be enabled on the SVM to allow ESXi hosts access through NFSv3, however, the question clearly states that an export policy was already created, hence D is incorrect
Yes but it is specified that a Vmware export policy was CREATED, but you also need to allow ESXi hosts in DEFAULT policy. (and that is not specified) Moreover I m not sure that an incorrect MTU prevent you from mounting a volume, it will cause misfunctions for sure but...
https://docs.netapp.com/us-en/ontap-sm-classic/nfs-config-esxi/task_configuring_host_iscsi_ports_vswitches.html step 4. Configure jumbo frames for the vSwitch (MTU size of 9000, if used).