<?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: FC loop misconfig in Disk Enclosures</title>
    <link>https://community.hpe.com/t5/disk-enclosures/fc-loop-misconfig/m-p/5116294#M42207</link>
    <description>Thanks for all the inputs . &lt;BR /&gt;As, i had some constraints in making 2C18D setup ( change in requirements ) , i finally made 2C12D configuration , successfully. :)</description>
    <pubDate>Fri, 27 Jun 2008 09:38:02 GMT</pubDate>
    <dc:creator>Manas Ranjan Patra</dc:creator>
    <dc:date>2008-06-27T09:38:02Z</dc:date>
    <item>
      <title>FC loop misconfig</title>
      <link>https://community.hpe.com/t5/disk-enclosures/fc-loop-misconfig/m-p/5116291#M42204</link>
      <description>Hi, &lt;BR /&gt;I'm using HSV-210 ( 2C18D ) , and the controllers are showing errors " FC loop misconfig " , while rebooting . &lt;BR /&gt;&lt;BR /&gt;can anyone tell me what could be the issue ? &lt;BR /&gt;&lt;BR /&gt;There are two loop switches are used with the configuration. &lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 27 Jun 2008 04:01:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/fc-loop-misconfig/m-p/5116291#M42204</guid>
      <dc:creator>Manas Ranjan Patra</dc:creator>
      <dc:date>2008-06-27T04:01:14Z</dc:date>
    </item>
    <item>
      <title>Re: FC loop misconfig</title>
      <link>https://community.hpe.com/t5/disk-enclosures/fc-loop-misconfig/m-p/5116292#M42205</link>
      <description>An EVA-8000/8100 2C18D uses four loop switches. This box is a very complicated piece of technology - please get help from a qualified engineer, otherwise you risk losing data if you experiment yourself. Maybe it is a swapped cable, but such diagnostic is really beyond what a public forum can do.</description>
      <pubDate>Fri, 27 Jun 2008 05:07:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/fc-loop-misconfig/m-p/5116292#M42205</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2008-06-27T05:07:03Z</dc:date>
    </item>
    <item>
      <title>Re: FC loop misconfig</title>
      <link>https://community.hpe.com/t5/disk-enclosures/fc-loop-misconfig/m-p/5116293#M42206</link>
      <description>Hi,&lt;BR /&gt;check if there are no disks in the following disk enclosures 16, 17, 19, 20 /bays 12-14 pls. These bays AL-PAs can conflict with the contollers AL-PAs or with the 4GB backend loop switches. Resume: Use of these slot is unsupported&lt;BR /&gt;</description>
      <pubDate>Fri, 27 Jun 2008 05:16:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/fc-loop-misconfig/m-p/5116293#M42206</guid>
      <dc:creator>IBaltay</dc:creator>
      <dc:date>2008-06-27T05:16:09Z</dc:date>
    </item>
    <item>
      <title>Re: FC loop misconfig</title>
      <link>https://community.hpe.com/t5/disk-enclosures/fc-loop-misconfig/m-p/5116294#M42207</link>
      <description>Thanks for all the inputs . &lt;BR /&gt;As, i had some constraints in making 2C18D setup ( change in requirements ) , i finally made 2C12D configuration , successfully. :)</description>
      <pubDate>Fri, 27 Jun 2008 09:38:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/fc-loop-misconfig/m-p/5116294#M42207</guid>
      <dc:creator>Manas Ranjan Patra</dc:creator>
      <dc:date>2008-06-27T09:38:02Z</dc:date>
    </item>
    <item>
      <title>Re: FC loop misconfig</title>
      <link>https://community.hpe.com/t5/disk-enclosures/fc-loop-misconfig/m-p/5116295#M42208</link>
      <description>Thanks.</description>
      <pubDate>Fri, 27 Jun 2008 09:39:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/fc-loop-misconfig/m-p/5116295#M42208</guid>
      <dc:creator>Manas Ranjan Patra</dc:creator>
      <dc:date>2008-06-27T09:39:09Z</dc:date>
    </item>
  </channel>
</rss>

