<?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: Using 10G ports for Cluster IP. in ONTAP Hardware</title>
    <link>https://community.netapp.com/t5/ONTAP-Hardware/Using-10G-ports-for-Cluster-IP/m-p/122558#M7574</link>
    <description>True, but you failed to notice that the OP was talking about the cluster management LIF (not apparent from the text but clear once you take a loko at his "net int show" output) &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt; YES, the cluster management LIF can definitely share a port with the "regular" data LIFs. This is a fully supported configuration -Michael</description>
    <pubDate>Tue, 23 Aug 2016 12:55:09 GMT</pubDate>
    <dc:creator>Darkstar</dc:creator>
    <dc:date>2016-08-23T12:55:09Z</dc:date>
    <item>
      <title>Using 10G ports for Cluster IP.</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/Using-10G-ports-for-Cluster-IP/m-p/122356#M7570</link>
      <description>&lt;P&gt;Does the Cluster IP need a separate network port? &amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;When the Vendor Engineerset this up, he configured the Cluster IP&amp;nbsp; on a separate Gig-E port (e0L).&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But due to limited # of network ports on the switches, I've configured the Cluster IP on the same&amp;nbsp; LACP aggregated 10GbE ports used by the vserver data LIF.&amp;nbsp; Also the Cluster IP is on the same subnet as the Da&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Here's my net int show.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Logical&amp;nbsp;&amp;nbsp;&amp;nbsp; Status&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Network&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Current&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Current Is&lt;BR /&gt;Vserver&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Interface&amp;nbsp; Admin/Oper Address/Mask&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;Node&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Port&amp;nbsp;&amp;nbsp;&amp;nbsp; Home&lt;BR /&gt;----------- ---------- ---------- &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&amp;nbsp; ------------------ &amp;nbsp;&amp;nbsp; &amp;nbsp;------------- &amp;nbsp; &amp;nbsp; &amp;nbsp;&amp;nbsp; -------&amp;nbsp; ----&lt;BR /&gt;Cluster&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; netapp1-01_clus1 up/up 169.254.213.48/16 &amp;nbsp;&amp;nbsp; &amp;nbsp;netapp1-01 &amp;nbsp;&amp;nbsp; &amp;nbsp;e0a true&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; netapp1-01_clus2 up/up 169.254.252.241/16&amp;nbsp;&amp;nbsp; netapp1-01 &amp;nbsp;&amp;nbsp; &amp;nbsp;e0b true&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; netapp1-01_clus3 up/up 169.254.19.64/16 &amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp; netapp1-01 &amp;nbsp;&amp;nbsp; &amp;nbsp;e0c true&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; netapp1-01_clus4 up/up 169.254.179.61/16 &amp;nbsp;&amp;nbsp; &amp;nbsp;netapp1-01 &amp;nbsp;&amp;nbsp; &amp;nbsp;e0d true&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; netapp1-02_clus1 up/up 169.254.188.244/16 &amp;nbsp; netapp1-02 &amp;nbsp;&amp;nbsp; &amp;nbsp;e0a true&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; netapp1-02_clus2 up/up 169.254.209.44/16 &amp;nbsp;&amp;nbsp; &amp;nbsp;netapp1-02 &amp;nbsp;&amp;nbsp; &amp;nbsp;e0b true&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; netapp1-02_clus3 up/up 169.254.227.147/16 &amp;nbsp; netapp1-02 &amp;nbsp;&amp;nbsp; &amp;nbsp;e0c true&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; netapp1-02_clus4 up/up 169.254.131.146/16 &amp;nbsp; netapp1-02 &amp;nbsp;&amp;nbsp; &amp;nbsp;e0d true&lt;BR /&gt;&lt;BR /&gt;netapp1&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;STRONG&gt;cluster&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&amp;nbsp; up/up 20.43.0.124/24&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp; netapp1-01 &amp;nbsp;&amp;nbsp; &amp;nbsp;a0a-2300 true&lt;/STRONG&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; netapp1-01_mgmt1 up/up 20.40.99.10/24 &amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp; netapp1-01 &amp;nbsp;&amp;nbsp; &amp;nbsp;e0M true&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; netapp1-02_mgmt1 up/up 20.40.99.11/24 &amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp; netapp1-02 &amp;nbsp;&amp;nbsp; &amp;nbsp;e0M true&lt;BR /&gt;&lt;BR /&gt;vserver1&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;STRONG&gt;vs01_nfs_cifs_lif1 up/up 20.43.0.40/24 &amp;nbsp;&amp;nbsp; &amp;nbsp; &amp;nbsp;&amp;nbsp; netapp1-01&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;a0a-2300 true&lt;/STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 19:30:08 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/Using-10G-ports-for-Cluster-IP/m-p/122356#M7570</guid>
      <dc:creator>Ven</dc:creator>
      <dc:date>2025-06-04T19:30:08Z</dc:date>
    </item>
    <item>
      <title>Re: Using 10G ports for Cluster IP.</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/Using-10G-ports-for-Cluster-IP/m-p/122378#M7571</link>
      <description>&lt;P&gt;A cluster LIF should not be on the same subnet as a management LIF or a data LIF.&lt;/P&gt;&lt;P&gt;The LIF that is used for intracluster traffic. Cluster LIFs can be configured only on cluster ports. Cluster LIFs must always be created on 10-GbE network ports. Note: Cluster LIFs need not be created on 10-GbE network ports in FAS2040 and FAS2220 platforms.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Refer &lt;A href="https://library.netapp.com/ecm/ecm_download_file/ECMP1196907" target="_self"&gt;Clustered Data ONTAP® 8.2 Network Management Guide&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 17 Aug 2016 05:15:11 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/Using-10G-ports-for-Cluster-IP/m-p/122378#M7571</guid>
      <dc:creator>Sahana</dc:creator>
      <dc:date>2016-08-17T05:15:11Z</dc:date>
    </item>
    <item>
      <title>Re: Using 10G ports for Cluster IP.</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/Using-10G-ports-for-Cluster-IP/m-p/122381#M7572</link>
      <description>&lt;P&gt;Your question unfortunately sounds very confusing. "Cluster LIF" has very special meaning in cDOT - as already explained it refers to backend interconnect between cluster nodes and it must be on dedicated physical ports that cannot be shared with any other traffic type. But what you actually mean is likely "cluster management LIF". This can share port with any other data and management LIF of&amp;nbsp; any other SVM.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;By default cluster management LIF is named cluster_mgmt. Plain "cluster" is rather poor choice as it is highly ambiguous,&amp;nbsp;especially when used as adjective ("cluster IP", "cluster LIF"). On your place I would consider renaming it, e.g. to default cluster_mgmt that makes it obvious what you are speaking about.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;And find some time to make yourself familiar with cDOT network organization and&amp;nbsp;terminology &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 17 Aug 2016 06:50:38 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/Using-10G-ports-for-Cluster-IP/m-p/122381#M7572</guid>
      <dc:creator>aborzenkov</dc:creator>
      <dc:date>2016-08-17T06:50:38Z</dc:date>
    </item>
    <item>
      <title>Re: Using 10G ports for Cluster IP.</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/Using-10G-ports-for-Cluster-IP/m-p/122558#M7574</link>
      <description>True, but you failed to notice that the OP was talking about the cluster management LIF (not apparent from the text but clear once you take a loko at his "net int show" output) &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt; YES, the cluster management LIF can definitely share a port with the "regular" data LIFs. This is a fully supported configuration -Michael</description>
      <pubDate>Tue, 23 Aug 2016 12:55:09 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/Using-10G-ports-for-Cluster-IP/m-p/122558#M7574</guid>
      <dc:creator>Darkstar</dc:creator>
      <dc:date>2016-08-23T12:55:09Z</dc:date>
    </item>
  </channel>
</rss>

