<?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: Head swap in 2-node MCC in ONTAP Hardware</title>
    <link>https://community.netapp.com/t5/ONTAP-Hardware/Head-swap-in-2-node-MCC/m-p/142560#M9000</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;yes this is supported. This should be in the documentation here:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="http://docs.netapp.com/platstor/topic/com.netapp.doc.hw-upgrade-controller/home.html?cp=8_4&amp;nbsp;" target="_blank"&gt;http://docs.netapp.com/platstor/topic/com.netapp.doc.hw-upgrade-controller/home.html?cp=8_4&amp;nbsp;&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;For finding out which guide to use.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;here is the guide using ARL:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="http://docs.netapp.com/platstor/topic/com.netapp.doc.hw-upgrade-controller/GUID-6F9CE102-FA28-4649-AB03-76B076C1BC75.html?cp=8_4_5_0" target="_blank"&gt;http://docs.netapp.com/platstor/topic/com.netapp.doc.hw-upgrade-controller/GUID-6F9CE102-FA28-4649-AB03-76B076C1BC75.html?cp=8_4_5_0&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You will find MetroCluster specific steps in that guide like this one here as an example:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;OL id="GUID-E7235795-8A05-493C-8915-5A1B81E5D31D__GUID-49AFF732-19EE-4C54-B3AB-5D3C5D9CF10C" class="ol steps"&gt;
&lt;LI id="GUID-E7235795-8A05-493C-8915-5A1B81E5D31D__STEP_FDBF10FF71054D119525D0AC32658E8F" class="li step stepexpand"&gt;&lt;SPAN class="ph cmd"&gt;If the original nodes are in a two-node MetroCluster configuration, switch over storage and client access and heal the root aggregates:&lt;/SPAN&gt;
&lt;OL id="GUID-E7235795-8A05-493C-8915-5A1B81E5D31D__SUBSTEPS_0A8DCA35BE5F4E3DA51E7B145CF4347D" class="ol substeps" type="a"&gt;
&lt;LI id="GUID-E7235795-8A05-493C-8915-5A1B81E5D31D__SUBSTEP_E2EC2744BFED4B9591492E69E3A1966A" class="li substep"&gt;&lt;SPAN class="ph cmd"&gt;Check the MetroCluster status by using the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class="keyword cmdname"&gt;metrocluster show&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;command to determine whether automatic switchover has occurred.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI id="GUID-E7235795-8A05-493C-8915-5A1B81E5D31D__SUBSTEP_805A1933CE46460CA042B7F85C414B33" class="li substep"&gt;&lt;SPAN class="ph cmd"&gt;If automatic switchover has not occurred, perform a planned switchover operation from the healthy node by using the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class="keyword cmdname"&gt;metrocluster switchover&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;command.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI id="GUID-E7235795-8A05-493C-8915-5A1B81E5D31D__SUBSTEP_3DD5AA50A5AE4BCAB18A2EBFF92B8CDC" class="li substep"&gt;&lt;SPAN class="ph cmd"&gt;Resynchronize the data aggregates by using the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class="keyword cmdname"&gt;metrocluster heal&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class="keyword option"&gt;-phase aggregates&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;command from the surviving cluster.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI id="GUID-E7235795-8A05-493C-8915-5A1B81E5D31D__SUBSTEP_3EB1B99B9CAF4265B66781AF4A4FAB8E" class="li substep"&gt;&lt;SPAN class="ph cmd"&gt;Heal the root aggregates by using the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class="keyword cmdname"&gt;metrocluster heal&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class="keyword option"&gt;-phase root-aggregates&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;command.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI id="GUID-E7235795-8A05-493C-8915-5A1B81E5D31D__SUBSTEP_8801B26F3DB946D39BE99D593E4898E4" class="li substep"&gt;&lt;SPAN class="ph cmd"&gt;Verify that the heal operation is complete by using the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class="keyword cmdname"&gt;metrocluster operation show&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;command on the destination cluster.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/OL&gt;
&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;&lt;SPAN class="ph cmd"&gt;Andy&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 06 Sep 2018 16:47:47 GMT</pubDate>
    <dc:creator>akiendl</dc:creator>
    <dc:date>2018-09-06T16:47:47Z</dc:date>
    <item>
      <title>Head swap in 2-node MCC</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/Head-swap-in-2-node-MCC/m-p/142552#M8999</link>
      <description>&lt;P&gt;Are there any concerns? My understanding is that it basically should be same as motherboard replacement which is supported. Of course it is necessary to adjust ports, licenses etc for new head, but that is not different to standard ARL head swap procedure.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I could not find any definitive answer whether this is "officially" supported or not.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;TIA&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;P.S. was too fast. The obvious problem will be NVRAM mirroring. No chance to do it non-disruptively?&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 13:21:00 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/Head-swap-in-2-node-MCC/m-p/142552#M8999</guid>
      <dc:creator>aborzenkov</dc:creator>
      <dc:date>2025-06-04T13:21:00Z</dc:date>
    </item>
    <item>
      <title>Re: Head swap in 2-node MCC</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/Head-swap-in-2-node-MCC/m-p/142560#M9000</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;yes this is supported. This should be in the documentation here:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="http://docs.netapp.com/platstor/topic/com.netapp.doc.hw-upgrade-controller/home.html?cp=8_4&amp;nbsp;" target="_blank"&gt;http://docs.netapp.com/platstor/topic/com.netapp.doc.hw-upgrade-controller/home.html?cp=8_4&amp;nbsp;&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;For finding out which guide to use.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;here is the guide using ARL:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="http://docs.netapp.com/platstor/topic/com.netapp.doc.hw-upgrade-controller/GUID-6F9CE102-FA28-4649-AB03-76B076C1BC75.html?cp=8_4_5_0" target="_blank"&gt;http://docs.netapp.com/platstor/topic/com.netapp.doc.hw-upgrade-controller/GUID-6F9CE102-FA28-4649-AB03-76B076C1BC75.html?cp=8_4_5_0&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You will find MetroCluster specific steps in that guide like this one here as an example:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;OL id="GUID-E7235795-8A05-493C-8915-5A1B81E5D31D__GUID-49AFF732-19EE-4C54-B3AB-5D3C5D9CF10C" class="ol steps"&gt;
