Is the datastore exported in the vfiler? It looks like SC cant find the datastore in the vfiler. Everything must be in the vfiler, if you exported from physical contoller things wont work. Can you send the output from "exportfs" command from vfiler and also the mount path in ESX for this datastore?
When I looked at the log, I didn't see /vol/tscdbm01. Did you run this against the same export point? If the change was against the vfiler, we would expect to see /vol/tscdbm01 in the ONTAP call but I didn't see it. You might want to run the same command against the vfiler, but use ZEDI:
I'm looking for differences in the output for those ONTAP calls (nfs-exportfs-list-rules, nfs-exportfs-list-rules-2) to see whether /vol/tscdbm01 is or isn't showing up in the --2 version but does show up in the original.
If you want connect to the vfiler and run the API call with ZEDI, that might be a better approach. You can send the results directly to 'firstname.lastname@example.org' that might help expedite the debugging process. Thanks,
The issue is we need to see the output differences for the ZAPI call to the vfiler. Can you return those results with ZEDI against the vfiler? That might give us a clue why it isn’t being found. Thanks!
Please re-run with the <pathname></pathname> and <persistent></persistent> deleted in the commands from the upper-middle window. Your API results are skewed because it thinks you are trying to enter a persistent value when you haven't provided one.
Simply running <nfs-exportfs-list-rules></nfs-exportfs-list-rules> and <nfs-exportfs-list-rules-2></nfs-exportfs-list-rules-2> is sufficient without the input options.