<?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: Cluster failover impact in VMware Solutions Discussions</title>
    <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/Cluster-failover-impact/m-p/55013#M5171</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I mean about CF takeover.&lt;/P&gt;&lt;P&gt;Perhaps it was due to timeout config in host driver .Since it was happened only on very few host.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 27 Feb 2012 03:37:59 GMT</pubDate>
    <dc:creator>saranraj456</dc:creator>
    <dc:date>2012-02-27T03:37:59Z</dc:date>
    <item>
      <title>Cluster failover impact</title>
      <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/Cluster-failover-impact/m-p/55000#M5165</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Frndz,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;While during an cluster failover,some of the VM's,LPAR &amp;amp; windows host using Netapp LUN become inaccessible.What could be the reason for this .?&lt;/P&gt;&lt;P&gt;Does the cluster failover will have any impact.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Saran&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 06:33:43 GMT</pubDate>
      <guid>https://community.netapp.com/t5/VMware-Solutions-Discussions/Cluster-failover-impact/m-p/55000#M5165</guid>
      <dc:creator>saranraj456</dc:creator>
      <dc:date>2025-06-05T06:33:43Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster failover impact</title>
      <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/Cluster-failover-impact/m-p/55005#M5168</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;When you say “cluster failover” do you mean NetApp takeover/giveback or host clustering?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For NetApp the usual reason is improper configuration of timeouts in host’s drivers. Another possibility is incorrect connection (e.g. no path via partner).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 27 Feb 2012 03:27:01 GMT</pubDate>
      <guid>https://community.netapp.com/t5/VMware-Solutions-Discussions/Cluster-failover-impact/m-p/55005#M5168</guid>
      <dc:creator>aborzenkov</dc:creator>
      <dc:date>2012-02-27T03:27:01Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster failover impact</title>
      <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/Cluster-failover-impact/m-p/55013#M5171</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I mean about CF takeover.&lt;/P&gt;&lt;P&gt;Perhaps it was due to timeout config in host driver .Since it was happened only on very few host.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 27 Feb 2012 03:37:59 GMT</pubDate>
      <guid>https://community.netapp.com/t5/VMware-Solutions-Discussions/Cluster-failover-impact/m-p/55013#M5171</guid>
      <dc:creator>saranraj456</dc:creator>
      <dc:date>2012-02-27T03:37:59Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster failover impact</title>
      <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/Cluster-failover-impact/m-p/55016#M5173</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I mean about CF takeover.&lt;/P&gt;&lt;P&gt;Perhaps it was due to timeout config in host driver .Since it was happened only on very few host.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 27 Feb 2012 03:37:59 GMT</pubDate>
      <guid>https://community.netapp.com/t5/VMware-Solutions-Discussions/Cluster-failover-impact/m-p/55016#M5173</guid>
      <dc:creator>saranraj456</dc:creator>
      <dc:date>2012-02-27T03:37:59Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster failover impact</title>
      <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/Cluster-failover-impact/m-p/55021#M5175</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We are running 3160s for our ESX guest images, RDMs, and NAS storage.&amp;nbsp; We had a bad CNA card that had to be replaced, the failover did not impact any of the services, including ESX guests, with RDMs and NAS storage.&amp;nbsp; The NAS side had a couple of timeouts, but none of the LUNs reported any issues.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Drivers and settings are always important, but the HBA's drivers and setting are extremely important.&amp;nbsp; We had issues with the VMs at one point when their default settings were too low, they would get timeout errors pretty regularly accessing their RDMs.&amp;nbsp; So our usual steps:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.) what is different between the working and affected hosts?&lt;/P&gt;&lt;P&gt;2.) drivers/settings/config checks&lt;/P&gt;&lt;P&gt;3.) best practices for the equipment involved checks&lt;/P&gt;&lt;P&gt;4.) multipathing software checks&lt;/P&gt;&lt;P&gt;5.) and my favorite...log scrubbing on everything to see what each piece reported(can be tedious and time consuming)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; - Scott&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 27 Feb 2012 14:11:00 GMT</pubDate>
      <guid>https://community.netapp.com/t5/VMware-Solutions-Discussions/Cluster-failover-impact/m-p/55021#M5175</guid>
      <dc:creator>columbus_admin</dc:creator>
      <dc:date>2012-02-27T14:11:00Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster failover impact</title>
      <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/Cluster-failover-impact/m-p/55029#M5178</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Scott,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For regarding the point1-whether we need to check the diff's in host end or storage end. ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please clarify.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Saran&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 29 Feb 2012 14:41:10 GMT</pubDate>
      <guid>https://community.netapp.com/t5/VMware-Solutions-Discussions/Cluster-failover-impact/m-p/55029#M5178</guid>
      <dc:creator>saranraj456</dc:creator>
      <dc:date>2012-02-29T14:41:10Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster failover impact</title>
      <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/Cluster-failover-impact/m-p/55033#M5179</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There really isn't anything to configure on the filer end in a cluster, so your hosts all should be running the same version of the HBA driver, have the same MPIO settings, the same firmware settings, etc.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; - Scott&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 29 Feb 2012 14:45:55 GMT</pubDate>
      <guid>https://community.netapp.com/t5/VMware-Solutions-Discussions/Cluster-failover-impact/m-p/55033#M5179</guid>
      <dc:creator>columbus_admin</dc:creator>
      <dc:date>2012-02-29T14:45:55Z</dc:date>
    </item>
  </channel>
</rss>