&lt;LI id="GUID-E7235795-8A05-493C-8915-5A1B81E5D31D__STEP_FDBF10FF71054D119525D0AC32658E8F" class="li step stepexpand"&gt;&lt;SPAN class="ph cmd"&gt;If the original nodes are in a two-node MetroCluster configuration, switch over storage and client access and heal the root aggregates:&lt;/SPAN&gt;
&lt;OL id="GUID-E7235795-8A05-493C-8915-5A1B81E5D31D__SUBSTEPS_0A8DCA35BE5F4E3DA51E7B145CF4347D" class="ol substeps" type="a"&gt;
&lt;LI id="GUID-E7235795-8A05-493C-8915-5A1B81E5D31D__SUBSTEP_E2EC2744BFED4B9591492E69E3A1966A" class="li substep"&gt;&lt;SPAN class="ph cmd"&gt;Check the MetroCluster status by using the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class="keyword cmdname"&gt;metrocluster show&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;command to determine whether automatic switchover has occurred.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI id="GUID-E7235795-8A05-493C-8915-5A1B81E5D31D__SUBSTEP_805A1933CE46460CA042B7F85C414B33" class="li substep"&gt;&lt;SPAN class="ph cmd"&gt;If automatic switchover has not occurred, perform a planned switchover operation from the healthy node by using the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class="keyword cmdname"&gt;metrocluster switchover&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;command.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI id="GUID-E7235795-8A05-493C-8915-5A1B81E5D31D__SUBSTEP_3DD5AA50A5AE4BCAB18A2EBFF92B8CDC" class="li substep"&gt;&lt;SPAN class="ph cmd"&gt;Resynchronize the data aggregates by using the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class="keyword cmdname"&gt;metrocluster heal&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class="keyword option"&gt;-phase aggregates&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;command from the surviving cluster.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI id="GUID-E7235795-8A05-493C-8915-5A1B81E5D31D__SUBSTEP_3EB1B99B9CAF4265B66781AF4A4FAB8E" class="li substep"&gt;&lt;SPAN class="ph cmd"&gt;Heal the root aggregates by using the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class="keyword cmdname"&gt;metrocluster heal&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class="keyword option"&gt;-phase root-aggregates&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;command.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI id="GUID-E7235795-8A05-493C-8915-5A1B81E5D31D__SUBSTEP_8801B26F3DB946D39BE99D593E4898E4" class="li substep"&gt;&lt;SPAN class="ph cmd"&gt;Verify that the heal operation is complete by using the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class="keyword cmdname"&gt;metrocluster operation show&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;command on the destination cluster.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/OL&gt;
&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;&lt;SPAN class="ph cmd"&gt;Andy&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 06 Sep 2018 16:47:47 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/Head-swap-in-2-node-MCC/m-p/142560#M9000</guid>
      <dc:creator>akiendl</dc:creator>
      <dc:date>2018-09-06T16:47:47Z</dc:date>
    </item>
    <item>
      <title>Re: Head swap in 2-node MCC</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/Head-swap-in-2-node-MCC/m-p/142576#M9001</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://community.netapp.com/t5/user/viewprofilepage/user-id/6949"&gt;@akiendl&lt;/a&gt;&amp;nbsp;wrote:&lt;BR /&gt;
