<?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 Removal of nodes from a cluster - Hardware Upgrade in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/Removal-of-nodes-from-a-cluster-Hardware-Upgrade/m-p/137015#M30205</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have a question around the permanent removal of nodes from a cluster, such as during a hardware refresh and I'm trying to establish the correct procedures/checklists to go through to ensure that during a hardware upgrade nothing is overlooked and user disruption is kept to a minimum.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Scenario: (All nodes running ONTAP 9.1 P7 and are HA pairs)&lt;/P&gt;&lt;P&gt;2 x FAS 8020 units (cluster nodes 1 to 4)&lt;/P&gt;&lt;P&gt;1 x AFF A200 unit (cluster nodes 5 and 6)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Assuming that all user data volumes have been migrated to the aggregates on the AFF nodes 5+6 then this should, I believe, just leave the following steps however I would welcome any comments to correct or enhance the process.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;• Migrate Data SVM root volumes from FAS8020 aggregates on to AFF nodes (we already have LS-mirror copies but the ‘live’ version is still on the 8020s)&lt;BR /&gt;• Data LIFs for CIFS and iSCSI (hosted on the 8020s) have to be removed, or migrated to the new AFF nodes.&lt;BR /&gt;• Make the 8020 nodes ineligible for cluster RDB operations (i.e. remove eligibility forcing it to use one of the AFF nodes) - using command: node modify -node nodenametoberemoved -eligibility false&lt;BR /&gt;• Perform a 'cluster leave' operation on the 8020’s - does this need to be performed on each node in a HA pair?&lt;/P&gt;&lt;P&gt;• Physically disconnect the node from cluster network&lt;BR /&gt;• Zero the data disks&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks in advance,&lt;/P&gt;&lt;P&gt;Garth&lt;/P&gt;</description>
    <pubDate>Wed, 04 Jun 2025 14:11:12 GMT</pubDate>
    <dc:creator>GLOYNSSNS</dc:creator>
    <dc:date>2025-06-04T14:11:12Z</dc:date>
    <item>
      <title>Removal of nodes from a cluster - Hardware Upgrade</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Removal-of-nodes-from-a-cluster-Hardware-Upgrade/m-p/137015#M30205</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have a question around the permanent removal of nodes from a cluster, such as during a hardware refresh and I'm trying to establish the correct procedures/checklists to go through to ensure that during a hardware upgrade nothing is overlooked and user disruption is kept to a minimum.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Scenario: (All nodes running ONTAP 9.1 P7 and are HA pairs)&lt;/P&gt;&lt;P&gt;2 x FAS 8020 units (cluster nodes 1 to 4)&lt;/P&gt;&lt;P&gt;1 x AFF A200 unit (cluster nodes 5 and 6)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Assuming that all user data volumes have been migrated to the aggregates on the AFF nodes 5+6 then this should, I believe, just leave the following steps however I would welcome any comments to correct or enhance the process.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;• Migrate Data SVM root volumes from FAS8020 aggregates on to AFF nodes (we already have LS-mirror copies but the ‘live’ version is still on the 8020s)&lt;BR /&gt;• Data LIFs for CIFS and iSCSI (hosted on the 8020s) have to be removed, or migrated to the new AFF nodes.&lt;BR /&gt;• Make the 8020 nodes ineligible for cluster RDB operations (i.e. remove eligibility forcing it to use one of the AFF nodes) - using command: node modify -node nodenametoberemoved -eligibility false&lt;BR /&gt;• Perform a 'cluster leave' operation on the 8020’s - does this need to be performed on each node in a HA pair?&lt;/P&gt;&lt;P&gt;• Physically disconnect the node from cluster network&lt;BR /&gt;• Zero the data disks&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks in advance,&lt;/P&gt;&lt;P&gt;Garth&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 14:11:12 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Removal-of-nodes-from-a-cluster-Hardware-Upgrade/m-p/137015#M30205</guid>
      <dc:creator>GLOYNSSNS</dc:creator>
      <dc:date>2025-06-04T14:11:12Z</dc:date>
    </item>
    <item>
      <title>Re: Removal of nodes from a cluster - Hardware Upgrade</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Removal-of-nodes-from-a-cluster-Hardware-Upgrade/m-p/143160#M31762</link>
      <description>&lt;P&gt;This is probably a bit late for you, but I'm going to reply anyway for my own future reference....&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;According to the doco, you remove the nodes one at a time, but you must remove both nodes of a HA pair.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://docs.netapp.com/ontap-9/index.jsp?topic=%2Fcom.netapp.doc.dot-cm-sag%2FGUID-6731B7F7-0C48-4474-A67B-E1F1CCBA77A6.html&amp;nbsp;" target="_blank"&gt;https://docs.netapp.com/ontap-9/index.jsp?topic=%2Fcom.netapp.doc.dot-cm-sag%2FGUID-6731B7F7-0C48-4474-A67B-E1F1CCBA77A6.html&amp;nbsp;&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We would also do a sanitise on all the disks (we either have to sanitise, or destroy the disks)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Be interested to know how it went!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Cheers,&lt;/P&gt;
&lt;P&gt;Stuart&lt;/P&gt;</description>
      <pubDate>Wed, 03 Oct 2018 00:28:40 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Removal-of-nodes-from-a-cluster-Hardware-Upgrade/m-p/143160#M31762</guid>
      <dc:creator>OZWALKERZ</dc:creator>
      <dc:date>2018-10-03T00:28:40Z</dc:date>
    </item>
  </channel>
</rss>

