<?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 HPE FC SN3000B firmware upgrades in HPE EVA Storage</title>
    <link>https://community.hpe.com/t5/hpe-eva-storage/hpe-fc-sn3000b-firmware-upgrades/m-p/6949658#M68045</link>
    <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;I need to do dome firmare upgrades from v7.2.x to v8.0.x on a couple of SN3000B switches. Reading through the release notes I can either do this distruptively but in fewer steps or non-disruptively in more steps. To minimise risk I would rather do more steps that are non-disruptive but I want to know if this is truely non-disutptive using this approach. The environment is very simple with 2 x FC switches, a small number of hosts and single storage array. Whereas some hosts are multipathed there are a couple of hosts with only a single HBA port and therefore connected to just one switch. My interpretation of 'non-disrutpive' is that a single pathed host will not suffer any outage when the switch is upgraded - is this what 'non-disruptive' means in the HPE\Brocade world or do I need to **bleep**down any single pathed hosts first?&lt;/P&gt;&lt;P&gt;Thanks in advance&lt;/P&gt;</description>
    <pubDate>Mon, 20 Mar 2017 16:24:49 GMT</pubDate>
    <dc:creator>jlangmead</dc:creator>
    <dc:date>2017-03-20T16:24:49Z</dc:date>
    <item>
      <title>HPE FC SN3000B firmware upgrades</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/hpe-fc-sn3000b-firmware-upgrades/m-p/6949658#M68045</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;I need to do dome firmare upgrades from v7.2.x to v8.0.x on a couple of SN3000B switches. Reading through the release notes I can either do this distruptively but in fewer steps or non-disruptively in more steps. To minimise risk I would rather do more steps that are non-disruptive but I want to know if this is truely non-disutptive using this approach. The environment is very simple with 2 x FC switches, a small number of hosts and single storage array. Whereas some hosts are multipathed there are a couple of hosts with only a single HBA port and therefore connected to just one switch. My interpretation of 'non-disrutpive' is that a single pathed host will not suffer any outage when the switch is upgraded - is this what 'non-disruptive' means in the HPE\Brocade world or do I need to **bleep**down any single pathed hosts first?&lt;/P&gt;&lt;P&gt;Thanks in advance&lt;/P&gt;</description>
      <pubDate>Mon, 20 Mar 2017 16:24:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/hpe-fc-sn3000b-firmware-upgrades/m-p/6949658#M68045</guid>
      <dc:creator>jlangmead</dc:creator>
      <dc:date>2017-03-20T16:24:49Z</dc:date>
    </item>
    <item>
      <title>Re: HPE FC SN3000B firmware upgrades</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/hpe-fc-sn3000b-firmware-upgrades/m-p/6949718#M68046</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;you can do it&amp;nbsp;&lt;SPAN&gt;non-disruptively it works fine&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;you should how ever do it in not in peak hours to keep&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;on the safe side. but&amp;nbsp;non-disruptively meens the ports don't&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;go down only the interface restarts.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I have done it many times.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Regards&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 20 Mar 2017 18:54:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/hpe-fc-sn3000b-firmware-upgrades/m-p/6949718#M68046</guid>
      <dc:creator>giladzzz</dc:creator>
      <dc:date>2017-03-20T18:54:20Z</dc:date>
    </item>
    <item>
      <title>Re: HPE FC SN3000B firmware upgrades</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/hpe-fc-sn3000b-firmware-upgrades/m-p/6949856#M68047</link>
      <description>&lt;P&gt;Great - many thanks&lt;/P&gt;&lt;P&gt;And the interface restart doesn't impact IO down that path?&lt;/P&gt;</description>
      <pubDate>Tue, 21 Mar 2017 08:24:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/hpe-fc-sn3000b-firmware-upgrades/m-p/6949856#M68047</guid>
      <dc:creator>jlangmead</dc:creator>
      <dc:date>2017-03-21T08:24:10Z</dc:date>
    </item>
    <item>
      <title>Re: HPE FC SN3000B firmware upgrades</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/hpe-fc-sn3000b-firmware-upgrades/m-p/6949905#M68048</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;managment interface restarts ports to host stay up&lt;/P&gt;&lt;P&gt;only equipment I saw that can sometimes notice&lt;/P&gt;&lt;P&gt;this are tape devices&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 21 Mar 2017 10:02:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/hpe-fc-sn3000b-firmware-upgrades/m-p/6949905#M68048</guid>
      <dc:creator>giladzzz</dc:creator>
      <dc:date>2017-03-21T10:02:24Z</dc:date>
    </item>
  </channel>
</rss>

