<?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 caution after upgrading 8.x metro cluster nodes (7mode) to 8.2.x (options cf.remote_syncmirror.enable) in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/caution-after-upgrading-8-x-metro-cluster-nodes-7mode-to-8-2-x-options-cf-remote/m-p/26730#M6287</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Community!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'd like to share the following experience with you.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We've recently upgraded 2 FAS3240 &lt;SPAN style="text-decoration: underline;"&gt;fabric-attached&lt;/SPAN&gt; &lt;STRONG&gt;Metrocluster &lt;/STRONG&gt;Nodes (HA Pair) running 8.0.2 &lt;STRONG&gt;7mode&lt;/STRONG&gt; and as well 2 newly arrived FAS3250 &lt;SPAN style="text-decoration: underline;"&gt;fabric-attached&lt;/SPAN&gt; &lt;STRONG&gt;Metrocluster &lt;/STRONG&gt;Nodes (running 8.1.x 7mode) to DOT 8.2.1 (7mode).&lt;/P&gt;&lt;P&gt;We've experienced the following issue during the pre-production failover tests of the new system:&lt;/P&gt;&lt;P&gt;Even if the MetroCluster Feature was licensed under 8.1 release correctly, the &lt;STRONG style="font-family: courier new,courier;"&gt;cf.remote_syncmirror.enable&lt;/STRONG&gt; option for this feature to work is not setup correctly by the update procedure. We had to do this manually!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That means, if you lose one complete side of the fabric attached HA Pair, the command &lt;STRONG style="font-family: courier new,courier;"&gt;cf forcetakeover -d&lt;/STRONG&gt; fails with the following message:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;cf: forcetakeover -d cannot be performed because remote synchronous mirroring is not enabled&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;for the MetroCluster Feature to work correctly you have to check the following 2 options:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;cf.mode&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; &lt;/SPAN&gt;&lt;/TD&gt;&lt;TD&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;&lt;STRONG&gt;ha&lt;/STRONG&gt;&lt;/SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/TD&gt;&lt;TD&gt; &lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;cf.remote_syncmirror.enable&lt;/SPAN&gt;&lt;STRONG&gt; &lt;BR /&gt;&lt;/STRONG&gt;&lt;/TD&gt;&lt;TD&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;&lt;STRONG&gt;on&lt;/STRONG&gt; (same value required in local+partner)&lt;/SPAN&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It's easier to check/set this options while both nodes are healthy &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;good luck&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Martin&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 05 Jun 2025 05:35:11 GMT</pubDate>
    <dc:creator>MARTINBARTH</dc:creator>
    <dc:date>2025-06-05T05:35:11Z</dc:date>
    <item>
      <title>caution after upgrading 8.x metro cluster nodes (7mode) to 8.2.x (options cf.remote_syncmirror.enable)</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/caution-after-upgrading-8-x-metro-cluster-nodes-7mode-to-8-2-x-options-cf-remote/m-p/26730#M6287</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Community!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'd like to share the following experience with you.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We've recently upgraded 2 FAS3240 &lt;SPAN style="text-decoration: underline;"&gt;fabric-attached&lt;/SPAN&gt; &lt;STRONG&gt;Metrocluster &lt;/STRONG&gt;Nodes (HA Pair) running 8.0.2 &lt;STRONG&gt;7mode&lt;/STRONG&gt; and as well 2 newly arrived FAS3250 &lt;SPAN style="text-decoration: underline;"&gt;fabric-attached&lt;/SPAN&gt; &lt;STRONG&gt;Metrocluster &lt;/STRONG&gt;Nodes (running 8.1.x 7mode) to DOT 8.2.1 (7mode).&lt;/P&gt;&lt;P&gt;We've experienced the following issue during the pre-production failover tests of the new system:&lt;/P&gt;&lt;P&gt;Even if the MetroCluster Feature was licensed under 8.1 release correctly, the &lt;STRONG style="font-family: courier new,courier;"&gt;cf.remote_syncmirror.enable&lt;/STRONG&gt; option for this feature to work is not setup correctly by the update procedure. We had to do this manually!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That means, if you lose one complete side of the fabric attached HA Pair, the command &lt;STRONG style="font-family: courier new,courier;"&gt;cf forcetakeover -d&lt;/STRONG&gt; fails with the following message:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;cf: forcetakeover -d cannot be performed because remote synchronous mirroring is not enabled&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;for the MetroCluster Feature to work correctly you have to check the following 2 options:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;cf.mode&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; &lt;/SPAN&gt;&lt;/TD&gt;&lt;TD&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;&lt;STRONG&gt;ha&lt;/STRONG&gt;&lt;/SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/TD&gt;&lt;TD&gt; &lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;cf.remote_syncmirror.enable&lt;/SPAN&gt;&lt;STRONG&gt; &lt;BR /&gt;&lt;/STRONG&gt;&lt;/TD&gt;&lt;TD&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;&lt;STRONG&gt;on&lt;/STRONG&gt; (same value required in local+partner)&lt;/SPAN&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It's easier to check/set this options while both nodes are healthy &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;good luck&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Martin&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 05:35:11 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/caution-after-upgrading-8-x-metro-cluster-nodes-7mode-to-8-2-x-options-cf-remote/m-p/26730#M6287</guid>
      <dc:creator>MARTINBARTH</dc:creator>
      <dc:date>2025-06-05T05:35:11Z</dc:date>
    </item>
    <item>
      <title>Re: caution after upgrading 8.x metro cluster nodes (7mode) to 8.2.x (options cf.remote_syncmirror.enable)</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/caution-after-upgrading-8-x-metro-cluster-nodes-7mode-to-8-2-x-options-cf-remote/m-p/26735#M6288</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you for that we have just come across this during testing before go live.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 19 Jun 2014 15:42:58 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/caution-after-upgrading-8-x-metro-cluster-nodes-7mode-to-8-2-x-options-cf-remote/m-p/26735#M6288</guid>
      <dc:creator>simon_wright</dc:creator>
      <dc:date>2014-06-19T15:42:58Z</dc:date>
    </item>
  </channel>
</rss>

