<?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: 43 Redundancy Failed MSA 1000 in HPE EVA Storage</title>
    <link>https://community.hpe.com/t5/hpe-eva-storage/43-redundancy-failed-msa-1000/m-p/3723434#M17374</link>
    <description>Eddie,&lt;BR /&gt;To add to Uwe response.  There are two methods to disable the controller.  Using ACU, you can disable the other controller or use cli command &amp;gt;disable controller &lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Fri, 03 Feb 2006 10:52:52 GMT</pubDate>
    <dc:creator>John Kufrovich</dc:creator>
    <dc:date>2006-02-03T10:52:52Z</dc:date>
    <item>
      <title>43 Redundancy Failed MSA 1000</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/43-redundancy-failed-msa-1000/m-p/3723432#M17372</link>
      <description>We have a new MSA1000 that we have just setup.  To test the redundancy we have pulled a controller and the second controller is giving an error message stating 43 Redundancy failed.  Hardware Failure.  What could be wrong?  The redundancy appears to be initalizing correctly and the redundancy light is lit green on both controllers.</description>
      <pubDate>Thu, 02 Feb 2006 15:30:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/43-redundancy-failed-msa-1000/m-p/3723432#M17372</guid>
      <dc:creator>Eddie Willett</dc:creator>
      <dc:date>2006-02-02T15:30:00Z</dc:date>
    </item>
    <item>
      <title>Re: 43 Redundancy Failed MSA 1000</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/43-redundancy-failed-msa-1000/m-p/3723433#M17373</link>
      <description>There is a customer advisory that explicitly warns against this "test", because it can cause controller hangs. Apart from that it seems like the message is to be expected, because one controller has failed.</description>
      <pubDate>Thu, 02 Feb 2006 15:46:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/43-redundancy-failed-msa-1000/m-p/3723433#M17373</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2006-02-02T15:46:03Z</dc:date>
    </item>
    <item>
      <title>Re: 43 Redundancy Failed MSA 1000</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/43-redundancy-failed-msa-1000/m-p/3723434#M17374</link>
      <description>Eddie,&lt;BR /&gt;To add to Uwe response.  There are two methods to disable the controller.  Using ACU, you can disable the other controller or use cli command &amp;gt;disable controller &lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 03 Feb 2006 10:52:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/43-redundancy-failed-msa-1000/m-p/3723434#M17374</guid>
      <dc:creator>John Kufrovich</dc:creator>
      <dc:date>2006-02-03T10:52:52Z</dc:date>
    </item>
    <item>
      <title>Re: 43 Redundancy Failed MSA 1000</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/43-redundancy-failed-msa-1000/m-p/3723435#M17375</link>
      <description>Without doing this, how can you be sure the redundant controller will take over in the event of a failure. &lt;BR /&gt;&lt;BR /&gt;If it is unadvisable to test redundancy by pulling the controller, is there a test you CAN do? Perhaps pull the fibre cable off the back so it forces you to the alternate path?&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;&lt;BR /&gt;Terry</description>
      <pubDate>Fri, 24 Feb 2006 18:04:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/43-redundancy-failed-msa-1000/m-p/3723435#M17375</guid>
      <dc:creator>Terry R Lecander</dc:creator>
      <dc:date>2006-02-24T18:04:58Z</dc:date>
    </item>
  </channel>
</rss>

