<?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: Performing maintenance on nodes of a cluster in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/Performing-maintenance-on-nodes-of-a-cluster/m-p/133080#M29047</link>
    <description>&lt;P&gt;Move epsilon before you start.&lt;/P&gt;&lt;P&gt;Send an ASUP&lt;/P&gt;&lt;P&gt;Run Config Advisor&amp;nbsp;&lt;/P&gt;&lt;P&gt;Ensure that none of your SVM root volumes are on that HA pair&lt;/P&gt;&lt;P&gt;Label everything, especially the FCoE links to make sure they get reconnected correctly.&lt;/P&gt;&lt;P&gt;Inhibit takeover when you shut them down&lt;/P&gt;&lt;P&gt;After you bring them back up, verify FCoE/ALUA/MPIO&lt;/P&gt;&lt;P&gt;Run ConfigAdvisor again&lt;/P&gt;&lt;P&gt;Do a Takeover/Giveback test in both directions&lt;/P&gt;&lt;P&gt;Send another ASUP&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 25 Jul 2017 16:53:43 GMT</pubDate>
    <dc:creator>SeanHatfield</dc:creator>
    <dc:date>2017-07-25T16:53:43Z</dc:date>
    <item>
      <title>Performing maintenance on nodes of a cluster</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Performing-maintenance-on-nodes-of-a-cluster/m-p/133079#M29046</link>
      <description>&lt;P&gt;Good afternoon experts,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have a six node (3 HA pair) cluster. Our cluster is relatively&amp;nbsp; simple in terms of how we use them. All SAN via FCoE. We want to perform maintenance on one of the HA pairs because we want to relocate to a different rack. We already accept the outage for any data hosted on the HA-pair.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there any thing I should watch out for when I shutdown this HA pair? Anything special I should take into consideration to make sure that the cluster and the remaining HA pairs continues to function?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;DB&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 14:48:24 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Performing-maintenance-on-nodes-of-a-cluster/m-p/133079#M29046</guid>
      <dc:creator>duanebachi1</dc:creator>
      <dc:date>2025-06-04T14:48:24Z</dc:date>
    </item>
    <item>
      <title>Re: Performing maintenance on nodes of a cluster</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Performing-maintenance-on-nodes-of-a-cluster/m-p/133080#M29047</link>
      <description>&lt;P&gt;Move epsilon before you start.&lt;/P&gt;&lt;P&gt;Send an ASUP&lt;/P&gt;&lt;P&gt;Run Config Advisor&amp;nbsp;&lt;/P&gt;&lt;P&gt;Ensure that none of your SVM root volumes are on that HA pair&lt;/P&gt;&lt;P&gt;Label everything, especially the FCoE links to make sure they get reconnected correctly.&lt;/P&gt;&lt;P&gt;Inhibit takeover when you shut them down&lt;/P&gt;&lt;P&gt;After you bring them back up, verify FCoE/ALUA/MPIO&lt;/P&gt;&lt;P&gt;Run ConfigAdvisor again&lt;/P&gt;&lt;P&gt;Do a Takeover/Giveback test in both directions&lt;/P&gt;&lt;P&gt;Send another ASUP&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 25 Jul 2017 16:53:43 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Performing-maintenance-on-nodes-of-a-cluster/m-p/133080#M29047</guid>
      <dc:creator>SeanHatfield</dc:creator>
      <dc:date>2017-07-25T16:53:43Z</dc:date>
    </item>
    <item>
      <title>Re: Performing maintenance on nodes of a cluster</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Performing-maintenance-on-nodes-of-a-cluster/m-p/133083#M29048</link>
      <description>&lt;P&gt;Thanks Sean,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I verified that epsilon is not on the affected nodes. If it is, how do one go about moving this to another node?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I verified that the root volumes of SVMs are not on the affected aggregates. WE do have the data protection for the SVM root volumes, is it not the purpose of that is to have redundancy?&lt;/P&gt;</description>
      <pubDate>Tue, 25 Jul 2017 17:23:26 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Performing-maintenance-on-nodes-of-a-cluster/m-p/133083#M29048</guid>
      <dc:creator>duanebachi1</dc:creator>
      <dc:date>2017-07-25T17:23:26Z</dc:date>
    </item>
    <item>
      <title>Re: Performing maintenance on nodes of a cluster</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Performing-maintenance-on-nodes-of-a-cluster/m-p/134520#M29460</link>
      <description>&lt;P&gt;Moving epsilon:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;cluster modify -node &amp;lt;current_node&amp;gt; -epsilon false&lt;BR /&gt;cluster modify -node &amp;lt;new_node&amp;gt; -epsilon true&lt;BR /&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;As for the load sharing, I'm asking about that as well in another thread (&lt;A href="https://community.netapp.com/t5/Data-ONTAP-Discussions/Temporary-Shut-Down-of-Two-Cluster-Nodes/m-p/134519#M29459" target="_blank"&gt;https://community.netapp.com/t5/Data-ONTAP-Discussions/Temporary-Shut-Down-of-Two-Cluster-Nodes/m-p/134519#M29459&lt;/A&gt;) because I need to do the same thing. Hopefully we can get an answer!&lt;/P&gt;</description>
      <pubDate>Fri, 15 Sep 2017 14:35:00 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Performing-maintenance-on-nodes-of-a-cluster/m-p/134520#M29460</guid>
      <dc:creator>TMADOCTHOMAS</dc:creator>
      <dc:date>2017-09-15T14:35:00Z</dc:date>
    </item>
  </channel>
</rss>

