<?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: Re-IPing node management and cluster address in ONTAP Hardware</title>
    <link>https://community.netapp.com/t5/ONTAP-Hardware/Re-IPing-node-management-and-cluster-address/m-p/124455#M7684</link>
    <description>&lt;P&gt;That seems to be a complicated setup&amp;nbsp;&lt;img id="smileysurprised" class="emoticon emoticon-smileysurprised" src="https://community.netapp.com/i/smilies/16x16_smiley-surprised.png" alt="Smiley Surprised" title="Smiley Surprised" /&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Are you still able to access the cluster through the 192 series address?&lt;/P&gt;&lt;P&gt;Since you mentioned "remote" site, I am assuming the you dont have direct console access.&lt;/P&gt;&lt;P&gt;I think you can do this only if you have uninterrupted access to CLI, which is only possible via Console or SP.&lt;/P&gt;&lt;P&gt;Is this in production right now?&lt;/P&gt;</description>
    <pubDate>Thu, 20 Oct 2016 08:46:44 GMT</pubDate>
    <dc:creator>georgevj</dc:creator>
    <dc:date>2016-10-20T08:46:44Z</dc:date>
    <item>
      <title>Re-IPing node management and cluster address</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/Re-IPing-node-management-and-cluster-address/m-p/124188#M7667</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks to the shortsightedness and general stupidity of our network team I need to completely change the IPs for everything on a Cluster mode FAS2554 at a remote site.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For node and cluster management IPs this seems to quite a challenge.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;When I installed it a few months ago it had node management IP's of 192.168.2.29 &amp;amp; 30 with a cluster management of .31. SP ports are in the same subnet and were working. Following the replacement of network switches and a re-IP, they need to be 172.16.103.x.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Because of the radical subnet change I don’t think it’s simply a series of “network modify” commands. I believe it’s going to involve creating a new broadcast domain and deleting the eM0 ports from the existing one.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Does anyone know if there’s detailed step by step guide to doing this sort of task, or has anyone done this before?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The SVMs also need to be re-IP’d but I think that will be simpler, just a case of removing a port at a time from it and adding it back with a new IP.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 18:38:39 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/Re-IPing-node-management-and-cluster-address/m-p/124188#M7667</guid>
      <dc:creator>nigelg1965</dc:creator>
      <dc:date>2025-06-04T18:38:39Z</dc:date>
    </item>
    <item>
      <title>Re: Re-IPing node management and cluster address</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/Re-IPing-node-management-and-cluster-address/m-p/124455#M7684</link>
      <description>&lt;P&gt;That seems to be a complicated setup&amp;nbsp;&lt;img id="smileysurprised" class="emoticon emoticon-smileysurprised" src="https://community.netapp.com/i/smilies/16x16_smiley-surprised.png" alt="Smiley Surprised" title="Smiley Surprised" /&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Are you still able to access the cluster through the 192 series address?&lt;/P&gt;&lt;P&gt;Since you mentioned "remote" site, I am assuming the you dont have direct console access.&lt;/P&gt;&lt;P&gt;I think you can do this only if you have uninterrupted access to CLI, which is only possible via Console or SP.&lt;/P&gt;&lt;P&gt;Is this in production right now?&lt;/P&gt;</description>
      <pubDate>Thu, 20 Oct 2016 08:46:44 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/Re-IPing-node-management-and-cluster-address/m-p/124455#M7684</guid>
      <dc:creator>georgevj</dc:creator>
      <dc:date>2016-10-20T08:46:44Z</dc:date>
    </item>
    <item>
      <title>Re: Re-IPing node management and cluster address</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/Re-IPing-node-management-and-cluster-address/m-p/124711#M7699</link>
      <description>&lt;P&gt;After a lot of faffing and blind alleys, I have found the solution with help from NetApp.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Simply create another bunch of lifs for node and cluster management on the same physical ports with the new IPs etc.&lt;/P&gt;</description>
      <pubDate>Tue, 25 Oct 2016 14:56:32 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/Re-IPing-node-management-and-cluster-address/m-p/124711#M7699</guid>
      <dc:creator>nigelg1965</dc:creator>
      <dc:date>2016-10-25T14:56:32Z</dc:date>
    </item>
    <item>
      <title>Re: Re-IPing node management and cluster address</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/Re-IPing-node-management-and-cluster-address/m-p/124714#M7700</link>
      <description>&lt;P&gt;That will work. &amp;nbsp;You can add the new subnet to the old&amp;nbsp;broadcast domain, along with the default gateway for the new subnet, and optionally a pool of IPs. &amp;nbsp;Build all new lifs, decomission the old lifs, and clean up things like dns and ntp if needed.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 25 Oct 2016 17:17:27 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/Re-IPing-node-management-and-cluster-address/m-p/124714#M7700</guid>
      <dc:creator>SeanHatfield</dc:creator>
      <dc:date>2016-10-25T17:17:27Z</dc:date>
    </item>
  </channel>
</rss>

