<?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: MSA1000 Failback in HPE MSA Storage</title>
    <link>https://community.hpe.com/t5/hpe-msa-storage/msa1000-failback/m-p/4284366#M9225</link>
    <description>It seems to have failed back to the primary controller overnight. Is this normal or would is it cause for concern that  a condition forced it back to the primary?</description>
    <pubDate>Fri, 10 Oct 2008 18:20:27 GMT</pubDate>
    <dc:creator>Josh Safranek</dc:creator>
    <dc:date>2008-10-10T18:20:27Z</dc:date>
    <item>
      <title>MSA1000 Failback</title>
      <link>https://community.hpe.com/t5/hpe-msa-storage/msa1000-failback/m-p/4284363#M9222</link>
      <description>I simulated a failover by disabling the HBA port in our switch. It failed over fine, but now what is the proper way to get it back? I'm nervous about reversing the procedure, disabling the backup HBA and having the system decide there are no paths left.&lt;BR /&gt;&lt;BR /&gt;BL460c &amp;gt; Brocade 4/24 SAN Switch &amp;gt; MSA1000</description>
      <pubDate>Thu, 09 Oct 2008 22:56:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-msa-storage/msa1000-failback/m-p/4284363#M9222</guid>
      <dc:creator>Josh Safranek</dc:creator>
      <dc:date>2008-10-09T22:56:32Z</dc:date>
    </item>
    <item>
      <title>Re: MSA1000 Failback</title>
      <link>https://community.hpe.com/t5/hpe-msa-storage/msa1000-failback/m-p/4284364#M9223</link>
      <description>Also, I do not have SecurePath only basic MPIO</description>
      <pubDate>Thu, 09 Oct 2008 23:04:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-msa-storage/msa1000-failback/m-p/4284364#M9223</guid>
      <dc:creator>Josh Safranek</dc:creator>
      <dc:date>2008-10-09T23:04:31Z</dc:date>
    </item>
    <item>
      <title>Re: MSA1000 Failback</title>
      <link>https://community.hpe.com/t5/hpe-msa-storage/msa1000-failback/m-p/4284365#M9224</link>
      <description>The basic MPIO does not have a management interface, so you cannot force a failback that way. You can only simulate another failure which causes the MPIO to do another failover (back) to controller-1 -- or leave it in the current state.</description>
      <pubDate>Fri, 10 Oct 2008 04:30:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-msa-storage/msa1000-failback/m-p/4284365#M9224</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2008-10-10T04:30:14Z</dc:date>
    </item>
    <item>
      <title>Re: MSA1000 Failback</title>
      <link>https://community.hpe.com/t5/hpe-msa-storage/msa1000-failback/m-p/4284366#M9225</link>
      <description>It seems to have failed back to the primary controller overnight. Is this normal or would is it cause for concern that  a condition forced it back to the primary?</description>
      <pubDate>Fri, 10 Oct 2008 18:20:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-msa-storage/msa1000-failback/m-p/4284366#M9225</guid>
      <dc:creator>Josh Safranek</dc:creator>
      <dc:date>2008-10-10T18:20:27Z</dc:date>
    </item>
    <item>
      <title>Re: MSA1000 Failback</title>
      <link>https://community.hpe.com/t5/hpe-msa-storage/msa1000-failback/m-p/4284367#M9226</link>
      <description>That does not sound OK to me. I would take a look into the Windows event log.</description>
      <pubDate>Sat, 11 Oct 2008 16:25:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-msa-storage/msa1000-failback/m-p/4284367#M9226</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2008-10-11T16:25:45Z</dc:date>
    </item>
  </channel>
</rss>

