<?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: Fibre Channel Resiliency single FC port in ONTAP Hardware</title>
    <link>https://community.netapp.com/t5/ONTAP-Hardware/Fibre-Channel-Resiliency-single-FC-port/m-p/1157#M138</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I would try to keep 2 fabrics (in case of fabric failure) and have the host multipath to both fabrics (as long as hosts have 2 paths) for the redundancy.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 21 May 2012 15:45:46 GMT</pubDate>
    <dc:creator>scottgelb</dc:creator>
    <dc:date>2012-05-21T15:45:46Z</dc:date>
    <item>
      <title>Fibre Channel Resiliency single FC port</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/Fibre-Channel-Resiliency-single-FC-port/m-p/1131#M124</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have a FAS2040 with servers accessing via FC, currently dual fabric.&lt;/P&gt;&lt;P&gt;The end user wants to use a FC attached tape for backup, but still requires FC resiliency for Server access &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So this means that 1 FC port will have to become an initiator, I guess for HA this would have to be done on both controllers?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I therefore believe this would reduce the current path count from 4 to 2 assuming path is available via the interconnect.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However how would I best zone such a solution for resiliency?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My thoughts are along the lines of two options:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Option 1&lt;/P&gt;&lt;P&gt;Controller A connected to Zone A&lt;/P&gt;&lt;P&gt;Controller B connected to Zone B&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However in this case how would it behave on failover? Would I have to zone the FC adaptor normally in Zone B onto Zone A and visa versa?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Option 2&lt;/P&gt;&lt;P&gt;Single Zone with FC switches interconnected.&lt;/P&gt;&lt;P&gt;Can a single server have two active connections to the same FC zone, albeit to two separate FC switches?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Are my assumptions concerning the interconnect providing the additional path correct?&lt;/P&gt;&lt;P&gt;Are my two options viable? If so which is best?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 06:26:46 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/Fibre-Channel-Resiliency-single-FC-port/m-p/1131#M124</guid>
      <dc:creator>Willybobs27</dc:creator>
      <dc:date>2025-06-05T06:26:46Z</dc:date>
    </item>
    <item>
      <title>Re: Fibre Channel Resiliency single FC port</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/Fibre-Channel-Resiliency-single-FC-port/m-p/1136#M126</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; We are using option3...isn't that always the way it is?&lt;/P&gt;&lt;P&gt;The zones are specific to each switch, we don't do any fabric or zone stretching.&amp;nbsp; This give us three of four paths, always squeezing that extra bit out!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;FilerA, port0 into switch A - host_filer-zone,FabricA&lt;/P&gt;&lt;P&gt;FilerB, port0 into switch A - tape_zone,FabricA&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;FilerA, port1 into switch B - host_filer-zone,FabricB&lt;/P&gt;&lt;P&gt;FilerB, port1 into Switch B - host_filer-zone,FabricB&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, 21 May 2012 15:06:50 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/Fibre-Channel-Resiliency-single-FC-port/m-p/1136#M126</guid>
      <dc:creator>columbus_admin</dc:creator>
      <dc:date>2012-05-21T15:06:50Z</dc:date>
    </item>
    <item>
      <title>Re: Fibre Channel Resiliency single FC port</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/Fibre-Channel-Resiliency-single-FC-port/m-p/1141#M129</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;depends also how your hosts are setup... if you have 2 hba ports on the host then you can have each host go to both fabrics to both zones.&amp;nbsp; If you have one HBA port on the guest then that changes things.&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The interconnect is used and you can see the hosts logged in with igroup show and seeing them logged in the vtic.&amp;nbsp; that is the interconnect connection through the controller that doesn't own the lun.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 21 May 2012 15:23:45 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/Fibre-Channel-Resiliency-single-FC-port/m-p/1141#M129</guid>
      <dc:creator>scottgelb</dc:creator>
      <dc:date>2012-05-21T15:23:45Z</dc:date>
    </item>
    <item>
      <title>Re: Fibre Channel Resiliency single FC port</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/Fibre-Channel-Resiliency-single-FC-port/m-p/1145#M131</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;So essentially I do the following:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Fabric A - A single switch&lt;/P&gt;&lt;P&gt;Fabric B - A single switch&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hosts have two FC connections, one to Fabric A and one to Fabric B&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;NetApp A connects to Fabric A via a single FC port&lt;/P&gt;&lt;P&gt;NetApp B connects to Fabric B via a single FC port&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Fabric A is zoned in for Hosts and NetApp A &lt;/P&gt;&lt;P&gt;Fabric B is zoned in for Hosts and NetApp B&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does Fabric A also have to be zoned in NetApp B and Fabric B for NetApp A?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I believe at this point I will see two paths to each NetApp controller. One direct and one via the interconnect. Is this correct?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 21 May 2012 15:34:27 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/Fibre-Channel-Resiliency-single-FC-port/m-p/1145#M131</guid>
      <dc:creator>Willybobs27</dc:creator>
      <dc:date>2012-05-21T15:34:27Z</dc:date>
    </item>
    <item>
      <title>Re: Fibre Channel Resiliency single FC port</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/Fibre-Channel-Resiliency-single-FC-port/m-p/1148#M134</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The fabrics would stay separate.  The host (needs MPIO setup) would see 2 paths.  One through fabric A and the other through fabric B.  Usually a zone is setup per initiator… so if there are 10 hosts, you would have 10 zones on fabric A (each zone with that host and the target port…the netapp target port in each zone).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Your MPIO setup should see both paths through fabric A/B when done and you can see the vtic login on the controller.  The controller that owns the lun is the primary path and the other controller a secondary path.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 21 May 2012 15:40:22 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/Fibre-Channel-Resiliency-single-FC-port/m-p/1148#M134</guid>
      <dc:creator>scottgelb</dc:creator>
      <dc:date>2012-05-21T15:40:22Z</dc:date>
    </item>
    <item>
      <title>Re: Fibre Channel Resiliency single FC port</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/Fibre-Channel-Resiliency-single-FC-port/m-p/1153#M136</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Good Morning Willy,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You may wish to zone Fabric A&amp;nbsp; in NetApp B and Fabric B for NetApp A for redundancy.&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;Henry&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 21 May 2012 15:42:58 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/Fibre-Channel-Resiliency-single-FC-port/m-p/1153#M136</guid>
      <dc:creator>HENRYPAN2</dc:creator>
      <dc:date>2012-05-21T15:42:58Z</dc:date>
    </item>
    <item>
      <title>Re: Fibre Channel Resiliency single FC port</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/Fibre-Channel-Resiliency-single-FC-port/m-p/1157#M138</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I would try to keep 2 fabrics (in case of fabric failure) and have the host multipath to both fabrics (as long as hosts have 2 paths) for the redundancy.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 21 May 2012 15:45:46 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/Fibre-Channel-Resiliency-single-FC-port/m-p/1157#M138</guid>
      <dc:creator>scottgelb</dc:creator>
      <dc:date>2012-05-21T15:45:46Z</dc:date>
    </item>
    <item>
      <title>Re: Fibre Channel Resiliency single FC port</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/Fibre-Channel-Resiliency-single-FC-port/m-p/1161#M140</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Henry,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Without two ports on each filer, that is not possible without stretching the fabrics, and not practical as there is still only one physical connection to each switch.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 21 May 2012 15:50:02 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/Fibre-Channel-Resiliency-single-FC-port/m-p/1161#M140</guid>
      <dc:creator>columbus_admin</dc:creator>
      <dc:date>2012-05-21T15:50:02Z</dc:date>
    </item>
  </channel>
</rss>

