For System Manager to create a VMware NFS datastore, an entry into the exports should be done irrespective of the nfs.export.auto-update option.
The nfs.export.auto-update option comes into picture when you are using the regular volume create.
The information that Amrita's asked for will help. We've tried reproducing this issue on an 7.3.7 and are unable to replicate this scenario. Mainly information on the ONTAP version, exports file before and after the operation and System Manager logs will help.
Your questions made me think... maybe this time it isn't System Manager??? Sometimes passed experience makes you jumping to conclusions, sorry.
I've went back in time and analyzed the exports in "My Autosupport" and found that the exports file changed back in Nov 27th, 2012. Thank god I never had to reboot the system in this time...
Now I'm trying to find out the reason for this change. I did run Config Advisor on this day, but assume this tool is not modifying any files in /etc, only analyzing them. The header in the exports file says (#Auto-generated by setup Tue Nov 27 11:29:06 CET 2012) but I'd never run setup on a tuesday in the middle of the day... strange.
i have the following test environment and reproduced the following:
Fas2240 7-mode Ontap 8.1.2
System Manager 2.1
When i create a volume with the "Provision Storage for VMware" option there are two different Results:
with the Data Ontap option "nfs.export.auto-update" to OFF the following accurs:
When I renamed the Volume after the Creation (with the System Manager 2.1), the exportfs File isn't updated, so after the next reboot or cluster takeover, the access from the ESX Servers is disconnected. (when no manuel editing of the exportfs File happens)
with the Data Ontap option "nfs.export.auto-update" to ON the following accurs:
The rename with the System Manger 2.1 happens successfully, the exportfs File is updated to the correct value.