<?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: Old Netapp is Cluster Interconnect Problem in ONTAP Hardware</title>
    <link>https://community.netapp.com/t5/ONTAP-Hardware/Old-Netapp-is-Cluster-Interconnect-Problem/m-p/80121#M5626</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'd check BURT 412390, Fixed in 7.3.4P2 and 7.3.3P5 &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 26 May 2014 00:25:34 GMT</pubDate>
    <dc:creator>shane_bradley</dc:creator>
    <dc:date>2014-05-26T00:25:34Z</dc:date>
    <item>
      <title>Old Netapp is Cluster Interconnect Problem</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/Old-Netapp-is-Cluster-Interconnect-Problem/m-p/80112#M5624</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P class="p1"&gt;I have an older Fas270C in our dev area. What a workhorse, it is still going after 7 years.&amp;nbsp; We have had a problem come up. The First volume failed and caused us to Force Failover.&amp;nbsp; We had spares, but I guess there is something special about the very first disk.&amp;nbsp; New drive in there and it has rebuilt. The device is up and data serving fine.&amp;nbsp; The parter controller will not come back with: cf giveback. &lt;/P&gt;&lt;P class="p1"&gt;We also swapped the controller for the parter controller. Just to make sure the partner controller failed.&amp;nbsp; We checked IPs and both sides' IPs are up and fine. We have iSCSI running over both and data is flowing. &lt;/P&gt;&lt;P class="p1"&gt;&lt;/P&gt;&lt;P class="p1"&gt;This looks like our main issue:&lt;STRONG&gt; cf.nm.nicReset:warning]: Initiating soft reset on Cluster Interconnect card 0 due to rendezvous jammed&lt;/STRONG&gt;&lt;/P&gt;&lt;P class="p1"&gt;Got any ideas how to diagnose this?&amp;nbsp; &lt;/P&gt;&lt;P class="p1"&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;/P&gt;&lt;P class="p1"&gt;storm2(takeover)&amp;gt; ifconfig -a&lt;/P&gt;&lt;P class="p1"&gt;e0a: flags=48e8043&amp;lt;UP,BROADCAST,RUNNING,MULTICAST,MULTIHOST,PARTNER_UP,NOWINS&amp;gt; mtu 1500&lt;/P&gt;&lt;P class="p1"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;inet 10.100.1.51 netmask 0xffffff00 broadcast 10.100.1.255&lt;/P&gt;&lt;P class="p1"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;partner inet 10.100.1.50 (e0a)&lt;/P&gt;&lt;P class="p1"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;ether 00:a0:98:03:9d:d5 (auto-1000t-fd-up) flowcontrol full&lt;/P&gt;&lt;P class="p1"&gt;e0b: flags=48e8043&amp;lt;UP,BROADCAST,RUNNING,MULTICAST,MULTIHOST,PARTNER_UP,NOWINS&amp;gt; mtu 1500&lt;/P&gt;&lt;P class="p1"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;inet 10.100.0.251 netmask 0xffffff00 broadcast 10.100.0.255&lt;/P&gt;&lt;P class="p1"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;partner inet 10.100.1.10 (e0b)&lt;/P&gt;&lt;P class="p1"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;ether 00:a0:98:03:9d:d6 (auto-1000t-fd-up) flowcontrol full&lt;/P&gt;&lt;P class="p1"&gt;lo: flags=19e8049&amp;lt;UP,LOOPBACK,RUNNING,MULTICAST,MULTIHOST,PARTNER_UP,TCPCKSUM&amp;gt; mtu 8160&lt;/P&gt;&lt;P class="p1"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;inet 127.0.0.1 netmask 0xff000000 broadcast 127.0.0.1&lt;/P&gt;&lt;P class="p1"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;ether f0:7b:af:37:04:00 (VIA Provider)&lt;/P&gt;&lt;P class="p1"&gt;storm2(takeover)&amp;gt; Sat Feb&amp;nbsp; 8 09:44:03 EST [storm2 (takeover): cf.nm.nicReset:warning]: Initiating soft reset on Cluster Interconnect card 0 due to rendezvous jammed&lt;/P&gt;&lt;P class="p2"&gt;&lt;/P&gt;&lt;P class="p1"&gt;storm2(takeover)&amp;gt; Sat Feb&amp;nbsp; 8 09:46:06 EST [storm2 (takeover): cf.nm.nicReset:warning]: Initiating soft reset on Cluster Interconnect card 0 due to rendezvous jammed&lt;/P&gt;&lt;P class="p1"&gt;Sat Feb&amp;nbsp; 8 09:47:08 EST [storm2 (takeover): cf.nm.nicReset:warning]: Initiating soft reset on Cluster Interconnect card 0 due to rendezvous jammed&lt;/P&gt;&lt;P class="p1"&gt;&lt;/P&gt;&lt;P class="p1"&gt;---------------------&lt;/P&gt;&lt;P class="p1"&gt;&lt;STRONG&gt;cf monitor &lt;/STRONG&gt;&lt;/P&gt;&lt;P class="p1"&gt;&amp;nbsp; current time: 08Feb2014 09:40:46&lt;/P&gt;&lt;P class="p1"&gt;&amp;nbsp; TAKEOVER 10:44:00, partner 'storm1', cluster monitor enabled&lt;/P&gt;&lt;P class="p1"&gt;storm2(takeover)&amp;gt; &lt;STRONG&gt;cf giveback&lt;/STRONG&gt;&lt;/P&gt;&lt;P class="p1"&gt;Partner not waiting for giveback, giveback cancelled.&lt;/P&gt;&lt;P class="p1"&gt;To do a giveback without checking for partner readiness, please either set option "cf.giveback.check.partner" to "off" before doing "cf giveback" again, or do "cf giveback -f".&lt;/P&gt;&lt;P class="p1"&gt;The first choice disables checking for all future "cf giveback", until it's turned back to "on". The second choice is good for this giveback only.&lt;/P&gt;&lt;P class="p1"&gt;&lt;/P&gt;&lt;P class="p1"&gt;storm2(takeover)&amp;gt; Sat Feb&amp;nbsp; 8 09:41:59 EST [storm2 (takeover): cf.nm.nicReset:warning]: Initiating soft reset on Cluster Interconnect card 0 due to rendezvous jammed&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 05:43:40 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/Old-Netapp-is-Cluster-Interconnect-Problem/m-p/80112#M5624</guid>
      <dc:creator>pointshop</dc:creator>
      <dc:date>2025-06-05T05:43:40Z</dc:date>
    </item>
    <item>
      <title>Re: Old Netapp is Cluster Interconnect Problem</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/Old-Netapp-is-Cluster-Interconnect-Problem/m-p/80117#M5625</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I meet same problem,just like you, do you have resolve this problem.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 20 May 2014 08:19:48 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/Old-Netapp-is-Cluster-Interconnect-Problem/m-p/80117#M5625</guid>
      <dc:creator>jizhengqing</dc:creator>
      <dc:date>2014-05-20T08:19:48Z</dc:date>
    </item>
    <item>
      <title>Re: Old Netapp is Cluster Interconnect Problem</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/Old-Netapp-is-Cluster-Interconnect-Problem/m-p/80121#M5626</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'd check BURT 412390, Fixed in 7.3.4P2 and 7.3.3P5 &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 26 May 2014 00:25:34 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/Old-Netapp-is-Cluster-Interconnect-Problem/m-p/80121#M5626</guid>
      <dc:creator>shane_bradley</dc:creator>
      <dc:date>2014-05-26T00:25:34Z</dc:date>
    </item>
    <item>
      <title>Re: Old Netapp is Cluster Interconnect Problem</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/Old-Netapp-is-Cluster-Interconnect-Problem/m-p/80125#M5627</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Many thanks for your timely help, I've been troubled for a long time for this question,&amp;nbsp; If do not patch microcode upgrades . It frequently happen?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 26 May 2014 01:04:27 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/Old-Netapp-is-Cluster-Interconnect-Problem/m-p/80125#M5627</guid>
      <dc:creator>jizhengqing</dc:creator>
      <dc:date>2014-05-26T01:04:27Z</dc:date>
    </item>
  </channel>
</rss>

