<?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 P6300 - Bad cabling configuration detected in the backend devices cabling - 2C4D in HPE EVA Storage</title>
    <link>https://community.hpe.com/t5/hpe-eva-storage/p6300-bad-cabling-configuration-detected-in-the-backend-devices/m-p/6939758#M68017</link>
    <description>&lt;P&gt;Hello community,&lt;BR /&gt;&lt;BR /&gt;I recently installed online a new disk enclosure for an already online-upgraded P6300.&lt;BR /&gt;&lt;BR /&gt;Initially they array had 2 disk enclosures. Some time ago I added a third below the others with no issues following the installation instructions.&lt;BR /&gt;&lt;BR /&gt;Now I follow the same steps to add a fourth disk enclosure but it went not that good. Enclosure was recognized with its disks but event log sporadically logs a message like this for both controllers:&lt;BR /&gt;&lt;BR /&gt;***Critical event*** Controller 2 Bad cabling configuration detected in the backend devices cabling. - 0685992d&lt;BR /&gt;I've uploaded images with the intermediate 2C3D cabling and the final 2C4D. The initial 2C2D was the same as in the M6625 installation intructions.&lt;/P&gt;&lt;P&gt;No other hardware warnings/alerts in Command View.&lt;/P&gt;&lt;P&gt;Any advice will be appreciated.&lt;/P&gt;&lt;P&gt;Thank you&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;</description>
    <pubDate>Mon, 13 Feb 2017 21:40:48 GMT</pubDate>
    <dc:creator>Sebastián Graña</dc:creator>
    <dc:date>2017-02-13T21:40:48Z</dc:date>
    <item>
      <title>P6300 - Bad cabling configuration detected in the backend devices cabling - 2C4D</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/p6300-bad-cabling-configuration-detected-in-the-backend-devices/m-p/6939758#M68017</link>
      <description>&lt;P&gt;Hello community,&lt;BR /&gt;&lt;BR /&gt;I recently installed online a new disk enclosure for an already online-upgraded P6300.&lt;BR /&gt;&lt;BR /&gt;Initially they array had 2 disk enclosures. Some time ago I added a third below the others with no issues following the installation instructions.&lt;BR /&gt;&lt;BR /&gt;Now I follow the same steps to add a fourth disk enclosure but it went not that good. Enclosure was recognized with its disks but event log sporadically logs a message like this for both controllers:&lt;BR /&gt;&lt;BR /&gt;***Critical event*** Controller 2 Bad cabling configuration detected in the backend devices cabling. - 0685992d&lt;BR /&gt;I've uploaded images with the intermediate 2C3D cabling and the final 2C4D. The initial 2C2D was the same as in the M6625 installation intructions.&lt;/P&gt;&lt;P&gt;No other hardware warnings/alerts in Command View.&lt;/P&gt;&lt;P&gt;Any advice will be appreciated.&lt;/P&gt;&lt;P&gt;Thank you&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;</description>
      <pubDate>Mon, 13 Feb 2017 21:40:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/p6300-bad-cabling-configuration-detected-in-the-backend-devices/m-p/6939758#M68017</guid>
      <dc:creator>Sebastián Graña</dc:creator>
      <dc:date>2017-02-13T21:40:48Z</dc:date>
    </item>
    <item>
      <title>Re: P6300 - Bad cabling configuration detected in the backend devices cabling - 2C4D</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/p6300-bad-cabling-configuration-detected-in-the-backend-devices/m-p/6943805#M68024</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I decided to unplug and plug cables again and now there are no more errors. So cabling was good after all.&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Mon, 27 Feb 2017 13:00:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/p6300-bad-cabling-configuration-detected-in-the-backend-devices/m-p/6943805#M68024</guid>
      <dc:creator>Sebastián Graña</dc:creator>
      <dc:date>2017-02-27T13:00:45Z</dc:date>
    </item>
  </channel>
</rss>

