<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: NFS exports to different sets of systems on the same SVM in Network and Storage Protocols</title>
    <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/NFS-exports-to-different-sets-of-systems-on-the-same-SVM/m-p/441732#M9815</link>
    <description>&lt;P&gt;Hi there!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Yes, clients must satisfy the entire set of export policies that apply to a path.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For your scenario, the default policy should allow read to all, and then you allow write and read to some for the sub folder policies.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;/ -&amp;nbsp; Policy "default"&lt;/P&gt;&lt;P&gt;-/volume_A - Policy "subset_A"&lt;/P&gt;&lt;P&gt;-/volume_B - Policy "subset_B"&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So in this example, if all clients can read by policy "default" but only 10.0.1.0/24 by policy Subset_A and 10.0.2.0/24 by policy Subset_B, 10.0.2.1 won't be able to read /volume_A&lt;/P&gt;</description>
    <pubDate>Fri, 17 Feb 2023 02:39:07 GMT</pubDate>
    <dc:creator>AlexDawson</dc:creator>
    <dc:date>2023-02-17T02:39:07Z</dc:date>
    <item>
      <title>NFS exports to different sets of systems on the same SVM</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/NFS-exports-to-different-sets-of-systems-on-the-same-SVM/m-p/441702#M9814</link>
      <description>&lt;P&gt;I seem to have misunderstood NFS Export Policies in ONTAP, or at least I can't&lt;BR /&gt;seem to get what I want to work. It seems to inherit the export policy "above" it.&lt;/P&gt;&lt;P&gt;I have a SVM with two volumes. The first is NFS exported to a bunch of hosts, I&lt;BR /&gt;wanted another volume, on the same SVM exported to a different host.&lt;/P&gt;&lt;P&gt;Host Group A should see Volume A&lt;BR /&gt;Host B should see Volume B&lt;/P&gt;&lt;P&gt;I thought I'd be able to do this by creating a new policy with the appropriate&lt;BR /&gt;rule, assign the policy to the volume and that would be it. I ran into problems&lt;BR /&gt;so I created a test SVM to reproduce the issue.&lt;/P&gt;&lt;P&gt;My test SVM has two export policies.&lt;/P&gt;&lt;P&gt;```&lt;BR /&gt;netapp::&amp;gt; vserver export-policy show -vserver test_vserver&lt;BR /&gt;Vserver Policy Name&lt;BR /&gt;--------------- -------------------&lt;BR /&gt;test_vserver default&lt;BR /&gt;test_vserver vmware_vc_backups&lt;BR /&gt;```&lt;/P&gt;&lt;P&gt;The default policy has no rules, the `vmware_vc_backups` does.&lt;/P&gt;&lt;P&gt;```&lt;BR /&gt;netapp::&amp;gt; vserver export-policy rule show -vserver test_vserver -policyname default -ruleindex 1&lt;BR /&gt;There are no entries matching your query.&lt;BR /&gt;```&lt;/P&gt;&lt;P&gt;```&lt;BR /&gt;netapp::&amp;gt; vserver export-policy rule show -vserver test_vserver -policyname vmware_vc_backups -ruleindex 1&lt;/P&gt;&lt;P&gt;Vserver: test_vserver&lt;BR /&gt;Policy Name: vmware_vc_backups&lt;BR /&gt;Rule Index: 1&lt;BR /&gt;Access Protocol: nfs3, nfs4, nfs&lt;BR /&gt;List of Client Match Hostnames, IP Addresses, Netgroups, or Domains: 1.1.1.1&lt;BR /&gt;RO Access Rule: any&lt;BR /&gt;RW Access Rule: any&lt;BR /&gt;User ID To Which Anonymous Users Are Mapped: 65534&lt;BR /&gt;Superuser Security Types: any&lt;BR /&gt;Honor SetUID Bits in SETATTR: true&lt;BR /&gt;Allow Creation of Devices: true&lt;BR /&gt;```&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 09:52:41 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/NFS-exports-to-different-sets-of-systems-on-the-same-SVM/m-p/441702#M9814</guid>
      <dc:creator>__mattb__</dc:creator>
      <dc:date>2025-06-04T09:52:41Z</dc:date>
    </item>
    <item>
      <title>Re: NFS exports to different sets of systems on the same SVM</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/NFS-exports-to-different-sets-of-systems-on-the-same-SVM/m-p/441732#M9815</link>
      <description>&lt;P&gt;Hi there!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Yes, clients must satisfy the entire set of export policies that apply to a path.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For your scenario, the default policy should allow read to all, and then you allow write and read to some for the sub folder policies.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;/ -&amp;nbsp; Policy "default"&lt;/P&gt;&lt;P&gt;-/volume_A - Policy "subset_A"&lt;/P&gt;&lt;P&gt;-/volume_B - Policy "subset_B"&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So in this example, if all clients can read by policy "default" but only 10.0.1.0/24 by policy Subset_A and 10.0.2.0/24 by policy Subset_B, 10.0.2.1 won't be able to read /volume_A&lt;/P&gt;</description>
      <pubDate>Fri, 17 Feb 2023 02:39:07 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/NFS-exports-to-different-sets-of-systems-on-the-same-SVM/m-p/441732#M9815</guid>
      <dc:creator>AlexDawson</dc:creator>
      <dc:date>2023-02-17T02:39:07Z</dc:date>
    </item>
  </channel>
</rss>

