<?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: EVA controller interconnect cable question in Disk Enclosures</title>
    <link>https://community.hpe.com/t5/disk-enclosures/eva-controller-interconnect-cable-question/m-p/5179509#M43141</link>
    <description>Hi J,&lt;BR /&gt;&lt;BR /&gt;I have a eva4400.&lt;BR /&gt;&lt;BR /&gt;Do u have any docs explaining the function of controller interconnect cable?&lt;BR /&gt;&lt;BR /&gt;LC</description>
    <pubDate>Fri, 05 Jun 2009 06:00:09 GMT</pubDate>
    <dc:creator>lc6606</dc:creator>
    <dc:date>2009-06-05T06:00:09Z</dc:date>
    <item>
      <title>EVA controller interconnect cable question</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva-controller-interconnect-cable-question/m-p/5179507#M43139</link>
      <description>I have 2 questions;&lt;BR /&gt;&lt;BR /&gt;1. What type of information flows thru the controller interconnect cable and MP port?&lt;BR /&gt;&lt;BR /&gt;2. What happen if the controller interconnect cable is broken; can both controller still function like normal?&lt;BR /&gt;</description>
      <pubDate>Fri, 05 Jun 2009 05:34:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva-controller-interconnect-cable-question/m-p/5179507#M43139</guid>
      <dc:creator>lc6606</dc:creator>
      <dc:date>2009-06-05T05:34:23Z</dc:date>
    </item>
    <item>
      <title>Re: EVA controller interconnect cable question</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva-controller-interconnect-cable-question/m-p/5179508#M43140</link>
      <description>Hello,&lt;BR /&gt;&lt;BR /&gt;which EVA model do you have ? The controller interconnect cable (in case of EVAs other than the 4400) is used for data like cache mirroring, synchronization, passing through read requests issued to non-owning controller etc. I haven't experienced an interconnect failure so far but I assume that it represents a serious condition as the above mentioned information is not passed between the controllers. However I am not able to say how the storage system reacts in that case.&lt;BR /&gt;&lt;BR /&gt;J.</description>
      <pubDate>Fri, 05 Jun 2009 05:56:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva-controller-interconnect-cable-question/m-p/5179508#M43140</guid>
      <dc:creator>Jozef_Novak</dc:creator>
      <dc:date>2009-06-05T05:56:17Z</dc:date>
    </item>
    <item>
      <title>Re: EVA controller interconnect cable question</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva-controller-interconnect-cable-question/m-p/5179509#M43141</link>
      <description>Hi J,&lt;BR /&gt;&lt;BR /&gt;I have a eva4400.&lt;BR /&gt;&lt;BR /&gt;Do u have any docs explaining the function of controller interconnect cable?&lt;BR /&gt;&lt;BR /&gt;LC</description>
      <pubDate>Fri, 05 Jun 2009 06:00:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva-controller-interconnect-cable-question/m-p/5179509#M43141</guid>
      <dc:creator>lc6606</dc:creator>
      <dc:date>2009-06-05T06:00:09Z</dc:date>
    </item>
    <item>
      <title>Re: EVA controller interconnect cable question</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva-controller-interconnect-cable-question/m-p/5179510#M43142</link>
      <description>Hello (again),&lt;BR /&gt;&lt;BR /&gt;EVA4400 is the only model that does not have an interconnect cable. The controller chassis is 2U in size, housing both controllers and the entire inter-controller communication goes through the chassis backplane.&lt;BR /&gt;&lt;BR /&gt;J.</description>
      <pubDate>Fri, 05 Jun 2009 07:14:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva-controller-interconnect-cable-question/m-p/5179510#M43142</guid>
      <dc:creator>Jozef_Novak</dc:creator>
      <dc:date>2009-06-05T07:14:14Z</dc:date>
    </item>
    <item>
      <title>Re: EVA controller interconnect cable question</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva-controller-interconnect-cable-question/m-p/5179511#M43143</link>
      <description>The interconnect cable was meant to enable a 'cross-kill'. One controller could force-reboot the other one. It wasn't functional at least on introduction.&lt;BR /&gt;&lt;BR /&gt;The MP (Mirror-Port) is used for controller to controller communication, data transfers to the mirror cache and proxied reads.&lt;BR /&gt;The first generation EVA had one MP, but could fail over to one of the DP ports.</description>
      <pubDate>Fri, 05 Jun 2009 08:34:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva-controller-interconnect-cable-question/m-p/5179511#M43143</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2009-06-05T08:34:02Z</dc:date>
    </item>
    <item>
      <title>Re: EVA controller interconnect cable question</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva-controller-interconnect-cable-question/m-p/5179512#M43144</link>
      <description>Hi all,&lt;BR /&gt;&lt;BR /&gt;Thanks for the comments; it is all cleared now.</description>
      <pubDate>Wed, 10 Jun 2009 08:37:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva-controller-interconnect-cable-question/m-p/5179512#M43144</guid>
      <dc:creator>lc6606</dc:creator>
      <dc:date>2009-06-10T08:37:48Z</dc:date>
    </item>
  </channel>
</rss>

