<?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: SAN switches maintenance in Network and Storage Protocols</title>
    <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/SAN-switches-maintenance/m-p/97957#M7510</link>
    <description>&lt;P&gt;Discussion on the same topic on VMware Communities concludes that FC switches can just be powered down.&lt;/P&gt;&lt;P&gt;&lt;A href="https://communities.vmware.com/thread/405268" target="_blank"&gt;https://communities.vmware.com/thread/405268&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any other opinion ?&lt;/P&gt;</description>
    <pubDate>Tue, 02 Dec 2014 19:12:33 GMT</pubDate>
    <dc:creator>NICOLAS_MELAY</dc:creator>
    <dc:date>2014-12-02T19:12:33Z</dc:date>
    <item>
      <title>SAN switches maintenance</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/SAN-switches-maintenance/m-p/97908#M7509</link>
      <description>&lt;P&gt;Hi all.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have a dual SAN fabric for our ESX cluster, backed with a FAS3140 MC.&lt;/P&gt;&lt;P&gt;SAN switches are (NetApp provided) Brocade 300's.&lt;/P&gt;&lt;P&gt;There are 2 completely separate SAN fabrics, each ESX and each FAS being joined to each fabric.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What would be the right and clean way to shutdown a SAN switch for maintenance ?&lt;/P&gt;&lt;P&gt;Should I disable FC links on the ESX side first ?&lt;/P&gt;&lt;P&gt;Can I just halt the switch and let it go and notify nodes, or even just power it down ?&lt;/P&gt;&lt;P&gt;What's the minimal set of steps required for NOT losing any I/O ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 05 Jun 2025 05:23:49 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/SAN-switches-maintenance/m-p/97908#M7509</guid>
      <dc:creator>NICOLAS_MELAY</dc:creator>
      <dc:date>2025-06-05T05:23:49Z</dc:date>
    </item>
    <item>
      <title>Re: SAN switches maintenance</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/SAN-switches-maintenance/m-p/97957#M7510</link>
      <description>&lt;P&gt;Discussion on the same topic on VMware Communities concludes that FC switches can just be powered down.&lt;/P&gt;&lt;P&gt;&lt;A href="https://communities.vmware.com/thread/405268" target="_blank"&gt;https://communities.vmware.com/thread/405268&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any other opinion ?&lt;/P&gt;</description>
      <pubDate>Tue, 02 Dec 2014 19:12:33 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/SAN-switches-maintenance/m-p/97957#M7510</guid>
      <dc:creator>NICOLAS_MELAY</dc:creator>
      <dc:date>2014-12-02T19:12:33Z</dc:date>
    </item>
    <item>
      <title>Re: SAN switches maintenance</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/SAN-switches-maintenance/m-p/97958#M7511</link>
      <description>&lt;P&gt;You can just power off a switch and the systems will compensate as long as all hosts have active paths through both switches.&lt;/P&gt;&lt;P&gt;If you want to try and avoid the timeouts, re-send of IOs, you can go into the hosts&amp;nbsp;and set the link of the switch that is staying up as the preferred for IO so it isn't using the path to the switch that is going down.&lt;/P&gt;&lt;P&gt;If you have to make changes to both switches, you should wait a few hours / day between reboots to ensure the path to the recently rebooted switch is healthy for all hosts before dropping the other side.&lt;/P&gt;</description>
      <pubDate>Tue, 02 Dec 2014 19:56:01 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/SAN-switches-maintenance/m-p/97958#M7511</guid>
      <dc:creator>rwelshman</dc:creator>
      <dc:date>2014-12-02T19:56:01Z</dc:date>
    </item>
  </channel>
</rss>

