<?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 Determining IP addresses needed for NFS deployment in ONTAP Hardware</title>
    <link>https://community.netapp.com/t5/ONTAP-Hardware/Determining-IP-addresses-needed-for-NFS-deployment/m-p/98639#M6021</link>
    <description>&lt;P&gt;I have an NFS deployment as such:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have one storage system (FAS2040). &amp;nbsp;There is a VIF on controller 1, and one VIF on controller 2. &amp;nbsp;I will have 3 NFS exports on the storage system. &amp;nbsp;If one controller fails, the other needs to be able to service all 3 NFS exports.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;How many IP addresses need to be assigned to the storage system? &amp;nbsp;Is it one IP address for VIF1 on controller 1, and another IP address for VIF 2 on controller 2?&lt;/P&gt;</description>
    <pubDate>Thu, 05 Jun 2025 05:21:56 GMT</pubDate>
    <dc:creator>CLOUDMINER</dc:creator>
    <dc:date>2025-06-05T05:21:56Z</dc:date>
    <item>
      <title>Determining IP addresses needed for NFS deployment</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/Determining-IP-addresses-needed-for-NFS-deployment/m-p/98639#M6021</link>
      <description>&lt;P&gt;I have an NFS deployment as such:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have one storage system (FAS2040). &amp;nbsp;There is a VIF on controller 1, and one VIF on controller 2. &amp;nbsp;I will have 3 NFS exports on the storage system. &amp;nbsp;If one controller fails, the other needs to be able to service all 3 NFS exports.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;How many IP addresses need to be assigned to the storage system? &amp;nbsp;Is it one IP address for VIF1 on controller 1, and another IP address for VIF 2 on controller 2?&lt;/P&gt;</description>
      <pubDate>Thu, 05 Jun 2025 05:21:56 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/Determining-IP-addresses-needed-for-NFS-deployment/m-p/98639#M6021</guid>
      <dc:creator>CLOUDMINER</dc:creator>
      <dc:date>2025-06-05T05:21:56Z</dc:date>
    </item>
    <item>
      <title>Re: Determining IP addresses needed for NFS deployment</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/Determining-IP-addresses-needed-for-NFS-deployment/m-p/98646#M6026</link>
      <description>&lt;P&gt;Quote:&lt;/P&gt;&lt;P&gt;I have one storage system (FAS2040). &amp;nbsp;There is a VIF on controller 1, and one VIF on controller 2. &amp;nbsp;I will have 3 NFS exports on the storage system. &amp;nbsp;If one controller fails, the other needs to be able to service all 3 NFS exports.&lt;/P&gt;&lt;P&gt;/quote&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You have to specify the partner VIF in the rc file. If you do not specify a partner interface, a takeover will result in losing datastore connectivity.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The local node must specify, using the &lt;STRONG&gt;partner&lt;/STRONG&gt; option of the &lt;STRONG&gt;ifconfig&lt;/STRONG&gt; command, the mapping of the partner's interface group. For example, to map the partner's ifgrp2 interface to the local ifgrp1 interface, the following command is required:&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;ifconfig&lt;/STRONG&gt; &lt;STRONG&gt;ifgrp1&lt;/STRONG&gt; &lt;STRONG&gt;partner&lt;/STRONG&gt; &lt;STRONG&gt;ifgrp2&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Note that the interface must be named, &lt;EM&gt;not&lt;/EM&gt; &lt;EM&gt;the&lt;/EM&gt; &lt;EM&gt;address.&lt;/EM&gt; The mapping must be at the top-level trunk, if trunks are nested. You do not map link-by-link.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Quote:&lt;/P&gt;&lt;P&gt;How many IP addresses need to be assigned to the storage system? &amp;nbsp;Is it one IP address for VIF1 on controller 1, and another IP address for VIF 2 on controller 2?&lt;/P&gt;&lt;P&gt;/quote&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It depends &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;&lt;P&gt;If all datastores reside on controller 1, then the minimum configuration is 1 ip address.&lt;/P&gt;&lt;P&gt;Since this is bad for multiple datastore (via nfs) you should provide at least 2 on one controller.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Michael&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 20 Dec 2014 01:31:00 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/Determining-IP-addresses-needed-for-NFS-deployment/m-p/98646#M6026</guid>
      <dc:creator>DAMNX6789</dc:creator>
      <dc:date>2014-12-20T01:31:00Z</dc:date>
    </item>
    <item>
      <title>Re: Determining IP addresses needed for NFS deployment</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/Determining-IP-addresses-needed-for-NFS-deployment/m-p/98704#M6030</link>
      <description>&lt;P&gt;If you want to load balance your NFS storage traffic from vSphere between the 1Gb physical ports you will need 2 IP addresses per VIF. 2 physical ports = 2 IP addresses.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You want to refer to NetApp TR-3749 NetApp Storage Best Practices for VMware vSphere.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 23 Dec 2014 18:56:20 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/Determining-IP-addresses-needed-for-NFS-deployment/m-p/98704#M6030</guid>
      <dc:creator>cgeck0000</dc:creator>
      <dc:date>2014-12-23T18:56:20Z</dc:date>
    </item>
  </channel>
</rss>

