I seem to have misunderstood NFS Export Policies in ONTAP, or at least I can't
seem to get what I want to work. It seems to inherit the export policy "above" it.
I have a SVM with two volumes. The first is NFS exported to a bunch of hosts, I
wanted another volume, on the same SVM exported to a different host.
Host Group A should see Volume A
Host B should see Volume B
I thought I'd be able to do this by creating a new policy with the appropriate
rule, assign the policy to the volume and that would be it. I ran into problems
so I created a test SVM to reproduce the issue.
My test SVM has two export policies.
```
netapp::> vserver export-policy show -vserver test_vserver
Vserver Policy Name
--------------- -------------------
test_vserver default
test_vserver vmware_vc_backups
```
The default policy has no rules, the `vmware_vc_backups` does.
```
netapp::> vserver export-policy rule show -vserver test_vserver -policyname default -ruleindex 1
There are no entries matching your query.
```
```
netapp::> vserver export-policy rule show -vserver test_vserver -policyname vmware_vc_backups -ruleindex 1
Vserver: test_vserver
Policy Name: vmware_vc_backups
Rule Index: 1
Access Protocol: nfs3, nfs4, nfs
List of Client Match Hostnames, IP Addresses, Netgroups, or Domains: 1.1.1.1
RO Access Rule: any
RW Access Rule: any
User ID To Which Anonymous Users Are Mapped: 65534
Superuser Security Types: any
Honor SetUID Bits in SETATTR: true
Allow Creation of Devices: true
```
In this configuration, my client cannot mount the NFS volume. If I copy the rule to the default policy, it mounts just fine. I don't even have to change the export policy assigned to the volume.
Is this just the way it works or am I doing something wrong. It seems that I can't currently have 2 different volumes on the same SVM mounted to diverse clients without crossover.
