<?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: FC SVM on AFF900 cluster 4 nodes in AFF</title>
    <link>https://community.netapp.com/t5/AFF/FC-SVM-on-AFF900-cluster-4-nodes/m-p/460751#M1420</link>
    <description>&lt;P&gt;When using SAN, it is a Best Practice to place ONE FC LIF from Each Fabric on EACH node.&lt;/P&gt;&lt;P&gt;2 node cluster = 2 LIFs per node = 4 FC LIFS&lt;/P&gt;&lt;P&gt;4 node cluster&amp;nbsp;= 2 LIFs per node = 8 FC LIFS&lt;/P&gt;&lt;P&gt;You then do your single initiator zoning for each host to the NetApp.&lt;/P&gt;&lt;P&gt;Then if you allow the defaults to happen, Selective LUN Mapping (SLM) will advertise the node hosting the LUN and the HA-Partner FC LIFs to clients. If you need to move the LUN, ONTAP will update the advertisement to use the FC LIFs on the destination nodes.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Bottom Line, please place at least TWO FC LIFs (one per Fabric) on each node.&lt;/P&gt;</description>
    <pubDate>Thu, 15 May 2025 14:42:33 GMT</pubDate>
    <dc:creator>TMACMD</dc:creator>
    <dc:date>2025-05-15T14:42:33Z</dc:date>
    <item>
      <title>FC SVM on AFF900 cluster 4 nodes</title>
      <link>https://community.netapp.com/t5/AFF/FC-SVM-on-AFF900-cluster-4-nodes/m-p/460743#M1419</link>
      <description>&lt;P&gt;Hi to all,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;we have a cluster with 4 nodes on the same rack,.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;AFF900-PA::cluster&amp;gt; cluster show&lt;BR /&gt;Node Health Eligibility&lt;BR /&gt;--------------------- ------- ------------&lt;BR /&gt;AFF900-PA-01 true true&lt;BR /&gt;AFF900-PA-02 true true&lt;BR /&gt;AFF900-PA-03 true true&lt;BR /&gt;AFF900-PA-04 true true&lt;BR /&gt;4 entries were displayed.&lt;/P&gt;&lt;P&gt;From gui we view cluster separated in 2 couple of group (view image):&lt;/P&gt;&lt;P&gt;G1 -&amp;gt; PA-01/PA-03&lt;/P&gt;&lt;P&gt;G2 -&amp;gt; PA-02/PA-04&lt;/P&gt;&lt;P&gt;We have defined an svm (only fc protocol) anc we create lif only on port 10a and 10b of physical port of G1.&lt;/P&gt;&lt;P&gt;I ask to you is it possible in case of disaster on G1 migrate automatically SVM_FC on G2?&lt;/P&gt;&lt;P&gt;If create SVM_FC with lif 10a and 11a of all 4 nodes, it is possible, in case of disaster of G1 migrate automatically SVM_FC on G2.&lt;/P&gt;&lt;P&gt;Thanks to all&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 15 May 2025 08:07:58 GMT</pubDate>
      <guid>https://community.netapp.com/t5/AFF/FC-SVM-on-AFF900-cluster-4-nodes/m-p/460743#M1419</guid>
      <dc:creator>ale</dc:creator>
      <dc:date>2025-05-15T08:07:58Z</dc:date>
    </item>
    <item>
      <title>Re: FC SVM on AFF900 cluster 4 nodes</title>
      <link>https://community.netapp.com/t5/AFF/FC-SVM-on-AFF900-cluster-4-nodes/m-p/460751#M1420</link>
      <description>&lt;P&gt;When using SAN, it is a Best Practice to place ONE FC LIF from Each Fabric on EACH node.&lt;/P&gt;&lt;P&gt;2 node cluster = 2 LIFs per node = 4 FC LIFS&lt;/P&gt;&lt;P&gt;4 node cluster&amp;nbsp;= 2 LIFs per node = 8 FC LIFS&lt;/P&gt;&lt;P&gt;You then do your single initiator zoning for each host to the NetApp.&lt;/P&gt;&lt;P&gt;Then if you allow the defaults to happen, Selective LUN Mapping (SLM) will advertise the node hosting the LUN and the HA-Partner FC LIFs to clients. If you need to move the LUN, ONTAP will update the advertisement to use the FC LIFs on the destination nodes.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Bottom Line, please place at least TWO FC LIFs (one per Fabric) on each node.&lt;/P&gt;</description>
      <pubDate>Thu, 15 May 2025 14:42:33 GMT</pubDate>
      <guid>https://community.netapp.com/t5/AFF/FC-SVM-on-AFF900-cluster-4-nodes/m-p/460751#M1420</guid>
      <dc:creator>TMACMD</dc:creator>
      <dc:date>2025-05-15T14:42:33Z</dc:date>
    </item>
  </channel>
</rss>