&lt;P&gt;yes this is supported. This should be in the documentation here:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="http://docs.netapp.com/platstor/topic/com.netapp.doc.hw-upgrade-controller/home.html?cp=8_4&amp;nbsp;" target="_blank"&gt;http://docs.netapp.com/platstor/topic/com.netapp.doc.hw-upgrade-controller/home.html?cp=8_4&amp;nbsp;&lt;/A&gt;&lt;/P&gt;
&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;Thanks for the link, but just wanted to make sure we are speaking about the same things.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;After head swap new controller most likely has different NVRAM size so NVRAM mirroring is disabled. Actually for 4-node cluster with ARL head swap MC FC FAQ explicitly warns "NVRAM mirroring between the sites must be disabled for the entire process" which logically also applies to 2-node cluster. And it goes on to add "Planned switchover is not possible while the upgrade is in process".&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;But for non-disruptive 2-node head swap we &lt;STRONG&gt;must&lt;/STRONG&gt; do planned switchover (and switchback). It is clear that initial switchover with old heads is possible. But the main question is - will switchback and subsequent switchover in opposite direction with one old and one new head be possible too? If yes, is it done by standard commands or some diagnostic mode magic is necessary?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Documentation rather sidesteps it&amp;nbsp;unfortunately ...&lt;/P&gt;</description>
      <pubDate>Fri, 07 Sep 2018 06:52:16 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/Head-swap-in-2-node-MCC/m-p/142576#M9001</guid>
      <dc:creator>aborzenkov</dc:creator>
      <dc:date>2018-09-07T06:52:16Z</dc:date>
    </item>
    <item>
      <title>Re: Head swap in 2-node MCC</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/Head-swap-in-2-node-MCC/m-p/142618#M9013</link>
      <description>&lt;P&gt;hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;there should be no special settings/options needed. I know the procedure has been tested recently and updated so following the setup should work.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Andy&lt;/P&gt;</description>
      <pubDate>Mon, 10 Sep 2018 08:08:59 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/Head-swap-in-2-node-MCC/m-p/142618#M9013</guid>
      <dc:creator>akiendl</dc:creator>
      <dc:date>2018-09-10T08:08:59Z</dc:date>
    </item>
  </channel>
</rss>

