<?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 MSA1000 force Controller failover in HPE EVA Storage</title>
    <link>https://community.hpe.com/t5/hpe-eva-storage/msa1000-force-controller-failover/m-p/3879876#M22035</link>
    <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I have a dual path MSA1000 SAN with the internal 2/8 switches.&lt;BR /&gt;&lt;BR /&gt;The system is currently running a MSCS Exchange cluster with 2 nodes. I am about to add 2 more boxes to the SAN running VMWare ESX3. Before I do this I need to setup SSP so that nothing conflicts. When doing this I have heard that people have had problems with one path not showing up in ACU to add to the SSP group. The fix is apparently to fail over the controller so the other path becomes active and then shows up.&lt;BR /&gt;&lt;BR /&gt;My question is how to initiate this failover manually?&lt;BR /&gt;&lt;BR /&gt;Cheers&lt;BR /&gt;Nathan</description>
    <pubDate>Fri, 13 Oct 2006 10:08:13 GMT</pubDate>
    <dc:creator>Nathan Winters</dc:creator>
    <dc:date>2006-10-13T10:08:13Z</dc:date>
    <item>
      <title>MSA1000 force Controller failover</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/msa1000-force-controller-failover/m-p/3879876#M22035</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I have a dual path MSA1000 SAN with the internal 2/8 switches.&lt;BR /&gt;&lt;BR /&gt;The system is currently running a MSCS Exchange cluster with 2 nodes. I am about to add 2 more boxes to the SAN running VMWare ESX3. Before I do this I need to setup SSP so that nothing conflicts. When doing this I have heard that people have had problems with one path not showing up in ACU to add to the SSP group. The fix is apparently to fail over the controller so the other path becomes active and then shows up.&lt;BR /&gt;&lt;BR /&gt;My question is how to initiate this failover manually?&lt;BR /&gt;&lt;BR /&gt;Cheers&lt;BR /&gt;Nathan</description>
      <pubDate>Fri, 13 Oct 2006 10:08:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/msa1000-force-controller-failover/m-p/3879876#M22035</guid>
      <dc:creator>Nathan Winters</dc:creator>
      <dc:date>2006-10-13T10:08:13Z</dc:date>
    </item>
    <item>
      <title>Re: MSA1000 force Controller failover</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/msa1000-force-controller-failover/m-p/3879877#M22036</link>
      <description>The simplest way would be to just disable the controller's port from the SAN Switch GUI.&lt;BR /&gt;&lt;BR /&gt;This will effectively tell your multipath software that there has been a path failure and will force it to initiate the failover.&lt;BR /&gt;&lt;BR /&gt;Disconnecting one of the active fibre cables should also produce a failover.&lt;BR /&gt;&lt;BR /&gt;If you are using SecurePath, you can initiate a path failover from the SP Manager.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Steven</description>
      <pubDate>Fri, 13 Oct 2006 10:15:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/msa1000-force-controller-failover/m-p/3879877#M22036</guid>
      <dc:creator>Steven Clementi</dc:creator>
      <dc:date>2006-10-13T10:15:39Z</dc:date>
    </item>
  </channel>
</rss>

