<?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: what is arbitrated loop and fabric topologies? in HPE EVA Storage</title>
    <link>https://community.hpe.com/t5/hpe-eva-storage/what-is-arbitrated-loop-and-fabric-topologies/m-p/3934087#M65859</link>
    <description>Fibre Channel fabric protocol uses a 24-bit address which allows all devices in a fabric to be able to communicate with each other (leaving zoning and such things aside...).&lt;BR /&gt;&lt;BR /&gt;FC_AL private loop uses an 8-bit address and is limited within that loop.&lt;BR /&gt;&lt;BR /&gt;FC_AL public loop uses an 8-bit address within the loop and a 16-bit "loop address" to form a 24-bit address. The enables a device anywhere in the fabric to address a device within a public loop.&lt;BR /&gt;A Fabric Switch connects with one of its ports 'into' the loop and provides services to insert data into the loop or pick up data and send it into the fabric.</description>
    <pubDate>Tue, 30 Jan 2007 04:08:14 GMT</pubDate>
    <dc:creator>Uwe Zessin</dc:creator>
    <dc:date>2007-01-30T04:08:14Z</dc:date>
    <item>
      <title>what is arbitrated loop and fabric topologies?</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/what-is-arbitrated-loop-and-fabric-topologies/m-p/3934084#M65856</link>
      <description>&lt;P&gt;dear all,&lt;BR /&gt;i could not quite understand the meaning of arbitrated loop and fabric topologies, could anyone offer me some explanation or document?&lt;BR /&gt;&lt;BR /&gt;thanks a lot&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;P.S, This thread has been moved&amp;nbsp;from General to Storage Area Networks (SAN) (Enterprise). - Hp Forum Moderator&lt;/P&gt;</description>
      <pubDate>Tue, 06 Jan 2015 05:44:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/what-is-arbitrated-loop-and-fabric-topologies/m-p/3934084#M65856</guid>
      <dc:creator>stephen peng</dc:creator>
      <dc:date>2015-01-06T05:44:52Z</dc:date>
    </item>
    <item>
      <title>Re: what is arbitrated loop and fabric topologies?</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/what-is-arbitrated-loop-and-fabric-topologies/m-p/3934085#M65857</link>
      <description>Fibre Channel Arbitrated Loop is a 'ring' of devices, a bit similar to FDDI or token ring where data goes _through_ each device.&lt;BR /&gt;&lt;BR /&gt;Of course, if a device goes down, the entire loop will be dead, so a Fibre Channel hub is used which provides some bypass logic. It moves the data across the device which does not work.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Fabric topologies describe how fabric switches are interconnected. E.g. cascaded means that multiple switches are connected, but there are not redundant links - it looks more or less like a tree.&lt;BR /&gt;&lt;BR /&gt;Other topologies are ring, mesh (lots of redundant links) and trees.&lt;BR /&gt;&lt;BR /&gt;Fabric topologies are explained in the SAN design guide:&lt;BR /&gt;&lt;A href="http://www.hp.com/go/sandesignguide" target="_blank"&gt;http://www.hp.com/go/sandesignguide&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;arbitrated loop is not much interesting for the end users these days, but it still lives on in the back-end of storage arrays, because Fibre Channel disk drives use FC_AL.</description>
      <pubDate>Mon, 29 Jan 2007 04:16:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/what-is-arbitrated-loop-and-fabric-topologies/m-p/3934085#M65857</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2007-01-29T04:16:18Z</dc:date>
    </item>
    <item>
      <title>Re: what is arbitrated loop and fabric topologies?</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/what-is-arbitrated-loop-and-fabric-topologies/m-p/3934086#M65858</link>
      <description>zessin,&lt;BR /&gt;hi! now i want to know the difference between fabric topologies and private loop, could you offer me some esplanation?&lt;BR /&gt;thanks</description>
      <pubDate>Tue, 30 Jan 2007 03:57:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/what-is-arbitrated-loop-and-fabric-topologies/m-p/3934086#M65858</guid>
      <dc:creator>stephen peng</dc:creator>
      <dc:date>2007-01-30T03:57:35Z</dc:date>
    </item>
    <item>
      <title>Re: what is arbitrated loop and fabric topologies?</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/what-is-arbitrated-loop-and-fabric-topologies/m-p/3934087#M65859</link>
      <description>Fibre Channel fabric protocol uses a 24-bit address which allows all devices in a fabric to be able to communicate with each other (leaving zoning and such things aside...).&lt;BR /&gt;&lt;BR /&gt;FC_AL private loop uses an 8-bit address and is limited within that loop.&lt;BR /&gt;&lt;BR /&gt;FC_AL public loop uses an 8-bit address within the loop and a 16-bit "loop address" to form a 24-bit address. The enables a device anywhere in the fabric to address a device within a public loop.&lt;BR /&gt;A Fabric Switch connects with one of its ports 'into' the loop and provides services to insert data into the loop or pick up data and send it into the fabric.</description>
      <pubDate>Tue, 30 Jan 2007 04:08:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/what-is-arbitrated-loop-and-fabric-topologies/m-p/3934087#M65859</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2007-01-30T04:08:14Z</dc:date>
    </item>
    <item>
      <title>Re: what is arbitrated loop and fabric topologies?</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/what-is-arbitrated-loop-and-fabric-topologies/m-p/3934088#M65860</link>
      <description>Zessin,&lt;BR /&gt;i could not quite catch your explanation, so could you please produce some examples to illustrate the upper items? or document to present detaied explain.&lt;BR /&gt;&lt;BR /&gt;thanks a lot</description>
      <pubDate>Wed, 31 Jan 2007 01:52:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/what-is-arbitrated-loop-and-fabric-topologies/m-p/3934088#M65860</guid>
      <dc:creator>stephen peng</dc:creator>
      <dc:date>2007-01-31T01:52:15Z</dc:date>
    </item>
    <item>
      <title>Re: what is arbitrated loop and fabric topologies?</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/what-is-arbitrated-loop-and-fabric-topologies/m-p/3934089#M65861</link>
      <description>Fabric topologies describe how Fibre Channel switches are connected - see above.&lt;BR /&gt;&lt;BR /&gt;Fibre Channel Arbitrated (private) Loop means that _devices_ (computers, disks / disk arrays, tape storage) are connected in a 'ring'.&lt;BR /&gt;&lt;BR /&gt;Public loop means that such a 'ring' is connected to a Fibre Channel switch and the devices are capable to address devices outside the loop/ring.</description>
      <pubDate>Wed, 31 Jan 2007 03:51:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/what-is-arbitrated-loop-and-fabric-topologies/m-p/3934089#M65861</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2007-01-31T03:51:06Z</dc:date>
    </item>
  </channel>
</rss>

