<?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 Failed Redundancy Path (error 409) In ACU in HPE EVA Storage</title>
    <link>https://community.hpe.com/t5/hpe-eva-storage/msa1000-failed-redundancy-path-error-409-in-acu/m-p/4449132#M38843</link>
    <description>Guys, I have just recently installed a replacement MSA1000 controller My backup/redundant controller suffered a failure and had to be replaced. &lt;BR /&gt;&lt;BR /&gt;When installing everything seemed to go OK according to the LCD screen on the controller. My primary controller states that "Redundancy Active/Active Controller"&lt;BR /&gt;&lt;BR /&gt;However, when using the ACU v 8.28.13.0 - it shows the 2nd redundant controller as "Failed redundancy Path"&lt;BR /&gt;&lt;BR /&gt;If i select my MSA1000 controller via the ACU, i see both controllers. My primary controller says "Active", and again the backup controller says "Failed Redundancy Path"&lt;BR /&gt;&lt;BR /&gt;According to the LCD on the MSA1000 all seem to be working as expected, however the ACU software seems to say a different story.&lt;BR /&gt;&lt;BR /&gt;Which one should i believe - the software or the hardware???&lt;BR /&gt;&lt;BR /&gt;So how do i fix this 'Failed redundance path' error, and ensure i have full redundant controllers?&lt;BR /&gt;&lt;BR /&gt;TIA&lt;BR /&gt;&lt;BR /&gt;PS - im on a classified network, and cannot upload documents...</description>
    <pubDate>Mon, 29 Jun 2009 12:35:42 GMT</pubDate>
    <dc:creator>Drumgod007</dc:creator>
    <dc:date>2009-06-29T12:35:42Z</dc:date>
    <item>
      <title>MSA1000 Failed Redundancy Path (error 409) In ACU</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/msa1000-failed-redundancy-path-error-409-in-acu/m-p/4449132#M38843</link>
      <description>Guys, I have just recently installed a replacement MSA1000 controller My backup/redundant controller suffered a failure and had to be replaced. &lt;BR /&gt;&lt;BR /&gt;When installing everything seemed to go OK according to the LCD screen on the controller. My primary controller states that "Redundancy Active/Active Controller"&lt;BR /&gt;&lt;BR /&gt;However, when using the ACU v 8.28.13.0 - it shows the 2nd redundant controller as "Failed redundancy Path"&lt;BR /&gt;&lt;BR /&gt;If i select my MSA1000 controller via the ACU, i see both controllers. My primary controller says "Active", and again the backup controller says "Failed Redundancy Path"&lt;BR /&gt;&lt;BR /&gt;According to the LCD on the MSA1000 all seem to be working as expected, however the ACU software seems to say a different story.&lt;BR /&gt;&lt;BR /&gt;Which one should i believe - the software or the hardware???&lt;BR /&gt;&lt;BR /&gt;So how do i fix this 'Failed redundance path' error, and ensure i have full redundant controllers?&lt;BR /&gt;&lt;BR /&gt;TIA&lt;BR /&gt;&lt;BR /&gt;PS - im on a classified network, and cannot upload documents...</description>
      <pubDate>Mon, 29 Jun 2009 12:35:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/msa1000-failed-redundancy-path-error-409-in-acu/m-p/4449132#M38843</guid>
      <dc:creator>Drumgod007</dc:creator>
      <dc:date>2009-06-29T12:35:42Z</dc:date>
    </item>
    <item>
      <title>Re: MSA1000 Failed Redundancy Path (error 409) In ACU</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/msa1000-failed-redundancy-path-error-409-in-acu/m-p/4449133#M38844</link>
      <description>Anyone????</description>
      <pubDate>Mon, 29 Jun 2009 15:07:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/msa1000-failed-redundancy-path-error-409-in-acu/m-p/4449133#M38844</guid>
      <dc:creator>Drumgod007</dc:creator>
      <dc:date>2009-06-29T15:07:37Z</dc:date>
    </item>
    <item>
      <title>Re: MSA1000 Failed Redundancy Path (error 409) In ACU</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/msa1000-failed-redundancy-path-error-409-in-acu/m-p/4449134#M38845</link>
      <description>do you have the CLI cable, if so check the output for the show tech_support command and look at the 'connections' part. Do they show as online?  also is the firmware the same on both controllers. I guess the MSA was powered up when the controller was swapped and the cloneing worked ok?  What firmware are you using.</description>
      <pubDate>Tue, 30 Jun 2009 09:25:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/msa1000-failed-redundancy-path-error-409-in-acu/m-p/4449134#M38845</guid>
      <dc:creator>Greybeard</dc:creator>
      <dc:date>2009-06-30T09:25:23Z</dc:date>
    </item>
    <item>
      <title>Re: MSA1000 Failed Redundancy Path (error 409) In ACU</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/msa1000-failed-redundancy-path-error-409-in-acu/m-p/4449135#M38846</link>
      <description>I am using Firmware 5.20 now on my primary controller. &lt;BR /&gt;&lt;BR /&gt;Before i just upgraded i was on 4.38.x. When i installed the new backup controller the LCD screen prompted me to upgrade/downgrade the firmware on the new backup controller. I selected Yes, and then it said it failed. &lt;BR /&gt;&lt;BR /&gt;Rebooted the MSA1000 and both controllers stated that they had the same firmware 4.38... Hummm....&lt;BR /&gt;&lt;BR /&gt;I will look into the SHOW CONNECTIONS command as you suggested to see if i can dig something up.</description>
      <pubDate>Tue, 30 Jun 2009 13:46:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/msa1000-failed-redundancy-path-error-409-in-acu/m-p/4449135#M38846</guid>
      <dc:creator>Drumgod007</dc:creator>
      <dc:date>2009-06-30T13:46:57Z</dc:date>
    </item>
    <item>
      <title>Re: MSA1000 Failed Redundancy Path (error 409) In ACU</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/msa1000-failed-redundancy-path-error-409-in-acu/m-p/4449136#M38847</link>
      <description>that sounds as if the cloning went the wrong way, that could cause a few issues.  if you have the CLI cable then do the upgrade from hyperterminal, it's easier. just use 1k xmodem transfer.  If you post the tech support output I'll have a look at that too.</description>
      <pubDate>Fri, 03 Jul 2009 10:06:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/msa1000-failed-redundancy-path-error-409-in-acu/m-p/4449136#M38847</guid>
      <dc:creator>Greybeard</dc:creator>
      <dc:date>2009-07-03T10:06:56Z</dc:date>
    </item>
    <item>
      <title>Re: MSA1000 Failed Redundancy Path (error 409) In ACU</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/msa1000-failed-redundancy-path-error-409-in-acu/m-p/4449137#M38848</link>
      <description>Did you get a resolution.&lt;BR /&gt;&lt;BR /&gt;I have one doing the same thing.  My question is does the ACU require a dedicated fiber link to each controller?  &lt;BR /&gt;&lt;BR /&gt;I only have a single fiber link from a windows server that I am running ACU on.  All the hosts that are using the MSA are ESX. &lt;BR /&gt; &lt;BR /&gt;I don't know if the failed redundancy path message is referring to the controllers links to the disk shelves, or to the ACU's possible requirement that it have a direct fiber link to each controller.</description>
      <pubDate>Mon, 01 Mar 2010 15:44:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/msa1000-failed-redundancy-path-error-409-in-acu/m-p/4449137#M38848</guid>
      <dc:creator>Richard C. Klimitchek</dc:creator>
      <dc:date>2010-03-01T15:44:52Z</dc:date>
    </item>
  </channel>
</rss>

