<?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: Clusters and iSCSI failover in ONTAP Hardware</title>
    <link>https://community.netapp.com/t5/ONTAP-Hardware/Clusters-and-iSCSI-failover/m-p/70331#M4970</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;PRE __jive_macro_name="quote" class="jive_text_macro jive_macro_quote"&gt;&lt;P&gt;Do I have to create iSCSI sessions / connections to the head (Head B) that doesn't run the live service to cater for Cluster Failover?&lt;/P&gt;&lt;/PRE&gt;&lt;P&gt;Nope, that's not required. In a fail-over situation the remaining cluster head will take over 'virtual' identity of the failed head with its igroups, LUN mappings, etc.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But there are some caveats:&lt;/P&gt;&lt;P&gt;- NIC ports from both heads need to have access to the same subnets / VLANs&lt;/P&gt;&lt;P&gt;- Addresses of IP interfaces on Head A need to be manually specified in the config of Head B, so it can take over these IP addresses, should the failure occur.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;BR /&gt;Radek&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 24 Jan 2011 16:36:36 GMT</pubDate>
    <dc:creator>radek_kubka</dc:creator>
    <dc:date>2011-01-24T16:36:36Z</dc:date>
    <item>
      <title>Clusters and iSCSI failover</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/Clusters-and-iSCSI-failover/m-p/70327#M4969</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have a FAS 3140 cluster.&lt;/P&gt;&lt;P&gt;Luns on one head (Head A) are being presented to a Windows Server running SQL using iSCSI. No active LUNs are on Head B&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Do I have to create iSCSI sessions / connections to the head (Head B) that doesn't run the live service to cater for Cluster Failover?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 07:01:43 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/Clusters-and-iSCSI-failover/m-p/70327#M4969</guid>
      <dc:creator>Willybobs27</dc:creator>
      <dc:date>2025-06-05T07:01:43Z</dc:date>
    </item>
    <item>
      <title>Re: Clusters and iSCSI failover</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/Clusters-and-iSCSI-failover/m-p/70331#M4970</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;PRE __jive_macro_name="quote" class="jive_text_macro jive_macro_quote"&gt;&lt;P&gt;Do I have to create iSCSI sessions / connections to the head (Head B) that doesn't run the live service to cater for Cluster Failover?&lt;/P&gt;&lt;/PRE&gt;&lt;P&gt;Nope, that's not required. In a fail-over situation the remaining cluster head will take over 'virtual' identity of the failed head with its igroups, LUN mappings, etc.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But there are some caveats:&lt;/P&gt;&lt;P&gt;- NIC ports from both heads need to have access to the same subnets / VLANs&lt;/P&gt;&lt;P&gt;- Addresses of IP interfaces on Head A need to be manually specified in the config of Head B, so it can take over these IP addresses, should the failure occur.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;BR /&gt;Radek&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 24 Jan 2011 16:36:36 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/Clusters-and-iSCSI-failover/m-p/70331#M4970</guid>
      <dc:creator>radek_kubka</dc:creator>
      <dc:date>2011-01-24T16:36:36Z</dc:date>
    </item>
    <item>
      <title>Re: Clusters and iSCSI failover</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/Clusters-and-iSCSI-failover/m-p/70335#M4971</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes it does work but make sure your system is configured correctly first.&amp;nbsp; Download the &lt;A href="https://now.netapp.com/eservice/toolchest?toolid=416" target="_blank"&gt;&lt;STRONG&gt;HA Configuration Checker (cf-config-check.cgi)&lt;/STRONG&gt;&lt;/A&gt; tool and test the config.&amp;nbsp; Even then it is best to take a 'pratice' before you do it with live data.&amp;nbsp; If your system is already in production, download the NetApp simulator and create a HA pair.&amp;nbsp; Then connect your iSCSI hosts to the VMs and begin testing.&amp;nbsp; This way you can confirm MPIO, IP routing and everything else is correct.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope it helps&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Bren&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 24 Jan 2011 20:55:34 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/Clusters-and-iSCSI-failover/m-p/70335#M4971</guid>
      <dc:creator>BrendonHiggins</dc:creator>
      <dc:date>2011-01-24T20:55:34Z</dc:date>
    </item>
  </channel>
</rss>

