<?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: One data LIF per node, per SVM? in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/One-data-LIF-per-node-per-SVM/m-p/141561#M31341</link>
    <description>&lt;P&gt;The importance of that advice relates to how you're using the system.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you have segmented Department A into SVM A on VLAN A, and Department B into SVM B on VLAN B, you don't need to have VLAN B IPs on SVM A.&lt;/P&gt;
&lt;P&gt;If you go further and have all of SVM A's volumes hosted on Node 1/Node 2 HA pair of a cluster, and all of SVM B's on Node 3/Node 4 HA pair, there's no need to have IPs for SVM B on Node 1 and Node 2.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hope this helps clarify the advice. Please feel free to ask any follow up questions!&lt;/P&gt;</description>
    <pubDate>Thu, 19 Jul 2018 04:09:32 GMT</pubDate>
    <dc:creator>AlexDawson</dc:creator>
    <dc:date>2018-07-19T04:09:32Z</dc:date>
    <item>
      <title>One data LIF per node, per SVM?</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/One-data-LIF-per-node-per-SVM/m-p/141556#M31337</link>
      <description>&lt;P&gt;&lt;STRONG&gt;&lt;EM&gt;"One data LIF per node, per SVM" this is suggested by multiple articles.&lt;/EM&gt;&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;&lt;EM&gt;My question is what if I need to have multiple VLAN connections, then I have to create multipel corresponding LIF's per node and per SVM. Would that have any issues with that?&amp;nbsp;&lt;/EM&gt;&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;&lt;EM&gt;Or it really should be "One data LIF per node, per SVM for each VLAN"&lt;/EM&gt;&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;&lt;EM&gt;Thank you for your inputs!&lt;/EM&gt;&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 13:30:06 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/One-data-LIF-per-node-per-SVM/m-p/141556#M31337</guid>
      <dc:creator>heightsnj</dc:creator>
      <dc:date>2025-06-04T13:30:06Z</dc:date>
    </item>
    <item>
      <title>Re: One data LIF per node, per SVM?</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/One-data-LIF-per-node-per-SVM/m-p/141561#M31341</link>
      <description>&lt;P&gt;The importance of that advice relates to how you're using the system.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you have segmented Department A into SVM A on VLAN A, and Department B into SVM B on VLAN B, you don't need to have VLAN B IPs on SVM A.&lt;/P&gt;
&lt;P&gt;If you go further and have all of SVM A's volumes hosted on Node 1/Node 2 HA pair of a cluster, and all of SVM B's on Node 3/Node 4 HA pair, there's no need to have IPs for SVM B on Node 1 and Node 2.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hope this helps clarify the advice. Please feel free to ask any follow up questions!&lt;/P&gt;</description>
      <pubDate>Thu, 19 Jul 2018 04:09:32 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/One-data-LIF-per-node-per-SVM/m-p/141561#M31341</guid>
      <dc:creator>AlexDawson</dc:creator>
      <dc:date>2018-07-19T04:09:32Z</dc:date>
    </item>
    <item>
      <title>Re: One data LIF per node, per SVM?</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/One-data-LIF-per-node-per-SVM/m-p/141569#M31343</link>
      <description>&lt;P&gt;You are right, if Dept A has the network infrastructure and able to reach VLAN B for Dept B.&lt;/P&gt;
&lt;P&gt;In my case, it is different.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Using your example. SVM A has VLAN A for Dept A, and SVM B has VLAN B for Dept B. both SVM's and VLAN's host own Datastores and yet in respective two seperated Layer-2 and non-routeble networks.&amp;nbsp; I would want to have Dept A to access datastores in SVM B. In this case, I would have to create LIF's in SVM B, and these new LIF's have to be created in VLAN A. Otherwise, Dept A cannot access Dept B's datastores.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;So, in this case, there are two data LIF's per node, per SVM. Any thoughts on that?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Thu, 19 Jul 2018 21:04:25 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/One-data-LIF-per-node-per-SVM/m-p/141569#M31343</guid>
      <dc:creator>heightsnj</dc:creator>
      <dc:date>2018-07-19T21:04:25Z</dc:date>
    </item>
    <item>
      <title>Re: One data LIF per node, per SVM?</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/One-data-LIF-per-node-per-SVM/m-p/141583#M31345</link>
      <description>&lt;P&gt;Perfectly fine.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The one LIF per node per SVM is a minimum, not a maximum.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;There is another school of thought which extends to one LIF per datastore - so if you move a datastore between nodes, you can move its hosting LIF. I have a&amp;nbsp;post on my site at&amp;nbsp;&lt;A href="https://alexdawson.net/2016/08/ontap-why-and-why-not-to-have-one-lif-per-nfs-volume/" target="_blank"&gt;https://alexdawson.net/2016/08/ontap-why-and-why-not-to-have-one-lif-per-nfs-volume/&lt;/A&gt; discussing why you might or might not want to do that.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hope this helps!&lt;/P&gt;</description>
      <pubDate>Thu, 19 Jul 2018 21:29:56 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/One-data-LIF-per-node-per-SVM/m-p/141583#M31345</guid>
      <dc:creator>AlexDawson</dc:creator>
      <dc:date>2018-07-19T21:29:56Z</dc:date>
    </item>
  </channel>
</rss>

